Imports are not updated when recompiling via the same (?) less object

[xinglie]

bug report
I write a compile tool for my project, it depend less.

my project style folder and files likes

- styles
   _utils.less
   index.less

and index.less　content is

@import "./utils"

I use less api to compile the less files like

let less=require('less');
//....
less.render(indexContent,options,(err,result)=>{
       console.log(result.css)
});

when i change _utils.less　content , the above code will automatically execute

but since 3.0.x , when i change _utils.less content ,the result.css is the first time result, whatever change how many times.

but 2.7.x is ok, when i change _utils.less content ,the result.css also changed.

[seven-phases-max]

Sounds similar to gulp-community/gulp-less#283.
I guess in a these "auto-watch" cases it's the same Less object used to compile each update, right? Then I guess it's something with not reseting some imports cache between different render calls or somewhat like that.

[xinglie]

@seven-phases-max yes,use the same Less object to compile each update.
i am not use gulp-less tool, i use less api directly .
it seems less cache the result and not update correctly

[seven-phases-max]

So the quick workaround (until the bug is fied) in your case wil be in:

require('less').render(indexContent,options,(err,result)=>{
       console.log(result.css)
});

[shobhitsharma]

Yes, it seems the issue lies in this commit where the calltree is manipulated based on arguments a48c24c#diff-a6b31db4e862654ae597161e441689bb

[seven-phases-max]

it seems the issue lies in this commit ...

Hmm, honestly there I can't see anything that could affect imports...

[tiodot]

In Node environment, manual clear less compile cached file:

const less = require('less');
const fileManagers = less.environment && less.environment.fileManagers || [];
fileManagers.forEach(fileManager => {
     if (fileManager.contents) {
               fileManager.contents = {};
     }
});

[TigersWay]

Thanks @tiodot it seems to be working so far... But hope we'll get a "cleaner" way soon!

[matthew-dean]

It might have something to do with these lines added for 3.0. https://github.com/less/less.js/blob/master/lib/less/tree/mixin-definition.js#L9

Try removing the specific if/else to just the else statement and see if the problem still happens. If it doesn't, this optimization may need to be removed. However, what would be more ideal is clearing the file manager or any internal cache per new parse/render call.