Reduce Payload Size with Inertia.js Partial Reloads and Lazy Props
Use Inertia.js partial reloads with lazy props to fetch only the data your component needs, cutting payload size without new API endpoints.
Loading…
ReadMeFeed / Community knowledge
#partial-reloads
Real questions. Useful conversations. Find the people who know your stack.
laravel
inertiajsUsing Inertia.js Partial Reloads to Keep UI State While Updating Data
Learn how Inertia.js partial reloads let you fetch only the props you need while preserving client‑side state, with a concrete Laravel/Vue example and notes on shallow merge limits.
Refresh One Prop Without Re-Rendering the Page: Inertia.js Partial Reloads
Refresh a single expensive prop without remounting the page: how Inertia partial reloads work over the wire, a Laravel + Vue example with lazy props, and the mistakes that bite in production.
Inertia.js Partial Reloads and Server-Side Rendering (SSR) Data Synchronization
Inertia.js provides a partial reload mechanism using the only property to request specific data keys, reducing payload sizes by omitting unnecessary datasets. When combined with Server-Side Rendering (SSR), the initial page load delivers a fully rendered HTML payload to the browser to improve First Contentful Paint (FCP). A design uncertainty arises when a p
When should a paginated Inertia.js list use deferred props instead of merge props?
Inertia.js transports page props as JSON and leaves date parsing, time-zone conversion and locale formatting to the backend serializer and the client formatter, so regional date handling is not something the adapter itself decides. A more relevant unresolved question is how deferred props should interact with partial reloads and merge-based pagination. Defer