-
Notifications
You must be signed in to change notification settings - Fork 45
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
Please fix deprecated dependencies #72
Comments
See this issue: npm/run-script#25 |
I see it, in the end it also depends on request, but apparently that is a different dependency path. |
And also:
|
Looks like a new major version of @npmcli/run-script, 2.0.0, was released today that updates their dependency on node-gyp to 8.x, which in turn, removes the dependency on request. I tried installing that into a clone of pacote, and it appears to work. After updating to it, the request, uuid, and har-validator packages only appear as children under tap, but since tap only appears as a devDependency here, picking up this new version of @npmcli/run-script should clean up the deprecation warnings for the downstream users of pacote. |
BTW, the way I avoided the deprecation messages was to bundle the dependencies with my package, as npm does. |
Installing a package which depends on pacote@11.3.1 triggers warnings:
These two deprecated dependencies are also used by tap:
Could you fix those dependencies?
BTW, I don't think that it is very useful for npm to complain about deprecated indirect dependencies, since there is not much the author of the top package can do to fix them.
The text was updated successfully, but these errors were encountered: