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

Created on 3 Nov 2018  ·  21Comments  ·  Source: sass/node-sass

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?

External - Node Invalid - Old Node-Sass
Source
picture stoplion
👍7 ❤1

Most helpful comment

npm rebuild node-sass

No force flag

On Sat., 3 Nov. 2018, 12:45 pm George C. Norris <[email protected]
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
.

picture xzyfer on 3 Nov 2018
👍167 ❤33 👎32 🎉13 😄11 🚀10 👀2

All 21 comments

npm rebuild node-sass

No force flag

On Sat., 3 Nov. 2018, 12:45 pm George C. Norris <[email protected]
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
.

xzyfer picture xzyfer on 3 Nov 2018
👍167 ❤33 👎32 🎉13 😄11 🚀10 👀2

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.

nschonni picture nschonni on 3 Nov 2018
👍2

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
rugaard picture rugaard on 5 Nov 2018

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

george-norris-salesforce picture george-norris-salesforce on 5 Nov 2018

What version of node-sass?

npm ls node-sass

On Tue., 6 Nov. 2018, 5:55 am George Norris <[email protected] wrote:

I've switched from N to NVM. Still getting this error. 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.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2536#issuecomment-435991773,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWHJGcAQEB4KSuIm2xQCQJrpfZlP7ks5usImfgaJpZM4YMlHa
.

xzyfer picture xzyfer on 5 Nov 2018

My CI is failing for the same reason... not sure what to do.

> [email protected] install /home/circleci/repo/node_modules/node-sass
> node scripts/install.js

internal/modules/cjs/loader.js:582
    throw err;
    ^

Error: Cannot find module 'process-nextick-args'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:580:15)
    at Function.Module._load (internal/modules/cjs/loader.js:506:25)
    at Module.require (internal/modules/cjs/loader.js:636:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (/home/circleci/repo/node_modules/are-we-there-yet/node_modules/readable-stream/lib/_stream_readable.js:26:11)
    at Module._compile (internal/modules/cjs/loader.js:688:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
    at Module.load (internal/modules/cjs/loader.js:598:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
    at Function.Module._load (internal/modules/cjs/loader.js:529:3)
npm WARN [email protected] No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `node scripts/install.js`
npm ERR! Exit status 1
rmariuzzo picture rmariuzzo on 10 Nov 2018

This is an npm or ci issue. Nothing new can do.

On Sun., 11 Nov. 2018, 1:36 am Rubens Mariuzzo <[email protected]
wrote:

My CI is failing for the same reason... not sure what to do.

[email protected] install /home/circleci/repo/node_modules/node-sass
node scripts/install.js

internal/modules/cjs/loader.js:582
throw err;
^

Error: Cannot find module 'process-nextick-args'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:580:15)
at Function.Module._load (internal/modules/cjs/loader.js:506:25)
at Module.require (internal/modules/cjs/loader.js:636:17)
at require (internal/modules/cjs/helpers.js:20:18)
at Object. (/home/circleci/repo/node_modules/are-we-there-yet/node_modules/readable-stream/lib/_stream_readable.js:26:11)
at Module._compile (internal/modules/cjs/loader.js:688:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
at Module.load (internal/modules/cjs/loader.js:598:32)
at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
at Function.Module._load (internal/modules/cjs/loader.js:529:3)
npm WARN [email protected] No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: node scripts/install.js
npm ERR! Exit status 1

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2536#issuecomment-437588166,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWFPrwaEBiem0pUaTkHEqYqDpqX6Oks5utuRtgaJpZM4YMlHa
.

xzyfer picture xzyfer on 10 Nov 2018

@xzyfer what is the issue exactly, so I can find a workaround?

rmariuzzo picture rmariuzzo on 10 Nov 2018

I don't know know. I don't build npm or your ci.

xzyfer picture xzyfer on 10 Nov 2018

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
hyperknot picture hyperknot on 13 Nov 2018

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 <[email protected] 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
.

xzyfer picture xzyfer on 13 Nov 2018
❤2 👍2 👀1

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

rmariuzzo picture rmariuzzo on 13 Nov 2018

npm rebuild node-sass worked for me

deepikachalanaClover picture deepikachalanaClover on 10 Jun 2019
👍8 🚀1 ❤1

When can we get v10 support?

NathanParsonKoroso picture NathanParsonKoroso on 24 Jun 2019

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
.

xzyfer picture xzyfer on 24 Jun 2019
👍2

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

arhoy picture arhoy on 14 Jul 2019

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
bkarlson picture bkarlson on 28 Aug 2019
❤2

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

will3bg picture will3bg on 11 Sep 2019

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

MayankFB picture MayankFB on 19 Sep 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

Davy-F picture Davy-F on 30 Sep 2019

I was facing the same issue.
It is because [email protected] 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

w3debugger picture w3debugger on 20 Oct 2019
Was this page helpful?
0 / 5 - 0 ratings

Related issues

mkbctrl picture mkbctrl  ·  4Comments
bgolubovic picture bgolubovic  ·  3Comments
amarbham picture amarbham  ·  3Comments
NathanKleekamp picture NathanKleekamp  ·  4Comments
pulkitnandan picture pulkitnandan  ·  4Comments