react-router-data-mode

Define a loader function on the route object that receives params and request, then access the returned data in your component with useLoaderData. Loaders for all matched routes run in parallel before rendering, eliminating waterfall requests.

Use useFetcher for inline mutations like likes, ratings, and toggles that should not trigger navigation. Use Form with method post for mutations that create resources and redirect, and Form with method get for search forms that update URL params.

Read fetcher.formData to display the pending submitted value immediately, falling back to server state when idle. If the action fails, loaders automatically revalidate and the UI reverts to the actual server state.

Yes, SSR works without the Vite plugin using createStaticHandler and createStaticRouter on the server with StaticRouterProvider, then hydrating on the client with createBrowserRouter and hydrateRoot using shared route definitions.

Manually calling setSearchParams inside onSubmit is an anti-pattern. Use the Form component with method get instead, which automatically serializes inputs into URL search params and triggers the route loader.