Figwheel always reloads dev.cljs

[tuhlmann]

I'm setting up a simple figwheel project using lein new figwheel fig1, then doing a lein figwheel.
This starts the app and I can change something in core.cljs and the app gets reloaded. I just don't understand why it also reloads dev.cljs:

Edits to this text should show up in your developer console.
utils.js:49 Figwheel: trying to open cljs reload socket
utils.js:49 Figwheel: socket connection established
utils.js:49 Figwheel: notified of file changes
core.js:48 xEdits to this text should show up in your developer console.
utils.js:49 Figwheel: loaded these files
utils.js:62 ("fig1/core.js" "fig1/dev.js")

I have this same problem with a lein new reagent project I'm trying to set up. In that case it tries to rebuild the Weasel connection each time I change something in core.cljs. The workaround I found is to add ^:figwheel-no-load to dev.cljs.

Am I doing something wrong?

[bensu]

dev.cljs gets recompiled every time because it depends on core.cljs and a new feature of the ClojureScript compiler is to recompile dependent namespaces to avoid stale code and inconsistencies. This is desirable behavior.

If you want to avoid compilation it's fine if you use ^:figwheel-no-load. In case you also need reloading in dev.cljs, but want to keep the Weasel connection, try defonce on an atom that remembers if Weasel is connected. That way, dev.cljs will be reloaded but Weasel's connection won't notice. If you run into trouble we could make a pull request to reagents template.

[tuhlmann]

Thanks for the explanation!

[bhauman]

It's also important to note that adding :recompile-dependents false to your build config disables this behavior. I'm starting to think that this should be the default for figwheel builds.