fix #2595 : update Node.js version requirement in README to match package.json

[subhamkumarr]

Fix Node.js version requirement documentation mismatch

Problem

The README.md incorrectly states "Node.js version 18+" while package.json specifies "node": "20.x" in the engines field. This inconsistency can mislead contributors who may install an incompatible Node.js version.

Solution

Updated README.md to specify "Node.js version 20.x" to match the actual requirement in package.json.

Changes

• Updated README.md line 14: Changed "Node.js version 18+" to "Node.js version 20.x"

Testing

• Verified that the change aligns with the package.json engines field
• No code changes, documentation only

Impact

• ✅ Prevents confusion for new contributors
• ✅ Ensures accurate setup instructions
• ✅ Aligns documentation with actual project requirements

Fixes #2595

---

Note

Low Risk
Documentation-only change that updates local build prerequisites; no runtime or build logic is modified.

Overview
Updates README.md to require Node.js 20.x (instead of 18+) when building the docs locally, aligning the setup instructions with the package.json engines.node requirement.

^{Written by Cursor Bugbot for commit 5b17bfb. This will update automatically on new commits. Configure here.}

[vercel]

@subhamkumarr is attempting to deploy a commit to the Consensys Team on Vercel.

A member of the Team first needs to authorize it.

[subhamkumarr]

@AyushBherwani1998 could you please review this and merge it when you get a chance? Thanks!
Issue #2595

[subhamkumarr]

@alexandratran could you please review this and merge it when you get a chance? Thanks!
Issue #2595

[bgravenorst]

Thanks for your contribution 🚀
lgtm

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
metamask-docs	Ready	Preview, Comment	Feb 10, 2026 11:37pm