Carlos Fontes

@Olical Makes sense. I'll only have time to try i.e., pinning an older ClojureScript compiler starting with next weekend.

Gave it a go with a ClojureScript version from 2018 (1.10.145) without success. Tried [:output-feature-set :es6](https://github.com/thheller/shadow-cljs/issues/643) as well, but the situation didn't change. By the way, this is a Reagent...

Why this wasn't merged yet?

Forget about the specific order of commands I said before. I cannot reproduce the issue like that anymore. Regarding an exception I have related to meta that is present in...

Please try a working fork that removes the exit hack and therefore allows use of trampoline: [ccfontes/lein-cljsbuild "0.3.2-no-exit"] Hopefully this hack would be removed from the main repo.

@xavi that's great, thanks! Your links helped me out on this one too. As stated at d836402217d8ce26bddb0283c2fa9eefed66d5f5 - "Without an explicit exit, the in-project subprocess seems to just hang for...

It happened here that, when deploying to heroku, the process hanged at `Compiling ClojureScript` for some minutes, but then completed the compilation and proceeded to other tasks. ``` -----> Deleting...

timed out one time: ``` > lein repl Compiling ClojureScript. Compiling "target/cljsbuild-main.js" from ["src-cljs"]... Successfully compiled "target/cljsbuild-main.js" in 26.958402 seconds. REPL server launch timed out. ``` but next try it...

new record: Successfully compiled "target/cljsbuild-main.js" in 312.549677798 seconds.

For those using trampoline because of the exceeded memory quota on heroku there is the following alternative: using the uberjar branch of [heroku-buildpack-clojure#uberjar](https://github.com/heroku/heroku-buildpack-clojure) . It solved not only boot timeouts...