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

force = true? #2

Closed
laurelnaiad opened this issue Feb 2, 2014 · 4 comments
Closed

force = true? #2

laurelnaiad opened this issue Feb 2, 2014 · 4 comments

Comments

@laurelnaiad
Copy link

Hi, just wondering why you're setting force to true for all tasks. Is this necessary? It seems like it has the potential to be dangerous and I wonder if there was a reason to do that rather than parameterize it.

@maxov
Copy link
Owner

maxov commented Feb 3, 2014

It's to prevent grunt from crashing on you when running long-lived tasks. Grunt aborts and manually stops the process when an error occurs, and this is not what you want when running it inside gulp.

@laurelnaiad
Copy link
Author

Ok, thanks.

@jblack10101
Copy link

Why is this not a configurable option? I would like for my gulp task to fail when my grunt task fails..

@vdh
Copy link

vdh commented Apr 21, 2017

Just got bitten bad by this horrible choice today. I regret ever deciding to go the plugin route instead of chaining via && in bash.

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