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

stoplion · 2018-11-03T01:45:23Z

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?

The text was updated successfully, but these errors were encountered:

xzyfer · 2018-11-03T03:43:17Z

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> .

nschonni · 2018-11-03T04:23:41Z

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 · 2018-11-05T12:02:31Z

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 · 2018-11-05T18:55:24Z

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 · 2018-11-05T20:50:22Z

What version of node-sass? npm ls node-sass

…

On Tue., 6 Nov. 2018, 5:55 am George Norris ***@***.*** 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 <#2536 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjZWHJGcAQEB4KSuIm2xQCQJrpfZlP7ks5usImfgaJpZM4YMlHa> .

hyperknot · 2018-11-13T15:55:26Z

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 · 2018-11-13T16:16:09Z

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 ***@***.*** 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 <#2536 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjZWI7ZHoPKAPhzpG-HwSEcTOohPmaPks5uuutvgaJpZM4YMlHa> .

rmariuzzo · 2018-11-13T17:25:05Z

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

deepikachalanaClover · 2019-06-10T06:05:43Z

npm rebuild node-sass worked for me

NathanParsonKoroso · 2019-06-24T17:39:31Z

When can we get v10 support?

xzyfer · 2019-06-24T19:06:27Z

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, ***@***.***> wrote: When can we get v10 support? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2536?email_source=notifications&email_token=AAENSWG6OYVLWKRA6NKUBJDP4EBFLA5CNFSM4GBSKHNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYNVRSY#issuecomment-505108683>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAENSWFLGB6HJD37ZRMD7ELP4EBFLANCNFSM4GBSKHNA> .

arhoy · 2019-07-14T06:47:59Z

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

bkarlson · 2019-08-28T06:58:06Z

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 · 2019-09-11T13:35:17Z

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

MayankFB · 2019-09-19T14:57:25Z

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

Davy-F · 2019-09-30T12:33:06Z

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 · 2019-10-20T18:11:22Z

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

This comment has been minimized.

Sign in to view

xzyfer closed this as completed Nov 10, 2018

xzyfer reopened this Nov 10, 2018

nschonni added the Awaiting Response label Nov 11, 2018

tomap mentioned this issue Nov 12, 2018

Hexo fails to install with Node 10.13.0 hexojs/hexo#3348

Closed

xzyfer closed this as completed Nov 13, 2018

Nixon-Joseph mentioned this issue Jan 31, 2019

Node Sass could not find a binding for your current environment #2588

Closed

chenbin92 mentioned this issue Mar 28, 2019

iceworks 2.18.0 功能 alibaba/ice#1695

Closed

devCrossNet mentioned this issue Jul 31, 2019

Dev-server returned status code: 500. vuesion/vuesion#423

Closed

saper added External - Node Invalid - Old Node-Sass and removed Awaiting Response labels Sep 8, 2019

kozr mentioned this issue Sep 29, 2019

dockerize lhd nwplus/LHD2020#45

Merged

sass locked as resolved and limited conversation to collaborators Oct 21, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

stoplion commented Nov 3, 2018 •

edited

Loading

xzyfer commented Nov 3, 2018 via email

nschonni commented Nov 3, 2018

rugaard commented Nov 5, 2018 •

edited

Loading

george-norris-salesforce commented Nov 5, 2018 •

edited

Loading

xzyfer commented Nov 5, 2018 via email

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

hyperknot commented Nov 13, 2018

xzyfer commented Nov 13, 2018 via email

rmariuzzo commented Nov 13, 2018

deepikachalanaClover commented Jun 10, 2019

NathanParsonKoroso commented Jun 24, 2019

xzyfer commented Jun 24, 2019 via email

arhoy commented Jul 14, 2019

bkarlson commented Aug 28, 2019 •

edited

Loading

will3bg commented Sep 11, 2019

MayankFB commented Sep 19, 2019

Davy-F commented Sep 30, 2019

w3debugger commented Oct 20, 2019

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

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

Comments

stoplion commented Nov 3, 2018 • edited Loading

xzyfer commented Nov 3, 2018 via email

nschonni commented Nov 3, 2018

rugaard commented Nov 5, 2018 • edited Loading

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

xzyfer commented Nov 5, 2018 via email

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

hyperknot commented Nov 13, 2018

xzyfer commented Nov 13, 2018 via email

rmariuzzo commented Nov 13, 2018

deepikachalanaClover commented Jun 10, 2019

NathanParsonKoroso commented Jun 24, 2019

xzyfer commented Jun 24, 2019 via email

arhoy commented Jul 14, 2019

bkarlson commented Aug 28, 2019 • edited Loading

will3bg commented Sep 11, 2019

MayankFB commented Sep 19, 2019

Davy-F commented Sep 30, 2019

w3debugger commented Oct 20, 2019

stoplion commented Nov 3, 2018 •

edited

Loading

rugaard commented Nov 5, 2018 •

edited

Loading

george-norris-salesforce commented Nov 5, 2018 •

edited

Loading

bkarlson commented Aug 28, 2019 •

edited

Loading