Skip to content
This repository has been archived by the owner on Sep 16, 2019. It is now read-only.

Failed at [email protected] #231

Closed
korndev opened this issue Feb 18, 2015 · 7 comments
Closed

Failed at [email protected] #231

korndev opened this issue Feb 18, 2015 · 7 comments

Comments

@korndev
Copy link

korndev commented Feb 18, 2015

Hey there,

Been using FoundationPress on a few projects with no issue, but today, tried to setup a new project and getting an error with attempting to install node-sass. Here is the error:

npm ERR! Darwin 14.1.0
npm ERR! argv "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,
npm ERR! not with npm itself.

I attempted to update the package.json to use sass 2.0.1 and the install works, however, the grunt build fails with:

Running "sass:dist" (sass) task
Fatal error: undefined is not a function

Running on OSX Yosemite, incase it matters.

Thanks for sharing FoundationPress with github. Been an awesome tool to use with WordPress to harness Foundation.

UPDATE: I've read that node-sass 1.2.3 is not compatible with node 0.12.0. I tried to roll back to node 0.11.9, but seem to get the same error:

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.

npm ERR! System Darwin 14.1.0
npm ERR! command "node" "/usr/local/bin/npm" "install"
npm ERR! cwd /Users/justin/Documents/Development/jobseekers/wp-content/themes/FoundationPress
npm ERR! node -v v0.11.9
npm ERR! npm -v 1.3.15
npm ERR! code ELIFECYCLE

@joshsmith01
Copy link
Contributor

We all just went through this.
Try the answers here. #208

@korndev
Copy link
Author

korndev commented Feb 18, 2015

Thanks, Josh. Sorry I missed that previous ticket. Just be clear, looks like you need node 0.10.33. Installing 0.10.33 fixed the issue for me.

@korndev korndev closed this as completed Feb 18, 2015
@joshsmith01
Copy link
Contributor

Hmm, not sure. I just folowed Ole's directions in the post and everything works now.

@olefredrik
Copy link
Owner

Hi guys. It's not ideal that grunt-sass is incompatible with the latest stable version of the node. But currently we have a choice to roll back node to v. 0.10.33 (as described in #208) or ditch libsass and use the much slower ruby/compass alternative. I'll stick with grunt-sass/libsass and keep an extra eye on future updates. Glad you got it working :)

@trompx
Copy link

trompx commented Apr 1, 2015

Hi,

I have problems too. I tried the following versions :

  • nodejs : 0.12.2
  • node-sass : 2.1.1
  • grunt-sass : 0.18.0

This config works on my host machine (windows 8.1) but I get the following error on my ubuntu 14.04 VM :
"Error: libsass bindings not found. Try reinstalling node-sass?"

I manage to make this works on the ubuntu VM with the following versions :

  • nodejs : 0.10.35
  • node-sass : 2.0.0-beta
  • grunt-sass : 0.17.0

Hope this helps!

@nsberrow
Copy link

nsberrow commented Jul 3, 2015

It's not node or grunt, it's the scss code. Double check you haven't got an error there, drove me crazy but that's all it was, a syntax error.

@phillbooth
Copy link

you may have the wrong type of scss install try removing all gems installed and then re-installing node-sass as per http://foundation.zurb.com/docs/sass.html

sudo npm install -g bower grunt-cli

sudo gem install foundation

bundle;

npm i;

bower install;

then...

grunt build --force && grunt watch --force;

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants