Skip to content

Add .nvmrc pinning Node 24 - #851

Open
krejko wants to merge 1 commit into
Listenarrs:canaryfrom
nexalapp:chore/add-nvmrc
Open

Add .nvmrc pinning Node 24#851
krejko wants to merge 1 commit into
Listenarrs:canaryfrom
nexalapp:chore/add-nvmrc

Conversation

@krejko

@krejko krejko commented Aug 20, 2026

Copy link
Copy Markdown

Summary

package.json declares "node": "^24.15.0" and CONTRIBUTING lists Node 24.x as a prerequisite, but there is no .nvmrc, so nvm users have to know the version and pass it by hand (nvm use 24) on every shell.

Adding one makes a bare nvm use resolve correctly from the repo root and from fe/ and listenarr.api/, since nvm walks up the tree.

Changes

Added

  • .nvmrc containing 24

Testing

nvm use in a clean shell selects Node 24 from the repo root and from subdirectories. No build or runtime behaviour is affected.

Notes

Tracks the major only rather than a full patch version, so it stays consistent with the existing ^24.15.0 engines range instead of needing a bump on every Node patch release.

🤖 Generated with Claude Code

package.json requires node ^24.15.0 and CONTRIBUTING lists Node 24.x as a
prerequisite, but there is nothing for nvm to read. Contributors using nvm have
to know the version and pass it manually.

Track the major only, so it stays consistent with the existing engines range
rather than pinning a patch that would need bumping.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@krejko
krejko requested a review from a team August 20, 2026 18:40
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