grunt-clix

The Grunt command line interface.

It is actually a grunt-cli fork with one additional param - --libpath. Original grunt-cli package is trying to find grunt whether in local node modules or in --basedir folder. Actually there are some cases when we need to have something more flexible.

In order not to confuse original "grunt" command, it is renamed to "gx".

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

npm install -g grunt-clix

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 "$(gx --completion=bash)"

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

Installing grunt-clix locally

If you prefer the idiomatic Node.js method to get started with a project (npm install && npm test) then install grunt-clix locally with npm install grunt-clix --save-dev. Then add a script to your package.json to run the associated grunt command: "scripts": { "test": "grunt test" } . Now npm test will use the locally installed ./node_modules/.bin/grunt executable to run your Grunt commands.

To read more about npm scripts, please visit the npm docs: https://npmjs.org/doc/misc/npm-scripts.html.