Skip to content

Omit registry URLs from npm lockfiles - #87

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

Omit registry URLs from npm lockfiles#87
Jamie Magee (JamieMagee) wants to merge 1 commit into
Azure-Samples:mainfrom
JamieMagee:fix/omit-lockfile-registry-resolved

Conversation

@JamieMagee

Copy link
Copy Markdown

Summary

  • Add omit-lockfile-registry-resolved=true to the UI project's .npmrc.
  • Regenerate the lockfile without changing its dependency graph, versions, integrity values, lockfileVersion, or other metadata.
  • Remove registry resolved fields so Azure Artifacts feed URLs are not persisted.

Validation

  • npx --yes npm@11.19.0 config get omit-lockfile-registry-resolved returned true.
  • A second npx --yes npm@11.19.0 install --package-lock-only --ignore-scripts made no changes.
  • ms-feed-2, ms-feed-12, ms-feed-17, and ms-feed-25 are absent from the lockfile.
  • npx --yes npm@11.19.0 ci --ignore-scripts passed.
  • npx --yes npm@11.19.0 test passed 46 tests.

Set npm's omit-lockfile-registry-resolved option for the UI project and regenerate the lockfile without changing dependencies.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@JamieMagee
Jamie Magee (JamieMagee) requested a review from a team August 24, 2026 22:59
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