cljs-dev 2025-05-16

about to release 1.12.40, I've fixed a bunch of things in GCL, goog.dom.query is back, goog.isString etc. is back

really, really old libraries like domina work again just fine

❤️ 1

ok 1.12.42, I switched to the shaded dep because the unshaded dep was failing the build - it's not clear to me anymore why the unshaded dep was desirable?

Alex Miller (Clojure team) 2025-05-16T04:02:18.363629Z

if you mean like for data.json etc, because the version you end up with is uncontrollable. if you include data.json and clojurescript, it's not random, but based on stuff you don't always control which one ends up first. If you are using a newer version of a lib with new features and another lib depends on those features, and you specified the newer version of data.json, you might not get it and it's very hard to tell. this happened to people pretty regularly before shading.

Alex Miller (Clojure team) 2025-05-16T04:03:07.004199Z

jars published in Maven should generally never include anyone else's unshaded libs

that's what I mean, we shaded the clj deps, so I don't know why we want unshaded Google Closure w/ all these deps to conflict w/

Alex Miller (Clojure team) 2025-05-16T04:20:39.860849Z

oh, I flipped the question when I read it

Alex Miller (Clojure team) 2025-05-16T04:20:56.826949Z

then yes, I'd say shaded :)

@alexmiller website updates are automatic if I recall?

the post is there, but I guess need a manual thing for the version number on the landing page?

Alex Miller (Clojure team) 2025-05-16T19:59:14.181349Z

that should all be automatic, but maybe that part got broken, I can check

Great news. Just noting the date on the page is 2024

thanks, fixed!

Alex Miller (Clojure team) 2025-05-16T20:07:30.114669Z

updated