Split a Route With PRPL
Use the PRPL pattern to decide what JavaScript and data load now, soon, later, or never.
The account route ships 420 KB of JavaScript for every visitor, including rare billing exports and admin tools. Use PRPL to stage work: preload what is critical, render the first route quickly, pre-cache likely next routes, and lazy-load lower-probability features. The common trap is route-level bundling by code ownership: everything the account team owns ships together, even when the user only needs the current invoice summary. P. Preload critical Preload only the route shell, account summary data, and current invoice code needed for the first useful view. Critical means necessary for the initial job, not merely owned by the route.…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in