How To Build CLJS Cache Files ?
superstructor opened this issue · 3 comments
Issue
How to build CLJS cache files ? For example if one wants to upgrade the version of re-frame used.
Files of Interest
So far have found:
This contains the dependencies to be cached used to build the class path with lein classpath:
These both appear to be different types of cache build scripts:
Issues of Interest
Questions
It would be extremely helpful if anyone has information on the following questions. This will help me understand enough to get the process working, fix it if required and document it.
In short, any pointers in the general direction of what needs to be generated and the intent of the scripts in question will help.
-
What is the history or intent behind the two build scripts ? One is Lumo-based and the other JVM-based ? Does one supersede the other or are they both used together to generate different files ?
-
How have these scripts been run in the past ? I suspect via a REPL ?
-
There are
viebel/forks for many dependencies (e.g. re-frame, http-fx, reagent, gadjett, poppoa etc) but in some cases there are no visible customization ? E.g. for re-frame it is obvious in viebel/re-frame@eb34941 which I can work to upstream today8/re-framebut http-fx contains no changes vs upstream ? Are there changes missing from GitHub ? -
scripts/generate-clojure-spec-cache.cljsis named 'spec-cache' but appears to generate more than just spec-related cache files ? Is it intended just for cljs.spec or is it simply misnamed ? -
There appears to be special-cases around cljs.spec, test, clojure.template ? Anything a Klipse user re-generating cache files needs to be aware of to make it work ?
Thanks!
Hello @superstructor
This part of Klipse is not well documented.
The code and docs relevant to your issue is located in cljs-analysis-cache repo.
Please take a look there and raise again questions that are not answered there.
I would be more than happy if you could contribute to documenting and improving the cache mechanism in Klipse.
This issue is now published on WorksHub. If you would like to work on this issue you can
start work on the WorksHub Issue Details page.