chore: format

.changeset/single-fetch.md

@@ -7,9 +7,9 @@
 
 New `future.unstable_singleFetch` flag
 
-- Naked objects returned from loaders/actions are no longer automatically converted to JSON responses.  They'll be streamed as-is via `turbo-stream` so `Date`'s will become `Date` through `useLoaderData()`
+- Naked objects returned from loaders/actions are no longer automatically converted to JSON responses. They'll be streamed as-is via `turbo-stream` so `Date`'s will become `Date` through `useLoaderData()`
 - You can return naked objects with `Promise`'s without needing to use `defer()` - including nested `Promise`'s
   - If you need to return a custom status code or custom response headers, you can still use the `defer` utility
-- `<RemixServer abortDelay>` is no longer used.  Instead, you should `export const streamTimeout` from `entry.server.tsx` and the remix server runtime will use that as the delay to abort the streamed response
-  - If you export your own streamTimeout, you should decouple that from aborting the react `renderToPipeableStream`.  You should always ensure that react is aborted _afer_ the stream is aborted so that abort rejections can be flushed down
+- `<RemixServer abortDelay>` is no longer used. Instead, you should `export const streamTimeout` from `entry.server.tsx` and the remix server runtime will use that as the delay to abort the streamed response
+  - If you export your own streamTimeout, you should decouple that from aborting the react `renderToPipeableStream`. You should always ensure that react is aborted _afer_ the stream is aborted so that abort rejections can be flushed down
 - Actions no longer automatically revalidate on 4xx/5xx responses (via RR `future.unstable_skipActionErrorRevalidation` flag) - you can return a 2xx to opt-into revalidation or use `shouldRevalidate`