As we all know, with every development choice, there are new considerations that ultimately emerge over time.
For instance, with a build-step based workflow, your build time can start to take longer, and your compiler configuration can become exceedingly more complex as your project’s source code grows.
Modules don’t require the overhead of a build step, which is great, but loading too many sub-modules at once can create a bottleneck that can increase the time it takes to load your web page completely.
It is possible to get a long way without running into this issue, but if it does arise, cutting down on requests can help.
Think about how you could apply this approach to delivering other payloads such as CSS or icons. You could even add a transpiler if you wanted.
Where we step through the code of an example app using this pattern. Deploy your own Progressive Bundling example app on Begin.