No REPL connection (fails to set port in time) about boot-cljs-repl HOT 9 CLOSED

This appears to be a regression from 0.1.7 to 0.1.8

from boot-cljs-repl.

Confirmed with 0.1.8.

from boot-cljs-repl.

Additionally I've noticed that with 0.1.7, the REPL connection is established only if there is no *.cljs.edn build specified (ie, the default 'main.js' is generated). When I do specify builds, the port appears in the server output but the client-side connection function is never called.

(Using boot-cljs from master, not clojars)

from boot-cljs-repl.

I guess it must be somewhere in this commit.

What's confusing to me is that in the weasel-connection function there is a 0 passed as port when none is specified but this has been the case before that commit as well?!

from boot-cljs-repl.

I just tested this with 0.0-2755 which ships some REPL fixes and that seems to fix the problem. I'll PR the boot-cljs repo. @pandeiro when I made that PR it'd be awesome if you could verify that what I'm saying is correct.

from boot-cljs-repl.

Just tested with 0.0-2760 and works fine. Still prints 0 as port:

boot.user=> (start-repl)
<< started Weasel server on ws://127.0.0.1:0 >>
Type `:cljs/quit` to stop the ClojureScript REPL
Writing boot_cljs_repl.cljs...

from boot-cljs-repl.

REPLs still breaking in projects that use CLJSJS-like libraries.

from boot-cljs-repl.

Is this still an outstanding issue?

from boot-cljs-repl.

Probably not. That new weasel stuff worked well when I tested it and this is really old anyways.

from boot-cljs-repl.