shadow-cljs

henrik 2026-05-14T08:07:40.306799Z

I think https://shadow-cljs.github.io/docs/UsersGuide.html#_output_language_options in the docs is now outdated, right? > Important > Note that this mostly affects imported JS code from npm or .js files from the classpath. CLJS will currently only generate ES5 output and is not affected by setting higher options.

thheller 2026-05-15T07:12:15.912389Z

stopped working how? es2018 is a bit conservative, so good to remove that

henrik 2026-05-15T07:13:32.114859Z

The strangest problem. No errors in the logs, completely silent on both backend and frontend, main.js loads, but main.js doesn’t run.

henrik 2026-05-20T07:56:13.489079Z

Btw, this turned out to be unrelated to shadow, complete fluke. Maybe it was a version bump of a lib or shadow itself, but the dev artifact exceeded 512mb uncompressed. In this scenario, it just fails to load silently in Chromium, no warnings or errors.

thheller 2026-05-20T07:56:41.604299Z

512mb? yikes 😛

henrik 2026-05-20T08:21:33.175009Z

Yeah, tell me about it. A fraction of that when compiled with advanced, but in dev it really balloons.

henrik 2026-05-20T08:23:11.929059Z

Also, compressed it’s ~20mb even in dev, which hints that it must be mostly ”air”.

thheller 2026-05-15T06:19:14.598709Z

kind of. the cljs compiler may now generate ES6+ code, but it is still not affected by any of those options

henrik 2026-05-15T06:35:44.724729Z

Right, but: > ClojureScript will use ES2016 moving forward where it delivers value and performance benefits.

henrik 2026-05-15T06:37:03.035139Z

I came across this because we apparently were using :es2018 (I don’t know why), and the app stopped working with the latest version of shadow-cljs. Removing :es2018 and using the defaults made it work again.