Read the Getting Started guide for instructions on using Grunt in your projects. Once you've done that, check out a Sample Gruntfile and learn more about Configuring Tasks.

The Creating Tasks guide lists the differences between the types of Grunt tasks and shows a number of sample tasks and configurations. For more information about writing custom tasks …

This document explains how to install specific versions of Grunt and Grunt plugins. If you haven't read the Getting Started guide, you should check that out first.

Run sudo npm install -g grunt-cli (Windows users should omit "sudo ", and may need to run the command-line with elevated privileges). The grunt command-line interface comes with a series …

To install and use any plugin listed here, checkout how to install and use the Grunt plugins section. You may also be interested on how to create your own Grunt plugin.

When a task is run, Grunt looks for its configuration under a property of the same name. Multi-tasks can have multiple configurations, defined using arbitrarily named "targets."

Once mastered all the basic concepts you might want to create your own Grunt tasks. Our step-by-step guide and the API documentation page will help you in achieving this goal.

To do that, we'll cover a Grunt plugin called grunt-contrib-watch. The latter runs predefined tasks, such as grunt-contrib-jshint, whenever files are added, changed, or deleted.

The grunt argument is a reference to grunt, containing all the grunt methods and libs. The init argument is an object containing methods and properties specific to this init template.

Every time Grunt is run, you specify one or more tasks to run, which tells Grunt what you'd like it to do. If you don't specify a task, but a task named "default" has been defined, that task will …