Skip to content

Support only the Node releases the toolchain does - #3

Open
vivecuervo7 wants to merge 2 commits into
mainfrom
node-versions
Open

vivecuervo7 wants to merge 2 commits into
mainfrom
node-versions

Conversation

@vivecuervo7

@vivecuervo7 vivecuervo7 commented Nov 3, 2026 •

Copy link
Copy Markdown
Owner

What

  • engines in web/package.json (and the lockfile) goes from >=22.13 to ^22.13.0 || ^24.0.0 || >=26.0.0.
  • Adds web/.nvmrc with 24, for nvm use and fnm.
  • The README's Node requirement says the same.

Why

Someone on Node 25 got EBADENGINE from npm install: vitest 5 supports ^22.12.0 || ^24.0.0 || >=26.0.0, and with npm's engine-strict on, that stops the install. Our >=22.13 claimed 25 was fine. The range now matches, with 22.13 still the floor for the built-in SQLite.

.nvmrc holds a single major version, and nvm refuses one that isn't installed. 26 only became LTS on 28 October, so 24 (any 24.x) works for more people today. Both pass the checks in #5.

🤖 Generated with Claude Code

`engines` said 22.13 or later, so Node 25 looked fine until vitest's own
range refused it at install. It now matches: 22.13+, 24, or 26 and up.
web/.nvmrc lets fnm and nvm pick 26 on their own.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
nvm refuses a version that isn't installed, and 26 only became LTS last
week; any 24.x satisfies `24`. Both pass the checks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant