Skip to content

chore: add .nvmrc for Node version consistency across environments#1069

Open
aniruddhaadak80 wants to merge 1 commit intof:mainfrom
aniruddhaadak80:add-nvmrc
Open

chore: add .nvmrc for Node version consistency across environments#1069
aniruddhaadak80 wants to merge 1 commit intof:mainfrom
aniruddhaadak80:add-nvmrc

Conversation

@aniruddhaadak80
Copy link

@aniruddhaadak80 aniruddhaadak80 commented Mar 10, 2026

📈 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

  • ✅ Added .nvmrc mapped to Node 20.

Copilot AI review requested due to automatic review settings March 10, 2026 15:18
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 .nvmrc pinning Node.js major version 20.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@@ -0,0 +1 @@
20
Copy link

Copilot AI Mar 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.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).

Suggested change
20
24

Copilot uses AI. Check for mistakes.
@coderabbitai
Copy link

coderabbitai bot commented Mar 10, 2026

📝 Walkthrough

Walkthrough

A new .nvmrc configuration file was added to specify Node.js version 20 for the project. This file allows Node version managers to automatically select the correct runtime version.

Changes

Cohort / File(s) Summary
Node.js Version Configuration
.nvmrc
Added configuration file specifying Node.js version 20.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop and a skip, version twenty's here,
Node.js locked in, crystal clear,
Consistency hops through our dev team's day,
No version mix-ups—hip hip hooray! 🎉

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title directly and clearly describes the main change: adding a .nvmrc file for Node version consistency, which matches the actual changeset of adding the .nvmrc file with Node 20.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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.

2 participants