-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
upgrade to npm 9 #9323
upgrade to npm 9 #9323
Conversation
|
"node": ">= 14", | ||
"npm": ">= 6" | ||
"node": ">=16" |
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.
I've dropped the npm engine declaration completely from the badge-maker/package.json
here. It is bad practice to include one because we're not distributing any lockfile, people might be installing it with yarn, etc
@@ -212,7 +212,7 @@ | |||
}, | |||
"engines": { | |||
"node": "^16.13.0", | |||
"npm": ">=8.0.0" | |||
"npm": "^9.0.0" |
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.
I've switched this to a caret. As we can see from this Pr, jumping a major NPM version tends to require some intervention/review from us
Closes #9075
🗒️ Notes:
npm i --lockfile-version 3 --package-lock-only
is the command to force alockfileVersion
2 --> 3 migration without actually installing/removing anything.