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
Currently why-is-node-running depends on Node.js' async-hooks API, however this API is actively recommended against by the Node.js documentation:
Please migrate away from this API, if you can. We do not recommend using the createHook, AsyncHook, and executionAsyncResource APIs as they have usability issues, safety risks, and performance implications. Async context tracking use cases are better served by the stable AsyncLocalStorage API. If you have a use case for createHook, AsyncHook, or executionAsyncResource beyond the context tracking need solved by AsyncLocalStorage or diagnostics data currently provided by Diagnostics Channel, please open an issue at https://github.com/nodejs/node/issues describing your use case so we can create a more purpose-focused API.
This makes it worth investigating whether it is possible to move away from this API, and if so move to one of the APIs outlined in the documentation.
The text was updated successfully, but these errors were encountered:
Currently
why-is-node-running
depends on Node.js'async-hooks
API, however this API is actively recommended against by the Node.js documentation:This makes it worth investigating whether it is possible to move away from this API, and if so move to one of the APIs outlined in the documentation.
The text was updated successfully, but these errors were encountered: