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

That worked for me:

npm --depth 9999 update
npm rebuild node-sass

from partsunlimited.

With "yarn add node-sass" worked for me

from partsunlimited.

@eamonnk Thank you! I can now build and debug the solution.

What I did:

1. Followed the directions on the updated page ("PandP"). That has better instructions and does, in fact, say NOT to use NodeJS 8x.
2. Uninstalled NodeJS 8x
3. Installed NodeJS 6.12.3
4. Cloned solution again to a different repository.
5. Ran npm rebuild node-sass due to error (the link has info about the error message).
6. Build solution. All is now good.

This issue is resolved. Thanks again!

from partsunlimited.

That worked for me:

npm --depth 9999 update
npm rebuild node-sass

Thanks, this works for me :)

from partsunlimited.

Hi

Can you try open up a cmd or Powershell window as administrator, go to the repo where the PartsUnlimitedWebsite src folder is located i.e. C:<repository path>\PartsUnlimited\src\PartsUnlimitedWebsite then run the below command and try again to build the solution.

npm rebuild node-sass

If you still get errors, check the version of node.js installed, if its not v6 but ver 8x, you could uninstall the 8x version thats currently installed and install ver 6.12.3 from the node.js LTS schedule page. Then try build the solution again.

Theres also an updated page available for this as well, https://microsoft.github.io/PartsUnlimited/pandp/200.1x-PandP-PUsetupwithVS2017.html. which has more details then the page you're currently looking at. It has a bit more detail for errrors which might help.

If its still not building after trying those things let us know and will have another look.

Thanks,
Eamonn

from partsunlimited.

npm --depth 9999 update
npm rebuild node-sass

This also worked for me!

from partsunlimited.

That worked for me:

npm --depth 9999 update
npm rebuild node-sass

This also worked for me! Thanks a lot, you saved my day !

from partsunlimited.

That worked for me:

npm --depth 9999 update
npm rebuild node-sass

Dosent work for me. She still block and dont move ...

from partsunlimited.

remove node_modules folder
run
npm i

from partsunlimited.

This shows that the version of node-sass you are trying to run is not compatible with the version of node installed. So you need to run
npm rebuild node-sass
and if this does not work, you should run the following command
npm uninstall node-sass && npm install node-sass (with -g if your node-sass installed globally)

from partsunlimited.

In case someone else has problem with Grunt Task Runner after following all the direction above. Please see this link https://developercommunity.visualstudio.com/content/problem/314581/gulpfilejs-fails-in-task-runner-in-visual-studio-2.html . Basically do this go to Tools -> Options -> Projects and Solutions -> Web Package Management -> External Web Tools and move the $(PATH) entry above $(VSInstalledExternalTools). Restart VS 2017, and voila grunt task runner no longer using the wrong version of Node. It would seem that task runner will run the latest version of Node even if you install Node 6. Fixed everything for me. PS: you will still need to rebuild node-sass

Result of task runner - Grunt
C:\edx\Repos\PartsUnlimited\src\PartsUnlimitedWebsite> cmd.exe /c grunt -b "C:\edx\Repos\PartsUnlimited\src\PartsUnlimitedWebsite" --gruntfile "C:\edx\Repos\PartsUnlimited\src\PartsUnlimitedWebsite\Gruntfile.js" bower --color
Running "bower:install" (bower) task
Cleaned target dir C:\edx\Repos\PartsUnlimited\src\PartsUnlimitedWebsite\wwwroot\lib
Installed bower packages
Copied packages to C:\edx\Repos\PartsUnlimited\src\PartsUnlimitedWebsite\wwwroot\lib
Done.
Process terminated with code 0.

from partsunlimited.

what npm --depth 9999 update is doing ?

"If no package name is specified, all packages in the specified location (global or local) will be updated. As of [email protected], the npm update will only inspect top-level packages. Prior versions of npm would also recursively inspect all dependencies. To get the old behavior, use npm --depth 9999 update ."

As retrieved today from https://docs.npmjs.com/cli/update.html.

from partsunlimited.

I am using node 12.1.0 version, angular 8.2. 14 and node-sass 4.13.0
Still facing the issue.

from partsunlimited.

what npm --depth 9999 update is doing ?

from partsunlimited.

That worked for me:

npm --depth 9999 update
npm rebuild node-sass

Thank you it worked. Could you explain what the first line does?

from partsunlimited.

That worked for me:

npm --depth 9999 update
npm rebuild node-sass

Thank you it worked. Could you explain what the first line does?

Just take a loot at package.json file after the command processed.
By the way it doesn't help me.

from partsunlimited.

That worked for me:

npm --depth 9999 update
npm rebuild node-sass

In my case, only run npm --depth 9999 update, then the newest node-sass binary is redownloaded, no need for npm rebuild node-sass.

from partsunlimited.

npm --depth 9999 update
npm rebuild node-sass
Thank you, That worked for my project.

from partsunlimited.

npm --depth 9999 update
npm rebuild node-sass
This worked for me. Thank you!

from partsunlimited.

npm --depth 9999 update
npm rebuild node-sass

Thanks a lot !!!
It really works

from partsunlimited.

That worked for me:

npm --depth 9999 update
npm rebuild node-sass

Worked for me too.

from partsunlimited.

npm --depth 9999 update
npm rebuild node-sass

It's really worked. Thanks

from partsunlimited.

That worked for me:

npm --depth 9999 update
npm rebuild node-sass

It's really worked, Huge thank you

from partsunlimited.

With "yarn add node-sass" worked for me

Worked for me

from partsunlimited.

With "yarn add node-sass" worked for me

Worked For Me

from partsunlimited.

That worked for me:

npm --depth 9999 update
npm rebuild node-sass

Work for me thank you

from partsunlimited.

In my case, i had nvm installed, and was using node 11.10.1 on MinGW, once i switched back to node 8.9.4, it worked and the error went away.

from partsunlimited.

With "yarn add node-sass" worked for me

Worked for me. thanks.

from partsunlimited.

npm --depth 9999 update
npm rebuild node-sass
It took a long time but it works thank you

from partsunlimited.

I am using Vue 4.5.4 and I got this error on yarn serve, I fixes this with just running yarn and again yarn serve.

from partsunlimited.

npm uninstall node-sass
npm install node-sass
its worked on mac osx 11 node 13

from partsunlimited.

If the problem still exists then first uninstall node.js and reinstall node. It works for me after 3 hours of struggle. Read every answer on SOF. Did almost everything that GitHub users said. But reinstalling works like a charm, on the first go.

from partsunlimited.

That worked for me:

npm --depth 9999 update
npm rebuild node-sass

Thank you, Worked for me.

from partsunlimited.