node-sass package is incompatible with latest version of node

[olefredrik]

When using the latest stable version of node (v0.12.0), the npm install && bower install will fail. I get the following error message

npm ERR! Darwin 14.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE

npm ERR! [email protected] postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] postinstall script 'node scripts/build.js'.
npm ERR! This is most likely a problem with the node-sass package,

A temporary solution (that works) is to switch back to node version 0.10.33.

I'm using the libsass version of Foundation in my FoundationPress repository. More info in this thread olefredrik/FoundationPress#209. I'm looking for a better and more elegant solution. If you should get this to work with node v.0.12.0, feel free to share your insights :)

[GriffRocks]

Thank you @olefredrik this works perfectly with Foundation libsass.

[jochenstu]

Just wanted to chime in. Took me a few frustrating hours of trial and error before I stumbled upon your post and was able to fix it. Thanks!

[victorleungtw]

Thanks @olefredrik! I got the same issue as well. Just a quick note on switching back to version 0.10:

1. Install nvm: curl https://raw.githubusercontent.com/creationix/nvm/v0.23.3/install.sh | bash
2. nvm install 0.10
3. nvm use 0.10
   fyi - https://github.com/creationix/nvm

[randmanrjr]

I put in a pull request on this repository to update the package.json to require node-sass v.2.0.1 and grunt-sass v.0.18.0.

As a work around, if you want to use node v.0.12.0

After an aborted install of foundation 5 with the cli using the -libsas flag:

If you edit the package.json and change these above two dependecies, then run npm update, grunt will build and everything will work with node v.0.12.0. It's also backwords compatible with node v0.10.33.

However if you run foundation update, it will break it again, as it will pull the old package.json from the repo.

I also forked the repo here and updated the package.json file:

https://github.com/randmanrjr/foundation-libsass-template

You can edit the foundation gem on your system to clone this repo instead of the zurb one until they get this issue fixed.

[dregini]

hi,
im newbie in web development, and i never used before node or scss, i tried to get foundation-press up and running without success... i keep getting the same error:
(i suppose is npm install)

npm ERR! [email protected] postinstall: node scripts/build.js
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the [email protected] postinstall 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 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! System Linux 2.6.32-504.8.1.el6.x86_64
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! cwd /var/www/html/wordpress/wp-content/themes/foundationpress
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR! not ok code 0

I'm using centos as SO, initially I installed node 0.10.36 (with yum) and overwritten with the 0.10.33 that i've obtained with n.

Do you have any suggestion? or idea in what I'm doing wrong??

Sorry for my english (it's not my language)

edit

i tried with this branch libsass-template and now i get

file to import not found or unreadable: settings

Current dir: /var/www/html/wordpress/wp-content/themes/libssasfoundation/scss/
Line 1 Column 9 scss/app.scss
Warning: Use --force to continue.
Aborted due to warnings.

[randmanrjr]

Hi,

try editing the package.json file and changing the following dependencies to the versions listed below:

“node-sass” : “~2.0.1”
“grunt-sass” : “~0.18.0”

then run npm update.

That is was worked for me.

Good luck.

On Mar 2, 2015, at 6:43 AM, dregini [email protected] wrote:

hi,
im newbie in web development, and i never used before node or scss, i tried to get foundation-press up and running without success... i keep getting the same error:

(i suppose is npm install)

npm ERR! [email protected] postinstall: node scripts/build.js
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the [email protected] postinstall 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 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! System Linux 2.6.32-504.8.1.el6.x86_64
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! cwd /var/www/html/wordpress/wp-content/themes/foundationpress
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE

npm ERR! not ok code 0

I'm using centos as SO, initially I installed node 0.10.36 (with yum) and overwritten with the 0.10.33 that i've obtained with n.

Do you have any suggestion? or idea in what I'm doing wrong??

Sorry for my english (it's not my language)

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

[dregini]

worked!!! thank you!!
you save my day :D

now i just have to understand why wordpress do not load the theme in the appearance manager...

[randmanrjr]

Make sure that you’ve uploaded the theme files to the correct directory in your wordpress install:

./wp-content/themes/FoundationPress

You may need to create the FoundationPress folder and then upload the theme via FTP.

On Mar 2, 2015, at 8:58 AM, dregini [email protected] wrote:

worked!!! thank you!!
you save my day :D

now i just have to understand why wordpress do not load the theme in the appearance manager...

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

[dregini]

solved the folder owner was me and not apache, changed that and everything was fine

Thanks again!

[nsberrow]

My issue was that the scss syntax had an error, exclude your scss files and then re-include them one by one.

[rtm3001]

In response to this thread, I changed version to 0.10. But still getting the error. Could you let me know what I can do to remedy this?

Ryans-MacBook-Pro-2:~ rmc8001$ source /.bashrc
Ryans-MacBook-Pro-2: rmc8001$ nvm use 0.10
Now using node v0.10.40 (npm v1.4.28)
Ryans-MacBook-Pro-2:~ rmc8001$ npm start
npm ERR! Error: ENOENT, open '/Users/rmc8001/package.json'
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! https://github.com/npm/npm/issues
npm ERR! System Darwin 14.3.0
npm ERR! command "/Users/rmc8001/.nvm/v0.10.40/bin/node" "/Users/rmc8001/.nvm/v0.10.40/bin/npm" "start"
npm ERR! cwd /Users/rmc8001
npm ERR! node -v v0.10.40
npm ERR! npm -v 1.4.28
npm ERR! path /Users/rmc8001/package.json
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/rmc8001/npm-debug.log
npm ERR! not ok code 0