@tomi.hukkalainen_slac I'm curious. Did you try shadow-cljs yet? I see that you are struggling to get CLJS+npm working I can tell you with confidence that this would all just work in shadow-cljs. 😉

Oh yes, I didn't ask here yet. I quickly checked the examples and noticed that they were all frontend only

I was wondering if there's a sample project that combines backend too, preferably with lein

just use lein for the backend. no need to change that

The docs seemed to give pretty strong encouragement to not use lein, but I'm guessing shadow can't handle plain clj on its own

you can use lein or tools.deps. I just recommend standalone shadow-cljs since its more tuned and takes care of some other stuff

I'd guess that about half of the people here use lein though. https://shadow-cljs.github.io/docs/UsersGuide.html#Leiningen

How does shadow handle dead code elimination with the closure compiler and es modules?

I'm trying to get to the bottom of where the problem even is, currently

node_modules never use the full DCE and only run through :simple (in shadow-cljs)

but if you require only the "components" you need thats usually good enough

and thats what the JS world does and recommends

getting :advanced working for node_modules is highly experimental and has never worked reliably for me

I though that https://clojurescript.org/news/2017-07-12-clojurescript-is-not-an-island-integrating-node-modules meant that it is doing that

sigh There are too many moving pieces

yeah its highly experimental and alpha. I don't think that anyone has ever gotten that to work. at least I never heard a single success story

it does work in a few isolated cases like just React+ReactDOM

but each package you add makes success less likely