Package Exports

grunt-cli/bin/grunt
grunt-cli/package.json

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (grunt-cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

grunt-cli

The Grunt command line interface.

Install this globally and you'll have access to the grunt command anywhere on your system.

npm install -g grunt-cli

Note: The job of the grunt command is to load and run the version of Grunt you have installed locally to your project, irrespective of its version. Starting with Grunt v0.4, you should never install Grunt itself globally. For more information about why, please read this.

See the Getting Started guide for more information.

Shell tab auto-completion

To enable tab auto-completion for Grunt, add one of the following lines to your ~/.bashrc or ~/.zshrc file.

# Bash, ~/.bashrc
eval "$(grunt --completion=bash)"

# Zsh, ~/.zshrc
eval "$(grunt --completion=zsh)"

Installing grunt-cli locally

If you don't have administrator rights, you may need to install grunt-cli locally to your project using npm install grunt-cli --save-dev. Unfortunately, this will not put the grunt executable in your PATH. You'll need to specify its explicit location when executing it, eg: ./node_modules/.bin/grunt,

Note: Using grunt-cli in this way is unsupported.