You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CHANGELOG.md
+7-18
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ We manage release notes in this file instead of the paginated Github Releases Pa
15
15
-[React Router Releases](#react-router-releases)
16
16
-[v7.5.0](#v750)
17
17
-[What's Changed](#whats-changed)
18
-
-[Object API for `route.lazy`](#object-api-for-routelazy)
18
+
-[`route.lazy` Object API](#routelazy-object-api)
19
19
-[Minor Changes](#minor-changes)
20
20
-[Patch Changes](#patch-changes)
21
21
-[Unstable Changes](#unstable-changes)
@@ -318,13 +318,13 @@ Date: YYYY-MM-DD
318
318
319
319
## v7.5.0
320
320
321
-
Date: 2025-04-03
321
+
Date: 2025-04-04
322
322
323
323
### What's Changed
324
324
325
-
#### Object API for `route.lazy`
325
+
#### `route.lazy` Object API
326
326
327
-
We've introduced a new `route.lazy` API which gives you more granular control over the lazy loading of route properties that you could not achieve with the `route.lazy` function signature. This is useful for Framework mode and performance-critical library mode applications.
327
+
We've introduced a new `route.lazy` API which gives you more granular control over the lazy loading of route properties that you could not achieve with the `route.lazy()` function signature. This is useful for Framework mode and performance-critical library mode applications.
328
328
329
329
```ts
330
330
createBrowserRouter([
@@ -339,20 +339,7 @@ createBrowserRouter([
339
339
]);
340
340
```
341
341
342
-
⚠️ This is a breaking change if you have adopted the `route.unstable_lazyMiddleware` API which has been removed in favor of `route.lazy.unstable_middleware`. If you want to lazily load middleware, you must use the new object-based `route.lazy` API:
343
-
344
-
```ts
345
-
createBrowserRouter([
346
-
{
347
-
path: "/show/:showId",
348
-
lazy: {
349
-
unstable_middleware: async () =>
350
-
(awaitimport("./show.middleware.js")).middleware,
351
-
// etc.
352
-
},
353
-
},
354
-
]);
355
-
```
342
+
⚠️ This is a breaking change if you have adopted the `route.unstable_lazyMiddleware` API which has been removed in favor of `route.lazy.unstable_middleware`. See the `Unstable Changes` section below for more information.
356
343
357
344
### Minor Changes
358
345
@@ -368,6 +355,8 @@ createBrowserRouter([
368
355
⚠️ _[Unstable features](https://reactrouter.com/community/api-development-strategy#unstable-flags) are not recommended for production use_
369
356
370
357
-`react-router` - Introduce `future.unstable_subResourceIntegrity` flag that enables generation of an `importmap` with `integrity` for the scripts that will be loaded by the browser ([#13163](https://github.com/remix-run/react-router/pull/13163))
358
+
-`react-router` - Remove support for the `route.unstable_lazyMiddleware` property ([#13294](https://github.com/remix-run/react-router/pull/13294))
359
+
- In order to lazily load middleware, you can use the new object-based `route.lazy.unstable_middleware` API
371
360
-`@react-router/dev` - When `future.unstable_viteEnvironmentApi` is enabled, ensure critical CSS in development works when using a custom Vite `base` has been configured ([#13305](https://github.com/remix-run/react-router/pull/13305))
- When `future.unstable_viteEnvironmentApi` is enabled, ensure critical CSS in development works when using a custom Vite `base` has been configured ([#13305](https://github.com/remix-run/react-router/pull/13305))
19
10
- Reinstate dependency optimization in the child compiler to fix `depsOptimizer is required in dev mode` errors when using `vite-plugin-cloudflare` and importing Node.js builtins ([#13317](https://github.com/remix-run/react-router/pull/13317))
0 commit comments