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.
stopped working how? es2018 is a bit conservative, so good to remove that
The strangest problem. No errors in the logs, completely silent on both backend and frontend, main.js loads, but main.js doesn’t run.
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.
512mb? yikes 😛
Yeah, tell me about it. A fraction of that when compiled with advanced, but in dev it really balloons.
Also, compressed it’s ~20mb even in dev, which hints that it must be mostly ”air”.
kind of. the cljs compiler may now generate ES6+ code, but it is still not affected by any of those options
Right, but: > ClojureScript will use ES2016 moving forward where it delivers value and performance benefits.
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.