-
Notifications
You must be signed in to change notification settings - Fork 43
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
Process never finishes #65
Comments
Yeh, I've had this problem for like 11 months, so much unlinted code has accumulated in my repository because I can't get this running during deployment :( |
@simeydotme
You'll also notice that anytime you go to do a commit it will run the Sass linter script before hand. Currently it doesn't stop the commit if it finds anything. But it will print out anything it finds and then perform the commit. So it at least forces you to acknowledge that there is a problem anytime you do a commit. If you make any improvements to this script, let me know so I can update mine. |
thanks @TheJaredWilcurt , I'll give it a shot :) I'm thinking that the |
I switched to |
That doesn't support |
I've tried the sample code from the README, and I've tried stealing someone else code from a random project.
In both cases Gulp-Sass-Lint will run, scan all the Sass files I told it to, then either do nothing, or display errors it found in the file. But it never actually stops running. I have to manually stop it.
This means, that if I have a
serve
task to run a local express server, I can't actually go to thelocalhost:8000
in the browser, nothing will load because the Gulp-Sass-Lint never stopped running. If I remove it from my list of default tasks, then the server runs fine:If I just run
gulp sasslint
, again, it works like normal, but it never finishes. Opening up task manager shows I have a node process maxing out one of my CPU's.Windows 7 Professional 64-bit
The text was updated successfully, but these errors were encountered: