Maybe stop using Grunt?
medium.com
Maybe stop using Grunt?
1–10 of 51 posts
Re: Maybe stop using Grunt?
#2I switched to skimming the article at:
[If] you just want to set up your single project with a task workflow,
then go ahead and use Grunt (or gulp). They will serve you just fine.Re: Maybe stop using Grunt?
#3I'm a bit confused, what are they using grunt for? We're using gulp, but it's basically the same software. It just compiles our coffeescript, tags some assets and moves some files around, perhaps run a minifier somewhere.
In what situation do you need your build toolchain to do more than that?
Re: Maybe stop using Grunt?
#4This article should be titled "Maybe you should stop using Grunt for things it was never meant to do to begin with"
Re: Maybe stop using Grunt?
#5I'm a bit confused, what are they using grunt for? We're using gulp, but it's basically the same software. It just compiles our coffeescript, tags some assets and moves some files around, perhaps run a minifier somewhere. In what situation do you need your build toolchain to do more than that?
I think I found myself in a similar situation as the OP. We have multiple different, but architecturally similar, products which each get their own Gruntfile. If we stop here, we're solid, perfect. Unfortunately, each product has multiple flavors which each need to build into their own separate output directories. For us, that's where the Grunt patterns break down and get awkward. It's actually been good enough for almost 2 years now, but I can definitely see the cracks.
Re: Maybe stop using Grunt?
#6...I would like the task system to provide an abstraction for pipelining tasks. (Perhaps gulp helps with this?)
Hmmm, perhaps someone needs to look at any gulpfile ever written, anywhere.
gulp.src('src')
.pipe(this())
.pipe(that());
Re: Maybe stop using Grunt?
#7I'm a bit confused, what are they using grunt for? We're using gulp, but it's basically the same software. It just compiles our coffeescript, tags some assets and moves some files around, perhaps run a minifier somewhere. In what situation do you need your build toolchain to do more than that?
I think I found myself in a similar situation as the OP. We have multiple different, but architecturally similar, products which each get their own Gruntfile. If we stop here, we're solid, perfect. Unfortunately, each product has multiple flavors which each need to build into their own separate output directories. For us, that's where the Grunt patterns break down and get awkward. It's actually been good enough for a…
Why don't you just write shell scripts?
Re: Maybe stop using Grunt?
#8I probably just don't have enough experience. I like the idea that Grunt and Gulp are written in JS so using JS to build JS seems like a win.
But...., aren't build systems supposed to do dependency checking and just built the minimal amount of stuff? Maybe few JS projects are big enough for it to matter or maybe I missed where the dependencies are checked but AFAICT the default is to build everything always.
Re: Maybe stop using Grunt?
#9Earlier quoted context omitted.
I think I found myself in a similar situation as the OP. We have multiple different, but architecturally similar, products which each get their own Gruntfile. If we stop here, we're solid, perfect. Unfortunately, each product has multiple flavors which each need to build into their own separate output directories. For us, that's where the Grunt patterns break down and get awkward. It's actually been good enough for a…
Why don't you just write shell scripts?
[deleted]
Re: Maybe stop using Grunt?
#10Earlier quoted context omitted.
I think I found myself in a similar situation as the OP. We have multiple different, but architecturally similar, products which each get their own Gruntfile. If we stop here, we're solid, perfect. Unfortunately, each product has multiple flavors which each need to build into their own separate output directories. For us, that's where the Grunt patterns break down and get awkward. It's actually been good enough for a…
Why don't you just write shell scripts?
I will probably go that route if we ever rebuild those tools.