Code Splitting With Server Side Rendering
summary
Argument: conditionally load only the modules needed during SSR by detecting environment and loading synchronously on server and asynchronously on client. Demonstrates a vanilla js pattern and then the concrete library path: give chunk metadata to loadable-components, call server-side render to render as a string, and send only the initial chunks. Concrete outcomes: SSR works with code splitting, initial bundle shrinks, and client picks up missing chunks dynamically.
AI-written summary · about
related talks
21mSSR Web Components
25mDemystifying Client & Server Rendering in SvelteKit
13mStraight Talk About Server-Side Rendering
04mA few things to know about SSR
19mAngular Hidden Gems: Hybrid Rendering, SSR and Modern Routing
31mFaster content websites via SSR and progressive hydration of Web Components
12mReact Server Components and SSR: How it Fits
45mGive Me Back My Frontend!