npm ERR! node-sass@2.0.1 postinstall: `node scripts/build.js` npm

[metasean]

While trying to install an npm package that requires gulp-sass, I'm getting installation errors for node-sass.

Background to explain output and log

I have one Snow Leopard and one Lion partition on my MacBook. I'm using Snow Leopard, but accessing a shared projects directory that is based in the Lion partition. For clarity in the output and log, I've changed the usernames to indicate which is which.

I have been using this dual system with npm for almost a year now. I've got over 700 packages in my user .npm directory, and never had a problem like this. In this case, I was installing the node packages for MEAN.js and the other 76 packages installed without a hiccup.

npm install node-sass

When trying to run npm install node-sass from iojs-v1.2.0, I get the following (I started with node v0.10.36, v0.33.00, and node v0.12.0 and got similar results with each):

-
> node-sass@2.0.1 install /Volumes/Lion Partition/Users/userOnLion/projects/adLoc-meanjs-node/node_modules/node-sass
> node scripts/install.js


> node-sass@2.0.1 postinstall /Volumes/Lion Partition/Users/userOnLion/projects/adLoc-meanjs-node/node_modules/node-sass
> node scripts/build.js

`darwin-x64-iojs-1.2` exists; testing
module.js:341
  Module._extensions[extension](this, filename);
                               ^
Error: dlopen(/Volumes/Lion Partition/Users/userOnLion/projects/adLoc-meanjs-node/node_modules/node-sass/vendor/darwin-x64-iojs-1.2/binding.node, 1): Library not loaded: /usr/lib/libc++.1.dylib
  Referenced from: /Volumes/Lion Partition/Users/userOnLion/projects/adLoc-meanjs-node/node_modules/node-sass/vendor/darwin-x64-iojs-1.2/binding.node
  Reason: image not found
    at Error (native)
    at Module.load (module.js:341:32)
    at Function.Module._load (module.js:296:12)
    at Module.require (module.js:351:17)
    at require (module.js:370:17)
    at Object.<anonymous> (/Volumes/Lion Partition/Users/userOnLion/projects/adLoc-meanjs-node/node_modules/node-sass/lib/index.js:188:15)
    at Module._compile (module.js:446:26)
    at Object.Module._extensions..js (module.js:464:10)
    at Module.load (module.js:341:32)
    at Function.Module._load (module.js:296:12)
npm ERR! Darwin 10.8.0
npm ERR! argv "node" "/Users/userOnSnowLeopard/.nvm/versions/io.js/v1.2.0/bin/npm" "install" "node-sass"
npm ERR! node v1.2.0
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE

npm ERR! node-sass@2.0.1 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the node-sass@2.0.1 postinstall script 'node scripts/build.js'.
npm ERR! 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 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!     /Volumes/Lion Partition/Users/userOnLion/projects/adLoc-meanjs-node/npm-debug.log

npm-debug.log

The npm-debug.log is available at https://gist.githubusercontent.com/metasean/6f2a4db81313fd971dfb/raw/npm-debug.log_for_npm_install_node-sass

_Any ideas on how I might be able to get node-sass to fully install?_

[metasean]

I copied the project from my Lion partition to my Snow Leopard partition and ran npm install and am still getting similar errors.

• Terminal output - https://gist.github.com/metasean/333609f0a1b5725cf42f
• npm-debug.log - https://gist.githubusercontent.com/metasean/040d3cbe17f59633c898/raw/npm-debug.log_for_meanjs_npm_install_all_Snow_Leopard

[xzyfer]

The error message is suggests that our osx binaries aren't compatible with
older versions of osx. They were compiled on 10.9 (mavricks) which is newer
than the versions you're running.

@andrew can you please confirm what version of osx you were previously
compiling the binaries on?

/cc @am11
On 22 Feb 2015 14:01, "metasean" notifications@github.com wrote:

I copied the project from my Lion partition to my Snow Leopard partition
and ran npm install and am still getting similar errors.

• Terminal output
  https://gist.github.com/metasean/333609f0a1b5725cf42f -
  https://gist.github.com/metasean/333609f0a1b5725cf42f

