npm ERR! Failed at the [email protected] install script. #428
Comments
|
Same problem encounted! |
|
Can you try upgrading node-gyp as well?
|
|
@andrew , I've tried but the error still exsits. |
|
Delete the |
|
Sorry the last reply was targeted for #427. |
|
I'm running into the same problem, even after deleting build and upgrading node-gyp. |
|
Yeah this is pretty much a showstopper. I'm trying to use |
|
I agree with @Jakobud , this is a big problem for us by way of sass-brunch. We had to peg an old version of sass-brunch (uses an older version of node-sass) to work around this issue. |
|
@blimmer I figured out a temporary workaround until In my This forces I'm not sure if order matters when specifying dependencies in your |
|
I'm just investigating this now, I have a hunch that everyone who's running into this issue is using a mac, if so I think I know what the fix is. |
|
Yep, Mac OS X 10.9.5. On Mon, Sep 22, 2014 at 10:35 AM, Andrew Nesbitt [email protected]
Ben Limmer |
|
👍 getting this problem as well, use Also @andrew I'm running into this error on 2 Ubuntu 13.10 machines |
|
I've just published v0.9.5-rc1, can you give that a try?
|
|
I still get the same error i had previously |
|
although actually @andrew apologies looks like my error with it is slightly different it does install, but then has issues with mapping. Sorry hadn't realised |
|
I'm running into the issue on a CentOS 6.3 server. |
|
I'm still getting the same error using I wasn't able to reproduce the failing spec on Ubuntu 14.04, Node v0.10.32; I tried both |
|
@Jakobud, you need to have python v2.7 installed in order to build the binaries (v3.x.x is not supported by node-gyp). |
|
@andrew 0.9.5-rc1 fixes the issue for me! EDIT (clarification): I ran |
|
@am11 Okay thanks. CentOS 6.3's Python is 2.6.6 by default. I will update it and see. The thing is, I can install |
|
Probably because I built *nix x86-32 and x86-64 binaries on Ubuntu 12 via vagrant (using sudo; which was my first hunch for permission error -- but not anymore, it is on python now :D), and on installing the binaries it checks the compatibility and try to rebuild it if there is an issue. Architecture mismatch or something..? |
|
Hi, new here, wanted to install node-sass to play around with it, after seeing as it didn't want to install for me I found this thread, still dosen't work with the version @andrew has posted. root@Orion:~# npm install -g [email protected]
npm install -g [email protected]
/usr/local/bin/node-sass -> /usr/local/lib/node_modules/node-sass/bin/node-sass
> [email protected] install /usr/local/lib/node_modules/node-sass
> node build.js
child_process: customFds option is deprecated, use stdio instead.
gyp ERR! configure error
gyp ERR! stack Error: "pre" versions of node cannot be installed, use the --nodedir flag instead
gyp ERR! stack at install (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/install.js:66:16)
gyp ERR! stack at Object.self.commands.(anonymous function) [as install] (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/node-gyp.js:66:37)
gyp ERR! stack at getNodeDir (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:152:20)
gyp ERR! stack at /usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:95:9
gyp ERR! stack at ChildProcess.exithandler (child_process.js:723:7)
gyp ERR! stack at ChildProcess.emit (events.js:110:17)
gyp ERR! stack at maybeClose (child_process.js:1000:16)
gyp ERR! stack at Socket.<anonymous> (child_process.js:1168:11)
gyp ERR! stack at Socket.emit (events.js:107:17)
gyp ERR! stack at Pipe.close (net.js:461:12)
gyp ERR! System Linux 2.6.32-042stab093.4
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/node-sass
gyp ERR! node -v v0.13.0-pre
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
Build failed
npm ERR! [email protected] install: `node build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
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 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! System Linux 2.6.32-042stab093.4
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "[email protected]"
npm ERR! cwd /root
npm ERR! node -v v0.13.0-pre
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR! not ok code 0
root@Orion:~# npm --version
npm --version
1.4.28
root@Orion:~# node --version
node --version
v0.13.0-pre |
|
@ZetaHunter, does this help: http://stackoverflow.com/a/12997047/863980? |
|
@am11, the thing is, I installed nodejs using apt-get :/ and if I did find where it put the binary, I doubt I actually have source anywhere. |
|
@ZetaHunter, you can run this commend to find out: It may give you multiple paths. Select the one with |
|
@am11, I seem to have fixed my case by using npm install -g n which just installed the stable node version. |
|
I've just released v0.9.6 which should solve these install issues. |
|
@Jakobud and other folks who were having this issue, is this fixed by v0.9.6? |
|
FWIW, after 0.9.6, we would have to update our build script to run gcc with |
|
Still an issue with 0.9.6 for me: My package.json: The dependant package is Is there any other debug information I can give you guys to help you on this one? I'd like to do whatever I can. |
|
@Jakobud what operating system did you get that error on? It looks like a node-gyp error, possibly related to permissions. |
|
|
|
It seems like a node-gyp issue. Perhaps this is related: nodejs/node-gyp#454. |
|
So going by last comment there; does this help: sudo npm install --unsafe-perm --verbose -g node-sass
# -g is optional and you can give it a try without sudo |
|
Not sure if this is a Am I the only one having this issue? |
|
Which present another node-gyp issue: nodejs/node-gyp#363. Go through the comments. Seems like the solutions by @laithshadeed and @rex worked for others. |
|
This definitely seems related to the @Jakobud I would recommend giving this a shot: nodejs/node-gyp#363 (comment) The credit for that fix goes to @springmeyer, I just elaborated on what he suggested here: nodejs/node-gyp#363 (comment) Additional possible fixes: @namuol - nodejs/node-gyp#363 (comment) @springmeyer, your teensy-tiny comment continues to save lives 🍻❗ Side Note: Holy shit that was a lot of name dropping. Fuck it. Credit where credit is due. |
|
@rex I did try nodejs/node-gyp#363 (comment) but after renaming Next I decided to completely remove
Then clear out the old
Finally reinstall:
And now... well everything seems to work. However I do still get that permission denied issue with I'm still not clear on what the problem was. I assume it was some out of date node module or something that got updated to the right version when I reinstalled |
|
@Jakobud hmm, that is weird. I'm really not sure why on earth the missing I'm glad you got it back working, though! |
|
@rex, actually that is another issue. On installation, it should use the prebuild binaries. However, in case the binary is flawed, then as a fallback the rebuild script is kicked in. Which means our binaries are flawed for certain architectures. For that matter we need to add some VMs to out build process and automate it. Lets track this issue further at #467. |
|
@am11 That sounds like a fantastic idea. Good luck! I'm not sure how much help I can be going forward but please don't hesitate to mention me if you'd like another set of eyes on an issue! |
|
Ugh, getting this error again but this time slightly different. Is this a node-sass issue or gyp issue? Doesn't seem to be any support from the gyp maintainer in their repo: |
|
It's a node-sass issue, I recommend going back to 1.0.3 until we can sort out the install issues |
|
@Jakobud Libsass now requires that the C++ complier support C++11 syntax. The line:
You can use the approach that we use for Travis to get a supported gcc version https://github.com/sass/node-sass/blob/master/.travis.yml#L10 I'm going to lock this issue since was spun off a previous release and there are newer build issue threads that should be used to track the issues @andrew I think the README probably needs to be updated to reflect the change. |
More Information at: sass/node-sass#428
# npm install node-sassResults in:
The text was updated successfully, but these errors were encountered: