it doesn't handle publishing at all, you use npm for that. but yes, the compiled output can be published to npm. the JS code that is, CLJS libs are published to clojars usually

and yes, shadow-cljs does all you need to build CLJS based things

@U05224H0W You're wicked fast 🙂 I loved that

Also related, just out of curiosity, isn't clojars supposed to be just for JARs?

(or are we just looking at JAR as a file format here, i.e. as a compressed file formart e.g. zip)

yes, jar is basically just a zip file containing all the files you want published

Aha I see. Any way to search in clojars specifically for CLJS/shadow-cljs packages?

there are no shadow-cljs packages on clojars, there are all generic CLJS packages

I don't know if there is a way to specifically search for CLJS though

So is it the case that currently the CLJS is just mixed together with CLJ packages with no metadata to distinguish between them?

If I were using CLJ on the JVM and I found a package on clojars that seemed to do what I liked, but it had no mention of CLJS that would be inconvenient (and vice versa if I were using CLJS in JS environments)

most libs specify when they are cross platform

but yes there are many CLJ only libs, as they are many CLJS only libs

Thanks so much 🙂 have a great day

While a filter in Clojars would be nice, as a practical matter it's pretty easy to tell whether an attempt was made at clj/cljs interoperability in a particular candidate library: follow Clojars' link to Github and take a quick look in the code repository for ".cljs" or, especially, ".cljc" files among the source files.