fix: use npm proxy registry for package resolution - #82
Open
Mattias Bälter (mattiasen1) wants to merge 1 commit into
Open
fix: use npm proxy registry for package resolution#82Mattias Bälter (mattiasen1) wants to merge 1 commit into
Mattias Bälter (mattiasen1) wants to merge 1 commit into
Conversation
Replace registry.npmjs.org with packagefeedproxy.microsoft.io/npm in .npmrc and package-lock.json to address security alerts from npmjs.org direct access.
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
Resolves security alerts caused by direct access to npmjs.org.
Changes
registry=https://packagefeedproxy.microsoft.io/npm/egistry.npmjs.org to packagefeedproxy.microsoft.io/npm (host-only change, identical path structure).
Verification
Run
npm cito verify packages resolve correctly through the proxy.