Code splitting in Proscenium will sometimes include duplicated JS files across page requests. This wouldn't usually be a problem when navigating across pages (MPA), but can be when requesting JS while still on the same page (SPA). We can disable code splitting in Proscenium with the code_splitting config option to attempt to resolve this.
However, by bundling (which Proscenium does by default), and when code splitting is disabled, we may actually increase the chances of duplicate code, as each bundle will contain all the code it needs, and the same code may be included in multiple bundles. And that can sometimes be worse.
It would be amazing if Proscenium should manage and track exactly which files are loaded, and where and how. And across requests (but not pages).
Code splitting in Proscenium will sometimes include duplicated JS files across page requests. This wouldn't usually be a problem when navigating across pages (MPA), but can be when requesting JS while still on the same page (SPA). We can disable code splitting in Proscenium with the
code_splittingconfig option to attempt to resolve this.However, by bundling (which Proscenium does by default), and when code splitting is disabled, we may actually increase the chances of duplicate code, as each bundle will contain all the code it needs, and the same code may be included in multiple bundles. And that can sometimes be worse.
It would be amazing if Proscenium should manage and track exactly which files are loaded, and where and how. And across requests (but not pages).