✳flâneur — a map of the web's best reading

lukeed/webpack-route-manifest: Generate an asset manifest file, keyed by route patterns!

github.com · 1,407 words · saved by 1 readers

Modern applications (should!) take advantage of route-based code splitting. This enables an application to be compartmentalized into smaller, highly relevant "chunks" for a particular section or feature of that application. By default, this means that your application is only giving its client(s) the code it needs for that page. The Problem While amazing, this isn't (yet) a perfect solution. The client wants to navigate to other pages! In a default, code-splitting configuration, when the client goes to a new page (eg; /blog), the blog page's assets only start downloading after the click has been made. What this means is that our super speedy and state of the art application is at the mercy of the client's network connection. Our client is staring at a loading screen/spinner — or worse, a split-second flash of the loader — until the blog's code has loaded. The Solution With this plugin, you regain control of your application's assets. 💪 You are given the knowledge of exactly which file

webpack-route-manifest Generate an asset manifest file, keyed by route patterns! The Context Modern applications (should!) take advantage of route-based code splitting. This enables an application to be compartmentalized into smaller, highly relevant "chunks" for a particular section or feature of that application. By default, this means that your application is only giving its client(s) the code it needs for that page. The Problem While amazing, this isn't (yet) a perfect solution. The client wants to navigate to other pages! In a default, code-splitting configuration, when the client goes to

Explore this link on the map →

related reading