"npm does not support Node.js v13.0.0" #30066

mgol · 2019-10-22T17:57:25Z

Version: v13.0.0
Platform: Darwin mgolebiowski-mac 18.7.0 Darwin Kernel Version 18.7.0: Tue Aug 20 16:57:14 PDT 2019; root:xnu-4903.271.2~2/RELEASE_X86_64 x86_64 i386 MacBookPro15,1 Darwin
Subsystem:

Under Node.js 13.0.0, running many commands using the included npm version (6.12.0) results in the message:

npm WARN npm npm does not support Node.js v13.0.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12.
npm WARN npm You can find the latest version at https://nodejs.org/

I can understand some npm versions not supporting a newly released Node.js version but the version that's bundled with Node shouldn't print such messages.

The text was updated successfully, but these errors were encountered:

mgol · 2019-10-22T18:02:37Z

I installed Node using nvm if that matters:

nvm install 13

Trott · 2019-10-22T18:04:18Z

Yeah, @ljharb and others are on the case: npm/cli#269

Once there's an npm release, updating npm will fix it.

I'm guessing once there's an npm release, we'll see a Node.js 13.0.1 or 13.1.0 pretty quickly to bundle the new npm.

Trott · 2019-10-22T18:06:49Z

@nodejs/releasers Might it make sense to float the patch in npm/cli#269 on core and push out a 13.0.1 quickly? I'm guessing that would be a ton of work that no one has the time for today or even this week, but asking anyway in case I'm wrong....

ljharb · 2019-10-22T18:08:48Z

If npm can merge and release that fix ASAP, i can get the node PR up shortly afterwards

This should keep the npm warning at bay until it is patched upstream. Refs: npm/cli#269 Refs: nodejs#30066

realJustinLee · 2019-10-23T06:35:58Z

Same issue encountered. Looking forward to the patch.

akash07k · 2019-10-23T07:14:40Z

