Repository navigation
fix(website): point package-lock.json at the public npm registry - #8368
Merged
Merged
Conversation
The lockfile added in #8366 had every resolved URL pointing at the internal Wix registry, which GitHub runners cannot reach, so `npm ci` failed in the documentation workflow.
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
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.
The
website/package-lock.jsonadded in #8366 had all 2124resolvedURLs pointing at the internal registry, which GitHub runners cannot resolve. This rewrites the URL prefix tohttps://registry.npmjs.org/. Versions andintegrityhashes are unchanged;package.jsonis untouched. Verified locally:npm ci --legacy-peer-depsinstalls 2124 packages in ~6s.