This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-01
Channels
- # beginners (133)
- # boot (59)
- # cider (5)
- # cljs-dev (30)
- # cljsrn (23)
- # clojure (212)
- # clojure-austin (3)
- # clojure-brasil (1)
- # clojure-chicago (5)
- # clojure-italy (10)
- # clojure-russia (5)
- # clojure-serbia (1)
- # clojure-spec (34)
- # clojure-turkiye (2)
- # clojure-uk (132)
- # clojurescript (163)
- # clojutre (1)
- # cursive (5)
- # datomic (58)
- # emacs (42)
- # events (1)
- # graphql (26)
- # hoplon (16)
- # jobs (1)
- # lumo (27)
- # numerical-computing (3)
- # off-topic (127)
- # om (9)
- # onyx (24)
- # re-frame (20)
- # reagent (20)
- # ring-swagger (14)
- # sql (19)
- # unrepl (28)
- # untangled (3)
- # vim (8)
- # yada (17)
Is cljs.analyzer
only required in om/next.cljc
because of self-hosted cljs?
Requiring cljs.analyzer
in om/next.cljc
adds ~92KB uncompressed to advanced compiled js.
If it's only there for self-hosted cljs, is it possible to some how not include it when one knows the code won't run in a self hosted environment?
@petterik it’s not there for self-hosted
I presume that the fact that the file is cljc
makes it be included in the CLJS build
if you use the JVM compiler, we only use the analyzer during defui
macroexpansion
I agree that it shouldn’t be included in the output but I don’t know how to fix