leonoel/missionary

Large dependency: missionary dependency grows uber jar by 26 MiB

lowecg opened this issue · 3 comments

We're hoping to use Missionary using the Clojure runtime on AWS Lambda. How we're running Clojure on Lambda involves compiling the app to an uber jar. Typically our app uber jars are about 18MiB which includes Clojure runtime, Cognitect AWS and a few other deps, but adding the Missionary dependency balloons this to 44MiB.

Much of the size comes from a transitive dependency on ClojureScript via cloroutine.

I see there is an issue for this already. From the ticket, I note the dependency arises from the requirement for cloroutine to support analysing ClojureScript from Clojure. Unless I'm mistaken, this doesn't appear to be a scenario that would happen from Missionary: its runtime is either CLJ or CLJS.

Is there anything that can be done to prevent having to carry the weight of ClojureScript around for Missionary running in Clojure?

Fixed in b.36

Thank you, Léo