miguelcastillo / bit-bundler-splitter Goto Github PK

you can reproduce it here. take a look at "dest/other.js", which has "Main.js" in it even though the module already exists in the bundle "main.js". https://github.com/MiguelCastillo/bit-bundler/tree/master/examples/splitter

When a split is configured as the last entry and does not match any modules, no context is returned. This causes any previously created splits to not be returned in the final result.

The issue is cause by the subroutine that shuffles modules between bundles because they exist in multiple places and these modules that are getting moved around are actually entry modules that need to execute early before the modules in the bundle the main module just got pushed to.

bit-bundler now provides extra meta data about dependencies that can tell us if a dependency is dynamic or static. It further tells us if the dependency is from an import call. So we now have enough information to be able to introduce auto splitting of bundles at each dynamic module loading.