TC39 proposal AsyncContext

[legendecas]

The TC39 proposal AsyncContext https://github.com/tc39/proposal-async-context has reached Stage 2 today. I'd like to bring the topic up again at the diagnostics meeting to discuss the integration of Node.js with the proposal and the next steps for it.

This is a revival of #375.

Related:

• AsyncResource constructor arguments node#46369
• AsyncLocalStorage without Async Hooks node#46265
• AsyncLocalStorage and deferred promises node#46262

[mhdawson]

Good to see that progressing in TC39.

[legendecas]

During the May 3rd TC39 AsyncContext call, there were no objections to using the reject's call time context for unhandledRejection: tc39/proposal-async-context#16 (comment).

We would like to know if it is feasible for Node.js to change the context of the unhandledRejection event and if there are any concerns regarding the decision.

I would like to bring this up to the next diag call and @jridgewell would like to join too.

[Qard]

Will you be at the collab summit next week? We have a diagnostics session on the agenda so we could bring it up there if you're around. :)

[legendecas]

Unfortunately, I'm unable to attend the summit next week :(.

[Flarna]

I will be also not there. I haven't even noticed that there is a summit and a diagnostics session... Seems I monitor the wrong channels/repos.

[Qard]

You can watch https://github.com/openjs-foundation/summit/ for future summits. :)

[legendecas]

Untagging diag-agenda as the issue is being discussed at tc39/proposal-async-context#16.

[github-actions]

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.