-
Notifications
You must be signed in to change notification settings - Fork 2.8k
npm install fails on node-sass binary #165
Comments
@JohnMilazzo - I ran into the same issue, initially. After node-sass@4.10.0 was installed, the install completed. However, when it came time to build, things got ugly again. For me, the resolution was:
After which,
fired up the server, which is now working quite well. |
Installing node-sass fixes the issue.
|
@Yonet |
@peterblazejewicz, I was running into other problems and I didn't have a chance to get the project to run. There wasn't any sass issues logged but I can't confirm there weren't any issues on runtime. |
This version bump should fix issue with `node-sass` installation on some systems. Tested on Win 10. Thanks! Closes microsoft#165
thx , I've made a PR bumping with minor version, for me it's solid on Win10, compared to |
This version bump should fix issue with `node-sass` installation on some systems. Tested on Win 10. Thanks! Closes #165
This version bump should fix issue with `node-sass` installation on some systems. Tested on Win 10. Thanks! Closes #165
This version bump should fix issue with `node-sass` installation on some systems. Tested on Win 10. Thanks! Closes microsoft#165
npm install
updating package.json to use ^4.10.0 seems to make life good again.
The text was updated successfully, but these errors were encountered: