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: packages/react-router-architect/CHANGELOG.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -182,7 +182,6 @@
182
182
### Major Changes
183
183
184
184
- For Remix consumers migrating to React Router, the `crypto` global from the [Web Crypto API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API) is now required when using cookie and session APIs. This means that the following APIs are provided from `react-router` rather than platform-specific packages: ([#11837](https://github.com/remix-run/react-router/pull/11837))
185
-
186
185
-`createCookie`
187
186
-`createCookieSessionStorage`
188
187
-`createMemorySessionStorage`
@@ -191,7 +190,6 @@
191
190
For consumers running older versions of Node, the `installGlobals` function from `@remix-run/node` has been updated to define `globalThis.crypto`, using [Node's `require('node:crypto').webcrypto` implementation.](https://nodejs.org/api/webcrypto.html)
192
191
193
192
Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:
Copy file name to clipboardExpand all lines: packages/react-router-cloudflare/CHANGELOG.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -161,7 +161,6 @@
161
161
162
162
- For Remix consumers migrating to React Router, all exports from `@remix-run/cloudflare-pages` are now provided for React Router consumers in the `@react-router/cloudflare` package. There is no longer a separate package for Cloudflare Pages. ([#11801](https://github.com/remix-run/react-router/pull/11801))
163
163
- For Remix consumers migrating to React Router, the `crypto` global from the [Web Crypto API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API) is now required when using cookie and session APIs. This means that the following APIs are provided from `react-router` rather than platform-specific packages: ([#11837](https://github.com/remix-run/react-router/pull/11837))
164
-
165
164
-`createCookie`
166
165
-`createCookieSessionStorage`
167
166
-`createMemorySessionStorage`
@@ -170,7 +169,6 @@
170
169
For consumers running older versions of Node, the `installGlobals` function from `@remix-run/node` has been updated to define `globalThis.crypto`, using [Node's `require('node:crypto').webcrypto` implementation.](https://nodejs.org/api/webcrypto.html)
171
170
172
171
Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:
Copy file name to clipboardExpand all lines: packages/react-router-dev/CHANGELOG.md
-7Lines changed: 0 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -698,7 +698,6 @@
698
698
```
699
699
700
700
This initial implementation targets type inference for:
701
-
702
701
- `Params` : Path parameters from your routing config in `routes.ts` including file-based routing
703
702
- `LoaderData` : Loader data from `loader` and/or `clientLoader` within your route module
704
703
- `ActionData` : Action data from `action` and/or `clientAction` within your route module
@@ -713,7 +712,6 @@
713
712
```
714
713
715
714
Check out our docs for more:
716
-
717
715
- [_Explanations > Type Safety_](https://reactrouter.com/dev/guides/explanation/type-safety)
718
716
- [_How-To > Setting up type safety_](https://reactrouter.com/dev/guides/how-to/setting-up-type-safety)
719
717
@@ -913,7 +911,6 @@
913
911
- Vite: Provide `Unstable_ServerBundlesFunction` and `Unstable_VitePluginConfig` types ([#8654](https://github.com/remix-run/remix/pull/8654))
914
912
915
913
- Vite: add `--sourcemapClient` and `--sourcemapServer` flags to `remix vite:build` ([#8613](https://github.com/remix-run/remix/pull/8613))
916
-
917
914
- `--sourcemapClient`
918
915
919
916
- `--sourcemapClient=inline`
@@ -1250,7 +1247,6 @@
1250
1247
- Add support for `clientLoader`/`clientAction`/`HydrateFallback` route exports ([RFC](https://github.com/remix-run/remix/discussions/7634)) ([#8173](https://github.com/remix-run/remix/pull/8173))
1251
1248
1252
1249
Remix now supports loaders/actions that run on the client (in addition to, or instead of the loader/action that runs on the server). While we still recommend server loaders/actions for the majority of your data needs in a Remix app - these provide some levers you can pull for more advanced use-cases such as:
1253
-
1254
1250
- Leveraging a data source local to the browser (i.e., `localStorage`)
1255
1251
- Managing a client-side cache of server data (like `IndexedDB`)
1256
1252
- Bypassing the Remix server in a BFF setup and hitting your API directly from the browser
@@ -1654,7 +1650,6 @@
1654
1650
- Output esbuild metafiles for bundle analysis ([#6772](https://github.com/remix-run/remix/pull/6772))
1655
1651
1656
1652
Written to server build directory (`build/` by default):
1657
-
1658
1653
- `metafile.css.json`
1659
1654
- `metafile.js.json` (browser JS)
1660
1655
- `metafile.server.json` (server JS)
@@ -1752,7 +1747,6 @@
1752
1747
- built-in tls support ([#6483](https://github.com/remix-run/remix/pull/6483))
1753
1748
1754
1749
New options:
1755
-
1756
1750
- `--tls-key` / `tlsKey`: TLS key
1757
1751
- `--tls-cert` / `tlsCert`: TLS Certificate
1758
1752
@@ -2023,7 +2017,6 @@
2023
2017
```
2024
2018
2025
2019
The dev server will:
2026
-
2027
2020
- force `NODE_ENV=development` and warn you if it was previously set to something else
2028
2021
- rebuild your app whenever your Remix app code changes
2029
2022
- restart your app server whenever rebuilds succeed
Copy file name to clipboardExpand all lines: packages/react-router-node/CHANGELOG.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -162,7 +162,6 @@
162
162
- Remove single fetch future flag. ([#11522](https://github.com/remix-run/react-router/pull/11522))
163
163
164
164
- For Remix consumers migrating to React Router, the `crypto` global from the [Web Crypto API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API) is now required when using cookie and session APIs. This means that the following APIs are provided from `react-router` rather than platform-specific packages: ([#11837](https://github.com/remix-run/react-router/pull/11837))
165
-
166
165
-`createCookie`
167
166
-`createCookieSessionStorage`
168
167
-`createMemorySessionStorage`
@@ -171,7 +170,6 @@
171
170
For consumers running older versions of Node, the `installGlobals` function from `@remix-run/node` has been updated to define `globalThis.crypto`, using [Node's `require('node:crypto').webcrypto` implementation.](https://nodejs.org/api/webcrypto.html)
172
171
173
172
Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:
174
-
175
173
-`createCookieFactory`
176
174
-`createSessionStorageFactory`
177
175
-`createCookieSessionStorageFactory`
@@ -579,12 +577,10 @@
579
577
- Introduces the `defer()` API from `@remix-run/router` with support for server-rendering and HTTP streaming. This utility allows you to defer values returned from `loader` functions by returning promises instead of resolved values. This has been refered to as _"sending a promise over the wire"_. ([#4920](https://github.com/remix-run/remix/pull/4920))
Copy file name to clipboardExpand all lines: packages/react-router-serve/CHANGELOG.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -581,12 +581,10 @@
581
581
- Introduces the `defer()`API from `@remix-run/router`with support for server-rendering and HTTPstreaming. This utility allows you to defer values returned from `loader` functions by returning promises instead of resolved values. This has been refered to as _"sending a promise over the wire"_. ([#4920](https://github.com/remix-run/remix/pull/4920))
Copy file name to clipboardExpand all lines: packages/react-router/CHANGELOG.md
-5Lines changed: 0 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -604,7 +604,6 @@
604
604
```
605
605
606
606
Similar to server-side requests, a fresh `context` will be created per navigation (or `fetcher` call). If you have initial data you'd like to populate in the context for every request, you can provide an `unstable_getContext` function at the root of your app:
- Remove `future.v7_normalizeFormMethod` future flag ([#11697](https://github.com/remix-run/react-router/pull/11697))
793
792
794
793
- For Remix consumers migrating to React Router, the `crypto` global from the [Web Crypto API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API) is now required when using cookie and session APIs. This means that the following APIs are provided from `react-router` rather than platform-specific packages: ([#11837](https://github.com/remix-run/react-router/pull/11837))
795
-
796
794
- `createCookie`
797
795
- `createCookieSessionStorage`
798
796
- `createMemorySessionStorage`
@@ -801,7 +799,6 @@ _No changes_
801
799
For consumers running older versions of Node, the `installGlobals` function from `@remix-run/node` has been updated to define `globalThis.crypto`, using [Node's `require('node:crypto').webcrypto` implementation.](https://nodejs.org/api/webcrypto.html)
802
800
803
801
Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:
804
-
805
802
- `createCookieFactory`
806
803
- `createSessionStorageFactory`
807
804
- `createCookieSessionStorageFactory`
@@ -957,7 +954,6 @@ _No changes_
957
954
```
958
955
959
956
This initial implementation targets type inference for:
960
-
961
957
- `Params` : Path parameters from your routing config in `routes.ts` including file-based routing
962
958
- `LoaderData` : Loader data from `loader` and/or `clientLoader` within your route module
963
959
- `ActionData` : Action data from `action` and/or `clientAction` within your route module
@@ -972,7 +968,6 @@ _No changes_
972
968
```
973
969
974
970
Check out our docs for more:
975
-
976
971
- [_Explanations > Type Safety_](https://reactrouter.com/dev/guides/explanation/type-safety)
977
972
- [_How-To > Setting up type safety_](https://reactrouter.com/dev/guides/how-to/setting-up-type-safety)
0 commit comments