Support specifying custom variables when calling lessc and less.js. #1655
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 offeringtemporary access to an image on S3, or anything else.
lessc has two new parameters,
--global-var
and--modify-var
. Both takea value of the form
"varname=value"
.--global-var
declares variablesimmediately before the content of the .less files, and
--modify-var
declares them after.
--global-var
is used when rules, imports, or other variables will dependon the provided variable.
--modify-var
is used to override a variable declared within the .lessfile.
less.js's equivalent for global variables is
less.globalVars
. This canbe set before loading less.js. There is no new equivalent to
--modify-var
, as less.modifyVars can be used for that purpose.Implements issue #731.