Rigger provides targetted include functionality (similar to sprockets) but with some additional functionality. A highlight of rigger functionality is outlined below:
- Simple include format for including files using a special comment syntax (
- Ability to include remote resources as well as local: (
- Ability to intelligently transpile from coffee-script, stylus, etc to their natural web equivalents (js, css, etc).
grunt-rigger you will need to include it in your
package.json file (I'd recommend under the
You will see in the example above,
coffee-script is also included in the
devDependencies section. In cases where you would like to leverage riggers ability to transpile files (e.g.
.js) you will need to include the appropriate node package in your
devDependencies as these are not automatically included in rigger itself (to avoid library bloat).
grunt-rigger within grunt itself is very simple. Consider the following sample
That should be pretty much it, if your source file contains any rigger comments they will be parsed and executed accordingly.