-
Notifications
You must be signed in to change notification settings - Fork 10
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
Support Gruntjs tasks #7
Comments
This issue is related to #1. |
See gruntjs/grunt#497 and https://github.com/tkellen/node-task for how grunt tasks might end up in grunt 0.5 |
Thanks @sindresorhus! Will take a look at it as soon as possible. It would be great if we managed to get this done. |
Just wanted to share the implementation I engineered for this issue. After investigating,
I could monkey patch
The |
- Process signals are only attached when necessary (and detached when possible) - Remove the callback support for the run() - Various bug fixes and improvements
It's done guys! :D |
Upcoming changes to |
Just wanted to say that this is just awesome! 👍 |
oh yeah :) |
It would be great if Automaton also could take Gruntjs tasks. The goal here would be to achieve a state in which the user could invoke some grunt task just like any other
autofile
. From my understanding, Grunt tasks have a set of options as input, just like automaton. The main difference is that they have targets, while we simply invoke the task separate times, with separate options, if necessary.This needs some proper planning before implementation, so if anyone wants to pick this, the first thing to do would be to discuss what you are planning to do.
The text was updated successfully, but these errors were encountered: