Node: "npm does not support Node.js v13.0.0"

Created on 22 Oct 2019 · 44Comments · Source: nodejs/node

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.

Source

mgol

👍25 👀1

Most helpful comment

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

targos on 23 Oct 2019

👍21 👀1

All 44 comments

I installed Node using nvm if that matters:

nvm install 13

mgol on 22 Oct 2019

❤4

Yeah, @ljharb and others are on the case: https://github.com/npm/cli/pull/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 on 22 Oct 2019

👍8 ❤1

@nodejs/releasers Might it make sense to float the patch in https://github.com/npm/cli/pull/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....

Trott on 22 Oct 2019

👍1

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

ljharb on 22 Oct 2019

Same issue encountered. Looking forward to the patch.

Great-Li-Xin on 23 Oct 2019

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

akash07k on 23 Oct 2019

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

tamhaneaniket on 23 Oct 2019

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

targos on 23 Oct 2019

👍21 👀1

till when we can expect the fix?

On 10/23/19, Michaël Zasso notifications@github.com 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:
https://github.com/nodejs/node/issues/30066#issuecomment-545306718

akash07k on 23 Oct 2019

fixed in v13.0.1

targos on 23 Oct 2019

👎2 👍2

@targos for some reason, I am still getting the same warnings,

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/

I downloaded .exe from http://nodejs.org/

Windows 10

Nothing-Works on 23 Oct 2019

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 on 23 Oct 2019

@targos and apparently if I npm install -g npm@latest it will give me these warnings, so in future versions, this issue can also be fixed right?

Nothing-Works on 23 Oct 2019

👍3

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 https://github.com/npm/cli/pull/269 is merged and a new npm version is released.

targos on 23 Oct 2019

👍5

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>
...

erg on 23 Oct 2019

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

ljharb on 23 Oct 2019

@ljharb @erg I believe if this can be merged then all the warnings will be gone.

Nothing-Works on 24 Oct 2019

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.

erg on 24 Oct 2019

👍3

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.

JaMoLpE88 on 24 Oct 2019

👍1

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

Trott on 24 Oct 2019

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

helpme1 on 26 Oct 2019

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

ljharb on 26 Oct 2019

👍3

[email protected] is now out, so npm install -g npm should fix this issue for people seeing it.

Trott on 29 Oct 2019

👍8

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

ljharb on 29 Oct 2019

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

@ljharb There already is one. https://github.com/nodejs/node/pull/30164

Trott on 29 Oct 2019

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

VahidN on 4 Nov 2019

npm install -g npm worked for me.

kabasele243 on 20 Nov 2019

👍1

"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

sarathkumarpgm on 23 Nov 2019

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

cuipengfei on 5 Dec 2019

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.

Trott on 5 Dec 2019

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/

cuipengfei on 5 Dec 2019

what does which node and which npm say?

ljharb on 5 Dec 2019

what does which node and which npm say?

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

cuipengfei on 5 Dec 2019

😕1

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 on 5 Dec 2019

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

/usr/bin/env node -v

Trott on 5 Dec 2019

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?

Trott on 5 Dec 2019

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.

cuipengfei on 6 Dec 2019

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

FJBDev on 27 Dec 2019

👍1

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

jufemaiz on 30 Dec 2019

👍1

MacOS Catalina 10.15.2

I used brew install node.

➜  Desktop npm --version
6.9.0
➜  Desktop node --version
v13.5.0
➜  Desktop npm list
npm WARN npm npm does not support Node.js v13.5.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/
/Users/e/Desktop
└── (empty)

Similar issue?