This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-01
Channels
- # announcements (1)
- # babashka (1)
- # beginners (49)
- # calva (111)
- # chlorine-clover (2)
- # cider (2)
- # circleci (9)
- # clojure (60)
- # clojure-europe (25)
- # clojure-nl (4)
- # clojure-taiwan (2)
- # clojure-uk (10)
- # code-reviews (5)
- # conjure (1)
- # cryogen (2)
- # cursive (1)
- # data-science (1)
- # datomic (1)
- # figwheel-main (1)
- # fulcro (23)
- # hoplon (2)
- # malli (4)
- # meander (1)
- # off-topic (149)
- # other-languages (1)
- # re-frame (40)
- # reagent (27)
- # reitit (2)
- # shadow-cljs (25)
- # slack-help (4)
- # spacemacs (7)
- # xtdb (11)
@mauricio.szabo What's the story with Chlorine/Clover and ClojureScript these days? I'm just starting to get (back) into ClojureScript (after nearly seven years!) and I think I'm most likely to use Figwheel, rather than Shadow, but it looks like that's not supported by Chlorine or Clover -- and I couldn't find an option in Clover to start an embedded cljs REPL (I haven't tried on Atom/Chlorine yet). I'm considering using .cljc
files and a socket REPL via the JVM, but it would be nice to have native cljs support -- is that something I can help with or are there fundamental reasons that the embedded cljs REPL cannot work with VS Code?
(and "Happy New Year!" 🙂 )