Due to it being detrimental to the reusability of a task, it's not at all common to have tasks depending on one another, due to it being detrimental to the reusability of a task. If tasks are so tightly coupled that they can't run independently, it should strongly be considered to combine them into a single task.
That being said, there are always exceptions, and Grunt provides for this by way of the grunt.task.requires function. When called, this function will check whether the task with the specified name has been successfully executed. If it finds that this is not the case, it will fail the current task.
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.
If any of the steps in this recipe seem hard to follow, be sure to check out the Creating a basic...