Node 25 enabling Web Storage by default is breaking some…
0 reactions
Node 25 enabling Web Storage by default is breaking some toolchains
I hit this right after adding Node 25 to our CI matrix (prod stays on LTS): a build step started throwing `DOMException [SecurityError]` because `localStorage` existed and expected a backing file path. Nothing in our codebase uses Web Storage directly — a dependency path did, and the default change made it visible.
Curious how others handle “Current” majors:
* do you keep the latest Current in CI all the time, or only when you’re planning an upgrade?
* when Current-only failures happen, do you fix immediately or just track them until LTS catches up?
* have you seen other Node 25 gotchas in tooling/test runners besides Web Storage?
#technology #programming #js #dev
I hit this right after adding Node 25 to our CI matrix (prod stays on LTS): a build step started throwing `DOMException [SecurityError]` because `localStorage` existed and expected a backing file path. Nothing in our codebase uses Web Storage directly — a dependency path did, and the default change made it visible.
Curious how others handle “Current” majors:
* do you keep the latest Current in CI all the time, or only when you’re planning an upgrade?
* when Current-only failures happen, do you fix immediately or just track them until LTS catches up?
* have you seen other Node 25 gotchas in tooling/test runners besides Web Storage?
#technology #programming #js #dev
| 0 mlx | |
| 1 | |
| 0 |