Download
Why use a task runner? In one word, automation. The less work you have to do when performing repetitive tasks like minification, compilation, unit testing, linting, etc, the easier your job becomes. After you've configured it through a Gruntfile, a task runner can do most of that mundane work for you and your team with basically zero effort. The Grunt ecosystem is huge and it's growing every day. With literally hundreds of plugins to choose from, you can use Grunt to automate just about anything with a minimum of effort. If someone hasn't already built what you need, authoring and publishing your own Grunt plugin to npm is a breeze. Many of the tasks you need are already available as Grunt Plugins, and new plugins are published every day. While installing grunt is simple, it's slightly more involved to get it running on your project.
Features
- Grunt and Grunt plugins are installed and managed via npm, the Node.js package manager
- Allows multiple versions of Grunt to be installed on the same machine simultaneously
- You can run grunt from any subfolder in your project
- Most grunt-init templates will automatically create a project-specific package.json file
- Most Grunt tasks rely on configuration data defined in an object passed to the grunt.initConfig method
- You can configure Grunt to run one or more tasks by default by defining a default task
Project Samples
