https://github.com/borkdude/babashka/releases/tag/v0.0.66

nice about the changes to support different ns per socket :thumbsup: (that's not something that shadow-cljs does unfortunately, making multiple connections to a process less useful -- actually that's the last i checked...may be things are different now) also appreciate the :reload support

all tests pass here for: 55238b52acc086bb08e91161a3bfdba32171e55f

good to hear. thanks to @mauricio.szabo for prompting me about some issues with the socket repl

@mauricio.szabo have you asked thheller about supporting a different ns per socket?

@sogaiu not really, the issues on bb were to support changing ns on a socket repl. Commands like ns and in-ns were failing when connected via socket.

I discovered the issue with per-connection ns after fixing that

I kept track of the current namespace in two places which went out of sync, but now it's only one place.

@mauricio.szabo ah ok, thanks. what i found is that for 2 sockets that are each in a cljs repl, they end up always being the same ns. if you in-ns in one, the other changes too.

cool that things have improved in bb :)

I'm guessing but for cljs it might be related to dynamic vars not being really dynamic vars, since there are no threads, they cannot have a thread-local binding

may be - though iiuc in-ns is "emulated" in the repl, and the repl itself is implemented in jvm clojure.

fwiw planck seems to do it correctly, although it's mostly JS + a bit of C

ah i didn't know that -- nice!

Also tested lumo which also does it correctly, runs on node

just verified for planck -- haven't installed lumo yet

if you have node, it's just npm install -g lumo-cljs

thanks -- i'm building from source.

verified -- lumo seems to work well in this regard. thanks for testing and mentioning these two :thumbsup: