Bug filed: https://github.com/boot-clj/boot-cljs/issues/183
On Monday, February 5, 2018 at 5:22:58 PM UTC+1, Khalid Jebbari wrote:
>
> I managed to create a minimal reproduction repository. It’s definitely a
> problem of Boot-cljs, not of the CLJS compiler itself.
>
> The repo (with problem
I managed to create a minimal reproduction repository. It’s definitely a
problem of Boot-cljs, not of the CLJS compiler itself.
The repo (with problem statement and instructions):
https://github.com/DjebbZ/code-splitting-bug-boot-cljs
Will post on boot-cljs issue too, it may help them spot the
No I'm really lazy loading from another namespace, our `yoda.tracking` where
all happens. This ns doesn't `require` at all the lazy loaded module, it just
`resolve` it. I will work on a minimal repro case based on boot-cljs next week.
Thanks for your attention.
--
Note that posts from new
I don't really understand your example. In your code snippet here it looks
like you're lazy loading the module from the module itself? If that was
unintentional, where is this lazy loading code happening?
Something a bit more minimal and more complete would be helpful.
David
On Mon, Jan 29,
Hello,
I'm trying to package all our trackers code (think Google analytics and the
likes) into different splits so that they don't make base JS package too
big and don't slow down time to interactive. Good idea, right ?
Our strategy is basically to write the trackers code in Javascript first
Hello,
I'm trying to package all our trackers code (think Google analytics and the
likes) into different splits so that they don't make base JS package too
big and don't slow down time to interactive. Good idea, right ?
Our strategy is basically to write the trackers code in Javascript first
