[BUG] Redirect Installation of package x when a request for package y installation is made using config in package.json

[ganeshkbhat]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Need to change the entire sourcecode for the npmjs project or use an local alias to install a different package B instead of package A.

Expected Behavior

I should be able to redirect installation of a npmjs A package to npmjs B package from package.json config.

Citing my repositories as an example to ensure not to make phpcgijs old versions unfindable. What I am wishing to do is redirect phpcgijs to cgijs

package.json

{
...
"repository": {
    "type": "git",
    "url": "https://github.com/ganeshkbhat/cgi-js.git",
    "redirect": "newpackagename_preferably--OR--differentrepository"
  }
}

OR

{
...
"redirect": "newpackagename_preferably"
"repository": {
    "type": "git",
    "url": "https://github.com/ganeshkbhat/cgi-js.git"
  }
}

Steps To Reproduce

NA

Environment

• npm: Current
• Node: Current
• OS: Windows / Linux / Mac
• platform: Windows / Linux / Mac

[ganeshkbhat]

Merging Issues. Seems this feature is being worked on already. I was not aware nor communicated. I though that was not nice at all.

npm/cli#5009
npm/config#76
#9

[ganeshkbhat]

Citing npm package being pushed in as spam based on these articles I wish to push this as a reason to avoid false positives for a few percent of npm packages which were published as new packages:

• https://blog.sandworm.dev/one-in-two-new-npm-packages-is-seo-spam-right-now , and
• https://developers.slashdot.org/story/23/03/30/184239/one-in-two-new-npm-packages-is-seo-spam-right-now

While there may be a lot of spam packages, if you have duplicate package - renamed or republished due to some reason allowing redirect of a npm package to a different package name is definitely going to be a critical feature. You may want to do two this as per my view here:

1. npm package one -> redirect -> npm package two using keyword in package.json (the feature will install npm package two instead of npm package one).
2. npm package one -> redirect -> npm package two when opening the npm website
   • Redirect the npmjs website desciption page for npm package one to npm package two since the package.json specifies config of redirect from npm package one to npm package two
   • Alternatively put a note in npmjs website in package description page that the npm package one is deprecated in favour of npm package two and that installation of npm package one will lead to installation of npm package two). This will help you to take a look at legacy npm package one package, its description, and its legacy code. This is expected and preferable.

I am now updating the expected behaviour in the issues from:

I should be able to redirect a npmjs A package to npmjs B package from package.json config. to I should be able to redirect installation of a npmjs A package to npmjs B package from package.json config.

[wraithgar]

overrides are what you're looking for.