-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Use Gulp for generator #1269
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
Comments
As long as we can get task parity, I'm sure it would be a nice fit. |
+1 I am personally more than willing to contribute towards this endeavour, albeit a bit unexperienced with contributions in general. Any additional resources or guidance would be great :) |
Looking forward to see Gulp can be used as an option when init the app :) |
Would be a great idea, especially if it means we can break this HUGE grunt file into multiple smaller gulp tasks. I usually store these tasks in a seperate '.gulp' folder, I'm not sure what the conventions are on that but it sure makes the task runner a lot more understandable. |
+1 |
I agree with @stefanKuijers . I would be really nice to support gulp. It's faster than grunt. Moreover, it would be great to break the grunt file into serval small chunks of tasks to be more understandable. |
+1 as well. Looking forward for this too. Would be awesome to have it as an option inside the generator. |
+1 |
+1 |
@Kageetai This issue is for using Gulp for the generator itself, not the generated project, so this issue won't really affect end-users. I have an incomplete Gulp branch with this PR: #1190 . If you'd like to try it out, check-out the |
Oh okay, I missunderstood the title then. Are there any other plans on using Gulp for the end user, too? |
I'd like to investigate whether using Gulp for the generator build tool would be better than Grunt for our work flow
The text was updated successfully, but these errors were encountered: