Skip to content

Pin npm version to fix a bug with 11.12.0#707

Merged
frankieroberto merged 3 commits intomainfrom
pin-npm-version
Mar 19, 2026
Merged

Pin npm version to fix a bug with 11.12.0#707
frankieroberto merged 3 commits intomainfrom
pin-npm-version

Conversation

@frankieroberto
Copy link
Collaborator

No description provided.

@frankieroberto frankieroberto temporarily deployed to record-a-vac-pin-npm-ve-zxtp6p March 19, 2026 13:38 Inactive
@frankieroberto frankieroberto temporarily deployed to record-a-vac-pin-npm-ve-zxtp6p March 19, 2026 13:57 Inactive
"engines": {
"node": "^24",
"npm": "^11.6.1"
"npm": "^11.6.1, <11.6.3 || ^11.6.4, <11.12.0"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Best keeping this as the default range in our other repos?

We'll never see npm v11.12.0 included by default in a Node.js release

Suggested change
"npm": "^11.6.1, <11.6.3 || ^11.6.4, <11.12.0"
"npm": "^11.6.1 <11.6.3 || ^11.6.4"

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having <11.12.0 is a good reminder if I run npm install -g npm@latest locally though!

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But when v11.13.0, v11.14.0, v11.15.0 comes out—more warnings

@frankieroberto frankieroberto merged commit b638049 into main Mar 19, 2026
1 check passed
@frankieroberto frankieroberto deleted the pin-npm-version branch March 19, 2026 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants