:preamble only respected with :advanced compilation? about chestnut

[plexus]

I thought it was only because we use optimizations :none. I thought it did prepend in :simple or :whitespace, but I could be wrong.

[martinklepsch]

You're right. Anything :optimisation setting that's not :none will prepend the files in preamble. This could be confusing but probably it's ok for now. Closing...

[plexus]

Ok... is there a sensible way to add this to the FAQ? Basically we use :none because it's required by Figwheel so it can reload individual files. It's not commonly used in general.

[martinklepsch]

I mean you could add it but it's more of a cljsbuild thing than chestnut specific. Not sure if it belongs there. On a side note I've grown tired of figwheel. Especially when experimenting with a browser repl the complete re-evaluation on save is annoying. Ever considered to make it optional? (I kind of see how this could be a super minimal template just with some great documentation on how to integrate some popular bits and pieces)

[plexus]

It's kind of a key component of the thing :) but I definitely need to make it easier again to run without figwheel

[martinklepsch]

Yeah, I see that. And it's fine when people work that way but I'm more used to eval from emacs. :-)

[martinklepsch]

I'm hijacking this thread but whatever: this is neat as well: https://github.com/immoh/lively
Does the things figwheel does without obfuscating the general process.