Uh oh!
There was an error while loading. Please reload this page.
[v25.x] lib: do not provide an empty Proxy from localStorage getter - #60776
[v25.x] lib: do not provide an empty Proxy from localStorage getter#60776Renegade334 wants to merge 1 commit into
Conversation
The
notable-change Please suggest a text for the release notes if you'd like to include a more detailed summary, then proceed to update the PR description with the text or a link to the notable change suggested text comment. Otherwise, the commit will be placed in the Other Notable Changes section. |
This comment was marked as outdated.
This comment was marked as outdated.
nodejs-github-bot
commented
Nov 19, 2025
RafaelGSS
commented
Dec 10, 2025
Landed in c57a40c |
aduh95
commented
Jan 12, 2026
c57a40c was removed from the staging branch, though I cannot reopen this PR (probably because the branch has been deleted). |
Renegade334
commented
Jan 12, 2026
mcollina
commented
Jan 12, 2026
@Renegade334 it’s not exactly equivalent, it should correctly not mark localStorage as enumerable. |
Addresses the original regression in a way that is more consistent with the user experience in v24.x where no storage-related CLI arguments are passed. Access now warns and returns
undefinedin the case where the requisite path is missing.As things stand, the behaviour will revert to exception-raising in v26.x; any discussion relating to this specifically should go in the associated issue, this PR is just to re-fix the regression for localStorage users in v25.
Refs: #60303