Multiple Versions page shows incorrect 'npm-registry dedupe' command
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start at the Multiple Versions page using the provided reproduction URL and trace where the dedupe alert command is generated. Confirm the browser report lacks a known package manager, then ensure the completed behavior does not display the invalid npm-registry dedupe command when no runnable package-manager command is available.
Written by the indexing model from the issue text.
Description
Describe the bug
The Multiple Versions page shows an alert informing the user of a dedupe command they could run.
However, when generating a report for a package via the browser, the package manager is not known ahead of time.
This causes the command to reference npm-registry dedupe, where npm-registry is an internal value instead of an actual runnable command.
Should this message be shown when we don't know the package manager of the user?
Reproduction
https://node-modules.dev/report/multiple-versions#install=eslint
System Info
Browsers:
Chrome: 152.0.7977.75
Firefox: 156.0.1
Firefox Developer Edition: 156.0.1
Used Package Manager
npm
Validations
- Follow our Code of Conduct
- Read the Contributing Guide.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
- The provided reproduction is a minimal reproducible of the bug.
Contributions
- I am willing to submit a PR to fix this issue
- I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 90
- Avg merge
- 3h 49m
- Merged PRs (30d)
- 4
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from antfu/node-modules-inspector
-
Support bun dedupeOpenenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
antfu/node-modules-inspector#214 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 38/100
antfu/node-modules-inspector#174 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
antfu/node-modules-inspector#145 ·
-
Redundant codeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
antfu/node-modules-inspector#123 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
antfu/node-modules-inspector#122 · 3 comments · 2 reactions ·
All issues in antfu/node-modules-inspector
Similar issues
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 68/100
remix-run/react-router#15558 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
solana-foundation/pay-kit#341 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#607 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day