There are all these tasks that we need to do as front end developers. Concatenate and compress our files. Run our preprocessors. Optimize images. Run tests. The list goes on and on. Using different tools for all of them is getting increasingly difficult. Running them manually makes it worse, and easy to screw up.
Grunt is perfect for reining all this in. Maybe you are familiar with tools like CodeKit (covered in this screencast) for doing this kind of thing. CodeKit is great. You might think of it like really specific Grunt setup with a nice interface. Grunt would be a replacement for CodeKit if you need to do more with your build process than CodeKit offers.
In this screencast we cover getting Grunt up and running on a simple project. This is meant to be an accompanying video to a more comprehensive article over on 24 ways.
- Make sure you’ve done first: Install Node
- Grunt site: getting started
- My Grunt Boilerplate – which does what we did in this screencast plus more stuff.
- Grunt plugins we talked about: Uglify, Sass, Watch
Note: I know I’m a Grunt newb. Got some great Grunt information to share? I’d love to hear in the comments. Annnnnd I know the video is kinda messed up at the end. Will fix.