-
Notifications
You must be signed in to change notification settings - Fork 60
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
Task hangs if running in Coffeescript and there is a compile error #56
Comments
I think you are absolutely right, it should return on error. |
I just realized @mhchen called me out for not using Coffeescript ☕ :) I'll switch, just so you don't think any lesser of me!! |
Haha @ericclemmons not a callout at all. I know it's somewhat controversial, so it really was just a small show of appreciation for supporting a subset of your user base that you don't personally belong to |
After writing tons of nested promises that use |
Closed via #57 |
Try out v0.4.18 to see if this fixes it! |
If I get any kind of compile error in my Coffeescript, the task hangs and never returns control to Grunt. I did a bit of debugging and found that if the output option is set, it only calls finished() if stdout has some output, but a compile error means only stderr will have output and finished() never gets called. In my own script I am getting around this by introducing a delay of 1, but this feels like not the right way to handle this. Would it make sense to introduce a change with a stderr.on('data') that does the same thing as the stdout.on('data')?
Here's the code snippet I'm referring to:
Thanks @ericclemmons for your maintenance of this project and for supporting Coffeescript even though you've said you don't use it very much yourself. It's much appreciated.
The text was updated successfully, but these errors were encountered: