Refresh Only What Changed: Inertia.js Partial Reloads with only and except
Use Inertia.js only and except to reload specific page props without resending the entire payload.
Loading…
ReadMeFeed / Community knowledge
#partial-reload
Real questions. Useful conversations. Find the people who know your stack.
react
inertiajsInertiaJS: Choosing Between Partial and Full Reloads for Shared Data
Decide when to refresh only specific shared data with Inertia.reload({ only: [...] }) versus a full page reload, with validation steps.
laravelCutting Payloads with Inertia.js Partial Reloads
Learn how Inertia's `only` option lets you fetch just the props you need, keeping client‑side state intact while shrinking network payloads.
Use Inertia.js Partial Reloads to Cut Bandwidth: The 'only' Prop Explained
Learn how Inertia.js’ ‘only’ prop lets you request and render just a component’s props, saving bandwidth and speeding up navigation in Laravel or Rails apps. See a step‑by‑step example, trade‑offs, and how to test it.
Using InertiaJS Partial Reloads to Keep Heavy Dashboards Responsive
Learn how to update only the data‑heavy parts of an InertiaJS page with the `visit` method’s `only` option, reducing payload size and avoiding unnecessary UI resets.
Unresolved need for a global cleanup hook in Inertia.js
Goal To determine whether Inertia.js should expose a framework‑agnostic lifecycle hook that guarantees the teardown of side effects (intervals, listeners, subscriptions) when a page component is discarded during a normal or partial navigation. Constraints Inertia.js only cleans its own internal events; Vue, React, and Svelte rely on their own unmount hooks.
Partial reload scroll restoration behavior in Inertia.js v1.x
When using Inertia.js partial reloads (v1.0.0+), the X-Inertia-Partial-Component header updates only the targeted component without a full page refresh. The current implementation does not automatically restore the scroll position after such a reload, leaving scroll handling to the application developer via the inertia:page-update event. This behavior create
Partial reloads vs. full visits for paginated Inertia tables when SEO and history matter
Context An Inertia.js application renders a large dataset using Laravel's LengthAwarePaginator serialized into Inertia's pagination object. The product team requires indexable URLs for each page (e.g., /posts?page=3 ) and browser history support so users can navigate back to a specific page. At the same time, the UX goal is to avoid full-page flashes when mo
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