Both lessc and less.js can now be provided with global variables that
all .less files will have immediate access to. This can be used to
provide, for example, a base path for an @import, signed URLs offering
temporary access to an image on S3, or anything else.
lessc has two new parameters, --global-var and --modify-var. Both take
a value of the form "varname=value". --global-var declares variables
immediately before the content of the .less files, and --modify-var
declares them after.
--global-var is used when rules, imports, or other variables will depend
on the provided variable.
--modify-var is used to override a variable declared within the .less
file.
less.js's equivalent for global variables is less.globalVars. This can
be set before loading less.js. There is no new requivalent to
--modify-var, as less.modifyVars can be used for that purpose.
* 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.
