In the previous episode, I showed you how to use JSHint to create a consistent and clean code base, while avoiding many of the most common syntax and formatting mistakes, you should be using JSHint (or another linting tool).
While JSHint and other linting tools are great, it gets to be rather annoying when you have to constantly re-run the linting process manually. Fortunately, JSHint and other grunt tasks can all be automated through the use of the grunt-contrib-watch plugin. This plugin allows you to specify files to watch on your file system, and it will run grunt tasks in response to those file changes.
In this episode, I'll show you how to get grunt-contrib-watch set up, and use it to automate your JSHint linting.