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

Latest version install causes hang up(memory, disk) on Windows 8.1 #115

Closed
MadLittleMods opened this issue Oct 31, 2014 · 5 comments
Closed

Comments

@MadLittleMods
Copy link

I was trying to install gulp-sass via npm install gulp-sass --save-dev today and whenever the install process reached the spot below it just blew up my memory and disk usage (99% for disk and 83% on memory; sometimes memory jumped up in the 90% range).

I'm not sure if this is a node-sass or gulp-sass problem but just thought you should be aware before using that version as a dependency.

> [email protected] install C:\wamp-2-4.64bit\www\random\potluck-game-jam\node_modules\gulp-sass\node_modules\node-sass
> node build.js

`win32-x64-v8-3.14` exists; testing

I have tried it multiple times and let it sit for over 5 minutes and it never finishes.

I am on Windows 8.1 64-bit, AMD A8 cpu, laptop.

I looked at another project I used gulp-sass on and just installed the version there which was gulp-sass@"^0.7.3" and it worked just fine and passed the tests.

@pokoot
Copy link

pokoot commented Nov 1, 2014

+1

@ngryman
Copy link

ngryman commented Nov 2, 2014

Same here, this is a known issue of node-sass: sass/node-sass#337.
@dlmanning can you pin the version to [email protected]? I think this one works.

@ngryman
Copy link

ngryman commented Nov 2, 2014

@MadLittleMods, @pokoot, you can install [email protected], the issue was not present.

@dlmanning
Copy link
Owner

There's a lot of churn in nodesass (the frontend of libsass that gulp-sass wraps) right now. There isn't anything I can do about installation errors due to nodesass's compilation. I suggest you check issues there.

@ngryman
Copy link

ngryman commented Nov 3, 2014

@dlmanning You can still pin temporarly node-sass to a version that works.
I bet that would solve the problem for a lot of people.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants