Skip to content

Add omit-lockfile-registry-resolved - #2174

Merged
veronika-alraheem merged 1 commit into
mainfrom
update-npmrc-lockfile
Aug 14, 2026
Merged

Add omit-lockfile-registry-resolved#2174
veronika-alraheem merged 1 commit into
mainfrom
update-npmrc-lockfile

Conversation

@veronika-alraheem

Copy link
Copy Markdown
Contributor

PR summary

Add omit-lockfile-registry-resolved=true to .npmrc and regenerate package-lock.json

PR Checklist

Please make sure that your PR fulfills the following requirements:

  • The commit message follows the
    Angular Commit Message Guidelines.
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • New tests
  • Build/CI related changes
  • Documentation content changes
  • Other (please describe)

What is the current behavior?

Running npm install generates a package-lock.json that includes "resolved" registry URLs for every package entry.

What is the new behavior?

"resolved" URLs are omitted from package-lock.json.

Does this PR introduce a breaking change?

  • Yes
  • No

@veronika-alraheem
veronika-alraheem requested a review from a team as a code owner August 14, 2026 09:02
@veronika-alraheem
veronika-alraheem merged commit 1fb3a5d into main Aug 14, 2026
9 checks passed
@veronika-alraheem
veronika-alraheem deleted the update-npmrc-lockfile branch August 14, 2026 10:29
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.

2 participants