@arohner: There are really good reasons for this. Speed being of primary importance. Fast reload times are important.

I’ve been dancing for quite some time around a pesky issue in cljs compiler I believe. My tests look like this[1] and that code desugars into one giant go block with long list of async calls (yep, those <!* things) I’m running into cljs compiler stack overflow errors when the list of async calls gets too long. I had to introduce chunkify macro[2] which works around it by breaking large go block into multiple smaller ones. I have a feeling that this could be related to CLJS-365[3] or something similar, because the number of commands where it breaks is 18 which is close enough to 20 🙂 Any insights? [1] https://github.com/binaryage/dirac/blob/master/test/browser/fixtures/src/tests/dirac/tests/tasks/suite01/completions.cljs [2] https://github.com/binaryage/dirac/commit/cce56470975a287c0164e6f79cd525d6ed27a543#diff-db6e7d7c1fc803fc1e362d704dce1d5bR30 [3] http://dev.clojure.org/jira/browse/CLJS-365

aren't docstrings supposed to be excluded when building a production cljs app with advanced compilation?

@joost-diepenmaat: docstrings become JS comments, and yes those will be removed

if you have docstring strings in your advanced output it’s because you’re dumping vars somewhere

make sure you aren’t doing that or accidentally including your test namespaces etc.

@dnolen: yeah I just figured out I seem to be building a different build (or multiple ones)

having a hard time ensuring lein ring uberwar includes the correct (and only the correct) build.

tweaking leiningen really is no fun at all

You can now fool around with cljs.spec in the Replete iOS ClojureScript REPL https://twitter.com/mfikes/status/739539963222560770

@mfikes: nice!

@joost-diepenmaat: fwiw this is why I usually don’t try to get Lein to do everything - usually some combination of bash + Lein to do what I want.

or bash + plain old Maven

Hey all, don't forget to give the new figwheel 0.5.4-SNAPSHOT a try. Perfect thing to do on a Sunday ... I'll take reports here if anyone has immediate problems.

I'm trying to eliminate some of the library load conflicts. I think I have eliminated/fixed a big part of the problem.

@bhauman: new warnings in repl are awesome

excellent 🙂

@mathpunk if you're ending the process after compiling your file, then you need to send whatever result you want to stdout in order to see it when node exits. Console.log works

In your script handle it same as the error.