This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-06
Channels
- # announcements (12)
- # asami (3)
- # babashka (59)
- # beginners (20)
- # biff (1)
- # calva (87)
- # cherry (8)
- # clj-kondo (41)
- # clj-together (4)
- # cljdoc (5)
- # cljfx (4)
- # cljs-dev (2)
- # cljsrn (6)
- # clojure (63)
- # clojure-europe (22)
- # clojure-nl (1)
- # clojure-norway (35)
- # clojure-uk (4)
- # clojurescript (5)
- # conjure (2)
- # datalevin (4)
- # datascript (8)
- # datomic (16)
- # events (1)
- # figwheel-main (1)
- # fulcro (9)
- # hyperfiddle (4)
- # introduce-yourself (1)
- # jobs (3)
- # kaocha (10)
- # lambdaisland (2)
- # lumo (7)
- # nbb (1)
- # off-topic (29)
- # pathom (15)
- # re-frame (80)
- # releases (1)
- # remote-jobs (4)
- # shadow-cljs (13)
- # spacemacs (9)
- # sql (25)
- # squint (32)
- # tools-deps (6)
- # uncomplicate (6)
- # xtdb (15)
Just pushed a new version of cherry-cljs to npm. Ported almost all fixes, etc from clavascript. I must say that it's becoming slightly annoying to have to maintain two almost identical code bases so I can't help that splitting some things into a library will make things easier, although there are sometimes tiny differences between the two. @mrdalloca if you want to help out (as you proposed in #clavascript), here are two issues that is just grunt work: https://github.com/clavascript/cherry/issues/57 https://github.com/clavascript/cherry/issues/58
should I submit as PR?
you’d need your own build process for that but given that these tools are themselves build tools may not be too out of reach
@U04V15CAJ it took me a while but now I'm starting on issue 57 😅