Skip to content

chore(deps-dev): bump npm from 11.6.2 to 11.9.0#42778

Merged
LeoMcA merged 2 commits intomainfrom
bump-npm
Mar 20, 2026
Merged

chore(deps-dev): bump npm from 11.6.2 to 11.9.0#42778
LeoMcA merged 2 commits intomainfrom
bump-npm

Conversation

@caugner
Copy link
Copy Markdown
Collaborator

@caugner caugner commented Jan 14, 2026

Description

Bumps npm from 11.6.2 to 11.9.0:

  • Updates package.json:
    • Sets packageManager field to npm@11.9.0.
    • Adds devEngines.packageManager field with { "name": "npm", "version": ">=11.8.0" }.
  • Updates .nvmrc from v24 to v24.14.0
  • Updates package-lock.json

Motivation

Avoids accidental package-lock.json files by contributors (npm 11.6.2 and 11.8.0 produce different lock files, due to a bug in npm 11.6.2).

Additional details

Related issues and pull requests

Part of mdn/fred#1205.

@caugner caugner requested review from a team and LeoMcA and removed request for a team January 14, 2026 15:10
@github-actions github-actions bot added system [PR only] Infrastructure and configuration for the project size/xs [PR only] 0-5 LoC changed labels Jan 14, 2026
@caugner caugner marked this pull request as ready for review January 14, 2026 16:05
@caugner caugner requested review from a team and mdn-bot as code owners January 14, 2026 16:05
@caugner
Copy link
Copy Markdown
Collaborator Author

caugner commented Jan 15, 2026

Closing for now.

@caugner caugner closed this Jan 15, 2026
Require npm 11.8.0 or later to avoid changes.
@caugner caugner changed the title chore(deps): bump npm from 11.6.2 to 11.7.0 chore(deps-dev): bump npm from 11.6.2 to 11.9.0 Mar 18, 2026
@caugner caugner reopened this Mar 18, 2026
@github-actions github-actions bot added size/s [PR only] 6-50 LoC changed and removed size/xs [PR only] 0-5 LoC changed labels Mar 18, 2026
@LeoMcA
Copy link
Copy Markdown
Member

LeoMcA commented Mar 18, 2026

@caugner can/should we put a point release in .nvmrc? It's a little confusing to have to run nvm install before nvm use, and putting the node version which released with npm 11.9.0 should mean that just nvm use is enough

@caugner
Copy link
Copy Markdown
Collaborator Author

caugner commented Mar 18, 2026

It's a little confusing to have to run nvm install before nvm use, and putting the node version which released with npm 11.9.0 should mean that just nvm use is enough

Yeah, I guess that makes sense.

Edit: Fixed via aee229a.

Copy link
Copy Markdown
Member

@LeoMcA LeoMcA left a comment

Choose a reason for hiding this comment

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

lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/s [PR only] 6-50 LoC changed system [PR only] Infrastructure and configuration for the project

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants