Clojurians Log v2

@tkjone I had no idea you were making those videos! Awesome job!

Ok, it might be that it's been too long since I've been working on my mac, but I don't recall compile reload cycles in figwheel to be ~32 seconds long... Really wanting to work out what's causing this as it's really disruptive...

[Figwheel] Compiling build dev to "resources/public/js/compiled/out/main.js"
[Figwheel] Successfully compiled build dev to "resources/public/js/compiled/out/main.js" in 31.289 seconds.
[Figwheel] Outputting main file: resources/public/js/compiled/out/main-auto-testing.js
[Figwheel] Compiling build dev to "resources/public/js/compiled/out/main.js"
[Figwheel] Successfully compiled build dev to "resources/public/js/compiled/out/main.js" in 32.904 seconds.
[Figwheel] Outputting main file: resources/public/js/compiled/out/main-auto-testing.js
[Figwheel] Compiling build dev to "resources/public/js/compiled/out/main.js"
[Figwheel] Successfully compiled build dev to "resources/public/js/compiled/out/main.js" in 31.106 seconds.
[Figwheel] Outputting main file: resources/public/js/compiled/out/main-auto-testing.js

Macros are the first point of order usually

@folcon you can use cljs.main and see how long incremental compiles take, to see if this is figwheel specific

but core async is notorious

Is there an easy way for me to get the command for cljs.main?

yeah with -m figwheel.main -pc

it will print out the compile options

with other stuff

remember you don’t need to get it up and running just see how long the initial compile is and then save a file or two and see how long the incremental compiles are

preferably change and save the files that were causing the long re-compiles

you don’t even need the bundle-cmd

but you do need target :bundle and probably :main for sure

What if I'm calling figwheel from the repl? IE:

(require '[figwheel.main.api :as fig])
(fig/start "dev")

(fig/start {:id "dev" :options {:main 'example.core :print-config true}})