I started using meta data to flag some functions in different namespaces. I wrote a shadow-cljs hook that compiles a manifest based off of the metadata of functions in different file. This worked great for development. However, no matter the optimization level I choose, when I go to do a release the value of (get-in build [:compiler-env :cljs.analyzer/namespaces]) is nil. Is this sort of data located somewhere else for release builds? If not, is there a recommended approach for providing such data to a release build? edit: actually the :compiler-env key is not present at all 😞

that info is unaffected by the optimizations and should always be available

which stage are you using it in?

:compiler-env is also present always? otherwise pretty much everything would fail 😛

This is the printed value from (pprint (sort (keys build))) :thinking_face:

the hook runs in :configure and :compile-prepare

at neither of those stages has any CLJS been compiled so :cljs.analyzer/namepaces will indeed be missing or empty?

I guess during development you are relying on caching or watch re-entering the :compile-prepare with data from the previous compile?

haha probably

my hooks currently cause it to always rebuild twice (haven’t looked into that yet) that’s probably what was saving me

are you creating files in that hook that will then be used in the compilation? if so don't 😉

accidental driven development

It generates a routing manifest that’s used by the router 😭

so I can mark which functions are routes for which url

just use a macro?

all of the routes are code split

just use a macro in each split? 😛

then there is a base app that loads the files and renders the route

how would the app know which routes are availble from a macro?

since that macro would only effect the code in the respective split

well what you could do in the hook is generate is manifest that you actually load dynamically at runtime

like .json file or something

I can just only spit the file when :compiler-env is present, and rely on an outdated version for now

hmmm

actually yeah that could work - I guess I could load that from the index.html

I've been thinking about how to do compile-on-demand in hooks

but still no clue how to get that all working properly with caching and hot-reload and everything else 😛

would like to avoid a index.html loading app loading manifest loading split loading component situation 😅

> but still no clue how to get that all working properly with caching and hot-reload and everything else you and me both! 😉

if you generate the .json in a hook

you could inline that json in your HTML

saves that extra load you are worried about 😉

well good thing I also have a hook for inlining build data into hiccup files to build my html

I will do what you said

ty for the quick response

This looks wild, and awesome.

If I want to include re-frame10x as a dependency, am I safe to include it under the top-level :dependencies and rely on it being dead-code-eliminated when it's not loaded in a production build? Or is there a better place to specify it as a dependency?