Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing binding win32-x64-48 #1645

Closed
antho227 opened this issue Jul 29, 2016 · 9 comments
Closed

Missing binding win32-x64-48 #1645

antho227 opened this issue Jul 29, 2016 · 9 comments

Comments

@antho227
Copy link

antho227 commented Jul 29, 2016

I get an error after upgrading NodeJS :

Issue :

Error: Missing binding C:\aglqng\src\main\webapp\node_modules\node-sass\vendor\win32-x64-48\binding.node
Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 6.x

Found bindings for the following environments:
  - Windows 64-bit with Node 0.12.x

This usually happens because your environment has changed since running `npm install`.
Run `npm rebuild node-sass` to build the binding for your current environment.
    at Object.<anonymous> (C:\aglqng\src\main\webapp\node_modules\node-sass\lib\index.js:15:11)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\aglqng\src\main\webapp\node_modules\gulp-sass\index.js:187:21)
    at Module._compile (module.js:541:32)

Versions :

node-sass 3.8.0 (Wrapper) [JavaScript]
libsass 3.3.6 (Sass Compiler) [C/C++]
nodejs v6.3.1

Platform : Windows 10 - x64

@xzyfer
Copy link
Contributor

xzyfer commented Jul 31, 2016

Did you try running npm rebuild node-sass as the error message suggests?

On 29 Jul 2016 4:42 PM, "Anthony Cluse" notifications@github.com wrote:

I get an error after upgrading NodeJS :

Issue :

`Error: Missing binding
C:\aglqng\src\main\webapp\node_modules\node-sass\vendor\win32-x64-48\binding.node
Node Sass could not find a binding for your current environment: Windows
64-bit with Node.js 6.x

Found bindings for the following environments:

  • Windows 64-bit with Node 0.12.x

This usually happens because your environment has changed since running npm
install.
Run npm rebuild node-sass to build the binding for your current
environment.
at Object.
(C:\aglqng\src\main\webapp\node_modules\node-sass\lib\index.js:15:11)
at Module._compile (module.js:541:32)
at Object.Module._extensions..js (module.js:550:10)
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at Object.
(C:\aglqng\src\main\webapp\node_modules\gulp-sass\index.js:187:21)
at Module._compile (module.js:541:32)`

Versions :

node-sass 3.8.0 (Wrapper) [JavaScript]
libsass 3.3.6 (Sass Compiler) [C/C++]
nodejs v6.3.1

Platform : Window 10 - x64


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1645, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWDpl0YluCoZ6JK6iXcd8C2tCL1ziks5qaaDMgaJpZM4JX6wG
.

@xzyfer
Copy link
Contributor

xzyfer commented Sep 4, 2016

This usually happens because your environment has changed since running npm install.
Run npm rebuild node-sass to build the binding for your current environment.

The error message is pretty clear on how to resolve this issue. Not sure what you're expecting from this issue.

@xzyfer xzyfer closed this as completed Sep 4, 2016
@iberodev
Copy link

I have the same issue and running npm rebuild node-sass does not fix the problem.
I have even reinstalled NodeJs to latest v4.5.0 but I keep getting:

[22:43:46] Error: Missing binding D:\dev\speEDI\SpeediCargo\src\Speedi.Cargo.Web\node_modules\gulp-sass\node_modules\node-sass\vendor\win32-ia32-47\binding.node
Node Sass could not find a binding for your current environment: Windows 32-bit with Node.js 5.x
Found bindings for the following environments:
  - Windows 64-bit with Node.js 4.x
This usually happens because your environment has changed since running `npm install`.
Run `npm rebuild node-sass` to build the binding for your current environment.
    at Object.<anonymous> (D:\dev\speEDI\SpeediCargo\src\Speedi.Cargo.Web\node_modules\gulp-sass\node_modules\node-sass\lib\index.js:15:11)
    at Module._compile (module.js:397:26)
    at Object.Module._extensions..js (module.js:404:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (D:\dev\speEDI\SpeediCargo\src\Speedi.Cargo.Web\node_modules\gulp-sass\index.js:187:21)
    at Module._compile (module.js:397:26)
    at Object.Module._extensions..js (module.js:404:10)

npm install does not fix the problem.

"D:\dev\speEDI\SpeediCargo\src\Speedi.Cargo.Web\node_modules\gulp-sass\node_modules\node-sass\vendor\win32-x64-46\binding.node" exists.
 testing binary.
Binary is fine; exiting.

Deleting node_modules and npm install again does not resolve the problem either.

Any idea?

@iberodev
Copy link

I found that the problem seems to be with Visual Studio (where I was running my gulp task).
For some reason it seems my Visual Studio was using a different version of node.
I just configured Visual Studio external web tools to look for my nodejs path first so that I'm sure it runs the version I think it has to run. I followed these instructions It's all good

@dcinadr
Copy link

dcinadr commented Jan 28, 2017

Thank you iberodev! This was the ticket for me.

@phannphong
Copy link

phannphong commented May 14, 2017

Thank @xzyfer
npm rebuild node-sass fix my issue.

@ghost
Copy link

ghost commented Jul 7, 2017

This is what happened to me: having multiple nodejs versions, even if I overriden the PATH environment variable in the CMD file before running grunt, for some reason sass it seems it was still be influenced by the system level PATH, looking at a newer version of node. So then sass was searching for the binding version 48 (new node, I suppose, v6.11.0), instead of 47 (old node, v5.6.0)
I had to revert the system level environment variable PATH, pointing back to the old version of node.

If you still have issues, remember to clean your project specific 'node_modules' directories, and 'npm' 'npm-cache' directories, in %APPDATA%

@thephw
Copy link

thephw commented Oct 3, 2017

VisualStudio 2017 fix instructions:

  1. Ensure you have a modern version of Node/NPM installed
  2. Add the modern version of Node to your external tools path (Tools|Options...Projects and Solutions | Web Package Management | External Web Toolsscreen shot 2017-10-03 at 12 40 58 pmscreen shot 2017-10-03 at 12 41 16 pm
  3. Restore npm packagesscreen shot 2017-10-03 at 12 44 19 pm
  4. Rebuild node-sass
cd <ProjectRoot>
npm rebuild node-sass
  1. Build your project as normal and voila! node-sass works again.

@joel1618
Copy link

npm doesn't seem to download the binding.node file automatically. you can download it from https://github.com/sass/node-sass/releases and put it in your project file at node_modules\node-sass\vendor\win32-x64-57 directly. This is what fixed it for me.

@sass sass locked as resolved and limited conversation to collaborators Jun 27, 2018
jiongle1 pushed a commit to scantist-ossops-m2/node-sass that referenced this issue Apr 7, 2024
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

7 participants