Unsupported version of node

[ilog2000]

I'm opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don't understand.
• Other (see below for feature requests):

What's going wrong?

"npm install" gives an error after installing node.js v9.0.0

npm WARN npm npm does not support Node.js v9.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 4, 6, 7, 8.
npm WARN npm You can find the latest version at https://nodejs.org/
C:\Program Files\nodejs\node.exe: src\node_zlib.cc:430: Assertion `args.Length() == 7 && "init(windowBits, level, memLevel, strategy, writeResult, writeCallback," " dictionary)"' failed.

How can the CLI team reproduce the problem?

Install node.js v9.0.0, open any project, type:
npm install

supporting information:

• npm -v prints: 5.5.1
• node -v prints: v9.0.0
• npm config get registry prints: npm WARN npm npm does not support Node.js v9.0.0
• Windows, OS X/macOS, or Linux?: Windows 10

[amritk]

Here's the issue from the node repo
nodejs/node#16649

[addaleax]

For now, you should be able to work around this

• by using npmc rather than npm, i.e. npx npmc install instead of npm install; or
• by using the version of npm that is bundled with Node 9 edit: see Unsupported version of node #19019 (comment) for how to do that; or
• by downgrading to npm@5.3.x: [sudo] npm install -g npm@5.3.x

The “real” fix would be waiting for the next npm release.

[ilovezfs]

Is there an ETA until the next npm release? In Homebrew we're planning to withhold node 9 indefinitely until npm has a compatible release.

[ilog2000]

Thank you for work around. I simply use yarn as for now, it shows a warning but works. I am just not sure if it is possible to upgrade npm with it after new version is out.

[LayZeeDK]

Uninstalling previous version of Node as well as deleting %AppData%\npm and %AppData%\npm-cache and then installing Node 9.0.0 worked for me. However, I had to install my globally installed packages again.

[ilog2000]

Thank you, uninstall Node v9.0.0, delete npm & npm-cache, then re-install Node v9.0.0 works for me as well.

[hatzipanis]

This is failing when building on Heroku but I'm not sure if this is the correct issue. Any ideas here?

[iwadam]

@hatzipanis Try this solution: https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
Basically you have to specify node version in your package.json file like this:

"engines": {
   "node": "8.x"
 }

[MuhammadHasham23]

I've just upgraded to Node v9 and ran into the same issue.Following the advice to uninstall a global instance of npm has resolved the issue for me, using:

npm uninstall -g npm

This caused my system to fall back on the version of npm installed by node 9.0.0, thereby resolving the warning.

[cybernetics]

@LayZeeDK I just deleted %AppData%\npm and %AppData%\npm-cache and then I reran node-v9.1.0-x64.msi setup without uninstalling existing node first. It prompted me to repair the existing setup and I went ahead with. after that I was able to run npm command.

npm -v
5.5.1

it saved me from the hassle of uninstalling & installation of global packages again.

[jameswomack]

Looks like it has to do with npm/lib/utils/unsupported.js

var supportedNode = [
  {ver: '4', min: '4.7.0'},
  {ver: '6', min: '6.0.0'},
  {ver: '7', min: '7.0.0'},
  {ver: '8', min: '8.0.0'}
]

[ghost]

Also had the same issue

[Yonezpt]

Followed @MohammadHasham steps in #19019 (comment) and the issue went away in node 9.1.0 update

[duggum]

@jameswomack said:

Looks like it has to do with npm/lib/utils/unsupported.js

That's it for sure. It looks like the Node.js folks may have just updated the unsupported file on their own.

//  This is from Node 9.1.0's npm/lib/utils/unsupported.js
var supportedNode = [
  {ver: '4', min: '4.7.0'},
  {ver: '6', min: '6.0.0'},
  {ver: '7', min: '7.0.0'},
  {ver: '8', min: '8.0.0'},
  {ver: '9', min: '9.0.0'}
]

The question is, what's the reason the npm folks haven't made such a simple change? Are they still testing compatibility before updating? If that's the case, then why would the node folks just make a potentially risky change before compatibility testing is finished?

[kenany]

Since it hasn't been linked here yet, #18964 is the PR which adds v9 to that supportedNode array 👍

[mutantkeyboard]

@MohammadHasham that did the trick for me too.

[djnaumov]

I think that I have the same issue with node 9.2.0

npm WARN npm npm does not support Node.js v9.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.
npm WARN npm You can find the latest version at https://nodejs.org/
WARNING: You are likely using a version of node-tar or npm that is incompatible with this version of Node.js.atus
Please use either the version of npm that is bundled with Node.js, or a version of npm (> 5.5.1 or < 5.4.0) or node-tar (> 4.0.1) that is compatible with Node.js 9 and above.
C:\Program Files\nodejs\node.exe: src\node_zlib.cc:437: Assertion `args.Length() == 7 && "init(windowBits, level, memLevel, strategy, writeResult, writeCallback," " dictionary)"' failed.

[bonesoul]

Yep same with 9.2.0

[rjdesignz]

I am having similar issues as well. Not able to run npm after upgrading to Node 9.2.0
Even uninstall of npm isn't working. It gives me error as follows:

rj$ npm uninstall -g npm
npm WARN npm npm does not support Node.js v9.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.
npm WARN npm You can find the latest version at https://nodejs.org/
up to date in 0.057s

[dnalborczyk]

wow, node v9.0 has been released almost a month ago. the ignorance of the npm folks speaks volumes, specially after putting a lot of afford into catching up with yarn and trying to regain user trust.

