Repository navigation
Backport ALS to use AsyncContextFrame as default for v22 #60102
Description
Activity
- changed the title
[-]Backport `AsyncContextFrame` as default to v22[/-][+]Backport ALS to use `AsyncContextFrame` as default for v22[/+]on Oct 1, 2025 Sounds good to me. Haven't seen any issues arise since the change. 🙂
- addedasync_local_storageIssues and PRs related to the AsyncLocalStorage API.Issues and PRs related to the AsyncLocalStorage API.
on Oct 2, 2025 The change did break existing code (#58204). While it would likely be an improvement in most cases, I am hesitant to suggest to go for that due to that.
Reacted by Tim Fish, Matteo Collina and surajtaghashWell,
enterWith(...)is experimental and from day one had a big doc warning to never use it. It also arguably fixed a bug in the prior behaviour. 🤷🏻But if others feel the change should be held back from backporting anyway I would not push for it. I think it's fine personally, though I don't feel strongly that it needs backporting necessarily. I'm all for more excuses to tell people they should upgrade. 🙈
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.- addedstaleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
on May 6, 2026 This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Node v24 had the default changed:
This was changed in a major version to be safer but has proven to be stable and not cause breaking changes so it should be backported to Node v22 too!