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

npm rebuild node-sass

No force flag

On Sat., 3 Nov. 2018, 12:45 pm George C. Norris <notifications@github.com 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 https://github.com/sass/node-sass/issues/2536, or mute the thread https://github.com/notifications/unsubscribe-auth/AAjZWNx2xKdieufnKhPU5QR77MMatMzWks5urPU0gaJpZM4YMlHa .

npm rebuild node-sass worked for me

Please read the documentation. It clearly states that 4.8.4 doesn’t support node 10.

https://github.com/sass/node-sass/releases/tag/v4.8.3

On Wed., 14 Nov. 2018, 2:55 am Zsolt Ero <notifications@github.com wrote:

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

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/sass/node-sass/issues/2536#issuecomment-438317838, or mute the thread https://github.com/notifications/unsubscribe-auth/AAjZWI7ZHoPKAPhzpG-HwSEcTOohPmaPks5uuutvgaJpZM4YMlHa .

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

Node 10 has been supported for over a year. Update to a newer version of node-sass.

On Tue., 25 Jun. 2019, 3:39 am NathanParsonKoroso, notifications@github.com wrote:

When can we get v10 support?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sass/node-sass/issues/2536?email_source=notifications&email_token=AAENSWG6OYVLWKRA6NKUBJDP4EBFLA5CNFSM4GBSKHNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYNVRSY#issuecomment-505108683, or mute the thread https://github.com/notifications/unsubscribe-auth/AAENSWFLGB6HJD37ZRMD7ELP4EBFLANCNFSM4GBSKHNA .

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.