-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
npm is not ready for Node 11 #23013
Comments
Given that the only reason for deprecating seems to be “reducing undocumented API surface”, we should also definitely consider reverting the deprecation. Aliases are cheap and come with very little maintenance overhead. |
Aliases are very cheap to maintain, so an unconditional runtime deprecation that affects existing ecosystem code is not a good idea. This commit turns the runtime deprecation into a `--pending-deprecation` one. Fixes: nodejs#23013
I contacted npm via twitter, their response was
So I'm in favor of downgrading the deprecation as well. |
Currently, npm uses the deprecated
crypto.pseudoRandomBytes
API through itsunique-slug
dependency.There is already a PR to fix it: npm/unique-slug#6
The text was updated successfully, but these errors were encountered: