yes, seems so.


nothing special, unbuntu 16.04 with firefox and chrome


I'm able to reproduce the issue on Firefox all the time, and sometimes on Chrome.


Notice in your last trace that on line 223 figwheel.repl/setup returns true, while in my case it returns {25535 #, 37797 #, 11110 #, ...}


submitted an issue

roti 2019-07-28T11:59:05.029400Z

I'm having problems getting figwheel to autoload my code. the re-rendering happens (I set up a figwheel hook, which works), but the new component version is not active, the old one is still references and used. any suggestions how I might get to the bottom of this?

roti 2019-07-28T11:59:21.029600Z

roughly the setup is following: the root component is app, is uses another component foo. when inside the figwheel dev repl, I change component foo, figwheel loads it automatically, and it is available (if I have a look at it inside the repl). however, app still references the old foo. strangely, figwheel says it loads the namespace where app is, but somehow app has a reference to the old foo

roti 2019-07-28T11:59:38.029900Z

(i'm using reagent)

roti 2019-07-28T12:04:33.031200Z

when figwheel says in the browser log: [Figwheel] loaded (foons barns), does this mean that the entire namespace foons and barns were compiled and hotloaded?

roti 2019-07-28T12:13:49.032200Z

nevermind, I found the problem, there was a defonce in between the referencing from app to foo 😋