This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-05
Channels
- # announcements (1)
- # babashka (6)
- # beginners (31)
- # calva (23)
- # cider (38)
- # clj-kondo (98)
- # cljs-dev (3)
- # clojure (56)
- # clojure-australia (2)
- # clojure-europe (14)
- # clojure-italy (1)
- # clojure-nl (2)
- # clojure-spec (17)
- # clojure-uk (27)
- # clojurescript (45)
- # code-reviews (1)
- # core-async (26)
- # core-logic (10)
- # cursive (11)
- # data-science (9)
- # datomic (7)
- # deps-new (4)
- # devcards (1)
- # emacs (4)
- # etaoin (2)
- # fulcro (14)
- # jobs (1)
- # kaocha (1)
- # leiningen (50)
- # malli (3)
- # parinfer (1)
- # pathom (7)
- # reitit (4)
- # remote-jobs (1)
- # reveal (45)
- # shadow-cljs (59)
- # sql (97)
- # tools-deps (1)
- # uncomplicate (4)
- # vim (18)
I'm sorry I can't be more helpful in this case, but this is one of the reasons we started work on kaocha-cljs2 and funnel, with kaocha-cljs it's super hard to debug stuff, since it's all completely opaque. It doesn't help that the node repl-env launches node and effectively throws away its stdout/stderr. It loads some code to redirect stdout/stderr over a network socket (IIRC, not sure if it's using a websocket or something else), but if anything goes wrong there and node prints out an error message and exits, you never get to see that.