-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Error: Missing binding #1527
Comments
The Atom shell isn't supported, see #1047 |
Correct atom shell is not supported. However this warning is about a missing binary. I don't know how this error could be any more clear. Problem
Hint
ExplanationYou previously install node-sass using Node.js. You're now on Node.js 5.
Steps to solve problem
|
@xzyfer @nschonni By not supported do you mean doesn't compile the correct binding into If I manually download the correct binding, which happens to be darwin-x64-47 in my case and put it into So from digging around in #1047 and other issues I tried multiple suggested approaches to work around this…
I'm guessing this is because my system Node ( All my past use of libsass has been via Would electron-rebuild be a solution to this? |
I want to preface what I'm about to say with noting that noone on the Node Sass team is particularly experienced with the atom shell.
Atom uses it's own (possibly forked) version of Node. Even if you have the correct binding for the reported Node version I believe with error. I can't confirm this but I have anecdotal evidence from previous issue threads. It seems you may be misunderstanding how the atom shells works. Node 5 (47) is your local version, however atom has it's own embedded Node 0.10 (11). This is why Atom plugins work in background, inside a special atom Node environment so it will install in a way that works for that environment. I can't imagine a circumstance under which you would need to interact with node-sass directly. It sounds like you're doing something not quite right with regards to the plugin. I open a discussion with the plugin authors to discuss what it is you're trying to do. |
I have the same issue in my ember.js project. I end up install different node version then this error gone. The For example: |
@szlike that's fine. Everytime you change your node version just run |
I am the plugin author… 😄 |
Found the solution. For my case, I was using both Meteor (requires Node 0.10.x) while React-Native (requires Node.js 6.x which is installed). And I was using brew to install Node. So followed the advise to use nvm to install older version of Node:
Switch node back to version 6 using Nutshell, install the lower version and switch it back to latest version.
|
I had the same problem and I had to terminals open to the same directory. I did ran Stupid mistake and I wasted 30 mins trying to fix it. Hope this helps someone. SolutionReload your terminal or run |
All appears to go well. However:
Uninstalling and re-installing Any thoughts about what could be wrong? Thanks, |
@controversial your "gulp" command and your "npm" command seem to refer to different node engines you have installed. "npm" uses 0.10 (is this a debian-like system with node 0.10 installed as "nodejs" - you didn't say?) while gulp uses something newer. Maybe you have both "nodejs" and "node". |
I'll check when I get a chance and report back. On Sun, Sep 11, 2016 at 6:33 PM Marcin Cieślak notifications@github.com
|
|
I have the same probem, and with
this work ok! tkx |
If is still not working, you can add manually the file : https://github.com/sass/node-sass/releases/tag/v4.2.0. This is what I did finally. |
OS X 10.11.4
Atom 1.7.3
Node v6.0.0
source-preview v0.5.0
I'm getting the following error with my Atom package source-preview-sass:
I was hoping that updating my
node-sass
dependency to^3.7.0
would fix this but it didn't 😞Possibly related to #1504 and #1515?
The text was updated successfully, but these errors were encountered: