If Muhammad will not go to the mountain, we must bring the mountain to Muhammad.

ClojureScript has a very specific goal set.
This singular focus is refreshing and frees the project to progress rapidly on core goals, cutting unnecessary burdens. That leaves out features that are rarely needed in "production", like runtime evaluation.

While the "development" and "production" time dichotomy is pragmatic, it is more probability distribution than tautology. If your use case falls in the false end of the distribution, [1] we must bring the mountain to Muhammad. A ClojureScript Compiler-as-a-Service (CaaS) could add back some dynamism.

Happily, a CaaS has more uses than just enabling a poor-mans runtime eval.
CaaS can be embedded, be hosted, and simplify a dev environment.

More importantly, it's a step towards lowering barrier-to-entry to a complex system such as ClojureScript's: install JVM, clone source tree, know a shell, set environment vars, run bootstrap, cross fingers, and you still don't have immediate browser feedback without extra setup or specially modifying your app.
This in comparison to JavaScript: launch browser, open dev console, done. [2]