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
#lazy-props
Real questions. Useful conversations. Find the people who know your stack.
laravel
inertiajsInertia.js lazy props SSR hydration timing mismatch
Context Lazy props in Inertia.js allow controllers to defer non-critical data so the initial server response omits it, reducing payload size and server render time. This directly lowers compute and bandwidth costs for low-traffic workloads. Constraint When server-side rendering (SSR) is enabled, the current v1.x behavior treats lazy props as client-only. The
Inertia.js partial reload shallow merge replaces nested objects entirely
Context Inertia.js partial reloads via Inertia.visit({ only: [...] }) perform a shallow merge at the top level of page props. When a requested prop contains nested objects, the entire nested structure is replaced rather than deeply merged. This behavior is documented but leaves developers without a built-in strategy for preserving unrelated nested fields dur
Partial reload `only` option behavior with lazy, deferred, and shared props
Goal: determine whether the `only` filter applied during a partial reload also limits shared middleware data and whether lazy or deferred props are treated as already requested when omitted from `only`. Constraints: the `only` option is scoped to a single request, does not persist across full navigations, and its interaction with lazy props (evaluated on dem