I recently added Node.js 25 to our CI environment, while still using LTS for production. Right after the switch, a build step started giving me `DOMException [SecurityError]`. This happened because it expected a backing file path for `localStorage`, which appeared due to a dependency that uses Web Storage. I'm curious about how others are managing transitions with the 'Current' versions of Node:
- Do you continuously integrate the latest Current version in your CI, or only when preparing for an upgrade?
- When you encounter issues specifically with Current versions, do you fix them right away or wait until LTS catches up?
- Have you experienced any other issues with Node 25 that relate to tooling or test runners, aside from the Web Storage change?
5 Answers
Thanks for testing out the Current version! It's important to share these findings. A lot of folks rely on testers like you. For me, it seems like we might just need to accept Current's instability for now, but at least it prevents a bigger issue in production down the line.
It's wild! I've been away from Node for about a year and didn't realize we were already at version 25. I generally ignore Current in build tooling because it feels like a "magical future land" I won't really use. Once version 26 is out, that changes, though! Then, ensuring compatibility before it goes LTS becomes essential.
I was surprised to hear that people use `localStorage` in Node.js. Is it mainly for creating libraries that can work in both browser and backend environments?
I guess testing libraries might utilize it as well.
Why even use Current Node.js? I stick with LTS for everything. In my ten-plus years with Node.js, I've never needed a feature from the bleeding-edge versions. Their docs suggest using only "Active LTS" or "Maintenance LTS" in production, which aligns with my CI strategy. These kinds of issues are exactly why I wait to upgrade!
Totally get that perspective! I keep production on LTS as well. I only use Current to detect possible ecosystem breakage early on, just like you.
There are quite a few reasons! The main one is when building local applications on Node, like CLIs. It's not typically used for server-side user data storage, though it could be misused for that.