@folcon @dominicm Yes it works now. I don’t have a lot to report as in the end I just worked through the figwheel-main testing docs which do apply equally well when :target is set to :bundle. The main gotcha is the :output-to and :final-output-to settings.

These are set in test.cljs.edn to

:final-output-to "resources/public/cljs-out/test/main_bundle.js"
 :bundle-cmd {:none ["npx" "webpack" "--mode=development" :output-to "-o" :final-output-to]};

:target-dir "resources"

But it’s easiest to check you are generating sane output paths with the -pc switch.

The apparent cacheing issue was nothing to do with cacheing.

I was using Calva jack-in in vscode, and there are a couple of subtleties there as mentioned above. You must generate a final webpack main_bundle.js before using a calva jack-in repl as calva will not proceed to make the webpack bundle. The neat thing is that once you have a webpack main-bundle it will work with the calva jack-in outputs so long as you haven’t added new scripts. So follow the figwheel docs to generate the bundle, and then you switch to a jack-in repl for nice inline evaluation.

There may be a way to persuade calva to run the npx webpack command after jack in - I haven’t investigated that.

There might be a way to persuade the Calva team, at least. 😎

@grumplet would you consider writing some doc page for http://calva.io about the ways to currently work with this?

Sure - I could try and put something together if it’s helpful.

Oh, yes. Super helpful!