node-sass: Node 6: Failed at the node-sass@3.6.0 postinstall script 'node scripts/build.js'
Looks like there’s an issue with the newly released Node 6.0.0
npm ERR! Linux 3.13.0-40-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v6.0.0/bin/node" "/home/travis/.nvm/versions/node/v6.0.0/bin/npm" "install"
npm ERR! node v6.0.0
npm ERR! npm v3.8.6
npm ERR! code ELIFECYCLE
npm ERR! node-sass@3.6.0 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@3.6.0 postinstall script 'node scripts/build.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node scripts/build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs node-sass
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls node-sass
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/travis/build/tleunen/react-mdl/npm-debug.log
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 39
- Comments: 58 (19 by maintainers)
Links to this issue
Commits related to this issue
- node-sass dying on Node v6 https://github.com/sass/node-sass/issues/1484 — committed to goblindegook/littlefoot by goblindegook 8 years ago
- Fix final Node 6 deprecation warnings This was partially addressed by bumping NAN in $1496. Fixes #1484 — committed to xzyfer/node-sass by xzyfer 8 years ago
- Fix final Node 6 deprecation warnings This was partially addressed by bumping NAN in #1496. https://github.com/nodejs/node/issues/6216 https://codereview.chromium.org/1839983002/patch/1/10002 Fixes... — committed to xzyfer/node-sass by xzyfer 8 years ago
- Fix final Node 6 deprecation warnings (#1498) This was partially addressed by bumping NAN in #1496. https://github.com/nodejs/node/issues/6216 https://codereview.chromium.org/1839983002/patch/1/1... — committed to sass/node-sass by xzyfer 8 years ago
node-sass@v3.7.0 has been released.
check out https://github.com/sass/node-sass/releases
npm rebuild node-sassfixed the issue hereThanks you we appreciate the heads up. These threads tend to devolve quickly. We are now aware of the issue.
Once we have a fix it’ll take a about a day to do a new release we because we need to prebuild a lot of binaries.
We’ll hopefully have something by next week. On 27 Apr 2016 9:00 AM, “David Newman” notifications@github.com wrote:
I’m seeing lots of JS+C stack traces & warnings when running node-sass 3.6.0 on Node 6.0.0, things like:
and:
@owndann I fixed use "npm rebuild node-sass "
@tleunen we’ll keep this open until we release v3.7.0 with proper Node.js 6 support.
Same issue as @ralekna.
node v6.0andOS X El Capitan x64:Why is this closed?
I still get the
Error: Node Sass does not yet support your current environment: Windows 64-bit with falseerrornode5.3 same as …
`> node scripts/install.js
Cannot download “https://github.com/sass/node-sass/releases/download/v3.6.0/win32-x64-48_binding.node”:` it is 404
failing on ubuntu sh: 1: node: not found npm ERR! Linux 4.4.0-31-generic npm ERR! argv “/usr/bin/nodejs” “/usr/bin/npm” “install” “node-sass” npm ERR! node v4.2.6 npm ERR! npm v3.5.2 npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn
npm ERR! node-sass@3.8.0 install:
node scripts/install.jsnpm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the node-sass@3.8.0 install script ‘node scripts/install.js’. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the node-sass package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node scripts/install.js npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs node-sass npm ERR! Or if that isn’t available, you can get their info via: npm ERR! npm owner ls node-sass npm ERR! There is likely additional logging output above.npm ERR! Please include the following file with any support request: npm ERR! /root/Desktop/PokemonGo-Map/npm-debug.log
@Yimiprod fixed in v3.7.0
For the node
brew install nodealso installs Node 6No worries @xzyfer It was purely informtive to let you guys know there’s an issue in Node 6. I’m not expecting this to be resolved in the hour 😉
Same as @mgol on Arch Linux with Node 6.0.0 and npm 3.8.7
Please read the documentation on how to file a bug. Saying “it doesn’t work” and screenshot don’t give us any information to help you.
On 6 Aug 2016 5:11 AM, “Alexander Harding” notifications@github.com wrote:
I’m having issues with 3.8.0, I think. Ubuntu, Node 6.3.1
Confirmed, thanks for the hard work.
I ran into this same error and came here to refute the “bleeding edge” claim because
nvmis now installing Node 6 when using thestablekeyword, but it turns out that that keyword is deprecated and now simply returns the latest (and apparently bleeding edge un-stable) version of Node.So if others are getting all this because you’re using
nvm install stable; nvm use stable, you may wish to update it to point to a specific version (e.g.nvm install v5; nvm use v5, which will get you the latest v5 dot release) or at least update it tonvm install node; nvm use nodeto make it more clear that you’re not necessarily getting a stable build.