Here’s a tough question. First some background. I have been using mies
template for CLJS development because, many moons ago when I tried figwheel
on my rather hairy web framework, it threw compile errors where the mies
build was OK. I saw there was the new “main” release and gave it a try and it seems to be running fine.
So the question is, does this sound right? Were any compilation issues addressed in the new release? My code is pretty crazy, with macros writing macros. Just curious mind you.
It seems possible, but your code probably works with the current version of lein-figwheel as well. Or you found a bug in lein-figwheel.
it may have just been a classpath thing created by introducing it into an already complex leinigen file
maybe if you had used figwheel-sidecar without the leiningen plugin it would have worked fine
@hiskennyness but its hard to really guess
figwheel-main eliminated a lot of complexity
and dependencies
Understood on “hard to guess”. 🙂 Congrats on the new release!
Small, unresearched datapoint: I was redoing my project with a clean start and decided just for the heck of it to try figwheel classic: no luck. Repeated fresh start with “main” and no problems.