What does --no-js mean?

[netAction]

Found here:

https://github.com/less/less-docs/blob/master/content/usage/command-line-usage.md#disable-javascript

How can Javascript be included if this flag is not activated?

[seven-phases-max]

It means exactly just that: "Disable inline JavaScript".

[seven-phases-max]

Closing as not an issue.

[netAction]

Thanks. Please be aware of the not. I would like to know how Javascript can be executed or imported or whatever if the flag is not set.

This is an issue as the information is missing in the referenced docs.

[seven-phases-max]

Yes, sorry - I initially misread your question. Inline JavaScript may be emitted via backticks. For example.

This is an issue as the information is missing in the referenced docs.

Yes, #415. (Technically it's not quite decided if it's really deprecated or not, but yes - "Nearly Deprecated" - hence no bothering to document that. Any JavaScript code should go into a plugin, since plugins have become extremely easy - see less/less.js#2479. The detailed plugin documentation is WIP in the next version of the docs since currently there're two plugin formats to be unified in v3 - WIP as well).

[matthew-dean]

@netAction Note also that inline JavaScript is disabled by default in Less 3.0 because of security concerns (and the much safer plugin method). Inline JS is essentially an eval() in your .less file, which can cause security problems if, for example, some of your variable values are set by users. (Whereas @plugin is subject to CORS restrictions.)

So, in Less 3.0 the option will be --js for lessc or javascriptEnabled: true for the Less JS API if you want to enable this option. However, using plugins is still recommended over that approach.

[matthew-dean]

Closing in favor of #415. This should be mentioned when documenting deprecation.