chore: add .nvmrc for Node version consistency across environments#1069
chore: add .nvmrc for Node version consistency across environments#1069aniruddhaadak80 wants to merge 1 commit intof:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
Adds an .nvmrc file to standardize the Node.js version used by local developer tooling and platforms that honor .nvmrc.
Changes:
- Added
.nvmrcpinning Node.js major version20.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -0,0 +1 @@ | |||
| 20 | |||
There was a problem hiding this comment.
.nvmrc pins Node 20, but the repo currently declares Node 24.x in package.json engines.node and CI workflows use node-version: '24'. This mismatch will cause local/dev tooling to use a different Node than CI/production; align .nvmrc to the same version (or update engines/CI together if 20 is intended).
| 20 | |
| 24 |
📝 WalkthroughWalkthroughA new Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
📈 Why is this useful?
Currently, developers have to manually parse package.json to know which Node version to use locally, and CI/CD tools might default to older versions.
This PR adds an .nvmrc file targeting Node 20 (the current active LTS) to automatically standardize the development environment. When contributors run
vm use, or when deployment bots (Netlify/Vercel) build the application, they will seamlessly pick up the intended Node version, preventing runtime and module resolution bugs.
🛠️ Key Changes