Skip to content

Omit registry URLs from the npm lockfile - #48

Open
Jamie Magee (JamieMagee) wants to merge 1 commit into
Azure:mainfrom
JamieMagee:chore/omit-lockfile-registry-resolved
Open

Jamie Magee (JamieMagee) wants to merge 1 commit into
Azure:mainfrom
JamieMagee:chore/omit-lockfile-registry-resolved

Conversation

@JamieMagee

Copy link
Copy Markdown
Member

Summary

Add a root npm setting so future lockfile updates do not record registry-specific resolved URLs. The lockfile was regenerated with npm 10.9.4. Its lockfile version and every field other than resolved remain unchanged.

Validation

  • npx --yes npm@10.9.4 config get omit-lockfile-registry-resolved returned true.
  • Regeneration was idempotent.
  • npx --yes npm@10.9.4 ci --ignore-scripts --no-audit --no-fund passed.
  • npm run build passed.
  • The package does not define a runnable test suite. Its npm test script is the existing placeholder that exits with an error.

Configure npm to keep registry-specific resolved URLs out of future lockfile updates.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.

1 participant