News for hackers. Stuff that matters.
Re:Eliminating Code Smell with Grunt by possibilistic on Monday December 02, 2013 @11:23AM (#6834570)
What does your build process look like? What's the tooling, and how do you invoke it? Just curious about alternatives.
Re:Eliminating Code Smell with Grunt by jaredhanson on Monday December 02, 2013 @12:49PM (#6835192)
I use make. You can see my typical setup for Node packages on GitHub, for example: https://github.com/jaredhanson/locomotive
Re:Eliminating Code Smell with Grunt by jayferd on Monday December 02, 2013 @11:28AM (#6834601)
I use make.
Re:Eliminating Code Smell with Grunt by brandonbloom on Monday December 02, 2013 @11:51AM (#6834755)
I generally prefer Make as well and I even made the case for Make when Grunt.js was first announced [1]. That said, I did use Grunt on a recent project and it worked out reasonably well. For myself, I'd prefer to keep using Make, but for many teams, Grunt is a reasonable choice.

I chose Grunt because Make generally requires a lot more background knowledge and ongoing discipline. Most Grunt tasks are configured by relatively constrained JSON data, so it's pretty hard for non-experts to muck it up unless they need to write a custom task. A Makefile would have created much greater education burden for me. That's particularly a concern when the team's Make/shell expert has time-limited involvement with the project.

[1]: https://news.ycombinator.com/item?id=3777393