fix(opentelemetry-context-async-hooks): Support AsyncLocalStorageContextManager
in non-Node.js runtimes
#4615
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
The
AsyncHooksContextManager
currently depends on the Node.js specific APIasync_hooks
in order to make use ofAsyncLocalStorage
. Other JS runtimes, like for example the Vercel Edge runtime, do not support this specific API, but provide other mechanisms for usindAsyncLocalStorage
, e.g. by exposing theAsyncLocalStorage
API on the global object. Using theAsyncLocalStorageContextManager
in these runtimes will fail since theasync_hooks
import is not available.Short description of the changes
Instead of importing the Node.js-specific API
async_hooks
which would break in non-Node.js runtimes during initialization, we go through a set of fallbacks to try and findAsyncLocalStorage
:globalThis.async_hooks.AsyncLocalStorage
(this would succeed in Node.js)globalThis.AsyncLocalStorage
(this would succeed in most other runtimes)Type of change
Bug fix (non-breaking change which fixes an issue)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: