chore: bump [email protected] to [email protected]

[Trott]

[email protected] has a dependency on an outdated version of fs-minipass that calls process.umask() with no arguments. That causes a runtime deprecation warning if commands such as npm ls are run either
with Node.js pending deprecations enabled or with the current Node.js 15.0.0 rc.

Update [email protected] to [email protected].

References

Related to nodejs/node#35332 (comment)
Related to #1103

[Trott]

Oh, bummer. If I'm understanding the test results, it looks like latest needs to support back to Node.js 6.x, but the oldest fixed version of tar (5.0.2) requires Node.js 8.x and above, and the version here (6.0.5) requires Node.js 10.x and above.

When will latest not need to support Node.js 6.x anymore? Is there a viable path forward for this at this time if it can only support Node.js 8.x and above?

[ruyadorno]

Oh, bummer. If I'm understanding the test results, it looks like latest needs to support back to Node.js 6.x, but the oldest fixed version of tar (5.0.2) requires Node.js 8.x and above, and the version here (6.0.5) requires Node.js 10.x and above.

yep 👍 pretty sure that's the case

When will latest not need to support Node.js 6.x anymore?

once we land release/v7.0.0-beta back into latest 😊

[darcyclarke]

Thanks for this @Trott! Apologize though, we're probably not going to be able to land/backport this as-is against 6.x. As @ruyadorno mentioned, our plan right now is to ship npm@7 asap (which will drop support for Node versions <10 & is using [email protected]). We should have a PR open against the Node.js 15.0.0 rc within the next day or two.

You can test out 7 today via npm i -g npm@next-7 or check it out here: https://github.com/npm/cli/tree/release/v7.0.0-beta. I believe the last outstanding ref to process.umask() on our end would be in lib/utils/config.js but I still think other deps may be bit by this (note: another related discussion/reference point: nodejs/node#32321)