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
Contributions
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, wherenpm-registryis 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.1Used Package Manager
npm
Validations
Contributions