Ah right, I missed that 0.5.13 was released. I've opened
https://github.com/bhauman/lein-figwheel/issues/597 to discuss the caching
issue further.
On Fri, Aug 25, 2017 at 8:44 AM Maarten Truyens <
maarten.truy...@siteffects.be> wrote:
> Thanks for the response!
>
> Isn't that change already activ
Thanks for the response!
Isn't that change already active in I noticed the change in 0.5.13? I
actually tried that release, but it did not make a difference for me. I
still need to have the DevTools visible, with "Disable cache" flagged in
the Network Panel, to avoid situations where a modific
Hi Maarten
Once https://github.com/bhauman/lein-figwheel/pull/586 is released, that
should improve your browser load time somewhat, as you won't need to do
empty your cache and do a hard reload.
On Thu, Aug 24, 2017 at 4:27 AM wrote:
> Shot in the dark, but dependent namespace compilation may b
Shot in the dark, but dependent namespace compilation may be the source of
your CLJS compiler slowdowns if you have tons of namespaces. Try seeing
what happens when you set :recompile-dependents to false in the CLJS
compiler options.
On Wednesday, August 23, 2017 at 11:54:44 AM UTC-4, Maarten T
Thanks, appreciated!
Compiling the CLJ side takes about 30 seconds, a non-optimized CLJS about
60 seconds, and an optimized CLJS about 120 seconds. I am very well aware
that these absolute numbers are not so high, at least compared to languages
such as Scala. However, I perform recompilations s
"My codebase (mix of CLJ, CLJS and CLJS) is about fifty thousand lines of
code, and compilation times are starting to interfere with my workflow
happiness. In addition, Chrome Devtools is becoming somewhat sluggish due
to the high number of separate namespaces loaded through Figwheel."
That's not
