Thomas Heller

Or is this just a communication problem? I added the `:ssl false` option in https://github.com/thheller/shadow-cljs/commit/cda1b21b2b1c99e5dee3a8797316b1d444b67bd7? Seems like I missed to reference the issue in the commit message? I maybe wrongly...

@JeromeDane do you actually consume separate namespaces directly from the JS side or is there a singular entry point that "bridges" the JSCLJS worlds? a) ``` // src/foo.js const {...

The intent of that log line is something you can actually click and open a browser on. http://0.0.0.0:9630 does not work, that is why the replacement is done. Not a...

This still doesn't clarify anything about why showing http://0.0.0.0:9630/ over http://localhost:9630/ changes anything? Neither will lead to the repl.it host? > Repl.it documentation says: expose one port on 0.0.0.0 and...

I'm lost. What is the problem? You don't want the shadow-cljs server exposed? You already had the fix for that in the initial post?

I can't remember exactly but I think the reason I didn't bother with source maps was that karma will process and rewrite the JS anyways and in the process discard...

Currently there is a hardcoded timeout of about 15sec on the server side that kicks runtimes that don't respond to heartbeats in that time. Usually that is enough since something...

Actually I forgot that there are various other reasons the heartbeat does what it does. Mostly around proper handling of websocket reconnects after Sleep since each Browser/OS seems to handle...

A basic version is already supported for `:node-test`, eg. `node out/test.js --test=some.ns/foo-test`. See https://github.com/thheller/shadow-cljs/blob/8169e663c0338ab01b31726b0cfcd7005563c581/src/main/shadow/test/node.cljs That could be smarter of course. PR welcome.

Can you write this as a standalone ns that doesn't use `shadow.test.node`? Just copy whatever you need from it over and adjust. I'd be open to an option that keeps...