unsupported: add node v13

[ljharb]

What / Why

npm in node 13 says node 13 is unsupported.

I'll update npm in node after this is released; hopefully ASAP as node 13 released today.

[isaacs]

Note to @npm/cli-team: we can make this file a lot simpler in npm v7 when we upgrade to a version of semver with the includePrereleases option.

[ljharb]

Why would that option matter? node 13 could probably have been added prior to its release, it just might not have been counted as "supported" then?

[ljharb]

yay, tests passed! how soon might this be able to get into a released version of npm?

[MylesBorins]

as soon as this lands on master I can make a backport to node.js core so we can get this sorted in advance of updating npm

[MylesBorins]

We've landed the patch in Node.js core and are planning a release for later today

PR for 13.0.1 opened nodejs/node#30081

[ruyadorno]

thanks @ljharb and @MylesBorins 🎉

we'll make sure to include it in the planned upcoming release, seeing that the patch already landed on node we're going to stick to our regular schedule 😊

[MylesBorins]

I would like to implore you to still get a release out asap. While the node release is fixed anyone installing npm separately will still be but by the bug, and we have seen folks report 13.0.1 not fixing their environment for this reason.

…

On Wed, Oct 23, 2019, 10:55 AM Ruy Adorno ***@***.***> wrote: thanks @ljharb <https://github.com/ljharb> and @MylesBorins <https://github.com/MylesBorins> 🎉 we'll make sure to include it in the planned upcoming release, seeing that the patch already landed on node we're going to stick to our regular schedule 😊 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#269?email_source=notifications&email_token=AADZYV7CTU44GMHK66GNDOLQQBQX5A5CNFSM4JDSOWOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECBWZNI#issuecomment-545483957>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADZYVZ2RWPNID7JOU4DOVTQQBQX5ANCNFSM4JDSOWOA> .

[Remzi1993]

@darcyclarke Could somebody merged this PR? It's still an annoying warning and I completely agree with @isaacs

[mikemimik]

Hello Everyone,

This update is slotted to be included in a release we are putting out next week, 6.12.1, on Tuesday October 29th, 2019. Until then, unfortunately you're going to see the warning message if you install npm outside of what's shipped with the latest node patch.