OK - finally got it to work! Interestingly running “lein figwheel” picked up some errors that “lein repl + other commands” did not (Such as a config option being in the wrong place in the Project.clj)

@jamesmintram: yep, the next release moves config validation down so that it works at a lower level

That’s awesome! Any advice around it not supporting profile merging? ie any tips in structuring your project.clj to get the benefits of splitting dev/prod config?

@jamesmintram: there is really no need to split out your :figwheel and :cljsbuild configs at all.

they are just data so they won't affect any runtime environment,

:figwheel is devtime only and :cljsbuild let's you have as many builds as you need

@bhauman: Ah OK thanks. That makes sense. It hadn’t occurred to me that the figwheel stuff would be ignored during a production build! I guess all the examples/templates I have seen keep the Figwheel stuff inside of a dev profile. Thanks 🙂

@jamesmintram: which templates? reagent-figwheel is correct. And I'm currently posting an issue on chestnut.

I think I used “lein new reagent” - I can check

Yeah - so

lein new reagent

Cool thanks, posted an issue there as well.