Skip to content

chore: add .nvmrc pinning Node 20 — match engines.node lower bound#248

Merged
CryptoJones merged 1 commit into
masterfrom
chore/add-nvmrc-pin-to-node-20
May 19, 2026
Merged

chore: add .nvmrc pinning Node 20 — match engines.node lower bound#248
CryptoJones merged 1 commit into
masterfrom
chore/add-nvmrc-pin-to-node-20

Conversation

@CryptoJones
Copy link
Copy Markdown
Owner

Closes #247.

Summary

Add .nvmrc with 20. nvm use / asdf install / mise install inside the repo now auto-select the right Node — matches the lower bound of engines.node >=20.0.0 and the CI matrix's 20.x lane.

Test plan

  • npm run lint clean
  • npm test — 688 passed (no behavior change)

Proudly Made in Nebraska. Go Big Red! 🌽 https://xkcd.com/2347/

Contributors using nvm, asdf, mise, or fnm have a per-project Node
version pinned via `.nvmrc`. Without one, they fall through to
whatever the shell's currently-active Node is — which can be ahead
or behind the project's `engines.node >=20.0.0` requirement.

Pin to `20` (the lower bound of `engines.node` + the lower end of
the CI matrix `[20.x, 22.x]`). Anyone running `nvm use` / `asdf
install` / `mise install` in this repo now lands on the version
the project actually supports and CI gates against.

Apache-2.0 / SPDX header isn't applicable to a single-line version
file (no comment syntax in nvm's parser); the file is content-only
per the nvmrc convention.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@CryptoJones CryptoJones merged commit 01e2472 into master May 19, 2026
3 checks passed
@CryptoJones CryptoJones deleted the chore/add-nvmrc-pin-to-node-20 branch May 19, 2026 12:23
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.

tooling: no .nvmrc — contributors using nvm/asdf/mise fall through to wrong Node

1 participant