Repository navigation
npm is not ready for Node 11 #23013
Description
Activity
- added this to the milestone
on Sep 22, 2018 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.
Reacted by Michaël Zasso and Henrique MattosReacted by @davalapar- added a commit that references this issue
on Sep 22, 2018 I contacted npm via twitter, their response was
I'm glad you asked about this. We can't guarantee that repo will be looked at in the near future.
So I'm in favor of downgrading the deprecation as well.
Reacted by @davalapar- added a commit that references this issue
on Jul 27, 2026
Currently, npm uses the deprecated
crypto.pseudoRandomBytesAPI through itsunique-slugdependency.There is already a PR to fix it: npm/unique-slug#6