This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-02
Channels
- # announcements (3)
- # aws (3)
- # bangalore-clj (1)
- # beginners (88)
- # boot (7)
- # braveandtrue (10)
- # cider (6)
- # cljdoc (8)
- # cljsrn (3)
- # clojure (33)
- # clojure-germany (2)
- # clojure-italy (1)
- # clojure-spec (44)
- # clojure-uk (8)
- # clojurescript (14)
- # datomic (5)
- # emacs (6)
- # events (1)
- # figwheel-main (8)
- # fulcro (9)
- # leiningen (11)
- # lumo (3)
- # off-topic (119)
- # parinfer (2)
- # pedestal (1)
- # re-frame (11)
- # reagent (12)
- # shadow-cljs (162)
- # unrepl (4)
Eg: Does core.async work in nodejs, or do we need to use a library like https://github.com/mfikes/andare
Exactly, it’s for Lumo/Planck. Core.async works in browser, on node, and on plain old JVM. Yes, CLJS libraries will work fine with Node, as long as they don’t specifically target browser tech. For example, Reagent has some stuff that relies on the DOM API, and other parts of the lib (for server-side rendering) that work fine on Node.
That's what I love about Clojure, it can work in Java, JVM, CLR, browser, nodejs, even python (more like Lisp-like
).
trying out clojure.pprint, I don`t understand how I can use the pprint-indent function, for instance:
[:pre (with-out-str (p/pprint-indent :block 10)
(p/pprint (:db @db/app-db)))]]])
@priornix the reason that library exists is core.async relies on certain behavior in the compiler for ClojureScript on the JVM that can’t (or is difficult to) be reproduced when using a bootstrapped ClojureScript compiler
@lilactown Got it. I guess not all CLJS libraries are self-hosted or bootstrapped compatible then