fix: preserve pnpm package source aliases#824
Open
V1RE wants to merge 1 commit into
Open
Conversation
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.
What
Preserves declared import/package names when pnpm package sources resolve to a differently named package in
.pnpm.Adds regression coverage for pnpm package source forms from the pnpm docs:
npm:<actual>@<version>aliasWhy
Closes #823.
pnpm package sources can map a declared dependency name to a different resolved source package, e.g.
jsr:ornpm:<actual>@<version>.Fallow should credit the declared/imported package name for unused/unlisted dependency analysis, rather than reporting the declared dependency as unused and the resolved source package as unlisted.
Test plan
cargo fmt --all -- --checkcargo clippy --workspace -- -D warningscargo test --workspace