question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (57)"

See original GitHub issue

Title

Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (57)

Functional impact

Results in solution failing to build.

Minimal repro steps

Following directions from here under the “Set up your machine” and “Get the source code”.

  1. Installed Visual Studio 2017 (enterprise).
  2. Install Azure Power Shell (irrelevant for this issue)
  3. Install NodeJS (8.9.4 LTS rather than 6.11.3 LTS that the article mentioned)
  4. Install bower and grunt.
  5. Clone source code from PartsUnlimited
  6. Build solution

Expected result

Successful build.

Actual result

Build failed with error message - “Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (57)”

Further technical details

Running a Windows 10 VM in Azure. Located this issue which indicated to update the gulp-sass version to 3.1.0. When I did a search of the solution, “gulp-sass” was only in the readme. But I did notice that npm install node-sass did result in a couple warnings. Namely that it could not find c:\repos\PartsUnlimited\package.json.

c:\repos\PartsUnlimited>npm install
npm WARN saveError ENOENT: no such file or directory, open 'c:\repos\PartsUnlimited\package.json'
npm WARN enoent ENOENT: no such file or directory, open 'c:\repos\PartsUnlimited\package.json'
npm WARN PartsUnlimited No description
npm WARN PartsUnlimited No repository field.
npm WARN PartsUnlimited No README data
npm WARN PartsUnlimited No license field.

up to date in 1.344s

c:\repos\PartsUnlimited>npm --version
5.6.0

c:\repos\PartsUnlimited>node --version
v8.9.4

I did also go through the git clean -fdx step as well to no avail.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:33 (1 by maintainers)

github_iconTop GitHub Comments

251reactions
DaFunkyAlexcommented, Jul 26, 2018

That worked for me:

npm --depth 9999 update
npm rebuild node-sass
105reactions
ghernandezfortescommented, Jun 19, 2018

With “yarn add node-sass” worked for me

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to fix “Error: Node Sass does not yet support your current ...
How to fix “Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)” · What to...
Read more >
Node Sass does not yet support your current environment
Node -sass incompatibility with the node version was the issue in my case. I had node-sass v4.13.1 with node version 14+ running in...
Read more >
Node Sass does not yet support your current environment
Here is how you can fix node incompatibility error, using "Node Sass does not yet support your current environment" as an example.
Read more >
Node Sass does not yet support your current environment ...
Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (57) #20.
Read more >
Node Sass does not yet support your current environment
Node Sass does not yet support your current environment : Linux 64-bit with Unsupported runtime (57) while running gulp command. I have tried ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found