diff options
Diffstat (limited to 'doc/api/async_hooks.md')
| -rw-r--r-- | doc/api/async_hooks.md | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/doc/api/async_hooks.md b/doc/api/async_hooks.md index 2628cc290a..601dad93e7 100644 --- a/doc/api/async_hooks.md +++ b/doc/api/async_hooks.md @@ -141,7 +141,6 @@ future. This is subject to change in the future if a comprehensive analysis is performed to ensure an exception can follow the normal control flow without unintentional side effects. - ##### Printing in AsyncHooks callbacks Because printing to the console is an asynchronous operation, `console.log()` @@ -257,7 +256,6 @@ the new resource to initialize and that caused `init` to call. This is different from `async_hooks.executionAsyncId()` that only shows *when* a resource was created, while `triggerAsyncId` shows *why* a resource was created. - The following is a simple demonstration of `triggerAsyncId`: ```js @@ -395,7 +393,6 @@ API the user's callback is placed in a `process.nextTick()`. The graph only shows *when* a resource was created, not *why*, so to track the *why* use `triggerAsyncId`. - ##### before(asyncId) * `asyncId` {number} @@ -413,7 +410,6 @@ asynchronous resources like a TCP server will typically call the `before` callback multiple times, while other operations like `fs.open()` will call it only once. - ##### after(asyncId) * `asyncId` {number} @@ -424,7 +420,6 @@ If an uncaught exception occurs during execution of the callback, then `after` will run *after* the `'uncaughtException'` event is emitted or a `domain`'s handler runs. - ##### destroy(asyncId) * `asyncId` {number} |