This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-24
Channels
- # architecture (4)
- # aws (1)
- # beginners (76)
- # boot (172)
- # cider (17)
- # cljs-dev (10)
- # cljs-experience (24)
- # cljsrn (45)
- # clojure (129)
- # clojure-berlin (1)
- # clojure-finland (1)
- # clojure-italy (8)
- # clojure-seattle-old (1)
- # clojure-sg (1)
- # clojure-spec (31)
- # clojure-uk (28)
- # clojurescript (88)
- # cursive (11)
- # data-science (1)
- # datomic (44)
- # fulcro (48)
- # hoplon (5)
- # jobs (3)
- # jobs-discuss (1)
- # leiningen (6)
- # luminus (42)
- # lumo (17)
- # off-topic (9)
- # om (29)
- # onyx (15)
- # pedestal (7)
- # protorepl (20)
- # re-frame (24)
- # reagent (46)
- # ring-swagger (2)
- # specter (2)
- # sql (3)
- # uncomplicate (58)
- # unrepl (29)
- # yada (5)
JS People are hard working on ensuring Closure can't support ES modules http://2ality.com/2017/01/import-operator.html 😄
@juhoteperi thats more along the lines of cljs.loader
so not a big deal
It will take some work for our module deps code and for Closure to support that, and analyzing dynamic imports is harder than static
But anyway, that is just a proposal so it is still possible that it won't be accepted
@juhoteperi being stage 3 means it's probably getting into the spec
But that's not a big deal. Dynamic import is for apps not libraries
Similar to goog.modulemanager and cljs.loader
Phew, finalized my abstract for ClojuTRE, now I have proper push to finalize the materials, as I can't cancel this anymore 😄 http://clojutre.org/2017/#clojurescript