Skip to content

Evaluate possiblity of moving away from async_hooks #64

@jonkoops

Description

@jonkoops

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.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions