* Added a synonym flag "-M" to "-depends" to match syntax of other compilers.
* Added support for recursive dependencies.
* Fixed some issues with path calculation when dependencies and recursive dependencies.
lukeapage - removed the actual writing of dependency lines ready for re-implementation
Although IE8 does support data-uris, it only does so with a limit of 32KB. It's a silly limitation, but a source of potential bugs. When the limit is exceeded, the data-uri() function will simply return a normal url() value with a relative path to the asset.
One may pass --no-ie-compat to lessc to avoid this safeguard.
It is up to the parser and compiler to rewrite them when those files are
imported by another LESS file.
- Modified and added test cases for import and import-once rules
- Fixed difference between client side and server side handling of relative urls
- Added a -rootpath option to lessc to specify another base path for the url
rewriting. By default, rootpath=''
If an output specifies a destination inside a directory that doesn't exist, it blows up unceremoniously. Let's avoid that.
Also, uses modern fs.writeFileSync instead of manual open/write/closeSync.
* env.dumpLineNumbers was being lost when doing "offline" compilation
(within node.js)
* Added documentation for the changed options
* --line-numbers now takes a parameter
(either "comments", "mediaquery" or "all")
* The system can now again output mediaqueries for FireLESS
* Moved comments tests in debug/comments, will duplicate
for mediaquery and for "all"
Everything is still utterly broken though, tests still fail.
- Fixed a bug, which prevents colors from being set in error messages.
- Created a helper object for lessc methods and moved the stylize function
into it. Changed test/less-test.js and lib/less/index.js to use new methods.
- Removed duplicate definitions of the stylize function.
This adds an optional `--include-path=foo` argument to the command line lessc script. Paths are evaluated relative to the current working directory, so paths like `../foo`, `./bar` and `baz` all work just like you'd expect.
Multiple paths can be supplied by separating them with colons, e.g. `--include-path=foo:../bar:/baz`
The basedir of the input file is always in the include path because that just makes sense.
