fix(ci): sync npm 11 lockfile dependencies#61
Merged
Conversation
Record encoding@0.1.13 and its iconv-lite@0.6.3 dependency in the npm lockfile. npm 11 validates optional transitive dependencies during npm ci and rejected the previous lockfile before any build, lint, test, or benchmark job could run.\n\nThe patch intentionally preserves every existing dependency version and peer marker; a clean Node 25/npm 11 install now succeeds.
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
1 participant
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.
What changed
encoding@0.1.13and its nestediconv-lite@0.6.3dependency inpackage-lock.json.Why
Node 25 ships npm 11, which validates optional transitive dependencies during
npm ci. The existing merge-base lockfile omitted these two records, so CI stopped during dependency installation before build, lint, tests, or performance comparisons could run.The performance workflow benchmarks the merge-base first, so this fix must land on
masterbefore optimization PR benchmarks can obtain a valid baseline.Validation
npm ci --ignore-scriptswith Node 25.7.0 / npm 11.10.1