Updating version number at compile time

31-Jul-2017 01:28

We have improved the source map options and path generation so the sourcemap should be generated at the correct path without specifying any options. If you want to install a bleeding-edge, unpublished version of lessc, follow the instructions for specifying a git URL as a dependency and be sure to specify an actual commit SHA (not a branch name) as the rule does not exist at that exact location, less will look for it at the location(s) passed to this option. Periodically, as new functionality is being developed, lessc builds will be published to npm, tagged as beta. Since patch releases are non-breaking we will publish patch releases immediately and alpha/beta/candidate versions will be published as minor or major version upgrades (we endeavour since 1.4.0 to follow semantic versioning).Type: in before v2) Whether to use the per session file cache.This caches less files so that you can call modify Vars and it will not retrieve all the less files again.This is not recommended for production, but for development it allows the compiler to produce a single output file which in browsers that support it, use the compiled css but show you the non-compiled less source.

So for the option above you might have This is the opposite of the rootpath option, it specifies a path which should be removed from the output paths.

This can be used in conjunction with the map inline option so that you do not need to have any additional external files at all.