transit is probably possible but still won’t be very efficient since I don’t think you can hook into this globally. So you end up with maybe calling transit once per Object. I did not spend too much time with next.js though, so it may be possible to customize all of this.
After looking at both options however I do agree that we can probably build something more usable in CLJS itself. I may experiment myself a bit given how much of the heavy-lifting shadow-cljs in regards to CLJS/JS already does. Generating a bit of boilerplate code + HTML should not be that difficult.