Eliminating Code Smell with Grunt

http://flippinawesome.org/2013/12/02/eliminating-code-smell-with-grunt/

by honzzz • 13 years ago

18 11 13 years ago

jaredhanson3• 13 years ago

I lol'd at the title. Just having a Gruntfile is the first smell I notice when looking at a project. Seriously, why take two simple tools and layer a unnecessary "task runner" on top of them?

dugmartin• 13 years ago

It makes sense when you use it with grunt-contrib-watch. Then you just keep it running as you are developing and listen for the error "ding" after a save.

jaredhanson3• 13 years ago

Actually, no. It's very easy to run a watcher which executes any command (like say jshint itself).

possibilistic• 13 years ago

What does your build process look like? What's the tooling, and how do you invoke it? Just curious about alternatives.

jneen2• 13 years ago

I use make.

jaredhanson3• 13 years ago

I use make. You can see my typical setup for Node packages on GitHub, for example: https://github.com/jaredhanson/locomotive

chadly• 13 years ago

I find having a "standard" way to run tasks enormously beneficial especially when working with developers cross-platform. Whatever OS you are running, just grunt and all is well. :)

jneen2• 13 years ago

s/Grunt/JSHint/

cleverjake• 13 years ago

JSHint is removing most style related rules out in favor of exterior plugins. JSCS is a great alternative - https://github.com/mdevils/node-jscs

antonpug• 13 years ago

Great article. Grunt is a wonderful tool, despite what some people on here might say.

Eliminating Code Smell with Grunt

Related Stories