Changing an imported file does not cause a re-compile (cache issue ?)

[vicb]

Version 1.0.22.min.js in firefox 3.6.3 on ubuntu 10.04

If the html links to a master.less file which @imports a slave.less:

• any change to the master.less file would cause changes to be taken into account,
• however changes in the slave.less file only would not cause changes to be taken into account, leaving the previous version active.

Probably some kind of cache issue ? (clearing ff cache does not help)

[cloudhead]

Yea, something I have to look into.

[cloudhead]

I made a change in 1.0.30, which refreshes the cache on page load only in development mode. It should work as a temporary fix for now.

[vicb]

That would work great when less.env === 'development' however this is not the case in my development environment as I am using a named based virtualhost on port 80 though http protocol which does not satisfy any condition to make an environment development - but I think is a pretty standard configuration.

Do you consider pulling my commit ?

This would:

• allow config like mine to force refreshing,
• offer a finer granularity for forcing refresh.

The condition could become something like
typeof(less.reload) == "undefined"?less.env==='development':less.reload

[raeldc]

Hi Alexis,

I'm also having some problems related to this issue. It seems that the changes in nested imports don't get recognized right away. Even though I ruined the imported less file, the changes seem to be ignored(using the cache perhaps?).

I just wonder how you cache the compiled less. I don't see it in cookies, and my browser's cache is disabled.

BTW, I found this issue when working on Dominik's Flawless. Check the issue here:
http://github.com/DominikGuzei/flawless.css/issues/issue/1/#comment_383069

Thanks!

[travisdahl]

Whew, thought I was losing my marbles there for a second. Glad I found this ticket to confirm that I'm not totally insane.
Thanks for all your hard work. Having too much fun with less.

[dave-the-rave]

yes, I second this, or 5th it, whatever. Been driving me mad trying to have a random value in an included file. Also, just changing the included file, I have to re-save all of the files which import it to see the changes.

[ahmadnassri]

why not rely on the server's Cache-Control Header along with ETags checks?

[t1mmen]

+1

I was tearing my hair out too!

[leobalter]

This issue made me stop using js to compile in development env and started using the Less App. But my windows mates are f****.

I gotta check @vicb commit or fork to try a sollution.

[cmwelsh]

I came here to report this issue too. I appreciate your work.

[givankin]

yeah, this issue is nearly show-stopper when working with multiple files

[leobalter]

It can be solved with a little trick: before calling less.js file, insert a script with:

less = {}; less.env = 'development';

This will force cache reload.

@cloudhead why not document this and close this issue?

[ahmadnassri]

@leobalter I've just been using

less.env = 'development';

is the first part required?

[leobalter]

it's only a fail safe, as I'm proposing to set it before loading less.js, you can get a 'less is not defined' error without setting it as an object.

[neonstalwart]

@ahmadnassri without less = {}; you're likely to get a javascript error since you're trying to set a property on an undefined variable.