Asset Pipeline pre-processing doesn't clear the cache when dynamic erb is used

Pre-processing in development mode caches after the first call - which
is usually fine - however, when using an erb template with potentially
dynamic output, the cache doesn’t clear.

For example, if I have a javascript file in the asset pipeline called
“time.js.erb”, which outputs an alert with like so:-

 alert('<%= %>');

I only get the time for the first request and all other requests are
the cached result. Surely the cache should be invalidated when the
dynamic erb output changes?

Hello guy, i have this problem and don’t found a solution on search.
Could you tell me how make to resolve this issue?
Thank you.

If you have this file in app/assets/javascript the file will be
only once, in development it is when you request it the first time after
download. In production it will be the time as you precompile it.

In production also it would be contraproductive if you would compile it
everytime, as it would mean to compile everyfile again and again and
concatenize and minify them. Your user would have to download a large
with every request, what would be just against the meaning of the
concatenized huge javascript file.

If you really need that javascript file to be dynamically created with
every request, use it as a view.

2013/5/27 [email protected]