Closed arichiardi closed 6 years ago
Each build runs isolated and does not share resources with other builds. That is by design and probably not changing anytime soon. Cache invalidation is hard enough as it is and building a cross-build cache would only make it harder.
Yes everything is compiled twice (once per build) but with the proper caching in place that should never be an issue?
That being said why not create one node-script which you call by bin/script create-publish-pipeline ...
or bin/script assert-environment ...
and do the dispatch manually in :main cd.core/main
?
I prefer to keep them separated, I wonder if 30 seconds sounds like normal when compiling one single file with a couple deps. I will try to enable verbosity and see what is cached and what not just to make sure. Thank you!
All seems good, with :whitespace
the release build was reduced to around 20 seconds. Closing.
Hi all and Thomas, A hopefully small feature request as cropped up today.
I have two scripts in my
shadow-cljs.edn
:The both live in
cd.core
. The problem is that when I doyarn shadow-cljs release :cpp :aenv
I see:Which seems to compile the namespace twice. I know that there is caching so I am not sure detecting and avoiding compiling twice would speed up things, but I am opening this issue nonetheless just to talk about it.