node-sass@1.2.3 postinstall failing on Ubuntu 12.04.5 #550
Comments
|
If it helps at all, I got here because broccoli-sass@0.3.2 needs this as a dependency (obviously.) |
|
I've done a little poking at the build and it seems like line 181 in As an experiment i gave it execute perms but that didn't do anything. A |
|
Getting this error as well. Building on OSX 10.10.1 I feel like this just started recently. |
|
Yes I believe that it's due to the most recent build of binding.node . 2014-11-20 22:29 GMT-05:00 Aram Zadikian notifications@github.com:
|
|
I'm pretty sure this is the offending build: sass/node-sass-binaries@9d6417d |
|
Getting this error as well - OSX 10.9.4 |
|
For now I'm getting around it by specifying node-sass version 1.2.2 explicitly in my package .json file |
|
Interesting. I guess I'll try to force broccoli-sass compiler to use an On Fri Nov 21 2014 at 1:52:33 PM Ryan Darge notifications@github.com
|
|
Also getting this, also forcing 1.2.2 seems to yield better results |
|
Not getting this here but it's also not Ubuntu. Are any of you using your distros releases instead of building yourself? $ npm install node-sass
npm WARN package.json bootstrap-markdown@2.7.0 'repositories' (plural) Not supported. Please pick one as the 'repository' field
npm WARN package.json mu2@0.5.20 No repository field.
\
> node-sass@1.2.3 install /home/user/repo/git/oujs/martii/OpenUserJS.org/node_modules/node-sass
> node scripts/install.js
Binary downloaded and installed at /home/user/repo/git/oujs/martii/OpenUserJS.org/node_modules/node-sass/vendor/linux-x64/binding.node
> node-sass@1.2.3 postinstall /home/user/repo/git/oujs/martii/OpenUserJS.org/node_modules/node-sass
> node scripts/build.js
`linux-x64` exists; testing
Binary is fine; exiting
node-sass@1.2.3 node_modules/node-sass
├── get-stdin@3.0.0
├── object-assign@1.0.0
├── replace-ext@0.0.1
├── shelljs@0.3.0
├── nan@1.4.1
├── mkdirp@0.5.0 (minimist@0.0.8)
├── cross-spawn@0.2.3 (lru-cache@2.5.0)
├── chalk@0.5.1 (escape-string-regexp@1.0.2, ansi-styles@1.1.0, supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
├── gaze@0.5.1 (globule@0.1.0)
├── mocha@2.0.1 (escape-string-regexp@1.0.2, diff@1.0.8, growl@1.8.1, commander@2.3.0, jade@0.26.3, glob@3.2.3, debug@2.0.0)
└── meow@2.0.0 (minimist@1.1.0, camelcase-keys@1.0.0, indent-string@1.2.0)
$ node -v
v0.10.32
$ npm --version
2.1.8
Current Ubuntu is mentioned to be Ubuntu 14.04.1 LTS. I can try building this on a spare machine if it helps anyone to debug. |
|
webpack sass-loader brought me here. |
|
Here's some results: Ubuntu 14.04.1 LTS $ node -v
v0.10.34-pre
$ npm -v
1.4.28
$ npm install node-sass
/
> node-sass@1.2.3 install /home/user/node_modules/node-sass
> node scripts/install.js
Binary downloaded and installed at /home/user/node_modules/node-sass/vendor/linux-x64/binding.node
> node-sass@1.2.3 postinstall /home/user/node_modules/node-sass
> node scripts/build.js
`linux-x64` exists; testing
Binary is fine; exiting
node-sass@1.2.3 ../node_modules/node-sass
├── get-stdin@3.0.2
├── object-assign@1.0.0
├── replace-ext@0.0.1
├── cross-spawn@0.2.3 (lru-cache@2.5.0)
├── mkdirp@0.5.0 (minimist@0.0.8)
├── shelljs@0.3.0
├── nan@1.4.1
├── chalk@0.5.1 (escape-string-regexp@1.0.2, ansi-styles@1.1.0, supports-color@0.2.0, has-ansi@0.1.0, strip-ansi@0.3.0)
├── meow@2.0.0 (minimist@1.1.0, camelcase-keys@1.0.0, indent-string@1.2.0)
├── gaze@0.5.1 (globule@0.1.0)
├── mocha@2.0.1 (escape-string-regexp@1.0.2, diff@1.0.8, growl@1.8.1, commander@2.3.0, glob@3.2.3, debug@2.0.0, jade@0.26.3)
└── request@2.48.0 (caseless@0.7.0, json-stringify-safe@5.0.0, aws-sign2@0.5.0, forever-agent@0.5.2, stringstream@0.0.4, oauth-sign@0.5.0, tunnel-agent@0.4.0, node-uuid@1.4.1, qs@2.3.3, mime-types@1.0.2, combined-stream@0.0.7, form-data@0.1.4, bl@0.9.3, tough-cookie@0.12.1, http-signature@0.10.0, hawk@1.1.1) |
|
Same here with a fresh install on Mac OS 10.9.4: Edit: |
|
I also was able to fix the problem by switching from node 0.11.x to 0.10.x. |
|
Yes I think it's been well shown that the binary breaks when required by node v0.11.x which is in development. This means that you should definitely be using 0.10.x in production :) (That said, I think it's reasonable to try to make node modules work with the current development branch of node or to document when it's known to break. Which of course means building version specific tests. The amount of references to this issue seems to show how many people are using bleeding edge versions of v8/node to develop with.) |
|
👍 As others have mentioned, I've only experienced this issue on node v0.11. |
|
I'm explicitly depending on node-sass 1.2.2 and am on node v0.10.33 and am still experiencing this issue on Heroku. |
|
Same on OS X 10.10.1, Node 0.11.14, npm 2.1.11. On Node 0.10.33 everything works fine, probably because it's pre-built. |
|
Same issue here on Windows 7-64, Node 0.11.9, npm 2.1.11. Running it with koa so can't migrate back down to node 1.10 :( Is there a current work-around or force-install that works? |
|
Same issue with ubuntu 14.04, npm 2.1.1. |
|
Same issue with node |
|
Fails on Travis CI with |
|
@enzy same issue. +1 |
|
We do not support njs nightly v0.11.* at this point, but only the stable one v0.10.33. From the solution perspective, this is same issue as #517. Lets follow it there. |
|
Getting this issue with Node 0.12 now. Any ideas how to solve this for node v0.12. |
|
Same. |
|
@briandela @kevinSuttle see #653. |
|
On Yosemite, node 0.12.0. Just resorted to this. See section 3b of the accepted answer in order to downgrade node to 0.10.33. |
|
Latest 0.10.x is 0.10.36 btw |
|
Guys lets not discuss scattered/random matters under closed issues. The related issue is opened here: #655 If you are facing particular issue, search the issue tracker for the opened ones first, if not found open a new one. @Martii, and 0.10.36 is supported by v2.0.0-beta. @mcgwiz, see the comments at #653. You can build the binary for Mac for both io.js and node.js v0.12. |
|
Would be nice if GH would mirror the |
|
@Martii, you can send feedback to GH team, they are very receptive (i.e. at the minimum, they reply to every email sooner or later). |
|
I'm seeing When node-sass version is 1.2.3 and Node.js version is 0.12.0. Update: problem solved by upgrading node-sass from 1.2.3 to 2.0.1. |
|
1.2.3 does not support node 0.12. Upgrade to 2.0.1 for for 0.12 support.
|
|
Still having this issue on OSX 10.10: Had to roll back to 1.2.2. |
|
I also had this version running node 0.11.13, Ubuntu 14.04. It's used as a dependency for gulp-sass so I can't change the version. I can confirm that using node 0.10.29 makes the error go away (but then I feel icky) |
|
Node 0.11 is simply unsupported. This will not change. Updating to 0.12
|
Output leading zeros on numbers as seen in input (Fixes sass#550)
----- It is inappropriate to include political and offensive content in public code repositories. Public code repositories should be neutral spaces for collaboration and community, free from personal or political views that could alienate or discriminate against others. Political content, especially that which targets or disparages minority groups, can be harmful and divisive. It can make people feel unwelcome and unsafe, and it can create a hostile work environment. Please refrain from adding such content to public code repositories.
and others
The following is the relevant section of the failure:
I've googled all over the place, but it seems as though this is a test failure and not anything to do with the actual build failing.
The text was updated successfully, but these errors were encountered: