test: derive uncaughtException ALS context from native microtask behavior
The fast setImmediate patch rethrows sync errors from a queueMicrotask.
Whether AsyncLocalStorage context is visible in the resulting
uncaughtException depends on the runtime: it is only preserved when
AsyncContextFrame is enabled (the default since Node 24). The two
affected tests hardcoded `undefined` and failed on Node 24.
Probe what a native queueMicrotask throw sees and assert that exact
value instead.
<!-- NEXT_JS_LLM -->
Co-authored-by:
Tobias Koppers <1365881+sokra@users.noreply.github.com>
Showing
Please
register
or
sign in
to comment