Same here, uninstalled and reinstall node and NPM but no luck. :(

tamhaneaniket · 2019-10-23T07:15:17Z

Having the same issue....Is there a workaround available?

targos · 2019-10-23T07:21:17Z

The workaround is to ignore the warning. It is not an error and you can still use npm until we release a fix.

This should keep the npm warning at bay until it is patched upstream. Refs: npm/cli#269 Refs: #30066 PR-URL: #30079 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>

akash07k · 2019-10-23T09:31:53Z

till when we can expect the fix?

…

On 10/23/19, Michaël Zasso ***@***.***> wrote: The workaround is to ignore the warning. It is not an error and you can still use npm until we release a fix. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #30066 (comment)

targos · 2019-10-23T10:43:54Z

fixed in v13.0.1

targos · 2019-10-23T11:00:09Z

the reason might be that you installed npm 6.12.0 manually on your system before. the fix is only present in the version bundled by Node.js

targos · 2019-10-23T11:26:52Z

yes, that's expected. The npm you get by installing with npm install -g npm is not controlled by Node.js and will have the warning until npm/cli#269 is merged and a new npm version is released.

erg · 2019-10-23T21:42:53Z

How do you ensure that you're using node's npm that contains this fix? (Asking because I tried to uninstall npm with npm uninstall -g npm and did a nvm use v13.0.1 and I'm still getting the warning message.)

(base) ➜  ~ which npm
/home/erg/.nvm/versions/node/v13.0.1/bin/npm
(base) ➜  ~ npm --version
6.12.0
(base) ➜  ~ npm
npm WARN npm npm does not support Node.js v13.0.1
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12.
npm WARN npm You can find the latest version at https://nodejs.org/

Usage: npm <command>
...

ljharb · 2019-10-23T21:53:36Z

Uninstall 13.0.1 and reinstall it, and don’t use nvm’s “install latest npm” feature?

erg · 2019-10-23T22:04:34Z

Wow, uninstalling and reinstalling nvm install v13.0.1 seems to work. That's kind of weird, why would it be running different code after a reinstall?

Edit: I think I get it. I had a script that did nvm install node --latest-npm after nvm install v13.0.1 the first time, so removing v13.0.1 removed the extra --latest-npm install. Cheers.

JaMoLpE88 · 2019-10-24T08:45:05Z

Uninstall 13.0.1 and reinstall it, and don’t use nvm’s “install latest npm” feature?

It has not worked for me. Still with the npm warn.
npm v13.0.1
npm 6.12.0
We need to wait for the official npm update to give it official support.

Trott · 2019-10-24T13:54:19Z

Uninstall 13.0.1 and reinstall it, and don’t use nvm’s “install latest npm” feature?

It has not worked for me. Still with the npm warn.

If that's the case, it means you are not using the npm shipped with Node.js 13.0.1. This can be happening for a number of reasons, some of which are listed above, but that is by no means an exhaustive list....

Perhaps Node.js should have shipped 13.0.1 with an npm with a slightly different version number than the standard release. Not sure that 6.12.0-node or something like that wouldn't have caused a lot of other problems, though.

We need to wait for the official npm update to give it official support.

That's one solution, and a perfectly viable one if you're OK with ignoring the warnings until then. It's also the easiest and most foolproof solution. :-D

helpme1 · 2019-10-26T07:06:46Z

I have the same problem with node v13.1. Can these warnings be ignored without side effects?

ljharb · 2019-10-26T07:11:21Z

@helpme1 v13.0.1, and yes, you can ignore them.

Trott · 2019-10-29T17:55:41Z

npm@6.12.1 is now out, so npm install -g npm should fix this issue for people seeing it.

ljharb · 2019-10-29T18:02:47Z

(I'm preparing the PR to update npm proper in node as we speak)

Trott · 2019-10-29T18:04:07Z

(I'm preparing the PR to update npm proper in node as we speak)

@ljharb There already is one. #30164

VahidN · 2019-11-04T10:48:20Z

Only this method worked for me on Windows: How to completely remove node.js from Windows
And then installing it from scratch!

This should keep the npm warning at bay until it is patched upstream. Refs: npm/cli#269 Refs: #30066 PR-URL: #30079 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>

kabasele243 · 2019-11-19T23:24:59Z

npm install -g npm worked for me.

sarathkumarpgm · 2019-11-23T19:27:28Z

"npm install -g npm"
This command i worked for me after that re-installed npm "npm install"

note: run cmd as administrator.
now its working fine

cuipengfei · 2019-12-05T06:14:36Z

FYI

$ uname -a
Darwin cpf 19.0.0 Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64 x86_64

$ npm -v
6.13.2

$ node -v
v13.2.0

getting warning in this setup

Trott · 2019-12-05T06:23:10Z

FYI

$ uname -a
Darwin cpf 19.0.0 Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64 x86_64

$ npm -v
6.13.2

$ node -v
v13.2.0

getting warning in this setup

There are lots of warnings you could be getting, but you are all-but-certainly not getting the warning reported in this issue if you are really running npm 6.13.2. This bug was fixed in 6.12.1. If you are seeing this, then you are running npm 6.12.0 or earlier.

cuipengfei · 2019-12-05T07:45:19Z

FYI
$ uname -a
Darwin cpf 19.0.0 Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64 x86_64

$ npm -v
6.13.2

$ node -v
v13.2.0
getting warning in this setup
There are lots of warnings you could be getting, but you are all-but-certainly not getting the warning reported in this issue if you are really running npm 6.13.2. This bug was fixed in 6.12.1. If you are seeing this, then you are running npm 6.12.0 or earlier.

Just tried this, when installing something, getting warning saying that "npm does not support Node.js v13.2.0"

# pfcui @ cpf in ~ [15:34:21]
$ node -v
v13.2.0

# pfcui @ cpf in ~ [15:43:05]
$ npm -v
6.13.2

# pfcui @ cpf in ~ [15:43:07]
$ npm install -g expo-cli
npm WARN npm npm does not support Node.js v13.2.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/

ljharb · 2019-12-05T07:46:46Z

what does which node and which npm say?

cuipengfei · 2019-12-05T07:49:04Z

what does which node and which npm say?

/usr/local/bin/node
/usr/local/bin/npm

Trott · 2019-12-05T15:09:12Z

The fact that it says that 9 is the highest supported version--not mentioning 10 or 12, much less 13--indicates that it is a very old version of npm. Whatever is going on here, it's something weird. I mean, like someone bumped the version of npm only but not the actual code otherwise and compiled it and installed it. Or you're running an otherwise weirdly-hacked npm. I mean, I'm not saying that's it. I'm just saying, something weird is going on.

What's the output of these commands?:

whereis npm
ls -l `which npm`
sum `which npm`

Trott · 2019-12-05T15:11:14Z

Oh! Maybe somehow npm is using a different node than your command line. What does this say?

/usr/bin/env node -v

Trott · 2019-12-05T15:12:22Z

And while we're at it, let's just be complete-ish:

whereis node
ls -l `which node`
sum `which node`

How did you install Node.js? With the default installer? Or a version manager? Or what?

cuipengfei · 2019-12-06T06:19:03Z

And while we're at it, let's just be complete-ish:
whereis node
ls -l `which node`
sum `which node`
How did you install Node.js? With the default installer? Or a version manager? Or what?

It was installed via brew.

I have done brew uninstall and reinstalled the LTS version, which have damaged the crime scene, however it seems to be fine now. No warnings anymore.

FJBDev · 2019-12-27T17:12:50Z

Encountered this issue today when I tried to install the latest version 13.5.0

npm WARN npm npm does not support Node.js v13.5.0

After several hours of searching and testing/rebooting/uninstalling..etc This is what fixed it to me

jufemaiz · 2019-12-29T23:23:17Z

@FJBDev i'm seeing the same on a node:13-alpine image.

ljharb · 2020-01-03T22:07:41Z

node 13.5 comes with npm 6.13.4, so there's something wrong with your node installation there.

eyalk5 · 2020-01-30T12:41:20Z

I get : npm does not support Node.js v13.6.0

Trott · 2020-01-30T15:02:02Z

I get : npm does not support Node.js v13.6.0

Then you're running a version of npm that didn't ship with the 13.6.0 binary.

Trott · 2020-01-30T15:02:51Z

I get : npm does not support Node.js v13.6.0

Then you're running a version of npm that didn't ship with the 13.6.0 binary.

Might be fixed if you run npm install -g npm but probably better to figure out why a different npm got in your path.

richardlau pinned this issue Oct 22, 2019

ljharb self-assigned this Oct 22, 2019

MylesBorins mentioned this issue Oct 23, 2019

deps: npm: patch support for 13.x #30079

Closed

MylesBorins pushed a commit to MylesBorins/node that referenced this issue Oct 23, 2019

deps: npm: patch support for 13.x

f8a689f

This should keep the npm warning at bay until it is patched upstream. Refs: npm/cli#269 Refs: nodejs#30066

targos closed this as completed Oct 23, 2019

targos unpinned this issue Oct 23, 2019

DRoet mentioned this issue Oct 23, 2019

Minor: WARN npm npm does not support Node.js v13.0.0 vuetifyjs/vue-cli-plugins#132

Closed

fatlinesofcode mentioned this issue Oct 23, 2019

update to node v13.0.1 alpinelinux/docker-alpine#47

Closed

ljharb mentioned this issue Oct 29, 2019

deps: upgrade npm to v6.12.1 #30168

Closed

2 tasks

This comment has been minimized.

Sign in to view

"npm does not support Node.js v13.0.0" #30066

"npm does not support Node.js v13.0.0" #30066

Comments

mgol commented Oct 22, 2019

mgol commented Oct 22, 2019

Trott commented Oct 22, 2019 • edited

Trott commented Oct 22, 2019

ljharb commented Oct 22, 2019

realJustinLee commented Oct 23, 2019

akash07k commented Oct 23, 2019

tamhaneaniket commented Oct 23, 2019

targos commented Oct 23, 2019

akash07k commented Oct 23, 2019 via email

targos commented Oct 23, 2019

targos commented Oct 23, 2019

targos commented Oct 23, 2019

erg commented Oct 23, 2019

ljharb commented Oct 23, 2019

erg commented Oct 23, 2019 • edited

JaMoLpE88 commented Oct 24, 2019

Trott commented Oct 24, 2019

helpme1 commented Oct 26, 2019

ljharb commented Oct 26, 2019

Trott commented Oct 29, 2019

ljharb commented Oct 29, 2019

Trott commented Oct 29, 2019

VahidN commented Nov 4, 2019

kabasele243 commented Nov 19, 2019

sarathkumarpgm commented Nov 23, 2019

cuipengfei commented Dec 5, 2019

Trott commented Dec 5, 2019

cuipengfei commented Dec 5, 2019

ljharb commented Dec 5, 2019

cuipengfei commented Dec 5, 2019

Trott commented Dec 5, 2019

Trott commented Dec 5, 2019

Trott commented Dec 5, 2019

cuipengfei commented Dec 6, 2019

FJBDev commented Dec 27, 2019 • edited

jufemaiz commented Dec 29, 2019

This comment has been minimized.

ljharb commented Jan 3, 2020

eyalk5 commented Jan 30, 2020 • edited

Trott commented Jan 30, 2020

Trott commented Jan 30, 2020

Trott commented Oct 22, 2019 •

edited

erg commented Oct 23, 2019 •

edited

FJBDev commented Dec 27, 2019 •

edited

eyalk5 commented Jan 30, 2020 •

edited