node-sass: v3.7.0: Node Sass could not find a binding for your current environment: Linux 64-bit with Node.js 6.x
I looked through all related issues and could find one addressing this particular case. Please take a look at this build log:
https://codeship.com/projects/144193/builds/15493676
You will be able to find the following:
Node Sass could not find a binding for your current environment: Linux 64-bit with Node.js 6.x
[0]
[0] Found bindings for the following environments:
[0] - Linux 64-bit with Node.js 5.x
node 6.2.1
npm 3.9.3
node-sass 3.7.0
Am I missing something?
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 28 (5 by maintainers)
Commits related to this issue
- Revert "upgrading to node 6.2.1", since node-sass still or sass-loader causes build to fail on linux box this may be dependent on https://github.com/jtangelder/sass-loader/pull/236 or https://github.c... — committed to Restuta/rcn.io by Restuta 8 years ago
- Consolidate the Declaration and Propset AST nodes In order to fix #1585 we need to introduce the `Trace` node from Ruby Sass. This node interacts with propsets in an interesting way. Have two node to... — committed to scantist-ossops-m2/node-sass by xzyfer 8 years ago
- Implement the Trace node from Ruby Sass. The Trace node is a simple wrapper around the result of a mixin call and `@content`. It exists as a way to group the resulting properties as a block but maint... — committed to scantist-ossops-m2/node-sass by xzyfer 8 years ago
- Implement the Trace node from Ruby Sass. The Trace node is a simple wrapper around the result of a mixin call and `@content`. It exists as a way to group the resulting properties as a block but maint... — committed to scantist-ossops-m2/node-sass by xzyfer 8 years ago
- Implement the Trace node from Ruby Sass. The Trace node is a simple wrapper around the result of a mixin call and `@content`. It exists as a way to group the resulting properties as a block but maint... — committed to scantist-ossops-m2/node-sass by xzyfer 8 years ago
npm rebuild node-sassworked well for me. Thanks @xzyferAs the message says you ran npm install with node 5 and now you’re on node 6. The error message should have instructed you to run
npm rebuild node-sassOn 9 Jun 2016 4:25 PM, “Anton Vynogradenko” notifications@github.com wrote:It’s work fine for me:
@nschonni that makes sense, so probably
npm cache cleanwould do the trick then. Great hint, I appreciate that, thanks!TL;DR
Issue is resolved: do
npm cache cleanon your build servers.“npm rebuild node-sass” worked for me
@xzyfer That is not true. Regradless of the interpretation as you can see in that build log this:
CodeShip is a cloud-based build server, they run new environment for every build, so it’s impossible to run “npm install” with one node version and then “reuse” that on different build.
Please reopen.
npm rebuild node-sassworked well for me.Didnt work for me, but on the right path. Needed https://cl.ly/hFPb
You have caching enabled in CircleCI, but not Travis. It is likely that the cache package was created when your builds were running on Node 5, and you updated. Check the CI documentation on how to fix/clear you cache and you won’t have to rebuild.
For me, i was able to get around this problem by installing node-sass globally…
npm install node-sass -g
More context Circle CI also failed: https://circleci.com/gh/Restuta/rcn.io/174 Travis CI did not, which is a mystery why: https://travis-ci.org/Restuta/rcn.io/jobs/136540366
Also it doesn’t fail on my local (OSX). Manually adding
npm rebuild node-sassfixed builds on both CodeShip and Circle-CI. This means I don’t understand something about it and the process.Does it make sense to run
npm rebuild node-sassevery time afternpm install? Any drawbacks of doing that? @xzyfer