UNPKG

react-router/CHANGELOG.md

Version:
31.1 kBMarkdownView Raw
1# `react-router`
2
3## 6.25.1
4
5No significant changes to this package were made in this release. [See the repo `CHANGELOG.md`](https://github.com/remix-run/react-router/blob/main/CHANGELOG.md) for an overview of all changes in v6.25.1.
6
7## 6.25.0
8
9### Minor Changes
10
11- Stabilize `future.unstable_skipActionErrorRevalidation` as `future.v7_skipActionErrorRevalidation` ([#11769](https://github.com/remix-run/react-router/pull/11769))
12
13 - When this flag is enabled, actions will not automatically trigger a revalidation if they return/throw a `Response` with a `4xx`/`5xx` status code
14 - You may still opt-into revalidation via `shouldRevalidate`
15 - This also changes `shouldRevalidate`'s `unstable_actionStatus` parameter to `actionStatus`
16
17### Patch Changes
18
19- Fix regression and properly decode paths inside `useMatch` so matches/params reflect decoded params ([#11789](https://github.com/remix-run/react-router/pull/11789))
20- Updated dependencies:
21 - `@remix-run/router@1.18.0`
22
23## 6.24.1
24
25### Patch Changes
26
27- When using `future.v7_relativeSplatPath`, properly resolve relative paths in splat routes that are children of pathless routes ([#11633](https://github.com/remix-run/react-router/pull/11633))
28- Updated dependencies:
29 - `@remix-run/router@1.17.1`
30
31## 6.24.0
32
33### Minor Changes
34
35- Add support for Lazy Route Discovery (a.k.a. Fog of War) ([#11626](https://github.com/remix-run/react-router/pull/11626))
36
37 - RFC: <https://github.com/remix-run/react-router/discussions/11113>
38 - `unstable_patchRoutesOnMiss` docs: <https://reactrouter.com/en/main/routers/create-browser-router>
39
40### Patch Changes
41
42- Updated dependencies:
43 - `@remix-run/router@1.17.0`
44
45## 6.23.1
46
47### Patch Changes
48
49- allow undefined to be resolved with `<Await>` ([#11513](https://github.com/remix-run/react-router/pull/11513))
50- Updated dependencies:
51 - `@remix-run/router@1.16.1`
52
53## 6.23.0
54
55### Minor Changes
56
57- Add a new `unstable_dataStrategy` configuration option ([#11098](https://github.com/remix-run/react-router/pull/11098))
58 - This option allows Data Router applications to take control over the approach for executing route loaders and actions
59 - The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix single-fetch, middleware/context APIs, automatic loader caching, and more
60
61### Patch Changes
62
63- Updated dependencies:
64 - `@remix-run/router@1.16.0`
65
66## 6.22.3
67
68### Patch Changes
69
70- Updated dependencies:
71 - `@remix-run/router@1.15.3`
72
73## 6.22.2
74
75### Patch Changes
76
77- Updated dependencies:
78 - `@remix-run/router@1.15.2`
79
80## 6.22.1
81
82### Patch Changes
83
84- Fix encoding/decoding issues with pre-encoded dynamic parameter values ([#11199](https://github.com/remix-run/react-router/pull/11199))
85- Updated dependencies:
86 - `@remix-run/router@1.15.1`
87
88## 6.22.0
89
90### Patch Changes
91
92- Updated dependencies:
93 - `@remix-run/router@1.15.0`
94
95## 6.21.3
96
97### Patch Changes
98
99- Remove leftover `unstable_` prefix from `Blocker`/`BlockerFunction` types ([#11187](https://github.com/remix-run/react-router/pull/11187))
100
101## 6.21.2
102
103### Patch Changes
104
105- Updated dependencies:
106 - `@remix-run/router@1.14.2`
107
108## 6.21.1
109
110### Patch Changes
111
112- Fix bug with `route.lazy` not working correctly on initial SPA load when `v7_partialHydration` is specified ([#11121](https://github.com/remix-run/react-router/pull/11121))
113- Updated dependencies:
114 - `@remix-run/router@1.14.1`
115
116## 6.21.0
117
118### Minor Changes
119
120- Add a new `future.v7_relativeSplatPath` flag to implement a breaking bug fix to relative routing when inside a splat route. ([#11087](https://github.com/remix-run/react-router/pull/11087))
121
122 This fix was originally added in [#10983](https://github.com/remix-run/react-router/issues/10983) and was later reverted in [#11078](https://github.com/remix-run/react-router/pull/11078) because it was determined that a large number of existing applications were relying on the buggy behavior (see [#11052](https://github.com/remix-run/react-router/issues/11052))
123
124 **The Bug**
125 The buggy behavior is that without this flag, the default behavior when resolving relative paths is to _ignore_ any splat (`*`) portion of the current route path.
126
127 **The Background**
128 This decision was originally made thinking that it would make the concept of nested different sections of your apps in `<Routes>` easier if relative routing would _replace_ the current splat:
129
130 ```jsx
131 <BrowserRouter>
132 <Routes>
133 <Route path="/" element={<Home />} />
134 <Route path="dashboard/*" element={<Dashboard />} />
135 </Routes>
136 </BrowserRouter>
137 ```
138
139 Any paths like `/dashboard`, `/dashboard/team`, `/dashboard/projects` will match the `Dashboard` route. The dashboard component itself can then render nested `<Routes>`:
140
141 ```jsx
142 function Dashboard() {
143 return (
144 <div>
145 <h2>Dashboard</h2>
146 <nav>
147 <Link to="/">Dashboard Home</Link>
148 <Link to="team">Team</Link>
149 <Link to="projects">Projects</Link>
150 </nav>
151
152 <Routes>
153 <Route path="/" element={<DashboardHome />} />
154 <Route path="team" element={<DashboardTeam />} />
155 <Route path="projects" element={<DashboardProjects />} />
156 </Routes>
157 </div>
158 );
159 }
160 ```
161
162 Now, all links and route paths are relative to the router above them. This makes code splitting and compartmentalizing your app really easy. You could render the `Dashboard` as its own independent app, or embed it into your large app without making any changes to it.
163
164 **The Problem**
165
166 The problem is that this concept of ignoring part of a path breaks a lot of other assumptions in React Router - namely that `"."` always means the current location pathname for that route. When we ignore the splat portion, we start getting invalid paths when using `"."`:
167
168 ```jsx
169 // If we are on URL /dashboard/team, and we want to link to /dashboard/team:
170 function DashboardTeam() {
171 // ❌ This is broken and results in <a href="/dashboard">
172 return <Link to=".">A broken link to the Current URL</Link>;
173
174 // ✅ This is fixed but super unintuitive since we're already at /dashboard/team!
175 return <Link to="./team">A broken link to the Current URL</Link>;
176 }
177 ```
178
179 We've also introduced an issue that we can no longer move our `DashboardTeam` component around our route hierarchy easily - since it behaves differently if we're underneath a non-splat route, such as `/dashboard/:widget`. Now, our `"."` links will, properly point to ourself _inclusive of the dynamic param value_ so behavior will break from it's corresponding usage in a `/dashboard/*` route.
180
181 Even worse, consider a nested splat route configuration:
182
183 ```jsx
184 <BrowserRouter>
185 <Routes>
186 <Route path="dashboard">
187 <Route path="*" element={<Dashboard />} />
188 </Route>
189 </Routes>
190 </BrowserRouter>
191 ```
192
193 Now, a `<Link to=".">` and a `<Link to="..">` inside the `Dashboard` component go to the same place! That is definitely not correct!
194
195 Another common issue arose in Data Routers (and Remix) where any `<Form>` should post to it's own route `action` if you the user doesn't specify a form action:
196
197 ```jsx
198 let router = createBrowserRouter({
199 path: "/dashboard",
200 children: [
201 {
202 path: "*",
203 action: dashboardAction,
204 Component() {
205 // ❌ This form is broken! It throws a 405 error when it submits because
206 // it tries to submit to /dashboard (without the splat value) and the parent
207 // `/dashboard` route doesn't have an action
208 return <Form method="post">...</Form>;
209 },
210 },
211 ],
212 });
213 ```
214
215 This is just a compounded issue from the above because the default location for a `Form` to submit to is itself (`"."`) - and if we ignore the splat portion, that now resolves to the parent route.
216
217 **The Solution**
218 If you are leveraging this behavior, it's recommended to enable the future flag, move your splat to it's own route, and leverage `../` for any links to "sibling" pages:
219
220 ```jsx
221 <BrowserRouter>
222 <Routes>
223 <Route path="dashboard">
224 <Route index path="*" element={<Dashboard />} />
225 </Route>
226 </Routes>
227 </BrowserRouter>
228
229 function Dashboard() {
230 return (
231 <div>
232 <h2>Dashboard</h2>
233 <nav>
234 <Link to="..">Dashboard Home</Link>
235 <Link to="../team">Team</Link>
236 <Link to="../projects">Projects</Link>
237 </nav>
238
239 <Routes>
240 <Route path="/" element={<DashboardHome />} />
241 <Route path="team" element={<DashboardTeam />} />
242 <Route path="projects" element={<DashboardProjects />} />
243 </Router>
244 </div>
245 );
246 }
247 ```
248
249 This way, `.` means "the full current pathname for my route" in all cases (including static, dynamic, and splat routes) and `..` always means "my parents pathname".
250
251### Patch Changes
252
253- Properly handle falsy error values in ErrorBoundary's ([#11071](https://github.com/remix-run/react-router/pull/11071))
254- Updated dependencies:
255 - `@remix-run/router@1.14.0`
256
257## 6.20.1
258
259### Patch Changes
260
261- Revert the `useResolvedPath` fix for splat routes due to a large number of applications that were relying on the buggy behavior (see <https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329>). We plan to re-introduce this fix behind a future flag in the next minor version. ([#11078](https://github.com/remix-run/react-router/pull/11078))
262- Updated dependencies:
263 - `@remix-run/router@1.13.1`
264
265## 6.20.0
266
267### Minor Changes
268
269- Export the `PathParam` type from the public API ([#10719](https://github.com/remix-run/react-router/pull/10719))
270
271### Patch Changes
272
273- Fix bug with `resolveTo` in splat routes ([#11045](https://github.com/remix-run/react-router/pull/11045))
274 - This is a follow up to [#10983](https://github.com/remix-run/react-router/pull/10983) to handle the few other code paths using `getPathContributingMatches`
275 - This removes the `UNSAFE_getPathContributingMatches` export from `@remix-run/router` since we no longer need this in the `react-router`/`react-router-dom` layers
276- Updated dependencies:
277 - `@remix-run/router@1.13.0`
278
279## 6.19.0
280
281### Minor Changes
282
283- Add `unstable_flushSync` option to `useNavigate`/`useSumbit`/`fetcher.load`/`fetcher.submit` to opt-out of `React.startTransition` and into `ReactDOM.flushSync` for state updates ([#11005](https://github.com/remix-run/react-router/pull/11005))
284- Remove the `unstable_` prefix from the [`useBlocker`](https://reactrouter.com/en/main/hooks/use-blocker) hook as it's been in use for enough time that we are confident in the API. We do not plan to remove the prefix from `unstable_usePrompt` due to differences in how browsers handle `window.confirm` that prevent React Router from guaranteeing consistent/correct behavior. ([#10991](https://github.com/remix-run/react-router/pull/10991))
285
286### Patch Changes
287
288- Fix `useActionData` so it returns proper contextual action data and not _any_ action data in the tree ([#11023](https://github.com/remix-run/react-router/pull/11023))
289
290- Fix bug in `useResolvedPath` that would cause `useResolvedPath(".")` in a splat route to lose the splat portion of the URL path. ([#10983](https://github.com/remix-run/react-router/pull/10983))
291
292 - ⚠️ This fixes a quite long-standing bug specifically for `"."` paths inside a splat route which incorrectly dropped the splat portion of the URL. If you are relative routing via `"."` inside a splat route in your application you should double check that your logic is not relying on this buggy behavior and update accordingly.
293
294- Updated dependencies:
295 - `@remix-run/router@1.12.0`
296
297## 6.18.0
298
299### Patch Changes
300
301- Fix the `future` prop on `BrowserRouter`, `HashRouter` and `MemoryRouter` so that it accepts a `Partial<FutureConfig>` instead of requiring all flags to be included. ([#10962](https://github.com/remix-run/react-router/pull/10962))
302- Updated dependencies:
303 - `@remix-run/router@1.11.0`
304
305## 6.17.0
306
307### Patch Changes
308
309- Fix `RouterProvider` `future` prop type to be a `Partial<FutureConfig>` so that not all flags must be specified ([#10900](https://github.com/remix-run/react-router/pull/10900))
310- Updated dependencies:
311 - `@remix-run/router@1.10.0`
312
313## 6.16.0
314
315### Minor Changes
316
317- In order to move towards stricter TypeScript support in the future, we're aiming to replace current usages of `any` with `unknown` on exposed typings for user-provided data. To do this in Remix v2 without introducing breaking changes in React Router v6, we have added generics to a number of shared types. These continue to default to `any` in React Router and are overridden with `unknown` in Remix. In React Router v7 we plan to move these to `unknown` as a breaking change. ([#10843](https://github.com/remix-run/react-router/pull/10843))
318 - `Location` now accepts a generic for the `location.state` value
319 - `ActionFunctionArgs`/`ActionFunction`/`LoaderFunctionArgs`/`LoaderFunction` now accept a generic for the `context` parameter (only used in SSR usages via `createStaticHandler`)
320 - The return type of `useMatches` (now exported as `UIMatch`) accepts generics for `match.data` and `match.handle` - both of which were already set to `unknown`
321- Move the `@private` class export `ErrorResponse` to an `UNSAFE_ErrorResponseImpl` export since it is an implementation detail and there should be no construction of `ErrorResponse` instances in userland. This frees us up to export a `type ErrorResponse` which correlates to an instance of the class via `InstanceType`. Userland code should only ever be using `ErrorResponse` as a type and should be type-narrowing via `isRouteErrorResponse`. ([#10811](https://github.com/remix-run/react-router/pull/10811))
322- Export `ShouldRevalidateFunctionArgs` interface ([#10797](https://github.com/remix-run/react-router/pull/10797))
323- Removed private/internal APIs only required for the Remix v1 backwards compatibility layer and no longer needed in Remix v2 (`_isFetchActionRedirect`, `_hasFetcherDoneAnything`) ([#10715](https://github.com/remix-run/react-router/pull/10715))
324
325### Patch Changes
326
327- Updated dependencies:
328 - `@remix-run/router@1.9.0`
329
330## 6.15.0
331
332### Minor Changes
333
334- Add's a new `redirectDocument()` function which allows users to specify that a redirect from a `loader`/`action` should trigger a document reload (via `window.location`) instead of attempting to navigate to the redirected location via React Router ([#10705](https://github.com/remix-run/react-router/pull/10705))
335
336### Patch Changes
337
338- Ensure `useRevalidator` is referentially stable across re-renders if revalidations are not actively occurring ([#10707](https://github.com/remix-run/react-router/pull/10707))
339- Updated dependencies:
340 - `@remix-run/router@1.8.0`
341
342## 6.14.2
343
344### Patch Changes
345
346- Updated dependencies:
347 - `@remix-run/router@1.7.2`
348
349## 6.14.1
350
351### Patch Changes
352
353- Fix loop in `unstable_useBlocker` when used with an unstable blocker function ([#10652](https://github.com/remix-run/react-router/pull/10652))
354- Fix issues with reused blockers on subsequent navigations ([#10656](https://github.com/remix-run/react-router/pull/10656))
355- Updated dependencies:
356 - `@remix-run/router@1.7.1`
357
358## 6.14.0
359
360### Patch Changes
361
362- Strip `basename` from locations provided to `unstable_useBlocker` functions to match `useLocation` ([#10573](https://github.com/remix-run/react-router/pull/10573))
363- Fix `generatePath` when passed a numeric `0` value parameter ([#10612](https://github.com/remix-run/react-router/pull/10612))
364- Fix `unstable_useBlocker` key issues in `StrictMode` ([#10573](https://github.com/remix-run/react-router/pull/10573))
365- Fix `tsc --skipLibCheck:false` issues on React 17 ([#10622](https://github.com/remix-run/react-router/pull/10622))
366- Upgrade `typescript` to 5.1 ([#10581](https://github.com/remix-run/react-router/pull/10581))
367- Updated dependencies:
368 - `@remix-run/router@1.7.0`
369
370## 6.13.0
371
372### Minor Changes
373
374- Move [`React.startTransition`](https://react.dev/reference/react/startTransition) usage behind a [future flag](https://reactrouter.com/en/main/guides/api-development-strategy) to avoid issues with existing incompatible `Suspense` usages. We recommend folks adopting this flag to be better compatible with React concurrent mode, but if you run into issues you can continue without the use of `startTransition` until v7. Issues usually boils down to creating net-new promises during the render cycle, so if you run into issues you should either lift your promise creation out of the render cycle or put it behind a `useMemo`. ([#10596](https://github.com/remix-run/react-router/pull/10596))
375
376 Existing behavior will no longer include `React.startTransition`:
377
378 ```jsx
379 <BrowserRouter>
380 <Routes>{/*...*/}</Routes>
381 </BrowserRouter>
382
383 <RouterProvider router={router} />
384 ```
385
386 If you wish to enable `React.startTransition`, pass the future flag to your component:
387
388 ```jsx
389 <BrowserRouter future={{ v7_startTransition: true }}>
390 <Routes>{/*...*/}</Routes>
391 </BrowserRouter>
392
393 <RouterProvider router={router} future={{ v7_startTransition: true }}/>
394 ```
395
396### Patch Changes
397
398- Work around webpack/terser `React.startTransition` minification bug in production mode ([#10588](https://github.com/remix-run/react-router/pull/10588))
399
400## 6.12.1
401
402> \[!WARNING]
403> Please use version `6.13.0` or later instead of `6.12.1`. This version suffers from a `webpack`/`terser` minification issue resulting in invalid minified code in your resulting production bundles which can cause issues in your application. See [#10579](https://github.com/remix-run/react-router/issues/10579) for more details.
404
405### Patch Changes
406
407- Adjust feature detection of `React.startTransition` to fix webpack + react 17 compilation error ([#10569](https://github.com/remix-run/react-router/pull/10569))
408
409## 6.12.0
410
411### Minor Changes
412
413- Wrap internal router state updates with `React.startTransition` if it exists ([#10438](https://github.com/remix-run/react-router/pull/10438))
414
415### Patch Changes
416
417- Updated dependencies:
418 - `@remix-run/router@1.6.3`
419
420## 6.11.2
421
422### Patch Changes
423
424- Fix `basename` duplication in descendant `<Routes>` inside a `<RouterProvider>` ([#10492](https://github.com/remix-run/react-router/pull/10492))
425- Updated dependencies:
426 - `@remix-run/router@1.6.2`
427
428## 6.11.1
429
430### Patch Changes
431
432- Fix usage of `Component` API within descendant `<Routes>` ([#10434](https://github.com/remix-run/react-router/pull/10434))
433- Fix bug when calling `useNavigate` from `<Routes>` inside a `<RouterProvider>` ([#10432](https://github.com/remix-run/react-router/pull/10432))
434- Fix usage of `<Navigate>` in strict mode when using a data router ([#10435](https://github.com/remix-run/react-router/pull/10435))
435- Updated dependencies:
436 - `@remix-run/router@1.6.1`
437
438## 6.11.0
439
440### Patch Changes
441
442- Log loader/action errors to the console in dev for easier stack trace evaluation ([#10286](https://github.com/remix-run/react-router/pull/10286))
443- Fix bug preventing rendering of descendant `<Routes>` when `RouterProvider` errors existed ([#10374](https://github.com/remix-run/react-router/pull/10374))
444- Fix inadvertent re-renders when using `Component` instead of `element` on a route definition ([#10287](https://github.com/remix-run/react-router/pull/10287))
445- Fix detection of `useNavigate` in the render cycle by setting the `activeRef` in a layout effect, allowing the `navigate` function to be passed to child components and called in a `useEffect` there. ([#10394](https://github.com/remix-run/react-router/pull/10394))
446- Switched from `useSyncExternalStore` to `useState` for internal `@remix-run/router` router state syncing in `<RouterProvider>`. We found some [subtle bugs](https://codesandbox.io/s/use-sync-external-store-loop-9g7b81) where router state updates got propagated _before_ other normal `useState` updates, which could lead to footguns in `useEffect` calls. ([#10377](https://github.com/remix-run/react-router/pull/10377), [#10409](https://github.com/remix-run/react-router/pull/10409))
447- Allow `useRevalidator()` to resolve a loader-driven error boundary scenario ([#10369](https://github.com/remix-run/react-router/pull/10369))
448- Avoid unnecessary unsubscribe/resubscribes on router state changes ([#10409](https://github.com/remix-run/react-router/pull/10409))
449- When using a `RouterProvider`, `useNavigate`/`useSubmit`/`fetcher.submit` are now stable across location changes, since we can handle relative routing via the `@remix-run/router` instance and get rid of our dependence on `useLocation()`. When using `BrowserRouter`, these hooks remain unstable across location changes because they still rely on `useLocation()`. ([#10336](https://github.com/remix-run/react-router/pull/10336))
450- Updated dependencies:
451 - `@remix-run/router@1.6.0`
452
453## 6.10.0
454
455### Minor Changes
456
457- Added support for [**Future Flags**](https://reactrouter.com/en/main/guides/api-development-strategy) in React Router. The first flag being introduced is `future.v7_normalizeFormMethod` which will normalize the exposed `useNavigation()/useFetcher()` `formMethod` fields as uppercase HTTP methods to align with the `fetch()` behavior. ([#10207](https://github.com/remix-run/react-router/pull/10207))
458
459 - When `future.v7_normalizeFormMethod === false` (default v6 behavior),
460 - `useNavigation().formMethod` is lowercase
461 - `useFetcher().formMethod` is lowercase
462 - When `future.v7_normalizeFormMethod === true`:
463 - `useNavigation().formMethod` is uppercase
464 - `useFetcher().formMethod` is uppercase
465
466### Patch Changes
467
468- Fix route ID generation when using Fragments in `createRoutesFromElements` ([#10193](https://github.com/remix-run/react-router/pull/10193))
469- Updated dependencies:
470 - `@remix-run/router@1.5.0`
471
472## 6.9.0
473
474### Minor Changes
475
476- React Router now supports an alternative way to define your route `element` and `errorElement` fields as React Components instead of React Elements. You can instead pass a React Component to the new `Component` and `ErrorBoundary` fields if you choose. There is no functional difference between the two, so use whichever approach you prefer 😀. You shouldn't be defining both, but if you do `Component`/`ErrorBoundary` will "win". ([#10045](https://github.com/remix-run/react-router/pull/10045))
477
478 **Example JSON Syntax**
479
480 ```jsx
481 // Both of these work the same:
482 const elementRoutes = [{
483 path: '/',
484 element: <Home />,
485 errorElement: <HomeError />,
486 }]
487
488 const componentRoutes = [{
489 path: '/',
490 Component: Home,
491 ErrorBoundary: HomeError,
492 }]
493
494 function Home() { ... }
495 function HomeError() { ... }
496 ```
497
498 **Example JSX Syntax**
499
500 ```jsx
501 // Both of these work the same:
502 const elementRoutes = createRoutesFromElements(
503 <Route path='/' element={<Home />} errorElement={<HomeError /> } />
504 );
505
506 const componentRoutes = createRoutesFromElements(
507 <Route path='/' Component={Home} ErrorBoundary={HomeError} />
508 );
509
510 function Home() { ... }
511 function HomeError() { ... }
512 ```
513
514- **Introducing Lazy Route Modules!** ([#10045](https://github.com/remix-run/react-router/pull/10045))
515
516 In order to keep your application bundles small and support code-splitting of your routes, we've introduced a new `lazy()` route property. This is an async function that resolves the non-route-matching portions of your route definition (`loader`, `action`, `element`/`Component`, `errorElement`/`ErrorBoundary`, `shouldRevalidate`, `handle`).
517
518 Lazy routes are resolved on initial load and during the `loading` or `submitting` phase of a navigation or fetcher call. You cannot lazily define route-matching properties (`path`, `index`, `children`) since we only execute your lazy route functions after we've matched known routes.
519
520 Your `lazy` functions will typically return the result of a dynamic import.
521
522 ```jsx
523 // In this example, we assume most folks land on the homepage so we include that
524 // in our critical-path bundle, but then we lazily load modules for /a and /b so
525 // they don't load until the user navigates to those routes
526 let routes = createRoutesFromElements(
527 <Route path="/" element={<Layout />}>
528 <Route index element={<Home />} />
529 <Route path="a" lazy={() => import("./a")} />
530 <Route path="b" lazy={() => import("./b")} />
531 </Route>
532 );
533 ```
534
535 Then in your lazy route modules, export the properties you want defined for the route:
536
537 ```jsx
538 export async function loader({ request }) {
539 let data = await fetchData(request);
540 return json(data);
541 }
542
543 // Export a `Component` directly instead of needing to create a React Element from it
544 export function Component() {
545 let data = useLoaderData();
546
547 return (
548 <>
549 <h1>You made it!</h1>
550 <p>{data}</p>
551 </>
552 );
553 }
554
555 // Export an `ErrorBoundary` directly instead of needing to create a React Element from it
556 export function ErrorBoundary() {
557 let error = useRouteError();
558 return isRouteErrorResponse(error) ? (
559 <h1>
560 {error.status} {error.statusText}
561 </h1>
562 ) : (
563 <h1>{error.message || error}</h1>
564 );
565 }
566 ```
567
568 An example of this in action can be found in the [`examples/lazy-loading-router-provider`](https://github.com/remix-run/react-router/tree/main/examples/lazy-loading-router-provider) directory of the repository.
569
570 🙌 Huge thanks to @rossipedia for the [Initial Proposal](https://github.com/remix-run/react-router/discussions/9826) and [POC Implementation](https://github.com/remix-run/react-router/pull/9830).
571
572- Updated dependencies:
573 - `@remix-run/router@1.4.0`
574
575### Patch Changes
576
577- Fix `generatePath` incorrectly applying parameters in some cases ([#10078](https://github.com/remix-run/react-router/pull/10078))
578- Improve memoization for context providers to avoid unnecessary re-renders ([#9983](https://github.com/remix-run/react-router/pull/9983))
579
580## 6.8.2
581
582### Patch Changes
583
584- Updated dependencies:
585 - `@remix-run/router@1.3.3`
586
587## 6.8.1
588
589### Patch Changes
590
591- Remove inaccurate console warning for POP navigations and update active blocker logic ([#10030](https://github.com/remix-run/react-router/pull/10030))
592- Updated dependencies:
593 - `@remix-run/router@1.3.2`
594
595## 6.8.0
596
597### Patch Changes
598
599- Updated dependencies:
600 - `@remix-run/router@1.3.1`
601
602## 6.7.0
603
604### Minor Changes
605
606- Add `unstable_useBlocker` hook for blocking navigations within the app's location origin ([#9709](https://github.com/remix-run/react-router/pull/9709))
607
608### Patch Changes
609
610- Fix `generatePath` when optional params are present ([#9764](https://github.com/remix-run/react-router/pull/9764))
611- Update `<Await>` to accept `ReactNode` as children function return result ([#9896](https://github.com/remix-run/react-router/pull/9896))
612- Updated dependencies:
613 - `@remix-run/router@1.3.0`
614
615## 6.6.2
616
617### Patch Changes
618
619- Ensure `useId` consistency during SSR ([#9805](https://github.com/remix-run/react-router/pull/9805))
620
621## 6.6.1
622
623### Patch Changes
624
625- Updated dependencies:
626 - `@remix-run/router@1.2.1`
627
628## 6.6.0
629
630### Patch Changes
631
632- Prevent `useLoaderData` usage in `errorElement` ([#9735](https://github.com/remix-run/react-router/pull/9735))
633- Updated dependencies:
634 - `@remix-run/router@1.2.0`
635
636## 6.5.0
637
638This release introduces support for [Optional Route Segments](https://github.com/remix-run/react-router/issues/9546). Now, adding a `?` to the end of any path segment will make that entire segment optional. This works for both static segments and dynamic parameters.
639
640**Optional Params Examples**
641
642- `<Route path=":lang?/about>` will match:
643 - `/:lang/about`
644 - `/about`
645- `<Route path="/multistep/:widget1?/widget2?/widget3?">` will match:
646 - `/multistep`
647 - `/multistep/:widget1`
648 - `/multistep/:widget1/:widget2`
649 - `/multistep/:widget1/:widget2/:widget3`
650
651**Optional Static Segment Example**
652
653- `<Route path="/home?">` will match:
654 - `/`
655 - `/home`
656- `<Route path="/fr?/about">` will match:
657 - `/about`
658 - `/fr/about`
659
660### Minor Changes
661
662- Allows optional routes and optional static segments ([#9650](https://github.com/remix-run/react-router/pull/9650))
663
664### Patch Changes
665
666- Stop incorrectly matching on partial named parameters, i.e. `<Route path="prefix-:param">`, to align with how splat parameters work. If you were previously relying on this behavior then it's recommended to extract the static portion of the path at the `useParams` call site: ([#9506](https://github.com/remix-run/react-router/pull/9506))
667
668```jsx
669// Old behavior at URL /prefix-123
670<Route path="prefix-:id" element={<Comp /> }>
671
672function Comp() {
673 let params = useParams(); // { id: '123' }
674 let id = params.id; // "123"
675 ...
676}
677
678// New behavior at URL /prefix-123
679<Route path=":id" element={<Comp /> }>
680
681function Comp() {
682 let params = useParams(); // { id: 'prefix-123' }
683 let id = params.id.replace(/^prefix-/, ''); // "123"
684 ...
685}
686```
687
688- Updated dependencies:
689 - `@remix-run/router@1.1.0`
690
691## 6.4.5
692
693### Patch Changes
694
695- Updated dependencies:
696 - `@remix-run/router@1.0.5`
697
698## 6.4.4
699
700### Patch Changes
701
702- Updated dependencies:
703 - `@remix-run/router@1.0.4`
704
705## 6.4.3
706
707### Patch Changes
708
709- `useRoutes` should be able to return `null` when passing `locationArg` ([#9485](https://github.com/remix-run/react-router/pull/9485))
710- fix `initialEntries` type in `createMemoryRouter` ([#9498](https://github.com/remix-run/react-router/pull/9498))
711- Updated dependencies:
712 - `@remix-run/router@1.0.3`
713
714## 6.4.2
715
716### Patch Changes
717
718- Fix `IndexRouteObject` and `NonIndexRouteObject` types to make `hasErrorElement` optional ([#9394](https://github.com/remix-run/react-router/pull/9394))
719- Enhance console error messages for invalid usage of data router hooks ([#9311](https://github.com/remix-run/react-router/pull/9311))
720- If an index route has children, it will result in a runtime error. We have strengthened our `RouteObject`/`RouteProps` types to surface the error in TypeScript. ([#9366](https://github.com/remix-run/react-router/pull/9366))
721- Updated dependencies:
722 - `@remix-run/router@1.0.2`
723
724## 6.4.1
725
726### Patch Changes
727
728- Preserve state from `initialEntries` ([#9288](https://github.com/remix-run/react-router/pull/9288))
729- Updated dependencies:
730 - `@remix-run/router@1.0.1`
731
732## 6.4.0
733
734Whoa this is a big one! `6.4.0` brings all the data loading and mutation APIs over from Remix. Here's a quick high level overview, but it's recommended you go check out the [docs](https://reactrouter.com), especially the [feature overview](https://reactrouter.com/start/overview) and the [tutorial](https://reactrouter.com/start/tutorial).
735
736**New APIs**
737
738- Create your router with `createMemoryRouter`
739- Render your router with `<RouterProvider>`
740- Load data with a Route `loader` and mutate with a Route `action`
741- Handle errors with Route `errorElement`
742- Defer non-critical data with `defer` and `Await`
743
744**Bug Fixes**
745
746- Path resolution is now trailing slash agnostic (#8861)
747- `useLocation` returns the scoped location inside a `<Routes location>` component (#9094)
748
749**Updated Dependencies**
750
751- `@remix-run/router@1.0.0`