if this library is distributed as a jar then it is not possible to tell ahead in which context it will be used. so you either have an option to split the library in two packages (for clj and cljs) or don't try to separate dependencies. first approach will lead to complicated building and releasing phase, second - in some cases will download unnecessary resource.

another option is to make dependency optional for both platforms, same way as clj-http makes cheshire optional. but this is definitely not a very generic solution

I think the latter option is more friendly though

👍 , thanks for the breakdown. I decided to just include the cljs dependency since it's pretty small. I did fork the dependency so that it doesn't include org.clojure/clojurescript so that users who don't care about cljs don't need to grab the cljs compiler.

such users could simply use :exclusions - clojurescript is a particularly usual exclusion (maybe you could declare the exclusion in your project? then consumers become responsible for pulling clojurescript themselves)