Now that we have Nodemon running in a container, we can edit code with the container watching it, and we can debug, it's time to start building an app.
But what happens when we forget to add that semi-colon? Or we accidentally put code after a “return” statement? If we're working on our local system, we can use JSHint to help us alleviate those mistakes.
How do we catch those types of simple errors in a container, though? The answer, of course, is to still use JSHint. Only now, we're going to use inside of a container.
Unlike nodemon, however, we don't want to change the way our container is started. Instead, we'll want to work within an existing container (the one running nodemon). And in this episode, you'll learn how to set that up, how to use grunt to execute JSHint from your container, and how to ensure your code passes these basic tests before moving on to the next task.