-
Notifications
You must be signed in to change notification settings - Fork 329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for npm package aliases #633
Comments
Great suggestion. I'm happy to support and provide guidance for a PR for this feature. |
@Cherry @l5x I attempted a fix in #715. Could you try |
@raineorshine Awesome! From some basic testing, things seem to work as I'd expect when using a package alias! Thanks for the feature addition! |
Great, thank you! I will merge into |
npm 6.9.0 added support for aliasing packages in your
package.json
, so for example, you could installpostman-request
, but into therequest
folder as per the syntax below:More references:
As per the example above, I'm using
[email protected]
which is out of date, but not being detected byncu
. The latest version at time of writing as per https://www.npmjs.com/package/postman-request, is2.88.1-postman.19
.There's a lot of use-cases for this, but one of the more common ones is actually as I'm describing above - migrating off of an older unmaintained library to another one with an identical API, without making too many code changes. It would be great to see this syntax supported in
npm-check-updates
.The text was updated successfully, but these errors were encountered: