Thank you @thheller
So this ought to work then?
clj -T:build:app uber
(I mean, it seems not to be throwing the same error.)
This may be a stupid (or irritating, I’m sorry) question. But if cljs.build.api has nothing to do with tools.build, why does it rely on a classpath sent as an argument to a tools.build script, for the dependencies? Why aren’t these an explicit argument to the cljs.build.api/build function? In the same way that the compile-clj function takes the “basis” as an explicit list of dependencies?
But I guess, is the take-home message here - for slow people like me, and maybe all the other n00bs trying to get this stuff to work - that actually Clojure and ClojureScript are now two entirely distinct communities and projects who aren’t really coordinating or trying to make their things work together? Or give a consistent build experience across the two languages?