Grunt 1.0.0 released
gruntjs.com
Grunt 1.0.0 released
1–10 of 106 posts
Re: Grunt 1.0.0 released
#2Lately the decline in popularity of Grunt has been more and more noticeable for me. When adding new packages there are always usage instructions for Gulp, sometimes webpack and alternatives as well but Grunt seems to be notably absent.
I'm contemplating switching to one of the more popular task runners, but that would mean having to rebuild a working flow.
The question also remains what happens when you have to revisit an existing site in x years. Will all the packages still be available, do I have to go back to node version x and will everything still work on Windows/Mac OS version y?
Re: Grunt 1.0.0 released
#3better late than never :)
Re: Grunt 1.0.0 released
#4Lately the decline in popularity of Grunt has been more and more noticeable for me. When adding new packages there are always usage instructions for Gulp, sometimes webpack and alternatives as well but Grunt seems to be notably absent. I'm contemplating switching to one of the more popular task runners, but that would mean having to rebuild a working flow. The question also remains what happens when you have to revis…
until the new shiny thing comes and replaces that. I still don't understand what's wrong with grunt (or whats better with gulp).
Re: Grunt 1.0.0 released
#5Lately the decline in popularity of Grunt has been more and more noticeable for me. When adding new packages there are always usage instructions for Gulp, sometimes webpack and alternatives as well but Grunt seems to be notably absent. I'm contemplating switching to one of the more popular task runners, but that would mean having to rebuild a working flow. The question also remains what happens when you have to revis…
until the new shiny thing comes and replaces that. I still don't understand what's wrong with grunt (or whats better with gulp).
The advantage of Gulp, in my opinion, is that it's driven by code rather than config - that is to say, in order to define your tasks you write JS code instead of JSON. That gives you a considerable advantage in cases where you want to do something outside of the scope of what the plugin developer was thinking.
Of course, that brings with it the disadvantage of needing to be able to write JS in order to configure it, and an additional point of failure (eg your own code).
Re: Grunt 1.0.0 released
#6Lately the decline in popularity of Grunt has been more and more noticeable for me. When adding new packages there are always usage instructions for Gulp, sometimes webpack and alternatives as well but Grunt seems to be notably absent. I'm contemplating switching to one of the more popular task runners, but that would mean having to rebuild a working flow. The question also remains what happens when you have to revis…
until the new shiny thing comes and replaces that. I still don't understand what's wrong with grunt (or whats better with gulp).
I never got what's so great about Grunt in the first place, and instead stuck to makefiles. Something like `cat src/*.js | uglify > build.js` would take me a lot more effort to do with Grunt (or Gulp).
Re: Grunt 1.0.0 released
#7Earlier quoted context omitted.
until the new shiny thing comes and replaces that. I still don't understand what's wrong with grunt (or whats better with gulp).
The advantage of Gulp, in my opinion, is that it's driven by code rather than config - that is to say, in order to define your tasks you write JS code instead of JSON. That gives you a considerable advantage in cases where you want to do something outside of the scope of what the plugin developer was thinking. Of course, that brings with it the disadvantage of needing to be able to write JS in order to configure it,…
I don't see how that's different from Grunt, which is also driven by code.
Re: Grunt 1.0.0 released
#8Lately the decline in popularity of Grunt has been more and more noticeable for me. When adding new packages there are always usage instructions for Gulp, sometimes webpack and alternatives as well but Grunt seems to be notably absent. I'm contemplating switching to one of the more popular task runners, but that would mean having to rebuild a working flow. The question also remains what happens when you have to revis…
until the new shiny thing comes and replaces that. I still don't understand what's wrong with grunt (or whats better with gulp).
I have large project built with Grunt and at one point I have tried to move it to Gulp. Gulp, as far as I can tell, requires much less code to do the same stuff. However, two things forced me to stick with Grunt. 1) The build scripts were working just fine. Why fix something it ain't broken? :) 2) When Sass or Coffee fails, gulp watch fails entirely. It's something I wasn't able to solve. Grunt will just pick up from it was before the error. Dunno!
Re: Grunt 1.0.0 released
#9Obsolete before it hit 1.0.
While grunt/gulp was fun for a while... i am not looking back to our 800 line grunt file, complicated async configuration and the tons of dev-dependencies.
Webpack blew everything out of the water. 80 lines of config, hot-reloading, code-spliting, hash-filenames... Looking forward to whats coming next.
Re: Grunt 1.0.0 released
#10Obsolete before it hit 1.0. While grunt/gulp was fun for a while... i am not looking back to our 800 line grunt file, complicated async configuration and the tons of dev-dependencies. Webpack blew everything out of the water. 80 lines of config, hot-reloading, code-spliting, hash-filenames... Looking forward to whats coming next.
Totally agree, the key was loaders...