Answer the question
In order to leave comments, you need to log in
WinLESS, problem with compiling nested @imports?
To compile LESS, I use the WinLESS 1.5.3 program.
If you request auxiliary files from the template file using the "@_import" construct, @_import "/../../../general.less";
style.less->general.less
then everything is fine, a css file is created, the WinLESS program displays a message that everything was successful.
But if other files are connected inside the file connected via "@_import" also via "@_import", then the program writes that everything was successfully compiled, but the css file is not created. style.less->general.less->reset.less
Is it possible to use such a cascade connection via "@_import", i.e. more than one level in LESS or is it just a program bug most likely?
Ps @_import read without underscore between @ and import
Answer the question
In order to leave comments, you need to log in
maxsite suggested that "Paths in nested import less files are specified as they are in the main style.less as if they were all on the same level."
The file began to compile normally, but the path to the 2nd level is different, because shared files are called from different places.
In one place it is
@_import "/../../../general.less";
In another place it is
@_import "/../../../../include/static/css/general.less";
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question