figwheel-main

figwheel-main http://figwheel.org
cch1 2019-12-02T00:37:24.032900Z

Is there a way to have figwheel-main not try to compile data_readers.cljc` Due to the namespaces of tag implementations not having been required, it leads to noisy errors.

2019-12-02T07:37:11.033900Z

what kinds of compile speeds are people seeing on actual real-life projects? Our figwheel.main setup has gotten quite slow, and I'm wondering if there's anything we can tweak to speed things up

ingesol 2019-12-03T21:58:13.034900Z

On our project I get 2-4 secs on my MacBook 2015. Not very satisfying, so sometimes I use repl evaluation instead

ingesol 2019-12-03T21:59:23.035100Z

I believe this a problem in js as well, maybe some new thinking here is the next cljs killer app?

2019-12-04T07:44:34.035300Z

same as we have. much too slow 😞

2019-12-04T07:44:56.035500Z

on new projects you get sub second updates, I'm curious what it is that makes it slow

2019-12-04T07:45:32.035700Z

I mean, for us it's slow even when I make changes that cause very little compilation

ingesol 2019-12-04T14:53:59.036900Z

Yes, if I change only the main ns, it takes about 2 seconds. If I go deeper into the tree and modify, it can double the time

ingesol 2019-12-04T14:55:27.037100Z

I believe I’ve been told before that this is, among other things, a function of your number of dependencies. Also, someone mentioned that shadow-cljs might have a more efficient way than figwheel-main of tracking modifications and what files to recompile.

ingesol 2019-12-04T14:57:03.037300Z

It’s certainly frustrating, that changing the class of a div takes 3 seconds to re-render when you are a couple of levels down the dep tree

2019-12-02T07:37:47.034600Z

I've tried to offload some source directories to :local/dir deps instead, to avoid compiling them all the time, but it is not giving quite the effect I was hoping for