Thomas Heller

I could add a no-ping config option if that would help. Also technically if you can open a websocket you have access to everything `cljs_eval` uses. So you could just...

I'm working on [shadow-cljs](https://github.com/thheller/shadow-cljs) which is a build tool for ClojureScript and I'm adding proper support for `react-native`. This is all working fine already with the exception of source maps....

That example was from rebel-readline + figwheel. Didn't involve shadow-cljs at all.

If you look at the implementation of `enable-console-print!` you'll see that it unconditionally sets `*print-fn*` and `*print-err-fn*`. `shadow-cljs` does set its own print-fn on load which will not only print...

Since names are important. Here are the terms I currently use. Suggestions welcome. ## Runtime As explained above. Basically anything that can `eval` JS code and is connected to a...

I already mentioned my reservations about this in the #cider slack but let me repeat it here so it doesn't get lost. The problem with `:cljs/resume` is that there may...

`shadow-cljs` does not support `:foreign-libs` and I don't think it is a good idea for figwheel to bundle its own version of those dependencies. In shadow-cljs you can fix this...

I guess the usual CLJSJS compatibility method can also be used here. Similar to https://github.com/thheller/shadow-cljsjs/blob/master/src/main/cljsjs/marked.cljs

The CLJS REPL has some other hidden "problems" in that `print` and `eval` happen in the JS runtime. This makes a custom `eval` and `print` tricky without having the code...

As far as the output streams go, it would probably be useful to make them thread aware to avoid garbled output like ``` user=> (dotimes [x 10] (future (Thread/sleep 1)...