Skip to content

chore: add .node-version file for nvm/fnm compatibility#229

Open
andrerfneves wants to merge 1 commit into
mainfrom
maintenance/add-node-version-20260630
Open

chore: add .node-version file for nvm/fnm compatibility#229
andrerfneves wants to merge 1 commit into
mainfrom
maintenance/add-node-version-20260630

Conversation

@andrerfneves

Copy link
Copy Markdown
Owner

Summary

Adds a .node-version file to enable automatic Node.js version switching for developers using nvm, fnm, n, or other Node.js version managers.

Why

The README already recommends Node.js 20+ in the Prerequisites section and the CI pipeline tests against Node.js 20.x and 22.x. Without a .node-version file, developers using version managers must manually switch to the correct Node version.

With this change, entering the project directory automatically switches to Node.js 20.

Changes

  • .node-version: New file containing 20

Test Plan

  • All 52 existing tests pass
  • Production build succeeds
  • No behavior change — configuration-only addition

The README recommends Node.js 20+. Adding a .node-version file
lets nvm, fnm, n, and other version managers automatically switch
to the correct Node version when entering the project directory.
@vercel

vercel Bot commented Jun 30, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
lightning-decoder Ready Ready Preview, Comment Jun 30, 2026 10:04pm

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