-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Install 0.6.5 on High Sierra is very heavy and on Windows causes an error #170
Comments
There are three versions available on npm: 0.6.0, 0.6.1, and 0.6.5. If either of the older versions work, I'd be curious to know. the windows error could be related to #153 |
@donmccurdy 0.6.0 and 0.6.1 installs super fast on Mac OS, comparing how long is being installed 0.6.5. So far I will use 0.6.0, and will be watching on details on Windows tomorrow also. UPD: On Windows
And on MacOS I have more modules, including dat.gui:
One 0.6.0 on win installed LONGER than 215 modules on MacOS :) |
I think #172 is likely to resolve this, as it replaces the sass loaders we were using and the deprecated babel plugin giving you an error on windows. If installation is still slow after this, I think that is likely just related to building Sass dependencies and not something we can fix here. If you'd like to test the next release before it goes to stable channel, try:
|
Mac OS High Sierra 10.12.13
NodeJS 8.9.4,
NPM 5.6.0
gem SASS 3.4.25 installed globally.
git version 2.14.3 (Apple Git-98)
On MacOS it's heavy, it loads CPU, but install at the end.
BUT, when it's installed on Windows, among other modules, it's simply cause an error:
Details (might be the issue with registry, but tried HTTP and HTTPS - both with errors during install dat.gui):
2018-01-18T21_44_40_221Z-debug.log
And btw, I wanted to downgrade, but it's failed due to not published NPM module for that version:
or much logs:
Not sure, but this might be the hint about errors/warnings about xcode.
nodejs/node-gyp#569
But on Windows no XCode, so error occurred due to ...
The text was updated successfully, but these errors were encountered: