hrm? that's possible but are you using the uberjar?

yes, by depending on the org.clojure/clojurescript {:mvn/version "1.10.844"} I guess we get the uberjar?

issue can be reproduced:

$ clj -Sdeps '{:deps {org.clojure/clojurescript {:mvn/version "1.10.773"} org.clojure/tools.reader {:mvn/version "1.3.2"}}}' -e "(require 'clojure.tools.reader.edn)"
WARNING: When invoking clojure.main, use -M

$ clj -Sdeps '{:deps {org.clojure/clojurescript {:mvn/version "1.10.844"} org.clojure/tools.reader {:mvn/version "1.3.2"}}}' -e "(require 'clojure.tools.reader.edn)"
Downloading: org/clojure/clojurescript/1.10.844/clojurescript-1.10.844.pom from central
Downloading: org/clojure/clojurescript/1.10.844/clojurescript-1.10.844.jar from central
WARNING: When invoking clojure.main, use -M
Syntax error compiling at (clojure/tools/reader/edn.clj:75:9).
No such var: err/throw-no-dispatch

Full report at:
/var/folders/c0/hfmx64kj4dx3y8dp772l_s6w0000gn/T/clojure-12053108925244442985.edn

likely the AOT'd code not the uberjar. you can use org.clojure/clojurescript$slim to avoid such conflicts

yes sorry, my bad. the 3fdaabed we tested before already was the change with the uberjar, as @mkvlr point out to me.

unfortunately since that is a different artifact id you'll still very likely get an additional org.clojure/clojurescript from some dependency 😛

would be better IMHO to have the slim as the default org.clojure/clojurescript and a separate opt-in org.clojure/clojurescript$aot but that would have the same issues so nothing gained really

And if you encounter libraries depending on org.clojure/clojurescript, I think it is a good idea to create issue about moving the dependency to dev profile or provided scope or such. Makes it easier for applications to select correct version.

@thheller thank you, I did not know how to get the slim version. @juhoteperi good point, will start with our own libs then 😅

@kommen no change to AOT JAR production as far as I know, that's done w/ Maven plugin

the deps.edn uberjar thing is for tests and alternate consumption

ok

we have 1.10.844 in production now