Conversation
The Multiple Versions page was showing "npm-registry dedupe" when viewing reports generated via the browser, where the package manager is not known. `npm-registry` is an internal value, not a runnable command. Now the dedupe hint is only shown when the package manager is known and supports the dedupe command (i.e., not `bun` and not `npm-registry`). Closes antfu#213
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.
🔗 Linked issue
Closes #213
🧭 Context
When you generate a report on node-modules.dev (no local project), the
package manager field is set to
npm-registry— an internal value usedby the registry resolver, not a real CLI command. The Multiple Versions
page then renders
npm-registry dedupeas the suggested command, whichyou can't actually run.
📚 Description
Added
npm-registryto the existingv-ifcondition that already hidesthe dedupe hint for
bun. Same idea: if we don't know the real packagemanager, don't show a command the user can't run.
One-line change in
MultipleVersions.vue, no other files affected.