compiler optionsince v0.0-2911Edit

Employ code-splitting to replace the usual :output-to file with separate logical modules. Every namespace is assigned to exactly one logical module. Code-motion will enable code to be pulled across module boundaries when possible, but this is avoided if the compiler knows it will already be included on the page:

  • :output-to - output file of a module
  • :entries - namespaces to include (modules must have no entries in common)
  • :depends-on - modules expected to be included on the page beforehand
{:foo {:output-to "js/foo.js" :entries #{"my.foo"}}
 :bar {:output-to "js/bar.js" :entries #{"my.bar"} :depends-on #{:foo}}
 :baz {:output-to "js/baz.js" :entries #{"my.baz"} :depends-on #{:bar}}

 :cljs-base ;; <-- leftover namespaces are placed here for you
 {:output-to "js/cljs_base.js"}} ;; <-- specify to change base output


(Only supported with simple and advanced :optimizations).

Including a module's :output-to file on a page will let you run anything inside the namespaces listed in :entries, granted you first include on the page any files in this module's :depends-on entry if present. :cljs-base is usually an implicit entry in :depends-on.

:cljs-base is the default module output to :output-dir/cljs_base.js, with an implicit :entries containing all namespaces in the build not included by the other modules.

A module's :entries must not intersect those of another (i.e. modules comprise a formal partition of the project's namespaces).

Set the top-level :source-map to true to build source maps for all modules.

For dynamic module loading at runtime, see conwip-modules.