Fork me on GitHub
#lein-figwheel
<
2017-03-01
>
isak16:03:22

@shaun-mahood I have confirmed that it is the figwheel process (java.exe) that is hanging on to these files using process explorer

devth19:03:33

occasionally i cause a client-side error that appears to prevent fighweel from reloading. anyone else experienced this, or tried to detect errors? solution is usually to fix the problem and hard refresh. would be awesome if figwheel could detect this and tell the user to reload

jdkealy19:03:23

anyone have suggestions for debugging a slow reload? CSS is pretty instant, cljs changes take 5-6 seconds

isak20:03:16

@jdkealy how many files get reloaded for cljs changes? maybe someone went nuts with ^:figwheel-always

shaun-mahood20:03:57

@isak: Probably worth filing an issue with relevant details. Is it something you want to put any time into fixing, or are you happy just knowing what's going on?

isak20:03:00

@shaun-mahood will do. And yea maybe, will have to try to get an overview of the code

jdkealy20:03:26

@isak how can i tell how many files get reloaded ?

isak20:03:01

@jdkealy if you check the devtools console, it gives you a list of the files it reloads

jdkealy20:03:53

the devtools console is just the chrome console with devtools installed ?

isak20:03:01

just normal console should show it

jdkealy20:03:09

it appears to only be loading a single file

isak20:03:04

hm then i'm not sure, I had the same problem before, but then it was because of that. https://github.com/bhauman/lein-figwheel/issues/88

isak20:03:18

(big list of files, i mean)

uwo22:03:20

so, has anyone encountered anything like the following? I suspect I’m misconfigured somehow. When I access my app the first time it works and reloading works as well. However, after triggering a hot reload, and then refreshing the page (F5), figwheel’s websocket connection disappears, and I also get the error goog.require could not find: figwheel.connect.build1

uwo22:03:33

(I do have multiple builds going on simultaneously)

uwo22:03:04

and I start figwheel with (figwheel-sidecar.repl-api/start-figwheel! "login" “build1" “imageviewer”)

uwo22:03:59

the problem goes away if I just build one of the targets with (figwheel-sidecar.repl-api/start-figwheel!)

uwo23:03:56

just figured it out. sharing output-dir across builds appears to work at first, but puts things in an inconsistent state (as you might expect!) https://github.com/bhauman/lein-figwheel/issues/453