This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-02
Channels
- # aws-lambda (5)
- # bangalore-clj (1)
- # beginners (96)
- # boot (66)
- # cider (39)
- # cljsjs (2)
- # cljsrn (5)
- # clojure (265)
- # clojure-android (1)
- # clojure-france (1)
- # clojure-greece (32)
- # clojure-italy (4)
- # clojure-russia (2)
- # clojure-sg (1)
- # clojure-spec (27)
- # clojure-uk (25)
- # clojurescript (88)
- # cursive (4)
- # datomic (31)
- # emacs (96)
- # hoplon (10)
- # immutant (14)
- # jobs (2)
- # luminus (1)
- # lumo (66)
- # off-topic (128)
- # om (8)
- # om-next (2)
- # onyx (9)
- # parinfer (5)
- # re-frame (37)
- # reagent (16)
- # rum (9)
- # schema (3)
- # specter (34)
- # unrepl (8)
- # yada (21)
@pesterhazy a unrepl implementation for lumo was possible all along but lumo would have to start it because the upgrade strategy doesn't work.
That's what my cljs-repl tries to fix: provide an upgradable socket repl implementation that can be supported by lumo or Planck.
The only thing missing on the Planck side is a way for user code to start a server. For lumo it's solved by node.
ah that's interesting
so the cljs-js-repl repo adds a way to upgrade a socket repl, or does it add a way to start a new unrepl-aware one?
It adds a way to make upgradable repls in the first place. Ideally I'd like it to become part of Clojurescript.
sounds good