refactor: do not include registry url in package keys #1759
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.
Pre-v9 pnpm lock files are a bit of a mess, as I keep learning.
It seems like when a non-default registry is used on a package the
package.*
key in pnpm-lock.yaml then gets the default registry as a prefix. Then theresolution
gets{registry: https://registry.yarnpkg.com/, tarball: https://registry.npmjs.org}
(that's right, thetarball
points to the default registry, despite our npmrc configuring the registry to the yarnpkg). See https://github.com/aspect-build/rules_js/blob/v2.0.0-rc1/npm/private/npm_translate_lock_helpers.bzl#L424-L429This PR drops that default registry from the
package.*
keys, which means all the generated bzl files, all the arrays of dep versions etc etc.See the diffs on all the snapshot tests.
Changes are visible to end-users: no
Test plan