The tasks we configured for our project tend to perform a single function and nothing more. As a project grows, we will probably start to identify groups of tasks that we tend to run together, in a specific order. It is at this point that an alias task can become quite helpful to us as it allows us to group a set of tasks together under a new task name.
In this example, we'll work with the basic project structure we created in the Installing Grunt on a project recipe in Chapter 1, Getting Started with Grunt. Be sure to refer to it if you are not yet familiar with its contents.
This recipe also contains an example that makes use of the Setting up a basic web server and the Watching files for changes recipe of Chapter 1, Getting Started with Grunt, and the Rendering Jade templates recipe in Chapter 3, Templating Engines in one setup. Be sure to refer to these if you'd like to gain a deeper understanding of each of these aspects.