Skip to content

Commit 243f788

Browse files
remix-run-botremix-run-bot
committed
chore: format
1 parent 21943f4 commit 243f788

File tree

7 files changed

+0
-23
lines changed

7 files changed

+0
-23
lines changed

‎integration/CHANGELOG.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@
55
### Minor Changes
66

77
- Unstable Vite support for Node-based Remix apps ([#7590](https://github.com/remix-run/remix/pull/7590))
8-
98
- `remix build` 👉 `vite build && vite build --ssr`
109
- `remix dev` 👉 `vite dev`
1110

‎packages/react-router-architect/CHANGELOG.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,6 @@
182182
### Major Changes
183183

184184
- 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-
186185
- `createCookie`
187186
- `createCookieSessionStorage`
188187
- `createMemorySessionStorage`
@@ -191,7 +190,6 @@
191190
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)
192191

193192
Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:
194-
195193
- `createCookieFactory`
196194
- `createSessionStorageFactory`
197195
- `createCookieSessionStorageFactory`

‎packages/react-router-cloudflare/CHANGELOG.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -161,7 +161,6 @@
161161

162162
- 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))
163163
- 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-
165164
- `createCookie`
166165
- `createCookieSessionStorage`
167166
- `createMemorySessionStorage`
@@ -170,7 +169,6 @@
170169
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)
171170

172171
Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:
173-
174172
- `createCookieFactory`
175173
- `createSessionStorageFactory`
176174
- `createCookieSessionStorageFactory`

‎packages/react-router-dev/CHANGELOG.md

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -698,7 +698,6 @@
698698
```
699699
700700
This initial implementation targets type inference for:
701-
702701
- `Params` : Path parameters from your routing config in `routes.ts` including file-based routing
703702
- `LoaderData` : Loader data from `loader` and/or `clientLoader` within your route module
704703
- `ActionData` : Action data from `action` and/or `clientAction` within your route module
@@ -713,7 +712,6 @@
713712
```
714713
715714
Check out our docs for more:
716-
717715
- [_Explanations > Type Safety_](https://reactrouter.com/dev/guides/explanation/type-safety)
718716
- [_How-To > Setting up type safety_](https://reactrouter.com/dev/guides/how-to/setting-up-type-safety)
719717
@@ -913,7 +911,6 @@
913911
- Vite: Provide `Unstable_ServerBundlesFunction` and `Unstable_VitePluginConfig` types ([#8654](https://github.com/remix-run/remix/pull/8654))
914912
915913
- Vite: add `--sourcemapClient` and `--sourcemapServer` flags to `remix vite:build` ([#8613](https://github.com/remix-run/remix/pull/8613))
916-
917914
- `--sourcemapClient`
918915
919916
- `--sourcemapClient=inline`
@@ -1250,7 +1247,6 @@
12501247
- 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))
12511248
12521249
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-
12541250
- Leveraging a data source local to the browser (i.e., `localStorage`)
12551251
- Managing a client-side cache of server data (like `IndexedDB`)
12561252
- Bypassing the Remix server in a BFF setup and hitting your API directly from the browser
@@ -1654,7 +1650,6 @@
16541650
- Output esbuild metafiles for bundle analysis ([#6772](https://github.com/remix-run/remix/pull/6772))
16551651
16561652
Written to server build directory (`build/` by default):
1657-
16581653
- `metafile.css.json`
16591654
- `metafile.js.json` (browser JS)
16601655
- `metafile.server.json` (server JS)
@@ -1752,7 +1747,6 @@
17521747
- built-in tls support ([#6483](https://github.com/remix-run/remix/pull/6483))
17531748
17541749
New options:
1755-
17561750
- `--tls-key` / `tlsKey`: TLS key
17571751
- `--tls-cert` / `tlsCert`: TLS Certificate
17581752
@@ -2023,7 +2017,6 @@
20232017
```
20242018
20252019
The dev server will:
2026-
20272020
- force `NODE_ENV=development` and warn you if it was previously set to something else
20282021
- rebuild your app whenever your Remix app code changes
20292022
- restart your app server whenever rebuilds succeed

‎packages/react-router-node/CHANGELOG.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -162,7 +162,6 @@
162162
- Remove single fetch future flag. ([#11522](https://github.com/remix-run/react-router/pull/11522))
163163

164164
- 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-
166165
- `createCookie`
167166
- `createCookieSessionStorage`
168167
- `createMemorySessionStorage`
@@ -171,7 +170,6 @@
171170
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)
172171

173172
Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:
174-
175173
- `createCookieFactory`
176174
- `createSessionStorageFactory`
177175
- `createCookieSessionStorageFactory`
@@ -579,12 +577,10 @@
579577
- 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))
580578
581579
Informational Resources:
582-
583580
- <https://gist.github.com/jacob-ebey/9bde9546c1aafaa6bc8c242054b1be26>
584581
- <https://github.com/remix-run/remix/blob/main/decisions/0004-streaming-apis.md>
585582
586583
Documentation Resources (better docs specific to Remix are in the works):
587-
588584
- <https://reactrouter.com/en/main/utils/defer>
589585
- <https://reactrouter.com/en/main/components/await>
590586
- <https://reactrouter.com/en/main/hooks/use-async-value>

‎packages/react-router-serve/CHANGELOG.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -581,12 +581,10 @@
581581
- 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))
582582

583583
Informational Resources:
584-
585584
- <https://gist.github.com/jacob-ebey/9bde9546c1aafaa6bc8c242054b1be26>
586585
- <https://github.com/remix-run/remix/blob/main/decisions/0004-streaming-apis.md>
587586

588587
Documentation Resources (better docs specific to Remix are in the works):
589-
590588
- <https://reactrouter.com/en/main/utils/defer>
591589
- <https://reactrouter.com/en/main/components/await>
592590
- <https://reactrouter.com/en/main/hooks/use-async-value>

‎packages/react-router/CHANGELOG.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -604,7 +604,6 @@
604604
```
605605

606606
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:
607-
608607
- Library mode - `createBrowserRouter(routes, { unstable_getContext })`
609608
- Framework mode - `<HydratedRouter unstable_getContext>`
610609

@@ -792,7 +791,6 @@ _No changes_
792791
- Remove `future.v7_normalizeFormMethod` future flag ([#11697](https://github.com/remix-run/react-router/pull/11697))
793792

794793
- 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-
796794
- `createCookie`
797795
- `createCookieSessionStorage`
798796
- `createMemorySessionStorage`
@@ -801,7 +799,6 @@ _No changes_
801799
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)
802800

803801
Since platform-specific packages no longer need to implement this API, the following low-level APIs have been removed:
804-
805802
- `createCookieFactory`
806803
- `createSessionStorageFactory`
807804
- `createCookieSessionStorageFactory`
@@ -957,7 +954,6 @@ _No changes_
957954
```
958955

959956
This initial implementation targets type inference for:
960-
961957
- `Params` : Path parameters from your routing config in `routes.ts` including file-based routing
962958
- `LoaderData` : Loader data from `loader` and/or `clientLoader` within your route module
963959
- `ActionData` : Action data from `action` and/or `clientAction` within your route module
@@ -972,7 +968,6 @@ _No changes_
972968
```
973969

974970
Check out our docs for more:
975-
976971
- [_Explanations > Type Safety_](https://reactrouter.com/dev/guides/explanation/type-safety)
977972
- [_How-To > Setting up type safety_](https://reactrouter.com/dev/guides/how-to/setting-up-type-safety)
978973

0 commit comments

Comments
 (0)