Skip to content
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 Upgrade for WIndows 10 Node v7 #3041

Closed
markheron91 opened this issue Nov 7, 2016 · 3 comments
Closed

Node Sass Upgrade for WIndows 10 Node v7 #3041

markheron91 opened this issue Nov 7, 2016 · 3 comments
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@markheron91
Copy link

markheron91 commented Nov 7, 2016

Please provide us with the following information:

OS?

Windows 10 64 bit

Versions.

angular-cli: 1.0.0-beta.19-3
node: 7.0.0
os: win32 x64

Repro steps.

Try to run an ng serve command using the setup provided above. Console complains about an unsupported runtime

The log given by the failure.

ERROR in ./src/app/setup/skin/list/skin-list.component.scss
Module build failed: Error: Node Sass does not yet support your current environment: Windows 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

Mention any other details that might be useful.

On the node-sass github it states that v3.11.1 supports all node versions on all os apart from FreeBSD - it would be good for the dependency in the repo to be updated to support the newest version of node.
sass/node-sass#1766


Thanks! We'll be in touch soon.

@wulfsberg
Copy link

Be aware that you'll break on Node 7 anyway: #837

@filipesilva filipesilva added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label Nov 21, 2016
@Brocco
Copy link
Contributor

Brocco commented Jan 22, 2017

The node-sass dep has been updated. Also, while we have tests for node 7, it is not officially a supported node version, yet.

@Brocco Brocco closed this as completed Jan 22, 2017
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

No branches or pull requests

4 participants