Lazy Compilation
When comes to a big project, you may want to split them into small pieces and load on demand. This can be achieved by dynamic imports.
By default, Farm will lazy compile these dynamic imports in development, only compile them when the module is really executed. Lazy compilation can really speedup the compiling of a large project.
Lazy Compilation are always disabled for production build.
Note that it is important to use the dynamic import properly to make lazy compilation work better. For example, if one of your page has a big dependencies, but this dependencies won't be used until this page rendered, then it is necessary to make sure that this big dependencies are dynamic imported, so it won't be compiled util the page rendered.
Configuring Lazy Compilation
Using compilation.lazyCompilation to enable or disable it:
How Lazy Compilation Work
When lazy compilation is enabled, Farm will analyze all of your dynamic import first, for example:
Farm will treat ./page as a module that should be lazy compiled and won't compile it, instead, Farm will return a virtual placeholder module for ./page like:
Above example illustrated a basic structure of that virtual placeholder module. When the placeholder executed, it will request the dev server to compile this module and its dependencies. After getting the lazy compiled result from dev server, the placeholder module will patch these changes to Farm's runtime module system.
