This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-20
Channels
- # arachne (11)
- # aws (2)
- # beginners (33)
- # boot (167)
- # cider (71)
- # clara (2)
- # cljs-dev (28)
- # cljsrn (3)
- # clojars (1)
- # clojure (83)
- # clojure-austin (21)
- # clojure-dev (24)
- # clojure-russia (19)
- # clojure-spec (33)
- # clojure-uk (108)
- # clojurescript (114)
- # component (1)
- # core-async (1)
- # cursive (7)
- # datomic (13)
- # editors (1)
- # emacs (15)
- # hoplon (10)
- # lein-figwheel (4)
- # leiningen (3)
- # mount (2)
- # om (134)
- # om-next (4)
- # onyx (42)
- # pedestal (41)
- # quil (2)
- # re-frame (29)
- # reagent (4)
- # remote-jobs (6)
- # ring-swagger (5)
- # untangled (9)
at least on this simple project I have over here it means ~3X faster compile times for cold build
mostly because we no longer analyze ClojureScript files in JARs we look at the cache analysis
I noticed that core.cljs analyzer bug today when hacking the compiler for dependency stats to graph
1.9.293
Compile sources, elapsed time: 59873.374855 msecs
1.9.331 (master)
Compile sources, elapsed time: 67232.714985 msecs
not sure how interested you are in those results since I'm using boot to rebuild the cljs instead of invoking the build api manually
this may or may not translate to faster cold builds that already have analysis caches written to :output-dir
in the project that I was currently working on it did make a huge difference - but I was only interested in cold build with caches - not recompile times or anything like that
So the next step in JS module processing landed in master \cc @bhauman @juhoteperi @anmonteiro
basically you can now specify a directory instead of just single file as a :foreign-libs
entry
all files found therein will be expanded with the same module settings and processing options
ohhh 👍