@ilovezfs is it possible to point the brew script to the node modified package?

[ilovezfs]

@dnalborczyk many workarounds are possible, but as you can see from this issue itself, they lead to chaos.

[robcresswell]

@dnalborczyk No need to insult them. Keep it civil and just ask for a tag.

[dnalborczyk]

@robcresswell you're joking, right?

[ilovezfs]

@dnalborczyk you should read, or re-read, the Code of Conduct

[dnalborczyk]

I don't really see how the above is an insult, just my personal opinion on that matter.

Not a single word or statement from npm regarding this issue, and I can give you guys plenty of references and cc's where people have asked for almost a month now.

npm is backed by npm, Inc. - and I'm more referring to the corporate entity, than the open source project.

Unfortunately npm is pretty much baked into node, and users are not given a choice of alternatives, and so here we are ...

[robcresswell]

@dnalborczyk I'm not joking. I also don't think saying "it's my opinion" is a valid way of defending an insult. The team (who are humans, not corporate robots) are clearly overburdened (1000+ issues) so I'd assume there is more to the story than them just being "ignorant". Just request prioritisation politely and apply a workaround in the meantime. It's a little inconvenient, but that's life, especially when you're dealing with software that costs you no money or time.

[robertmain]

👍 +1 on this issue

[zkat]

I spoke to @MylesBorins about this, but I'm literally cooking up the next release of npm right now. It'll go into next once that's done, and y'all should wait a week to merge it into node, because we want to make sure there's no surprises, since it does involve some nontrivial refactorings and a couple new features. It should be ready for Node to consume by next Thursday (7 Dec).

[MylesBorins]

Thanks for the update and hard work @zkat!

[zkat]

https://twitter.com/maybekatz/status/935357840872554496 And it's out.

Please go ahead and try it out. We'll be watching for early warnings on breakage for the next week to make sure everything looks ok. Thanks y'all for your patience. It's been a hell of a couple of months for the team :s

[ilovezfs]

Thanks @zkat! You're awesome :)

[magiksd]

Hello, I'm stuck with npm 5.5.1 on Node.js 9.2.0, I can't update npm with "npm i -g npm" or "npm i -g npm@next", I'm getting this error :

$ npm i -g npm@next
npm WARN npm npm does not support Node.js v9.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.
npm WARN npm You can find the latest version at https://nodejs.org/
WARNING: You are likely using a version of node-tar or npm that is incompatible with this version of Node.js.
Please use either the version of npm that is bundled with Node.js, or a version of npm (> 5.5.1 or < 5.4.0) or node-tar (> 4.0.1) that is compatible with Node.js 9 and above.
/usr/bin/node[23747]: ../src/node_zlib.cc:437:static void node::{anonymous}::ZCtx::Init(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args.Length() == 7 && "init(windowBits, level, memLevel, strategy, writeResult, writeCallback," " dictionary)"' failed.
 1: node::Abort() [npm]
 2: node::Assert(char const* const (*) [4]) [npm]
 3: 0x1255aff [npm]
 4: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) [npm]
 5: 0xb77f9c [npm]
 6: v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [npm]
 7: 0x2d3e12842fd
Aborted

[magiksd]

Found a "solution" :

npm remove -g npm
apt-get install --reinstall nodejs
npm i -g npm@next

[ilovezfs]

brew install --devel node will now give you node 9.2.0 + npm 5.6.0

[Evanto]

I've started having this npm does not support Node.js v9.2.0 issue along with:

eva@eva-CR70-2M-CX70-2OC-CX70-2OD:~/Develop/Netlify/pizza4$ ws --spa index.htmlServing at http://eva-CR70-2M-CX70-2OC-CX70-2OD:8050, http://127.0.0.1:8050, http://192.168.0.103:8050
12:09:20: Middleware error
Error: ENOENT: no such file or directory, stat '/home/eva/Develop/Netlify/pizza4/src/index.html'

Are they related? My project worked fine previously, so I'm guessing ENOENT err is not about code, is it some conflict in software or a result of incompatible node/npm versions?
Also I have npm update check failed.

I tried I think every solution offered in this thread, but can't get rid of ENOENT and npm update check failed.
Ubuntu 16.04.3 LTS
Nodejs v9.2.0
npm 5.6.0

[mutantkeyboard]

@Evanto try doing npm install --no-optional, and see what it returns.

[Evanto]

@mutantkeyboard

eva@eva-CR70-2M-CX70-2OC-CX70-2OD:~/Develop/Netlify/pizza4$ sudo npm install --no-optional

npm WARN logo.pizza@2.0.0 No repository field.
npm WARN logo.pizza@2.0.0 No license field.
npm WARN The package gulp-jshint is included as both a dev and production dependency.
npm WARN The package gulp-uglify is included as both a dev and production dependency.
npm WARN The package jshint is included as both a dev and production dependency.

up to date in 1.122s

[cloakedninjas]

Downloaded the 9.2.0 package from the NodeJS homepage and have ended up here... So looks like this is still an issue?

[robcresswell]

@cloakedninjas Could you give some more information or open a new issue? Just commenting "me too" on a closed bug is not terribly helpful :)

[cloakedninjas]

Unfortunately I didn't keep my shell output, but after some digging around node-gyp, it looks like my specific issue was related to deps of deps. Specifically webpack and fsevents, bumping to latest webpack release allowed me to install without issue.

[thornjad]

Node 9.2.1 + npm 5.6.0 using nvm seems to be all back to normal!

[zkat]

npm@5.6.0 became latest yesterday. I'm locking this now.