Skip to content
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

Merged
merged 2 commits into from
Jul 16, 2023
Merged

upgrade to npm 9 #9323

merged 2 commits into from
Jul 16, 2023

Conversation

chris48s
Copy link
Member

@chris48s chris48s commented Jun 26, 2023

Closes #9075

  • update lockfile to version 3
  • require npm 9
  • stop testing package on node 14

🗒️ Notes:

  • We'll need to update the branch protection rules to remove the node 14 package builds
  • If you need to rebuild the lockfile again due to merge conflicts, npm i --lockfile-version 3 --package-lock-only is the command to force a lockfileVersion 2 --> 3 migration without actually installing/removing anything.

@chris48s chris48s added developer-experience Dev tooling, test framework, and CI npm-package Badge generation and badge templates labels Jun 26, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Jun 26, 2023

Messages
📖 ✨ Thanks for your contribution to Shields, @chris48s!
📖

Thanks for contributing to our documentation. We ❤️ our documentarians!

Generated by 🚫 dangerJS against df5c661

"node": ">= 14",
"npm": ">= 6"
"node": ">=16"
Copy link
Member Author

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"
Copy link
Member Author

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

@chris48s chris48s mentioned this pull request Jul 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer-experience Dev tooling, test framework, and CI npm-package Badge generation and badge templates
Projects
None yet
Development

Successfully merging this pull request may close these issues.

generating lockfile with npm 9 breaks node 14 package build
2 participants