Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 10.x #2536

Closed
stoplion opened this issue Nov 3, 2018 · 21 comments
Closed

Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 10.x #2536

stoplion opened this issue Nov 3, 2018 · 21 comments
Labels
External - Node Invalid - Old Node-Sass

Comments

@stoplion
Copy link

stoplion commented Nov 3, 2018 •
edited
Loading

Using n to switch Node versions. Ran npm rebuild node-sass --force many many times.

Getting this error:
Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 10.x

This usually happens because your environment has changed since running npm install.
Run npm rebuild node-sass --force to build the binding for your current environment.
Anyone have any idea how to fix?

Also.. When running this command..

npm rebuild node-sass --force
I get..

npm WARN using --force I sure hope you know what you are doing.
Doens't seem like it is doing anything..

I've tried to delete node_modules and clean the cache. The error keeps happening over and over again.

https://stackoverflow.com/questions/53125291/build-fails-npm-rebuild-node-sass-force?noredirect=1#comment93145585_53125291

Is there a way to fix this?
@xzyfer
Copy link
Contributor

xzyfer commented Nov 3, 2018 via email

@nschonni
Copy link
Contributor

nschonni commented Nov 3, 2018

I'm not sure if n plays nice with native addons, but I haven't used it myself. When the build is called it is spawning out the process and is likely picking up a local Node install. If you look inside the vendor folder and look at the number in the binding.node name it will tell you what version of node that is being picked up.

@rugaard
Copy link

rugaard commented Nov 5, 2018 •
edited
Loading

I'm constantly getting this error, even after I've tried npm rebuild node-sass with and without the
--force flag.

It started out of the blue last thursday (01-11-2018). I'm not even using Node 10, so I don't understand why it's trying to use that?

❯ node -v
v8.12.0

❯ npm -v
6.4.1

@george-norris-salesforce
Copy link

george-norris-salesforce commented Nov 5, 2018 •
edited
Loading

I've switched from N to NVM. Still getting this error.

Rebuilt Node-Sass many times. Cleaned the cache.

Totally stuck on this.

Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 10.x

Found bindings for the following environments:
  - OS X 64-bit with Node.js 10.x

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

https://stackoverflow.com/questions/53125291/build-fails-npm-rebuild-node-sass-force

@xzyfer
Copy link
Contributor

xzyfer commented Nov 5, 2018 via email

@rmariuzzo

This comment has been minimized.

Sign in to view
@xzyfer

This comment has been minimized.

Sign in to view
@rmariuzzo

This comment has been minimized.

Sign in to view
@xzyfer

This comment has been minimized.

Sign in to view
@xzyfer xzyfer closed this as completed Nov 10, 2018
@xzyfer xzyfer reopened this Nov 10, 2018
@tomap tomap mentioned this issue Nov 12, 2018
Closed
@hyperknot
Copy link

Yarn also has errors under 10.x, but it's a different one.

verbose 27.889 Downloading binary from https://github.com/sass/node-sass/releases/download/v4.8.3/darwin-x64-64_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.8.3/darwin-x64-64_binding.node":

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
      try setting a proxy via HTTP_PROXY, e.g.

      export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

@xzyfer xzyfer closed this as completed Nov 13, 2018
@xzyfer
Copy link
Contributor

xzyfer commented Nov 13, 2018 via email

@rmariuzzo
Copy link

@xzyfer thank you. Yesterday, I update to v4.10.0 and now it works well with Node 10.

@Nixon-Joseph Nixon-Joseph mentioned this issue Jan 31, 2019
Closed
@chenbin92 chenbin92 mentioned this issue Mar 28, 2019
Closed
@deepikachalanaClover
Copy link

npm rebuild node-sass worked for me

@NathanParsonKoroso
Copy link

When can we get v10 support?

@xzyfer
Copy link
Contributor

xzyfer commented Jun 24, 2019 via email

@arhoy
Copy link

arhoy commented Jul 14, 2019

I got this error when I inadvertently installed node v10, and did not notice it was sitting in my package.json file. In my case deleting your node_modules folder did not do anything and neither did npm rebuild node-sass

@devCrossNet devCrossNet mentioned this issue Jul 31, 2019
Closed
@bkarlson
Copy link

bkarlson commented Aug 28, 2019 •
edited
Loading

in my case I had global node-sass v 4.11, incompatible with Node v12

Removed and upgraded to v.4.12:

npm -g uninstall node-sass
npm -g i node-sass

@will3bg
Copy link

will3bg commented Sep 11, 2019

I get this error when using Platformio Ide terminal on Atom in Windows 10. Using ubuntu terminal helped me get past this problem

@MayankFB
Copy link

npm rebuild node-sass No force flag
…
On Sat., 3 Nov. 2018, 12:45 pm George C. Norris @.*** wrote: Using n to switch Node versions. Ran npm rebuild node-sass --force many many times. Getting this error: Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 10.x This usually happens because your environment has changed since running npm install. Run npm rebuild node-sass --force to build the binding for your current environment. Anyone have any idea how to fix? Also.. When running this command.. npm rebuild node-sass --force I get.. npm WARN using --force I sure hope you know what you are doing. Doens't seem like it is doing anything.. I've tried to delete node_modules and clean the cache. The error keeps happening over and over again. https://stackoverflow.com/questions/53125291/build-fails-npm-rebuild-node-sass-force?noredirect=1#comment93145585_53125291 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2536>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAjZWNx2xKdieufnKhPU5QR77MMatMzWks5urPU0gaJpZM4YMlHa .

this works

@kozr kozr mentioned this issue Sep 29, 2019
Merged
@Davy-F
Copy link

Davy-F commented Sep 30, 2019

I'm constantly getting this error, even after I've tried npm rebuild node-sass with and without the
--force flag.

It started out of the blue last thursday (01-11-2018). I'm not even using Node 10, so I don't understand why it's trying to use that?

❯ node -v
v8.12.0

❯ npm -v
6.4.1

Exactly the same. Tried every possible 'solution' to no luck

@w3debugger
Copy link

I was facing the same issue.
It is because node-sass@4.12.0 is NOT compatible with Node v9.11.2
It is working fine when I switched to Node v10.16.0 by using nvm use 10

@sass sass locked as resolved and limited conversation to collaborators Oct 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
External - Node Invalid - Old Node-Sass
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests