This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-10
Channels
- # announcements (2)
- # aws (11)
- # babashka (11)
- # beginners (22)
- # calva (28)
- # cider (1)
- # clj-kondo (3)
- # clojars (14)
- # clojure (41)
- # clojure-europe (45)
- # clojure-norway (1)
- # clojure-uk (2)
- # clojured (31)
- # clojureindia (4)
- # cursive (5)
- # datahike (15)
- # datomic (11)
- # deps-new (11)
- # events (1)
- # holy-lambda (19)
- # introduce-yourself (1)
- # minecraft (17)
- # music (1)
- # nbb (3)
- # off-topic (37)
- # reagent (6)
- # reveal (3)
- # shadow-cljs (46)
- # tools-deps (8)
- # xtdb (22)
Experience report: Converted about 2k loc cljs to be nbb compatible (actually nbb-logseq compatible) - https://github.com/logseq/logseq/tree/master/deps . Overall, the conversion was smooth. The only code that was forced to differ from cljs was default requires for npm libs like https://github.com/logseq/logseq/blob/23e46588b35d85461e93ac470fbb87f16818d45a/deps/graph-parser/src/logseq/graph_parser/mldoc.cljc#L5-L6. Since we are on a fast moving codebase, nbb compatibility could accidentally break so we have a linting task to prevent that - https://github.com/logseq/bb-tasks/blob/main/src/logseq/bb_tasks/nbb/test.clj
Forgot to mention that https://github.com/logseq/logseq/tree/master/deps/graph-parser/test/logseq contains a test suite that runs on cljs and nbb with no difference between the two