UNPKG

29.5 kB Markdown View Raw
1 # `react-router`
2
3 ## 6.23.1
4
5 ### Patch Changes
6
7 - allow undefined to be resolved with `<Await>` ([#11513](https://github.com/remix-run/react-router/pull/11513))
8 - Updated dependencies:
9 - `@remix-run/router@1.16.1`
10
11 ## 6.23.0
12
13 ### Minor Changes
14
15 - Add a new `unstable_dataStrategy` configuration option ([#11098](https://github.com/remix-run/react-router/pull/11098))
16 - This option allows Data Router applications to take control over the approach for executing route loaders and actions
17 - 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
18
19 ### Patch Changes
20
21 - Updated dependencies:
22 - `@remix-run/router@1.16.0`
23
24 ## 6.22.3
25
26 ### Patch Changes
27
28 - Updated dependencies:
29 - `@remix-run/router@1.15.3`
30
31 ## 6.22.2
32
33 ### Patch Changes
34
35 - Updated dependencies:
36 - `@remix-run/router@1.15.2`
37
38 ## 6.22.1
39
40 ### Patch Changes
41
42 - Fix encoding/decoding issues with pre-encoded dynamic parameter values ([#11199](https://github.com/remix-run/react-router/pull/11199))
43 - Updated dependencies:
44 - `@remix-run/router@1.15.1`
45
46 ## 6.22.0
47
48 ### Patch Changes
49
50 - Updated dependencies:
51 - `@remix-run/router@1.15.0`
52
53 ## 6.21.3
54
55 ### Patch Changes
56
57 - Remove leftover `unstable_` prefix from `Blocker`/`BlockerFunction` types ([#11187](https://github.com/remix-run/react-router/pull/11187))
58
59 ## 6.21.2
60
61 ### Patch Changes
62
63 - Updated dependencies:
64 - `@remix-run/router@1.14.2`
65
66 ## 6.21.1
67
68 ### Patch Changes
69
70 - 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))
71 - Updated dependencies:
72 - `@remix-run/router@1.14.1`
73
74 ## 6.21.0
75
76 ### Minor Changes
77
78 - 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))
79
80 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))
81
82 **The Bug**
83 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.
84
85 **The Background**
86 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:
87
88 ```jsx
89
90 <Routes>
91 <Route path="/" element={<Home />} />
92 <Route path="dashboard/*" element={<Dashboard />} />
93 </Routes>
94
95 ```
96
97 Any paths like `/dashboard`, `/dashboard/team`, `/dashboard/projects` will match the `Dashboard` route. The dashboard component itself can then render nested `<Routes>`:
98
99 ```jsx
100 function Dashboard() {
101 return (
102 <div>
103 <h2>Dashboard</h2>
104 <nav>
105 <Link to="/">Dashboard Home</Link>
106 <Link to="team">Team</Link>
107 <Link to="projects">Projects</Link>
108 </nav>
109
110 <Routes>
111 <Route path="/" element={<DashboardHome />} />
112 <Route path="team" element={<DashboardTeam />} />
113 <Route path="projects" element={<DashboardProjects />} />
114 </Routes>
115 </div>
116 );
117 }
118 ```
119
120 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.
121
122 **The Problem**
123
124 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 `"."`:
125
126 ```jsx
127 // If we are on URL /dashboard/team, and we want to link to /dashboard/team:
128 function DashboardTeam() {
129 // ❌ This is broken and results in <a href="/dashboard">
130 return <Link to=".">A broken link to the Current URL</Link>;
131
132 // ✅ This is fixed but super unintuitive since we're already at /dashboard/team!
133 return <Link to="./team">A broken link to the Current URL</Link>;
134 }
135 ```
136
137 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.
138
139 Even worse, consider a nested splat route configuration:
140
141 ```jsx
142
143 <Routes>
144 <Route path="dashboard">
145 <Route path="*" element={<Dashboard />} />
146 </Route>
147 </Routes>
148
149 ```
150
151 Now, a `<Link to=".">` and a `<Link to="..">` inside the `Dashboard` component go to the same place! That is definitely not correct!
152
153 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:
154
155 ```jsx
156 let router = createBrowserRouter({
157 path: "/dashboard",
158 children: [
159 {
160 path: "*",
161 action: dashboardAction,
162 Component() {
163 // ❌ This form is broken! It throws a 405 error when it submits because
164 // it tries to submit to /dashboard (without the splat value) and the parent
165 // `/dashboard` route doesn't have an action
166 return <Form method="post">...</Form>;
167 },
168 },
169 ],
170 });
171 ```
172
173 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.
174
175 **The Solution**
176 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:
177
178 ```jsx
179
180 <Routes>
181 <Route path="dashboard">
182 <Route index path="*" element={<Dashboard />} />
183 </Route>
184 </Routes>
185
186
187 function Dashboard() {
188 return (
189 <div>
190 <h2>Dashboard</h2>
191 <nav>
192 <Link to="..">Dashboard Home</Link>
193 <Link to="../team">Team</Link>
194 <Link to="../projects">Projects</Link>
195 </nav>
196
197 <Routes>
198 <Route path="/" element={<DashboardHome />} />
199 <Route path="team" element={<DashboardTeam />} />
200 <Route path="projects" element={<DashboardProjects />} />
201 </Router>
202 </div>
203 );
204 }
205 ```
206
207 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".
208
209 ### Patch Changes
210
211 - Properly handle falsy error values in ErrorBoundary's ([#11071](https://github.com/remix-run/react-router/pull/11071))
212 - Updated dependencies:
213 - `@remix-run/router@1.14.0`
214
215 ## 6.20.1
216
217 ### Patch Changes
218
219 - Revert the `useResolvedPath` fix for splat routes due to a large number of applications that were relying on the buggy behavior (see ). 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))
220 - Updated dependencies:
221 - `@remix-run/router@1.13.1`
222
223 ## 6.20.0
224
225 ### Minor Changes
226
227 - Export the `PathParam` type from the public API ([#10719](https://github.com/remix-run/react-router/pull/10719))
228
229 ### Patch Changes
230
231 - Fix bug with `resolveTo` in splat routes ([#11045](https://github.com/remix-run/react-router/pull/11045))
232 - 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`
233 - This removes the `UNSAFE_getPathContributingMatches` export from `@remix-run/router` since we no longer need this in the `react-router`/`react-router-dom` layers
234 - Updated dependencies:
235 - `@remix-run/router@1.13.0`
236
237 ## 6.19.0
238
239 ### Minor Changes
240
241 - 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))
242 - 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))
243
244 ### Patch Changes
245
246 - 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))
247
248 - 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))
249
250 - ⚠️ 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.
251
252 - Updated dependencies:
253 - `@remix-run/router@1.12.0`
254
255 ## 6.18.0
256
257 ### Patch Changes
258
259 - 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))
260 - Updated dependencies:
261 - `@remix-run/router@1.11.0`
262
263 ## 6.17.0
264
265 ### Patch Changes
266
267 - 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))
268 - Updated dependencies:
269 - `@remix-run/router@1.10.0`
270
271 ## 6.16.0
272
273 ### Minor Changes
274
275 - 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))
276 - `Location` now accepts a generic for the `location.state` value
277 - `ActionFunctionArgs`/`ActionFunction`/`LoaderFunctionArgs`/`LoaderFunction` now accept a generic for the `context` parameter (only used in SSR usages via `createStaticHandler`)
278 - 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`
279 - 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))
280 - Export `ShouldRevalidateFunctionArgs` interface ([#10797](https://github.com/remix-run/react-router/pull/10797))
281 - 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))
282
283 ### Patch Changes
284
285 - Updated dependencies:
286 - `@remix-run/router@1.9.0`
287
288 ## 6.15.0
289
290 ### Minor Changes
291
292 - 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))
293
294 ### Patch Changes
295
296 - Ensure `useRevalidator` is referentially stable across re-renders if revalidations are not actively occurring ([#10707](https://github.com/remix-run/react-router/pull/10707))
297 - Updated dependencies:
298 - `@remix-run/router@1.8.0`
299
300 ## 6.14.2
301
302 ### Patch Changes
303
304 - Updated dependencies:
305 - `@remix-run/router@1.7.2`
306
307 ## 6.14.1
308
309 ### Patch Changes
310
311 - Fix loop in `unstable_useBlocker` when used with an unstable blocker function ([#10652](https://github.com/remix-run/react-router/pull/10652))
312 - Fix issues with reused blockers on subsequent navigations ([#10656](https://github.com/remix-run/react-router/pull/10656))
313 - Updated dependencies:
314 - `@remix-run/router@1.7.1`
315
316 ## 6.14.0
317
318 ### Patch Changes
319
320 - Strip `basename` from locations provided to `unstable_useBlocker` functions to match `useLocation` ([#10573](https://github.com/remix-run/react-router/pull/10573))
321 - Fix `generatePath` when passed a numeric `0` value parameter ([#10612](https://github.com/remix-run/react-router/pull/10612))
322 - Fix `unstable_useBlocker` key issues in `StrictMode` ([#10573](https://github.com/remix-run/react-router/pull/10573))
323 - Fix `tsc --skipLibCheck:false` issues on React 17 ([#10622](https://github.com/remix-run/react-router/pull/10622))
324 - Upgrade `typescript` to 5.1 ([#10581](https://github.com/remix-run/react-router/pull/10581))
325 - Updated dependencies:
326 - `@remix-run/router@1.7.0`
327
328 ## 6.13.0
329
330 ### Minor Changes
331
332 - 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))
333
334 Existing behavior will no longer include `React.startTransition`:
335
336 ```jsx
337
338 <Routes>{/*...*/}</Routes>
339
340
341
342 ```
343
344 If you wish to enable `React.startTransition`, pass the future flag to your component:
345
346 ```jsx
347
348 <Routes>{/*...*/}</Routes>
349
350
351
352 ```
353
354 ### Patch Changes
355
356 - Work around webpack/terser `React.startTransition` minification bug in production mode ([#10588](https://github.com/remix-run/react-router/pull/10588))
357
358 ## 6.12.1
359
360 > \[!WARNING]
361 > 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.
362
363 ### Patch Changes
364
365 - Adjust feature detection of `React.startTransition` to fix webpack + react 17 compilation error ([#10569](https://github.com/remix-run/react-router/pull/10569))
366
367 ## 6.12.0
368
369 ### Minor Changes
370
371 - Wrap internal router state updates with `React.startTransition` if it exists ([#10438](https://github.com/remix-run/react-router/pull/10438))
372
373 ### Patch Changes
374
375 - Updated dependencies:
376 - `@remix-run/router@1.6.3`
377
378 ## 6.11.2
379
380 ### Patch Changes
381
382 - Fix `basename` duplication in descendant `<Routes>` inside a `<RouterProvider>` ([#10492](https://github.com/remix-run/react-router/pull/10492))
383 - Updated dependencies:
384 - `@remix-run/router@1.6.2`
385
386 ## 6.11.1
387
388 ### Patch Changes
389
390 - Fix usage of `Component` API within descendant `<Routes>` ([#10434](https://github.com/remix-run/react-router/pull/10434))
391 - Fix bug when calling `useNavigate` from `<Routes>` inside a `<RouterProvider>` ([#10432](https://github.com/remix-run/react-router/pull/10432))
392 - Fix usage of `<Navigate>` in strict mode when using a data router ([#10435](https://github.com/remix-run/react-router/pull/10435))
393 - Updated dependencies:
394 - `@remix-run/router@1.6.1`
395
396 ## 6.11.0
397
398 ### Patch Changes
399
400 - Log loader/action errors to the console in dev for easier stack trace evaluation ([#10286](https://github.com/remix-run/react-router/pull/10286))
401 - Fix bug preventing rendering of descendant `<Routes>` when `RouterProvider` errors existed ([#10374](https://github.com/remix-run/react-router/pull/10374))
402 - Fix inadvertent re-renders when using `Component` instead of `element` on a route definition ([#10287](https://github.com/remix-run/react-router/pull/10287))
403 - 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))
404 - 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))
405 - Allow `useRevalidator()` to resolve a loader-driven error boundary scenario ([#10369](https://github.com/remix-run/react-router/pull/10369))
406 - Avoid unnecessary unsubscribe/resubscribes on router state changes ([#10409](https://github.com/remix-run/react-router/pull/10409))
407 - 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))
408 - Updated dependencies:
409 - `@remix-run/router@1.6.0`
410
411 ## 6.10.0
412
413 ### Minor Changes
414
415 - 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))
416
417 - When `future.v7_normalizeFormMethod === false` (default v6 behavior),
418 - `useNavigation().formMethod` is lowercase
419 - `useFetcher().formMethod` is lowercase
420 - When `future.v7_normalizeFormMethod === true`:
421 - `useNavigation().formMethod` is uppercase
422 - `useFetcher().formMethod` is uppercase
423
424 ### Patch Changes
425
426 - Fix route ID generation when using Fragments in `createRoutesFromElements` ([#10193](https://github.com/remix-run/react-router/pull/10193))
427 - Updated dependencies:
428 - `@remix-run/router@1.5.0`
429
430 ## 6.9.0
431
432 ### Minor Changes
433
434 - 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))
435
436 **Example JSON Syntax**
437
438 ```jsx
439 // Both of these work the same:
440 const elementRoutes = [{
441 path: '/',
442 element: <Home />,
443 errorElement: <HomeError />,
444 }]
445
446 const componentRoutes = [{
447 path: '/',
448 Component: Home,
449 ErrorBoundary: HomeError,
450 }]
451
452 function Home() { ... }
453 function HomeError() { ... }
454 ```
455
456 **Example JSX Syntax**
457
458 ```jsx
459 // Both of these work the same:
460 const elementRoutes = createRoutesFromElements(
461 <Route path='/' element={<Home />} errorElement={<HomeError /> } />
462 );
463
464 const componentRoutes = createRoutesFromElements(
465 <Route path='/' Component={Home} ErrorBoundary={HomeError} />
466 );
467
468 function Home() { ... }
469 function HomeError() { ... }
470 ```
471
472 - **Introducing Lazy Route Modules!** ([#10045](https://github.com/remix-run/react-router/pull/10045))
473
474 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`).
475
476 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.
477
478 Your `lazy` functions will typically return the result of a dynamic import.
479
480 ```jsx
481 // In this example, we assume most folks land on the homepage so we include that
482 // in our critical-path bundle, but then we lazily load modules for /a and /b so
483 // they don't load until the user navigates to those routes
484 let routes = createRoutesFromElements(
485 <Route path="/" element={<Layout />}>
486 <Route index element={<Home />} />
487 <Route path="a" lazy={() => import("./a")} />
488 <Route path="b" lazy={() => import("./b")} />
489 </Route>
490 );
491 ```
492
493 Then in your lazy route modules, export the properties you want defined for the route:
494
495 ```jsx
496 export async function loader({ request }) {
497 let data = await fetchData(request);
498 return json(data);
499 }
500
501 // Export a `Component` directly instead of needing to create a React Element from it
502 export function Component() {
503 let data = useLoaderData();
504
505 return (
506 <>
507 <h1>You made it!</h1>
508 <p>{data}</p>
509 </>
510 );
511 }
512
513 // Export an `ErrorBoundary` directly instead of needing to create a React Element from it
514 export function ErrorBoundary() {
515 let error = useRouteError();
516 return isRouteErrorResponse(error) ? (
517 <h1>
518 {error.status} {error.statusText}
519 </h1>
520 ) : (
521 <h1>{error.message || error}</h1>
522 );
523 }
524 ```
525
526 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.
527
528 🙌 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).
529
530 - Updated dependencies:
531 - `@remix-run/router@1.4.0`
532
533 ### Patch Changes
534
535 - Fix `generatePath` incorrectly applying parameters in some cases ([#10078](https://github.com/remix-run/react-router/pull/10078))
536 - Improve memoization for context providers to avoid unnecessary re-renders ([#9983](https://github.com/remix-run/react-router/pull/9983))
537
538 ## 6.8.2
539
540 ### Patch Changes
541
542 - Updated dependencies:
543 - `@remix-run/router@1.3.3`
544
545 ## 6.8.1
546
547 ### Patch Changes
548
549 - Remove inaccurate console warning for POP navigations and update active blocker logic ([#10030](https://github.com/remix-run/react-router/pull/10030))
550 - Updated dependencies:
551 - `@remix-run/router@1.3.2`
552
553 ## 6.8.0
554
555 ### Patch Changes
556
557 - Updated dependencies:
558 - `@remix-run/router@1.3.1`
559
560 ## 6.7.0
561
562 ### Minor Changes
563
564 - Add `unstable_useBlocker` hook for blocking navigations within the app's location origin ([#9709](https://github.com/remix-run/react-router/pull/9709))
565
566 ### Patch Changes
567
568 - Fix `generatePath` when optional params are present ([#9764](https://github.com/remix-run/react-router/pull/9764))
569 - Update `<Await>` to accept `ReactNode` as children function return result ([#9896](https://github.com/remix-run/react-router/pull/9896))
570 - Updated dependencies:
571 - `@remix-run/router@1.3.0`
572
573 ## 6.6.2
574
575 ### Patch Changes
576
577 - Ensure `useId` consistency during SSR ([#9805](https://github.com/remix-run/react-router/pull/9805))
578
579 ## 6.6.1
580
581 ### Patch Changes
582
583 - Updated dependencies:
584 - `@remix-run/router@1.2.1`
585
586 ## 6.6.0
587
588 ### Patch Changes
589
590 - Prevent `useLoaderData` usage in `errorElement` ([#9735](https://github.com/remix-run/react-router/pull/9735))
591 - Updated dependencies:
592 - `@remix-run/router@1.2.0`
593
594 ## 6.5.0
595
596 This 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.
597
598 **Optional Params Examples**
599
600 - `<Route path=":lang?/about>` will match:
601 - `/:lang/about`
602 - `/about`
603 - `<Route path="/multistep/:widget1?/widget2?/widget3?">` will match:
604 - `/multistep`
605 - `/multistep/:widget1`
606 - `/multistep/:widget1/:widget2`
607 - `/multistep/:widget1/:widget2/:widget3`
608
609 **Optional Static Segment Example**
610
611 - `<Route path="/home?">` will match:
612 - `/`
613 - `/home`
614 - `<Route path="/fr?/about">` will match:
615 - `/about`
616 - `/fr/about`
617
618 ### Minor Changes
619
620 - Allows optional routes and optional static segments ([#9650](https://github.com/remix-run/react-router/pull/9650))
621
622 ### Patch Changes
623
624 - 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))
625
626 ```jsx
627 // Old behavior at URL /prefix-123
628 }>
629
630 function Comp() {
631 let params = useParams(); // { id: '123' }
632 let id = params.id; // "123"
633 ...
634 }
635
636 // New behavior at URL /prefix-123
637 }>
638
639 function Comp() {
640 let params = useParams(); // { id: 'prefix-123' }
641 let id = params.id.replace(/^prefix-/, ''); // "123"
642 ...
643 }
644 ```
645
646 - Updated dependencies:
647 - `@remix-run/router@1.1.0`
648
649 ## 6.4.5
650
651 ### Patch Changes
652
653 - Updated dependencies:
654 - `@remix-run/router@1.0.5`
655
656 ## 6.4.4
657
658 ### Patch Changes
659
660 - Updated dependencies:
661 - `@remix-run/router@1.0.4`
662
663 ## 6.4.3
664
665 ### Patch Changes
666
667 - `useRoutes` should be able to return `null` when passing `locationArg` ([#9485](https://github.com/remix-run/react-router/pull/9485))
668 - fix `initialEntries` type in `createMemoryRouter` ([#9498](https://github.com/remix-run/react-router/pull/9498))
669 - Updated dependencies:
670 - `@remix-run/router@1.0.3`
671
672 ## 6.4.2
673
674 ### Patch Changes
675
676 - Fix `IndexRouteObject` and `NonIndexRouteObject` types to make `hasErrorElement` optional ([#9394](https://github.com/remix-run/react-router/pull/9394))
677 - Enhance console error messages for invalid usage of data router hooks ([#9311](https://github.com/remix-run/react-router/pull/9311))
678 - 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))
679 - Updated dependencies:
680 - `@remix-run/router@1.0.2`
681
682 ## 6.4.1
683
684 ### Patch Changes
685
686 - Preserve state from `initialEntries` ([#9288](https://github.com/remix-run/react-router/pull/9288))
687 - Updated dependencies:
688 - `@remix-run/router@1.0.1`
689
690 ## 6.4.0
691
692 Whoa 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).
693
694 **New APIs**
695
696 - Create your router with `createMemoryRouter`
697 - Render your router with `<RouterProvider>`
698 - Load data with a Route `loader` and mutate with a Route `action`
699 - Handle errors with Route `errorElement`
700 - Defer non-critical data with `defer` and `Await`
701
702 **Bug Fixes**
703
704 - Path resolution is now trailing slash agnostic (#8861)
705 - `useLocation` returns the scoped location inside a `<Routes location>` component (#9094)
706
707 **Updated Dependencies**
708
709 - `@remix-run/router@1.0.0`