Skip to content

chore: add .nvmrc for consistent Node versioning#1550

Open
srinidhi-2006-bit wants to merge 1 commit into
Priyanshu-byte-coder:mainfrom
srinidhi-2006-bit:chore/add-nvmrc
Open

chore: add .nvmrc for consistent Node versioning#1550
srinidhi-2006-bit wants to merge 1 commit into
Priyanshu-byte-coder:mainfrom
srinidhi-2006-bit:chore/add-nvmrc

Conversation

@srinidhi-2006-bit
Copy link
Copy Markdown
Contributor

Summary

Added an .nvmrc file to define a consistent Node.js version for contributors and development environments.

Closes #993


Type of Change

  • Bug fix
  • New feature
  • Documentation / Developer Experience improvement
  • Refactor / code cleanup

Changes Made

  • Added .nvmrc file at the repository root
  • Specified Node.js version 20
  • Improved environment consistency across contributors
  • Simplified project setup for developers using NVM

How to Test

  1. Ensure .nvmrc exists in the repository root
  2. Run:
nvm use
  1. Verify the correct Node.js version is selected
  2. Run the project normally and confirm everything works as expected

Screenshots (if UI change)

N/A


Checklist

  • Linked issue in summary
  • Self-reviewed the diff
  • No breaking changes introduced
  • Added only the required configuration file
  • Added/updated tests if applicable

Additional Notes

Adding .nvmrc helps contributors use a consistent Node.js version, reducing setup issues and environment-related bugs.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 29, 2026

@srinidhi-2006-bit is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot added gssoc26 GSSoC 2026 contribution type:feature GSSoC type bonus: new feature labels May 29, 2026
@github-actions
Copy link
Copy Markdown

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

  • level:beginner — 20 pts
  • level:intermediate — 35 pts
  • level:advanced — 55 pts
  • level:critical — 80 pts

Quality (optional):

  • quality:clean — ×1.2 multiplier
  • quality:exceptional — ×1.5 multiplier

Validation (required to score):

  • gssoc:approved — counts for points
  • gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

@srinidhi-2006-bit
Copy link
Copy Markdown
Contributor Author

Hi @Priyanshu-byte-coder,

I've completed the requested changes and submitted the PR for review. When you review it, could you please add the gssoc:approved label before merging if everything looks good?

Thank you for your time and feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gssoc26 GSSoC 2026 contribution type:feature GSSoC type bonus: new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add .nvmrc file for consistent Node versioning

1 participant