Omit registry URLs from npm lockfile - #353
Open
Jamie Magee (JamieMagee) wants to merge 1 commit into
Open
Conversation
Add a project npm setting that keeps registry tarball URLs out of package-lock.json. Regenerate the lockfile without changing its dependency graph or integrity data. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Summary
omit-lockfile-registry-resolved=trueto the project.npmrc.package-lock.json, removing 417 registryresolvedfields, including thems-feedURL.lockfileVersion: 3, dependency versions, dependency relationships, integrity values, and all other lockfile metadata unchanged.Validation
npm --version:11.19.0npm config get omit-lockfile-registry-resolved:truenpm install --package-lock-only --ignore-scripts: completed twice; the second run left the lockfile hash unchanged.npm ci --ignore-scripts: passed.npm run build: passed on Node.js22.23.2.npm test: fails with 16 request tracing failures. The same failures occur on the unmodifiedmainbaseline with this patch stashed.