E.g.

{...
 :output-dir "public/js"
 :modules
 {:shared
  {:entries [my.app.common]}
  :home
  {:entries [my.app.home]
   :depends-on #{:shared}}
  :login
  {:entries [my.app.login]
   :depends-on #{:shared}}
  :protected
  {:entries [my.app.protected]
   :depends-on #{:shared}}

No, but in this case none of my modules depend on one another. They’re essentially independent apps.

Modules are used for dynamic load in one app, different apps should have their own build. localhost:9630 is the default web console of shadow-cljs, you can use it to start/stop your builds.

Ok, thanks - I’ll separate them into different builds then.

no. definitely use :modules

but the difference to regular CLJS is that there is no default :cljs-base module.

Ok, what should I use for the default module, then?

so as @U0G75S29H showed you need to declare one :shared module that all others depend on. you can use :entries []

Ah, ok, I’ll do that, thanks.

that'll move all actually shared code there

So when I deploy a production build, will that load two JS files for each page? The shared and then the page-specific?

in the pages then just load shared.js and the-page-you-are-on.js via HTML

Right, snap.

no need to use the loader.

Ok, thanks, I’ll try that.

So this is what I ended up with:

:modules    {:shared      {:entries []}
             :pay         {:init-fn    site.pay/init!
                           :depends-on #{:shared}}
             :quote       {:init-fn    site.quote/init!
                           :depends-on #{:shared}}
             :buy         {:init-fn    site.buy/init!
                           :depends-on #{:shared}}
             :renew       {:init-fn    site.renew/init!
                           :depends-on #{:shared}}

[:site] Build failure:
Module Entry "site.buy" was moved out of module ":buy".
It was moved to ":shared" and used by #{:buy :quote}.

this means that the site.buy ns was used somewhere in the :quote module. likely a direct (:require [site.quote ...])

you can either make the buy module depend on quote

or move the shared code into an extra ns so it can be moved out

or just combine quote/buy into one

Ah, I see - I’ll play with that tomorrow, thanks.

It’s amazing how much shadow has removed the incidental complexity in my project, it’s very nice indeed.

If I make my quote module depend on buy and shared, then I guess I need to load both in my HTML? i.e. I need shared.js, buy.js and quote.js in quote.html? Or is the shared code all moved out to shared.js?

I remember seeing in the doc that shared code is moved to the leaves as much as possible, is Shadow smart enough to see that shared is common to both buy and quote, and to put the code required by both there?

no you need to load them all. the goal is to move code as close to the "edges" as possible. the goal is to keep shared as small as possible

Ah, I see - thanks.

Is the order of loading the modules in the HTML important? I know I have to load shared before quote, but is there a good way to know that I need (presumably) buy after shared but before quote?

yes order is important. order is logical. all depends-on must be loaded before and that applies to all moduels being loaded

Yes, that makes sense, thanks.

A simple question about the syntax this hook (or hook in generally), this is exactly the same, right ? (defn ^:dev/after-load... vs (defn {:dev/after-load true}...

yes

well no. the map has to come after the name but the ^ comes before 😛

Haha Ok thx 🙂

You can use the :karma target for cli tests (which has a "browser" runner as well IIRC)