Fork me on GitHub

I have a program that constantly watches changing js files (aka the output of shadow) and produces corresponding artifact out. What’s the recommended way to run it alongside with shadow? Should I run it and shadow in parallel, or let shadow invoke it whenever some cljs file is updated?


@i that is entirely up to you and your personal preference. I personally don't like combining stuff and just let each tool do its thing independently. for releases I typically do npx shadow-cljs release app && other stuff


Is there any file that is always generated in the out/public once the compilation has finished (while using shadow-cljs watch app)? I am looking for a file that I can watch for a different (Python) integration test watcher?


running integration tests against a watch? doesn't sound like a good idea to me?


the output files of your build are always generated though? or the manifest.edn is too?