What does your development workflow for CLJS browser extensions look like? Do you have to rebuild and reload the extension on your development machine each time you change the code? Is it possible to use Figwheel when writing browser extensions?
This system has some disadvantages, though. The main one is the glacial feedback loop - due to strict CSP restrictions in web extensions, I had trouble compiling the CLJS with {:optimizations :none}, so each save-compile-reload cycle takes ~30 seconds from when I save the source file to when I see the results of the change in the browser. I also did not figure out how to set up a REPL environment connected to the code running in the web extension.
Lots of room for improvement here, basically.
[0]: https://github.com/binaryage/chromex-sample#chromex-sample-p...
[1]: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Ge...