Menu icon Foundation
Errors with foundation new project_name --libsass

Hi, I'm trying to setup a work space for F5 using bower/grunt but I'm having trouble. I've completed the following actions on a brand new install of Yosemite 10.10.2.

Installed xcode 6.1.1 from the App store
Installed GIT 2.2.1
Installed node.js (I used the .pkg from the website, not Homebrew)
Checked that /usr/bin/local is in my path using "echo $PATH" (It is)

Ran "sudo npm install -g bower grunt-cli" in terminal, no errors
Ran "sudo gem install foundation" in terminal, output stated that '2 gems were installed', all seems well here.

Now when I try and create a new project, i get the below errors. I've recently moved over from a W7 platform so a lot of this is new to me. When I've tried to find solutions it's either gone straight over my head or I've tried and broken my install (see above, brand new install). Can anyone advise what I am doing wrong?

Any help greatly appreciated (especially if you dumb it down to my level)
Griff

ans-MBP:sites Griff$ foundation new projectTest01 --libsass
Creating ./projectTest01
      create  projectTest01
Cloning into 'projectTest01'...
remote: Counting objects: 165, done.
remote: Total 165 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (165/165), 233.35 KiB | 297.00 KiB/s, done.
Resolving deltas: 100% (58/58), done.
Checking connectivity... done.
Installing dependencies with bower...
bower jquery-placeholder#~2.0.7         mismatch Version declared in the json (2.0.8) is different than the resolved one (2.0.9)
bower modernizr#>= 2.7.2            invalid-meta modernizr is missing "main" entry in bower.json
bower modernizr#>= 2.7.2            invalid-meta modernizr is missing "ignore" entry in bower.json
         run  npm install from "./projectTest01"
npm WARN package.json [email protected] No repository field.
\
> [email protected] install /Users/Griff/Sites/projectTest01/node_modules/node-sass
> node scripts/install.js

Binary downloaded and installed at /Users/Griff/Sites/projectTest01/node_modules/node-sass/vendor/darwin-x64/binding.node

> [email protected] postinstall /Users/Griff/Sites/projectTest01/node_modules/node-sass
> node scripts/build.js

`darwin-x64` exists; testing
module.js:355
  Module._extensions[extension](this, filename);
                               ^
Error: Module did not self-register.
    at Error (native)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/Users/Griff/Sites/projectTest01/node_modules/node-sass/lib/index.js:181:15)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
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.
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!     /Users/Griff/Sites/projectTest01/npm-debug.log
         run  grunt build from "./projectTest01"
Loading "sass.js" tasks...ERROR
>> Error: Cannot find module 'node-sass'
Warning: Task "sass" not found. Use --force to continue.

Aborted due to warnings.
./projectTest01 was created
            

         

bowerGruntinstallnode-sass

Hi, I'm trying to setup a work space for F5 using bower/grunt but I'm having trouble. I've completed the following actions on a brand new install of Yosemite 10.10.2.

Installed xcode 6.1.1 from the App store
Installed GIT 2.2.1
Installed node.js (I used the .pkg from the website, not Homebrew)
Checked that /usr/bin/local is in my path using "echo $PATH" (It is)

Ran "sudo npm install -g bower grunt-cli" in terminal, no errors
Ran "sudo gem install foundation" in terminal, output stated that '2 gems were installed', all seems well here.

Now when I try and create a new project, i get the below errors. I've recently moved over from a W7 platform so a lot of this is new to me. When I've tried to find solutions it's either gone straight over my head or I've tried and broken my install (see above, brand new install). Can anyone advise what I am doing wrong?

Any help greatly appreciated (especially if you dumb it down to my level)
Griff

ans-MBP:sites Griff$ foundation new projectTest01 --libsass
Creating ./projectTest01
      create  projectTest01
Cloning into 'projectTest01'...
remote: Counting objects: 165, done.
remote: Total 165 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (165/165), 233.35 KiB | 297.00 KiB/s, done.
Resolving deltas: 100% (58/58), done.
Checking connectivity... done.
Installing dependencies with bower...
bower jquery-placeholder#~2.0.7         mismatch Version declared in the json (2.0.8) is different than the resolved one (2.0.9)
bower modernizr#>= 2.7.2            invalid-meta modernizr is missing "main" entry in bower.json
bower modernizr#>= 2.7.2            invalid-meta modernizr is missing "ignore" entry in bower.json
         run  npm install from "./projectTest01"
npm WARN package.json [email protected] No repository field.
\
> [email protected] install /Users/Griff/Sites/projectTest01/node_modules/node-sass
> node scripts/install.js

Binary downloaded and installed at /Users/Griff/Sites/projectTest01/node_modules/node-sass/vendor/darwin-x64/binding.node

> [email protected] postinstall /Users/Griff/Sites/projectTest01/node_modules/node-sass
> node scripts/build.js

`darwin-x64` exists; testing
module.js:355
  Module._extensions[extension](this, filename);
                               ^
Error: Module did not self-register.
    at Error (native)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/Users/Griff/Sites/projectTest01/node_modules/node-sass/lib/index.js:181:15)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
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.
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!     /Users/Griff/Sites/projectTest01/npm-debug.log
         run  grunt build from "./projectTest01"
Loading "sass.js" tasks...ERROR
>> Error: Cannot find module 'node-sass'
Warning: Task "sass" not found. Use --force to continue.

Aborted due to warnings.
./projectTest01 was created
            

         

This post has been closed. No new replies can be added.

Ian Griffiths almost 5 years ago

For anyone who stumbles across this, I found a fix.

It turns out that the latest version of node (v0.12.0) is causing the issue. I used an older version of node (v0.10.33) and now foundation with libsass is working again.

You can revert to the older version using the below commands:

NPM install -g n
n 0.10.33

Once this is done, "foundation new project_name --libsass" now works. For more details, see:

https://github.com/olefredrik/FoundationPress/issues/209

No doubt this issue will be fixed in time.