• npm-debug.log
  https://gist.githubusercontent.com/metasean/040d3cbe17f59633c898/raw/npm-debug.log_for_meanjs_npm_install_all_Snow_Leopard

  https://gist.githubusercontent.com/metasean/040d3cbe17f59633c898/raw/npm-debug.log_for_meanjs_npm_install_all_Snow_Leopard

—
Reply to this email directly or view it on GitHub
#693 (comment).

[andrew]

I've been using 10.9 for the past year or so to build the Mac binaries.

[am11]

For both versions of Mac, please make separate gist with the output for this script (in case it fails as well): https://gist.github.com/am11/e5de3c49c219f0811e1d#comment-1386582.

That might help us narrowing down the issue.

[pheew]

I'm also having trouble on Arch linux.
My npm-debug.log and output of the script mentioned by @am11 (installing gulp-sass):
https://gist.github.com/pheew/3540d5a86c5df835481f#file-

[am11]

@pheew, going by your logs, everything seems fine. :)

On top of it, you can re-reconfirm by compiling little Sass:

With pwd == /temp1:

$ node
// this is node interactive console
require('node-sass').render({data: 'a{b:c}', success: function(result) {console.dir(result)}})

If that works as well, then it could be the npm cache thingy (https://docs.npmjs.com/cli/cache) or gulp-sass issue..

[pheew]

Yeah, it does seem to install correctly when just installing it seperately, ie: npm install node-sass
I cleared the cache and tried again but still have the same error when running: npm update gulp-sass

4496 verbose stack Error: node-sass@0.9.6 install: `node build.js`
4496 verbose stack Exit status 1
4496 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:213:16)
4496 verbose stack at EventEmitter.emit (events.js:110:17)
4496 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:14:12)
4496 verbose stack at ChildProcess.emit (events.js:110:17)
4496 verbose stack at maybeClose (child_process.js:1008:16)
4496 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:1080:5)
4497 verbose pkgid node-sass@0.9.6 

That said, i'm not entirely sure it's a node-sass issue.

[pheew]

Ah, appears I've solved the issue. I've totally read over the python errors in the output. Forcing python to v2.7 by calling:

npm update --python=python2.7

solved the issue on my part. Thanks for the help!

[am11]

node-sass@0.9.6

Ouch! That's a very old version. The latest stable is at 2.0.1 mark.

[pheew]

Haha, yeah, it's been a while. Have not been working on the frontend for a while :)

[am11]

Congrats! BTW it should not require consumer to have python installed. Python is required to manually build the binary, which kicks in when the prebuild binary is incompatible; something which we are trying to avoid (#655). I would suggest to upgrade node-sass version to 2.0.1 in gulp-sass.

[metasean]

@xzyfer, @andrew, & @am11 -
Holy smokes, y'all are the most responsive project I've ever dealt with. Thank you!

@am11 -

• gist with both results
• snow leopard results raw
• lion results raw

I did a find and replace on the machine (partition) and user names, just to make sure it was clear which partition was which.

[am11]

@metasean, that is too verbose than necessary and makes it 10x harder to parse! Besides, you don't have to copy paste my entire gist with the comment there.

I specifically referenced a link to a gist comment for Mac, which says:

For Linux/Mac:

mkdir /temp1
cd /temp1

# diagnostic information
npm -v              
node -v
node -p process.versions
node -p process.platform
node -p process.arch

# installation
npm install node-sass

# if installed successfully
node -p console.log(require('node-sass').info())

# else if it fails
cd node_modules/node-sass/vendor

# delete darwin-or-linux<something>\binding.node file and 
# download the appropriate file in that directory manually from:
# https://github.com/sass/node-sass-binaries/tree/v<<insert-latest-version-here>>
#
# (for instance: https://github.com/sass/node-sass-binaries/tree/v2.0.1)

node -p console.log(require('node-sass').info())

# once this is done, delete temp1
rm -r /temp1

Please read the instructions, run the commands and only show the outputs like @pheew did in his 43-liner reply gist: https://gist.github.com/pheew/3540d5a86c5df835481f#file-.