LESS Tests has many more features than we've been able to document thus far. So while we work to improve the docs, please let us know if you have any questions or have any trouble getting LESS Tests to work. And feel free to create an Issue, we're here to help.

This is a convenience task to "Run predefined tasks whenever watched file patterns are added, changed or deleted". Requires grunt-contrib-watch, npm i grunt-contrib-watch.

Should you encounter problems with installing dependencies or running the grunt commands, be sure to first uninstall any previous versions (global and local) you may have installed, and then rerun npm install.

Specified files will be prepended to the beginning of src files, not to the concatenated output. This feature is useful for "inlining" globaly-required LESS files, such as variables or mixins, so that they do not need to be referenced with @import statements inside any individual files.

Specifies directories to scan for @import directives when parsing. The default value is the directory of the specified source files. In other words, the paths option allows you to specify paths for your @import statements in the less task, as an alternative to specifying a path on every @import statement that appears throughout your LESS files. So instead of doing this:

This project uses the extremely flexible assemble-less Grunt plugin for compiling LESS to CSS. The less plugin leverages JSON and underscore for defining any number of LESS "bundles", UI components, compressed stylesheets or themes.

This Grunt.js plugin and some of the documentation on this page, is derived from grunt-contrib-less, authored by Tyler Kellen. This plugin was modified for this project to concat LESS files first, and then compile them into CSS files. This allows for prepending globally required LESS files, and it also adds the ability to build out individual CSS files, rather than building a single conctatenated file.

Want to help make less-tests even better? All constructive feedback and contributions are welcome, so please consider contributing! We can always use help creating, tests, documentation or resolving Issues, but if you have other ideas for how you can help, Brian and I would love to hear them!