or just a :post-process-hooks [processor1 processor2] where each "processor" is a function takes the compile configuration and has the compile-env already bound.

@bhauman you are basically describing the idea behind shadow-cljs … thats why it has :target :browser, :node-library, :node-script, :npm-module and can easily be extended to more

:target basically defines how the final code is bundled together and takes different configuration accordingly

https://github.com/thheller/shadow-cljs-examples/tree/master/cljs-react-native-app

the example is a bit old but it is create-react-native-app out of the box with no modifications working with specially bundled CLJS code

@bhauman not particularly interested in a public thing - if there’s some internal hook you’d like to see, then we can talk about that

@thheller I will look at that

@dnolen coolio

@alexmiller so the only enhancement here is to look for the cljc as well right ?

yep

aha , I was a little bit confused over this

I mean in Clojure

I have no idea in CLJS

thanks