Build: Update package-lock.json to remove extra peer: true entries#5771
Merged
mgol merged 1 commit intojquery:mainfrom Feb 14, 2026
Merged
Build: Update package-lock.json to remove extra peer: true entries#5771mgol merged 1 commit intojquery:mainfrom
peer: true entries#5771mgol merged 1 commit intojquery:mainfrom
Conversation
mgol
added a commit
to mgol/jquery
that referenced
this pull request
Feb 13, 2026
These extra `peer: true` entries started to appear in npm `11.6.1` and the behavior reverted to the previous one in npm `11.6.3`. But because `11.6.2` was bundled into the latest Node 24 for a while, we updated the lockfile with this temporary version. This change updates the lockfile back to the format used in versions `>=11.6.3` and `<11.6.1`. On the npm side, PR npm/cli#8645 landed in `11.6.3`. It explicitly mentions: > reverts much of fix: corrects peer dependency flag propagation #8579, > which I think mistakenly changed peer dep calculation logic That referenced PR landed in `11.6.1`, so it does look like a mistake. Ref jquerygh-5771 Ref npm/cli#8579 Ref npm/cli#8645
These extra `peer: true` entries started to appear in npm `11.6.1` and the behavior reverted to the previous one in npm `11.6.3`. But because `11.6.2` was bundled into the latest Node 24 for a while, we updated the lockfile with this temporary version. This change updates the lockfile back to the format used in versions `>=11.6.3` and `<11.6.1`. On the npm side, PR npm/cli#8645 landed in `11.6.3`. It explicitly mentions: > reverts much of fix: corrects peer dependency flag propagation #8579, > which I think mistakenly changed peer dep calculation logic That referenced PR landed in `11.6.1`, so it does look like a mistake. Ref jquerygh-5772 Ref npm/cli#8579 Ref npm/cli#8645
7def00f to
c82e7d5
Compare
timmywil
approved these changes
Feb 13, 2026
mgol
added a commit
that referenced
this pull request
Feb 14, 2026
These extra `peer: true` entries started to appear in npm `11.6.1` and the behavior reverted to the previous one in npm `11.6.3`. But because `11.6.2` was bundled into the latest Node 24 for a while, we updated the lockfile with this temporary version. This change updates the lockfile back to the format used in versions `>=11.6.3` and `<11.6.1`. On the npm side, PR npm/cli#8645 landed in `11.6.3`. It explicitly mentions: > reverts much of fix: corrects peer dependency flag propagation #8579, > which I think mistakenly changed peer dep calculation logic That referenced PR landed in `11.6.1`, so it does look like a mistake. Closes gh-5772 Ref gh-5771 Ref npm/cli#8579 Ref npm/cli#8645
mgol
added a commit
to jquery/jquery-migrate
that referenced
this pull request
Feb 23, 2026
These extra `peer: true` entries started to appear in npm `11.6.1` and the behavior reverted to the previous one in npm `11.6.3`. But because `11.6.2` was bundled into the latest Node 24 for a while, we updated the lockfile with this temporary version. This change updates the lockfile back to the format used in versions `>=11.6.3` and `<11.6.1`. On the npm side, PR npm/cli#8645 landed in `11.6.3`. It explicitly mentions: > reverts much of fix: corrects peer dependency flag propagation #8579, > which I think mistakenly changed peer dep calculation logic That referenced PR landed in `11.6.1`, so it does look like a mistake. Ref jquery/jquery#5771 Ref jquery/jquery#5772 Ref npm/cli#8579 Ref npm/cli#8645
mgol
added a commit
to jquery/jquery-migrate
that referenced
this pull request
Feb 23, 2026
These extra `peer: true` entries started to appear in npm `11.6.1` and the behavior reverted to the previous one in npm `11.6.3`. But because `11.6.2` was bundled into the latest Node 24 for a while, we updated the lockfile with this temporary version. This change updates the lockfile back to the format used in versions `>=11.6.3` and `<11.6.1`. On the npm side, PR npm/cli#8645 landed in `11.6.3`. It explicitly mentions: > reverts much of fix: corrects peer dependency flag propagation #8579, > which I think mistakenly changed peer dep calculation logic That referenced PR landed in `11.6.1`, so it does look like a mistake. Ref jquery/jquery#5771 Ref jquery/jquery#5772 Ref npm/cli#8579 Ref npm/cli#8645
mgol
added a commit
to mgol/jquery-migrate
that referenced
this pull request
Feb 24, 2026
These extra `peer: true` entries started to appear in npm `11.6.1` and the behavior reverted to the previous one in npm `11.6.3`. But because `11.6.2` was bundled into the latest Node 24 for a while, we updated the lockfile with this temporary version. This change updates the lockfile back to the format used in versions `>=11.6.3` and `<11.6.1`. On the npm side, PR npm/cli#8645 landed in `11.6.3`. It explicitly mentions: > reverts much of fix: corrects peer dependency flag propagation #8579, > which I think mistakenly changed peer dep calculation logic That referenced PR landed in `11.6.1`, so it does look like a mistake. Ref jquery/jquery#5771 Ref jquery/jquery#5772 Ref npm/cli#8579 Ref npm/cli#8645
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
These extra
peer: trueentries started to appear in npm11.6.1and the behavior reverted to the previous one in npm11.6.3. But because11.6.2was bundled into the latest Node 24 for a while, we updated the lockfile with this temporary version. This change updates the lockfile back to the format used in versions>=11.6.3and<11.6.1.On the npm side, PR npm/cli#8645 landed in
11.6.3. It explicitly mentions:That referenced PR landed in
11.6.1, so it does look like a mistake.Ref gh-5772
Ref npm/cli#8579
Ref npm/cli#8645
Checklist
New tests have been added to show the fix or feature worksIf needed, a docs issue/PR was created at https://github.com/jquery/api.jquery.com