Repository navigation
npm does not support Node.js v9.0.0 #16649
Description
Activity
I can confirm similar failure on CentOS.
bash-4.2$ npm install npm info it worked if it ends with ok 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/ npm info using npm@5.5.1 npm info using node@v9.0.0 npm info lifecycle node-echo@0.0.1~preinstall: node-echo@0.0.1 npm http fetch GET 200 https://registry.npmjs.org/roi 23ms (from cache) /usr/local/bin/node[32]: ../src/node_zlib.cc:430: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: 0x1251ea1 [npm] 4: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) [npm] 5: 0xb74c3c [npm] 6: v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [npm] 7: 0x1a5bf6a842fd Aborted bash-4.2$ uname -a Linux afbccd39ba67 4.9.44-linuxkit-aufs #1 SMP Fri Aug 25 10:00:41 UTC 2017 x86_64 x86_64 x86_64 GNU/LinuxHave the same problem on Win 10, x64
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.lem@adrianchia are you using the version of npm that came bundled with node? The current upstream version of npm does not work with Node.js 9.x which is why we floated b8888f5 and 9f33a24
Is it possible you are not using the bundled version of npm?
/cc @nodejs/npm
Reacted by Yahor Siarheyenka, Benjamin Gruenbaum and Anna HenningsenIf you have npm updated from bundled with node, just remove it manually from global packages.
@nodejs/collaborators Do you think it makes sense to keep this open until npm fixes this upstream? If so it may make sense to lock this issue and make a comment in the OP with the solution
Reacted by Anatoli Papirovski, Andreas Madsen, Lance Ball, Luigi Pinca, Yahor Siarheyenka, Daijiro Wachi, Benjamin Gruenbaum, Anna Henningsen and Jon Mossfailed on Ubuntu 16.10 as well
node: 9.0.0
npm: 5.5.1npm 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/ /home/amritk/.nvm/versions/node/v9.0.0/bin/node[13315]: ../src/node_zlib.cc:430: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: 0x1251ea1 [npm] 4: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) [npm] 5: 0xb74c3c [npm] 6: v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [npm] 7: 0x3a93576842fd Aborted (core dumped)Reacted by Dong NguyenI am confirming it failed also on Ubuntu 16.04.3 LTS
node: 9.0.0
npm: 5.5.1- added a commit that references this issue
on Oct 31, 2017 There's a workaround posted in npm/npm#19019 (comment) by @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; 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.Reacted by John-David Dalton, MongoExpUser, Robby and Mikita Melnikau@amritk : I got the same error here:
ndaidong@bella-mint /var/www/projects/news-loader $ npm i 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/ /usr/local/bin/node[3204]: ../src/node_zlib.cc:430: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: 0x12beb2a [npm] 4: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) [npm] 5: 0xb09a37 [npm] 6: v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [npm] 7: 0x28ecaed842fd AbortedAnd another issue with natural and webworker-threads at audreyt/node-webworker-threads#169
It looks like there are many packages need to be upgraded to catch up Node.js 9 serie.
- added a commit that references this issue
on Nov 1, 2017 I can confirm similar failure on Travis CI Linux trusty stable using npm latest
$ node --version v9.0.0 $ npm --version 5.5.1 $ nvm --version 0.33.6 before_install 13.91s$ npm install -g npm@latest /home/travis/.nvm/versions/node/v9.0.0/bin/npm -> /home/travis/.nvm/versions/node/v9.0.0/lib/node_modules/npm/bin/npm-cli.js /home/travis/.nvm/versions/node/v9.0.0/bin/npx -> /home/travis/.nvm/versions/node/v9.0.0/lib/node_modules/npm/bin/npx-cli.js + npm@5.5.1 updated 2 packages in 13.185s 124.56s$ npm install 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/ /home/travis/.nvm/versions/node/v9.0.0/bin/node[2758]: ../src/node_zlib.cc:430: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: 0x1251ea1 [npm] 4: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) [npm] 5: 0xb74c3c [npm] 6: v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [npm] 7: 0x249eff1842fd /home/travis/.travis/job_stages: line 236: 2758 Aborted (core dumped) npm install
- added a commit that references this issue
on Nov 1, 2017 FWIW if you don't mind using NodeJS v8.9.0 on Travis CI, you can do
node_js: "lts/*"to work around this.- locked and limited conversation to collaborators
on Nov 1, 2017 If so it may make sense to lock this issue and make a comment in the OP with the solution
Done.
- added a commit that references this issue
on Dec 1, 2017 This is fixed
ATTN: Go here for a workaround: npm/npm#19019 (comment)
After installing Node.js v9.0.0 on Windows 10 x64, npm returns the following message: