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

Node Sass does not yet support your current environment (macOS 10.12.1, Node 7.0.0) #1764

Closed
msc117 opened this Issue Oct 25, 2016 · 10 comments

Comments

Projects
None yet
9 participants
@msc117

msc117 commented Oct 25, 2016

macOS 10.12.1

When reporting an bug, you must provide this information:

  • NPM version (npm -v): 3.10.8
  • Node version (node -v): 7.0.0
  • Node Process (node -p process.versions):
{ http_parser: '2.7.0',
  node: '7.0.0',
  v8: '5.4.500.36',
  uv: '1.9.1',
  zlib: '1.2.8',
  ares: '1.10.1-DEV',
  icu: '57.1',
  modules: '51',
  openssl: '1.0.2j' }
  • Node Platform (node -p process.platform): tform darwin
  • Node architecture (node -p process.arch): x64
  • node-sass version (node -p "require('node-sass').info"):
node_modules/node-sass/lib/index.js:13
    throw new Error(errors.unsupportedEnvironment());
    ^

Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (51)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v3.10.1
    at Object.<anonymous> (/Users/msantos/Projects/internal-user-dashboard/node_modules/node-sass/lib/index.js:13:11)
    at Module._compile (module.js:573:32)
    at Object.Module._extensions..js (module.js:582:10)
    at Module.load (module.js:490:32)
    at tryModuleLoad (module.js:449:12)
    at Function.Module._load (module.js:441:3)
    at Module.require (module.js:500:17)
    at require (internal/module.js:20:19)
    at [eval]:1:1
    at ContextifyScript.Script.runInThisContext (vm.js:25:33)
  • npm node-sass versions (npm ls node-sass): 3.10.1

When encountering a syntax, or compilation issue:

If you delete this text without following it, your issue will be closed.

@alexburgos

This comment has been minimized.

Show comment
Hide comment
@alexburgos

alexburgos Oct 25, 2016

Running into the same issue when using webpack and npm:

NPM version: 3.10.8
Mac OS: 10.12
Node: v7.0.0

{ http_parser: '2.7.0',
node: '7.0.0',
v8: '5.4.500.36',
uv: '1.9.1',
zlib: '1.2.8',
ares: '1.10.1-DEV',
icu: '57.1',
modules: '51',
openssl: '1.0.2j' }

ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (51) For more information on which environments are supported please see: https://github.com/sass/node-sass/releases/tag/v3.10.1 @ ./src/styles/main.scss 4:14-189

alexburgos commented Oct 25, 2016

Running into the same issue when using webpack and npm:

NPM version: 3.10.8
Mac OS: 10.12
Node: v7.0.0

{ http_parser: '2.7.0',
node: '7.0.0',
v8: '5.4.500.36',
uv: '1.9.1',
zlib: '1.2.8',
ares: '1.10.1-DEV',
icu: '57.1',
modules: '51',
openssl: '1.0.2j' }

ERROR in Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (51) For more information on which environments are supported please see: https://github.com/sass/node-sass/releases/tag/v3.10.1 @ ./src/styles/main.scss 4:14-189

@t3chnoboy

This comment has been minimized.

Show comment
Hide comment
@t3chnoboy

t3chnoboy Oct 25, 2016

Removing node_modules and running npm install fixed those errors for me.

t3chnoboy commented Oct 25, 2016

Removing node_modules and running npm install fixed those errors for me.

@alexburgos

This comment has been minimized.

Show comment
Hide comment
@alexburgos

alexburgos Oct 25, 2016

Update: running npm rebuild node-sass also helps.

alexburgos commented Oct 25, 2016

Update: running npm rebuild node-sass also helps.

@msc117

This comment has been minimized.

Show comment
Hide comment
@msc117

msc117 Oct 25, 2016

Yep, rebuilding node-sass fixed this for me. I'll close this issue. Thanks!

msc117 commented Oct 25, 2016

Yep, rebuilding node-sass fixed this for me. I'll close this issue. Thanks!

@msc117 msc117 closed this Oct 25, 2016

@nschonni

This comment has been minimized.

Show comment
Hide comment
@nschonni

nschonni Oct 25, 2016

Contributor

You can subscribe to #1766

Contributor

nschonni commented Oct 25, 2016

You can subscribe to #1766

@danyadsmith

This comment has been minimized.

Show comment
Hide comment
@danyadsmith

danyadsmith Nov 14, 2016

I can confirm that running npm rebuild node-sass also worked for me.

danyadsmith commented Nov 14, 2016

I can confirm that running npm rebuild node-sass also worked for me.

@jorgecarmona

This comment has been minimized.

Show comment
Hide comment
@jorgecarmona

jorgecarmona Nov 23, 2016

npm rebuild node-sass worked like a charm. Thanks!

jorgecarmona commented Nov 23, 2016

npm rebuild node-sass worked like a charm. Thanks!

@radix21

This comment has been minimized.

Show comment
Hide comment
@radix21

radix21 Nov 29, 2016

npm rebuild node-sass Works for me too! Thanks buddy @alexburgos

radix21 commented Nov 29, 2016

npm rebuild node-sass Works for me too! Thanks buddy @alexburgos

@kevingimbel

This comment has been minimized.

Show comment
Hide comment
@kevingimbel

kevingimbel Dec 4, 2016

Can confirm npm rebuild node-sass worked for me on MacOS Sierra (10.12.1). Everything else like re-installing node_modules did not work.

It might be worth linking to this issue or describing the work-around/fix from the release page.

kevingimbel commented Dec 4, 2016

Can confirm npm rebuild node-sass worked for me on MacOS Sierra (10.12.1). Everything else like re-installing node_modules did not work.

It might be worth linking to this issue or describing the work-around/fix from the release page.

@xtremehit

This comment has been minimized.

Show comment
Hide comment
@xtremehit

xtremehit Dec 20, 2016

Yup -- npm rebuild node-sass - worked for me.

xtremehit commented Dec 20, 2016

Yup -- npm rebuild node-sass - worked for me.

@sass sass locked and limited conversation to collaborators Dec 20, 2016

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.