-
Couldn't load subscription status.
- Fork 28
fix:Align runtime to Node 20 LTS and enforce version #1183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…rc; update README
WalkthroughUpdates project runtime/tooling configuration to Node.js 20 LTS. Adds strict engine enforcement for npm, configures Yarn to node-modules linker, pins Node version via .nvmrc, sets engines and packageManager in package.json, and adjusts README prerequisites and setup steps accordingly. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related issues
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ 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 |
|
I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
|
I have read the CLA Document and I hereby sign the CLA |
|
closes #1182 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (2)
package.json (1)
67-73: Align engines.node with .nvmrc/README for consistency.Consider requiring >=20.19.0 to match .nvmrc and docs. engines.yarn is optional given packageManager, but fine to keep.
Apply:
"engines": { - "node": ">=20.18.0 <21", + "node": ">=20.19.0 <21", "yarn": ">=4.0.0 <5" },README.md (1)
57-68: Minor setup clarity: group nvm command; optionally mention nvm install.Shell clarity/readability:
- nvm use || nvm install 20.19.0 && nvm use 20.19.0 + nvm use || (nvm install 20.19.0 && nvm use 20.19.0)Optionally add a note/link to install nvm if the command is missing, and/or run:
- corepack use yarn@4.9.4 (not required with packageManager, but makes the step explicit).
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (2)
.yarn/install-state.gzis excluded by!**/.yarn/**,!**/*.gzyarn.lockis excluded by!**/yarn.lock,!**/*.lock
📒 Files selected for processing (5)
.npmrc(1 hunks).nvmrc(1 hunks).yarnrc.yml(1 hunks)README.md(1 hunks)package.json(1 hunks)
🔇 Additional comments (3)
.nvmrc (1)
1-2: Pinned Node version looks good..npmrc (1)
1-2: No npm usage detected in CI workflows
Verified that GitHub workflows contain nonpm installornpm ciinvocations; retainingengine-strict=trueis safe..yarnrc.yml (1)
1-1: LGTM. .gitignore has no.yarnentries, so Yarn metadata won’t be ignored.
|
recheck |
|
I have read the CLA Document and I hereby sign the CLA |
Align runtime to Node.js 20 LTS and enforce versions to avoid Corepack/Yarn issues and improve reproducibility.
Changes:
Testing:
Note: One peer warning (@cowprotocol/cow-sdk → ethers), non-blocking.
Summary by CodeRabbit
Documentation
Chores