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: docs/upgrading/future.md
+56Lines changed: 56 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,4 +48,60 @@ If you're using `react-router-serve`, then you should not need to make any updat
48
48
49
49
You should only need to update your code if you are using the `context` parameter in `loader` and `action` functions. This only applies if you have a custom server with a `getLoadContext` function. Please see the docs on the middleware [`getLoadContext` changes](../how-to/middleware#changes-to-getloadcontextapploadcontext) and the instructions to [migrate to the new API](../how-to/middleware#migration-from-apploadcontext).
50
50
51
+
## `future.v8_splitRouteModules`
52
+
53
+
[MODES: framework]
54
+
55
+
<br/>
56
+
<br/>
57
+
58
+
**Background**
59
+
60
+
This feature enables splitting client-side route exports (`clientLoader`, `clientAction`, `clientMiddleware`, `HydrateFallback`) into separate chunks that can be loaded independently from the route component. This allows these exports to be fetched and executed while the component code is still downloading, improving performance for client-side data loading.
61
+
62
+
This can be set to `true` for opt-in behavior, or `"enforce"` to require all routes to be splittable (which will cause build failures for routes that cannot be split due to shared code).
No code changes are required. This is an optimization feature that works automatically once enabled.
79
+
80
+
## `future.v8_viteEnvironmentApi`
81
+
82
+
[MODES: framework]
83
+
84
+
<br/>
85
+
<br/>
86
+
87
+
**Background**
88
+
89
+
This enables support for the experimental Vite Environment API, which provides a more flexible and powerful way to configure Vite environments. This is only available when using Vite 6+.
No code changes are required unless you have custom Vite configuration that needs to be updated for the Environment API. Most users won't need to make any changes.
0 commit comments