You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
***Pretty Error:** Errors and stack traces printed in a structured way and fully accessible through _JSON_ (e.g. external Log services)
84
-
***Stack frame:**`tslog` captures and displays the source code that lead to an error, making it easier to debug
84
+
***Code frame:**`tslog` captures and displays the source code that lead to an error, making it easier to debug
85
85
***Object/JSON highlighting:** Nicely prints out an object
86
-
***Instance Name:** Logs capture instance name (default hos name) making it easy to distinguish logs coming from different instances (e.g. serverless)
86
+
***Instance Name:** Logs capture instance name (default host name) making it easy to distinguish logs coming from different instances (e.g. serverless)
87
87
***Named Logger:** Logger can be named (e.g. useful for packages/modules and monorepos)
88
88
***Highly configurable:** All settings can be changed through a typed object
89
89
***Short paths:** Paths are relative to the root of the application folder
@@ -204,7 +204,7 @@ Usually, only _Errors_ and log level `trace` logs would capture the entire stack
204
204
By enabling this option **every** stack trace of every log message is going to be captured.
205
205
206
206
```typescript
207
-
newLogger({ exposeStack: true });
207
+
newLogger({ exposeStack: true });
208
208
```
209
209
210
210

@@ -290,7 +290,7 @@ like sending a message to _Slack_ or _Telegram_ in case of an urgent error.
290
290
When attaching a transport, you _must_ implement every log level.
291
291
All of them could be potentially handled by the same function, though.
<li><strong>Pretty Error:</strong> Errors and stack traces printed in a structured way and fully accessible through <em>JSON</em> (e.g. external Log services) </li>
138
-
<li><strong>Stack frame:</strong><code>tslog</code> captures and displays the source code that lead to an error, making it easier to debug</li>
138
+
<li><strong>Code frame:</strong><code>tslog</code> captures and displays the source code that lead to an error, making it easier to debug</li>
139
139
<li><strong>Object/JSON highlighting:</strong> Nicely prints out an object </li>
140
-
<li><strong>Instance Name:</strong> Logs capture instance name (default hos name) making it easy to distinguish logs coming from different instances (e.g. serverless)</li>
140
+
<li><strong>Instance Name:</strong> Logs capture instance name (default host name) making it easy to distinguish logs coming from different instances (e.g. serverless)</li>
141
141
<li><strong>Named Logger:</strong> Logger can be named (e.g. useful for packages/modules and monorepos)</li>
142
142
<li><strong>Highly configurable:</strong> All settings can be changed through a typed object</li>
143
143
<li><strong>Short paths:</strong> Paths are relative to the root of the application folder</li>
<p>Usually, only <em>Errors</em> and log level <code>trace</code> logs would capture the entire stack trace.<br>By enabling this option <strong>every</strong> stack trace of every log message is going to be captured.</p>
<p><imgsrc="https://raw.githubusercontent.com/fullstack-build/tslog/master/docs/assets/tslog_stacktrace.png" alt="tslog with a stack trace"></p>
248
248
<blockquote>
249
249
<p><strong>Hint:</strong> When working in an IDE like <em>WebStorm</em> or an editor like <em>VSCode</em> you can click on the path leading you directly to the position in your source code. </p>
@@ -314,7 +314,7 @@ <h4>Transports</h4>
314
314
like sending a message to <em>Slack</em> or <em>Telegram</em> in case of an urgent error. </p>
315
315
<p>When attaching a transport, you <em>must</em> implement every log level.
316
316
All of them could be potentially handled by the same function, though.</p>
317
-
<p>Each <em>transport</em> can hav its own <code>minLevel</code>. </p>
317
+
<p>Each <em>transport</em> can have its own <code>minLevel</code>. </p>
0 commit comments