what is your build config?

this usually just means that this namespace is just not included in the build at all

Currently I have 2 builds: • The main app • One for portfolio

:dev-http {4005 ["resources/portfolio/public" "classpath:public"]}
:builds   {:app          {:target           :browser
                          :output-dir       "resources/public/js"
                          :asset-path       "/js"
                          :module-loader    true
                          :modules          {:diffusion-frontend-main {:entries [myapp.diffusion.frontend.core]}
                                            :nomenclature            {:entries [myapp.diffusion.domain.nomenclature.public
                                                                                myapp.diffusion.domain.nomenclature.genre
                                                                                myapp.diffusion.domain.nomenclature.theme
                                                                                myapp.diffusion.domain.nomenclature.support
                                                                                myapp.diffusion.domain.nomenclature.source
                                                                                myapp.diffusion.domain.nomenclature.fiction
                                                                                myapp.diffusion.domain.nomenclature.scolaire
                                                                                myapp.diffusion.domain.nomenclature.types-fichiers
                                                                                myapp.diffusion.domain.nomenclature.type-produit] :depends-on #{:diffusion-frontend-main}}
                                            :app                     {:entries [myapp.diffusion.frontend.pages.root] :depends-on #{:diffusion-frontend-main :nomenclature}}
                          :compiler-options {:closure-defines     {"re_frame.trace.trace_enabled_QMARK_"        true
                                                                  "day8.re_frame.tracing.trace_enabled_QMARK_" true}
                                            :strip-type-prefixes #{"cljs.pprint"}}}
          :portfolio    {:target           :browser
                          :output-dir      "resources/portfolio/public/js"
                          :asset-path      "/js"
                          :modules         {:main {:entries [myapp.diffusion.frontend.portfolio]}}

yeah. you need to add the lazy loaded namespaces to the entries there

Portfolio live in proper directory in project root :

portfolio/
├── myapp
│   └── diffusion
│       └── frontend
│           └── portfolio.cljs

in the :portfolio build I mean, otherwise it is not included in the build at all

and therefore can also not be lazy loaded

OK, thanks! it seems obvious to me now 🙂

Last thing, Is there a clean solution to avoid duplicate modules settings between builds?

no. managing code splitting properly is a manual task

are you sure you are benefitting from code splitting at all? I mean does the initial app render without triggering a load of the other modules? the setup seems kinda like it would always load everything anways?

Good question. I don't really know if code splitting is currently benefic as this setup is already in place when I started to work on this project. As you say, I think an audit performance will be interesting in future.

May can I ask what about the setup seems always load everything? The different dependencies I suppose.

Is Shadow-cljs report a good start to debug this?

debug what? only you can answer how you use your code. my question was: when the user loads the initial page, does this additional module get loaded anyways?

or is it actually delayed until the user clicks something or so?

since there were so many namespaces that kinda seemed like it was essential to your app in some way?

Yes indeed, this is the case. Some modules is loaded only when user clicks to access some pages and/or advanced features.

but this is not what your module setup says?

you have an :app module, which I took to be the root of your app

that depends on the two others, which means they'll always be loaded as well

but I guess thats not it

First of all, thanks for this very informative exchange.

in case you didn't see yet https://code.thheller.com/blog/shadow-cljs/2019/03/03/code-splitting-clojurescript.html

Already read at some time but thanks I'll refresh my memory.

About the current configuration, here is an loading execution example: 1. Hard reload on the homepage 2. Navigate to cart page load notice.js and panier.js 3. Go to advanced template settings page load gabarit.js

Seems good to me, right?

hmm no clue what notice,panier and gabarit are, they are not defined in the above config

and if the 4 files highlighted in green are all loaded at once, then what is the point is splitting them?

you can add :release {:js-options {:resolve {"pseudolocale" false}}} to the build config

that will remove the lib from the release build, if its actually unused that should be fine

Perfect, thanks @U05224H0W! (also thanks so much for your work on shadow-cljs!)