hrm turns out we were still doing a lot of unnecessary analysis

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

also there was a bug where core.cljs was getting analyzed unnecessarily

about to push

would like to see people test master

I noticed that core.cljs analyzer bug today when hacking the compiler for dependency stats to graph

pushed please test master if you are able

1.9.293
Compile sources, elapsed time: 59873.374855 msecs
1.9.331 (master)
Compile sources, elapsed time: 67232.714985 msecs

@jr full compile times aren’t going to change

only dev compile times

@jr but also interested in the fact that nothing broke 🙂

https://gist.github.com/JacobNinja/593f6a3162183352b7fa237eb181550e

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

@jr I don’t think those numbers are showing much

yeah I need to enable verbose and see which files are getting re-analyzed

the numbers from top to bottom are consecutive rebuilds of the same file

@jr it just doesn’t seem related to what my latest pushes are about though

I only want info about whether analysis is avoided

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

dang son

all files found therein will be expanded with the same module settings and processing options

consider it somewhat experimental for now

ohhh 👍

I don’t want to say it’s done until the Closure Node module stuff lands which is imminent