Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Multiple Versions page shows incorrect 'npm-registry dedupe' command

Open
#213 0 comments 0 reactions 0 assignees View on GitHub

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?

Image
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from antfu/node-modules-inspector

All issues in antfu/node-modules-inspector

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.