fix(deps): update remix monorepo to v2.15.0 - autoclosed #32

renovate · 2022-06-18T13:12:10Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@remix-run/css-bundle (source)	`2.7.2` -> `2.15.0`
@remix-run/dev (source)	`2.7.2` -> `2.15.0`
@remix-run/express (source)	`2.7.2` -> `2.15.0`
@remix-run/node (source)	`2.7.2` -> `2.15.0`
@remix-run/react (source)	`2.7.2` -> `2.15.0`

Release Notes

remix-run/remix (@remix-run/css-bundle)

`v2.15.0`

Compare Source

`v2.14.0`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.14.0.

`v2.13.1`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.13.1.

`v2.13.0`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.13.0.

`v2.12.1`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.12.1.

`v2.12.0`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.12.0.

`v2.11.2`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.11.2.

`v2.11.1`

Compare Source

`v2.11.0`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.11.0.

`v2.10.3`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.10.3.

`v2.10.2`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.10.2.

`v2.10.1`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.10.1.

`v2.10.0`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.10.0.

`v2.9.2`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.9.2.

`v2.9.1`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.9.1.

`v2.9.0`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.9.0.

`v2.8.1`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.8.1.

`v2.8.0`

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.8.0.

remix-run/remix (@remix-run/dev)

`v2.15.0`

Compare Source

Patch Changes

Stabilize the future.v3_routeConfig future flag, replacing future.unstable_routeConfig. This enables support for routes.ts to assist with the migration to React Router v7. (#10236)

Note that if you had already enabled the future.unstable_routeConfig flag, your route config in app/routes.ts is no longer defined via the routes export and must now be defined via the default export.
```
import { type RouteConfig } from "@&#8203;remix-run/route-config";

-export const routes: RouteConfig = [];
+export default [] satisfies RouteConfig;
```
Updated dependencies:
- @remix-run/node@2.15.0
- @remix-run/server-runtime@2.15.0

`v2.14.0`

Compare Source

Minor Changes

Add support for routes.ts behind future.unstable_routeConfig flag to assist with the migration to React Router v7. (#10107)

Config-based routing is the new default in React Router v7, configured via the routes.ts file in the app directory. Support for routes.ts and its related APIs in Remix are designed as a migration path to help minimize the number of changes required when moving your Remix project over to React Router v7. While some new packages have been introduced within the @remix-run scope, these new packages only exist to keep the code in routes.ts as similar as possible to the equivalent code for React Router v7.

When the unstable_routeConfig future flag is enabled, Remix's built-in file system routing will be disabled and your project will opted into React Router v7's config-based routing.

To enable the flag, in your vite.config.ts file:
```
remix({
  future: {
    unstable_routeConfig: true,
  },
});
```
A minimal routes.ts file to support Remix's built-in file system routing looks like this:
```
// app/routes.ts
import { flatRoutes } from "@&#8203;remix-run/fs-routes";
import type { RouteConfig } from "@&#8203;remix-run/route-config";

export const routes: RouteConfig = flatRoutes();
```
Log deprecation warnings for v3 future flags (#10126)
- Add @deprecated annotations to json/defer utilities

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.14.0
- @remix-run/node@2.14.0

`v2.13.1`

Compare Source

Patch Changes

Revert future.v3_optimizeDeps back to future.unstable_optimizeDeps as it was not intended to stabilize in Remix v2 (#10099)
Updated dependencies:
- @remix-run/node@2.13.1
- @remix-run/server-runtime@2.13.1

`v2.13.0`

Compare Source

Minor Changes

Stabilize the future.unstable_optimizeDeps flag into future.v3_optimizeDeps (#10092)
Stabilize React Router APIs in Remix (#9980)
- Adopt stabilized React Router APIs internally
  - Single Fetch: unstable_dataStrategy -> dataStrategy
  - Lazy Route Discovery: unstable_patchRoutesOnNavigation -> patchRoutesOnNavigation
- Stabilize public-facing APIs
  - Single Fetch: unstable_data() -> data()
  - unstable_viewTransition -> viewTransition (Link, Form, navigate, submit)
  - unstable_flushSync> -> <Link viewTransition> (Link, Form, navigate, submit, useFetcher)
Stabilize future flags (#10072)
- future.unstable_singleFetch -> future.v3_singleFetch
- future.unstable_lazyRouteDiscovery -> future.v3_lazyRouteDiscovery

Patch Changes

Stop passing request.signal as the renderToReadableStream signal to abort server rendering for cloudflare/deno runtimes because by the time that request is aborted, aborting the rendering is useless because there's no way for React to flush down the unresolved boundaries (#10047)
- This has been incorrect for some time, but only recently exposed due to a bug in how we were aborting requests when running via remix vite:dev because we were incorrectly aborting requests after successful renders - which was causing us to abort a completed React render, and try to close an already closed ReadableStream.
- This has likely not shown up in any production scenarios because cloudflare/deno production runtimes are (correctly) not aborting the request.signal on successful renders
- The built-in entry.server files no longer pass a signal to renderToReadableStream because adding a timeout-based abort signal to the default behavior would constitute a breaking change
- Users can configure this abort behavior via their own entry.server via remix reveal entry.server, and the template entry.server files have been updated with an example approach for newly created Remix apps
Fix adapter logic for aborting request.signal so we don't incorrectly abort on the close event for successful requests (#10046)
Updated dependencies:
- @remix-run/server-runtime@2.13.0
- @remix-run/node@2.13.0

`v2.12.1`

Compare Source

Patch Changes

Properly abort request.signal during vite dev when the node response is closed (#9976)
CSS imports with ?inline, ?inline-css and ?raw are no longer incorrectly injected during SSR in development (#9910)
Updated dependencies:
- @remix-run/server-runtime@2.12.1
- @remix-run/node@2.12.1

`v2.12.0`

Compare Source

Minor Changes

New future.unstable_optimizeDeps flag for automatic dependency optimization (#9921)
- You can now opt-in to automatic dependency optimization during development by using the future.unstable_optimizeDeps future flag
- For details, check out the docs at Guides > Dependency optimization
- For users who were previously working around this limitation, you no longer need to explicitly add routes to Vite's optimizeDeps.entries nor do you need to disable the remix-dot-server plugin

Patch Changes

Handle circular dependencies in modulepreload manifest generation (#9917)
Fix dest already exists build errors by only moving SSR assets to the client build directory when they're not already present on disk (#9901)
Updated dependencies:
- @remix-run/server-runtime@2.12.0
- @remix-run/node@2.12.0

`v2.11.2`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.11.2
- @remix-run/node@2.11.2

`v2.11.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.11.1
- @remix-run/node@2.11.1

`v2.11.0`

Compare Source

Minor Changes

Rename future.unstable_fogOfWar to future.unstable_lazyRouteDiscovery for clarity (#9763)

Patch Changes

Handle absolute Vite base URLs (#9700)
Updated dependencies:
- @remix-run/node@2.11.0
- @remix-run/server-runtime@2.11.0

`v2.10.3`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.10.3
- @remix-run/server-runtime@2.10.3

`v2.10.2`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.10.2
- @remix-run/node@2.10.2

`v2.10.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.10.1
- @remix-run/server-runtime@2.10.1

`v2.10.0`

Compare Source

Patch Changes

Upgrade express dependency to ^4.19.2 (#9184)
Updated dependencies:
- @remix-run/server-runtime@2.10.0
- @remix-run/node@2.10.0

`v2.9.2`

Compare Source

Patch Changes

Fix dest already exists error when running remix vite:build (#9305)
Vite: Fix issue resolving critical CSS during development when route files are located outside of the app directory. (#9194)
Remove @remix-run/node from Vite plugin's optimizeDeps.include list since it was unnecessary and resulted in Vite warnings when not depending on this package. (#9287)
Clean up redundant ?client-route=1 imports in development (#9395)
Ensure Babel config files are not referenced when applying the react-refresh Babel transform within the Remix Vite plugin (#9241)
Updated dependencies:
- @remix-run/server-runtime@2.9.2
- @remix-run/node@2.9.2

`v2.9.1`

Compare Source

Patch Changes

Fix issue where consumers who had added Remix packages to Vite's ssr.noExternal option were being overridden by the Remix Vite plugin adding Remix packages to Vite's ssr.external option (#9301)
Updated dependencies:
- @remix-run/node@2.9.1
- @remix-run/server-runtime@2.9.1

`v2.9.0`

Compare Source

Minor Changes

New future.unstable_singleFetch flag (#8773)
- 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
- 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

Patch Changes

Improve getDependenciesToBundle resolution in monorepos (#8848)
Fix SPA mode when single fetch is enabled by using streaming entry.server (#9063)
Vite: added sourcemap support for transformed routes (#8970)
Update links printed to the console by the Remix CLI/Dev Server to point to updated docs locations (#9176)
Updated dependencies:
- @remix-run/node@2.9.0
- @remix-run/server-runtime@2.9.0

`v2.8.1`

Compare Source

Patch Changes

Support reading from Vite config when running remix reveal and remix routes CLI commands (#8916)
Add Vite commands to Remix CLI --help output (#8939)
Vite: Fix support for build.sourcemap option in Vite config (#8965)
Clean up redundant client route query strings on route JavaScript files in production builds (#8969)
Vite: Fix error when using Vite's server.fs.allow option without a client entry file (#8966)
Updated dependencies:
- @remix-run/node@2.8.1
- @remix-run/server-runtime@2.8.1

`v2.8.0`

Compare Source

Minor Changes

Pass resolved viteConfig to Remix Vite plugin's buildEnd hook (#8885)

Patch Changes

Mark Layout as browser safe route export in esbuild compiler (#8842)
Vite: Silence build warnings when dependencies include "use client" directives (#8897)
Vite: Fix serverBundles issue where multiple browser manifests are generated (#8864)
Support custom Vite build.assetsDir option (#8843)
Updated dependencies:
- @remix-run/node@2.8.0
- @remix-run/server-runtime@2.8.0

remix-run/remix (@remix-run/express)

`v2.15.0`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.15.0

`v2.14.0`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.14.0

`v2.13.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.13.1

`v2.13.0`

Compare Source

Patch Changes

Fix adapter logic for aborting request.signal so we don't incorrectly abort on the close event for successful requests (#10046)
Updated dependencies:
- @remix-run/node@2.13.0

`v2.12.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.12.1

`v2.12.0`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.12.0

`v2.11.2`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.11.2

`v2.11.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.11.1

`v2.11.0`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.11.0

`v2.10.3`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.10.3

`v2.10.2`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.10.2

`v2.10.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.10.1

`v2.10.0`

Compare Source

Patch Changes

Upgrade express dependency to ^4.19.2 (#9184)
Updated dependencies:
- @remix-run/node@2.10.0

`v2.9.2`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.9.2

`v2.9.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.9.1

`v2.9.0`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.9.0

`v2.8.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.8.1

`v2.8.0`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/node@2.8.0

remix-run/remix (@remix-run/node)

`v2.15.0`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.15.0

`v2.14.0`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.14.0

`v2.13.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.13.1

`v2.13.0`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.13.0

`v2.12.1`

Compare Source

Patch Changes

Single Fetch: Re-export interface Future through @remix-run/node/@remix-run/cloudflare/@remix-run/deno packages so that pnpm doesn't complain about @remix-run/server-runtime not being a dependency (#9982)
Updated dependencies:
- @remix-run/server-runtime@2.12.1

`v2.12.0`

Compare Source

Patch Changes

Single Fetch: Improved typesafety (#9893)

If you were already using previously released unstable single-fetch types:
- Remove "@remix-run/react/future/single-fetch.d.ts" override from tsconfig.json > compilerOptions > types
- Remove defineLoader, defineAction, defineClientLoader, defineClientAction helpers from your route modules
- Replace UIMatch_SingleFetch type helper with UIMatch
- Replace MetaArgs_SingleFetch type helper with MetaArgs
Then you are ready for the new typesafety setup:
```
// vite.config.ts

declare module "@&#8203;remix-run/server-runtime" {
  interface Future {
    unstable_singleFetch: true; // 👈 enable _types_ for single-fetch
  }
}

export default defineConfig({
  plugins: [
    remix({
      future: {
        unstable_singleFetch: true, // 👈 enable single-fetch
      },
    }),
  ],
});
```
For more information, see Guides > Single Fetch in our docs.
Updated dependencies:
- @remix-run/server-runtime@2.12.0

`v2.11.2`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.11.2

`v2.11.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.11.1

`v2.11.0`

Compare Source

Minor Changes

Single Fetch: Add a new unstable_data() API as a replacement for json/defer when custom status/headers are needed (#9769)
Add a new replace(url, init?) alternative to redirect(url, init?) that performs a history.replaceState instead of a history.pushState on client-side navigation redirects (#9764)

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.11.0

`v2.10.3`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.10.3

`v2.10.2`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.10.2

`v2.10.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.10.1

`v2.10.0`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.10.0

`v2.9.2`

Compare Source

Patch Changes

Typesafety for single-fetch: defineLoader, defineClientLoader, defineAction, defineClientAction (#9372, #9404)
Updated dependencies:
- @remix-run/server-runtime@2.9.2

`v2.9.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.9.1

`v2.9.0`

Compare Source

Minor Changes

Use undici as our fetch polyfill going forward (#9106, #9111)
Put undici fetch polyfill behind a new installGlobals({ nativeFetch: true }) parameter (#9198)
- remix-serve will default to using undici for the fetch polyfill if future._unstable_singleFetch is enabled because the single fetch implementation relies on the undici polyfill
  - Any users opting into Single Fetch and managing their own polfill will need to pass the flag to installGlobals on their own to avoid runtime errors with Single Fetch

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.9.0

`v2.8.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.8.1

`v2.8.0`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.8.0

remix-run/remix (@remix-run/react)

`v2.15.0`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.15.0

`v2.14.0`

Compare Source

Patch Changes

Fix defaultShouldRevalidate value when using single fetch (#10139)
Updated dependencies:
- @remix-run/server-runtime@2.14.0

`v2.13.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.13.1

`v2.13.0`

Compare Source

Minor Changes

Stabilize React Router APIs in Remix (#9980)
- Adopt stabilized React Router APIs internally
  - Single Fetch: unstable_dataStrategy -> dataStrategy
  - Lazy Route Discovery: unstable_patchRoutesOnNavigation -> patchRoutesOnNavigation
- Stabilize public-facing APIs
  - Single Fetch: unstable_data() -> data()
  - unstable_viewTransition -> viewTransition (Link, Form, navigate, submit)
  - unstable_flushSync> -> <Link viewTransition> (Link, Form, navigate, submit, useFetcher)
Stabilize future flags (#10072)
- future.unstable_singleFetch -> future.v3_singleFetch
- future.unstable_lazyRouteDiscovery -> future.v3_lazyRouteDiscovery

Patch Changes

Fix bug with clientLoader.hydrate in a layout route when hydrating with bubbled errors (#10063)
Updated dependencies:
- @remix-run/server-runtime@2.13.0

`v2.12.1`

Compare Source

Patch Changes

Updated dependencies:
- @remix-run/server-runtime@2.12.1

`v2.12.0`

Compare Source

Patch Changes

Lazy Route Discovery: Sort /__manifest query parameters for better caching (#9888)
Single Fetch: fix revalidation behavior bugs (#9938)
- With Single Fetch, existing routes revalidate by default
- This means requests do not need special query params for granular route revalidations out of the box - i.e., GET /a/b/c.data
- There are two conditions that will trigger granular revalidation:
  - If a route opts out of revalidation via shouldRevalidate, it will be excluded from the single fetch call
  - If a route defines a clientLoader then it will be excluded from the single fetch call and if you call serverLoader() from your clientLoader, that will make a separarte HTTP call for just that route loader - i.e., GET /a/b/c.data?_routes=routes/a for a clientLoader in routes/a.tsx
- When one or more routes are excluded from the single fetch call, the remaining routes that have loaders are included as query params:
  - For example, if A was excluded, and the root route and routes/b had a loader but routes/c did not, the single fetch request would be GET /a/b/c.data?_routes=root,routes/a
Remove hydration URL check that was originally added for React 17 hydration issues and we no longer support React 17 (#9890)
- Reverts the logic originally added in Remix v1.18.0 via #6409
- This was added to resolve an issue that could arise when doing quick back/forward history navigations while JS was loading which would cause a mismatch between the server matches and client matches: #1757
- This specific hydration issue would then cause this React v17 only looping issue: #1678
- The URL comparison that we added in 1.18.0 turned out to be subject to false positives of it's own which could also put the user in looping scenarios
- Remix v2 upgraded it's minimal React version to v18 which eliminated the v17 hydration error loop
- React v18 handles this hydration error like any other error and does not result in a loop
- So we can remove our check and thus avoid the false-positive scenarios in which it may also trigger a loop
Single Fetch: Improved typesafety (#9893)

If you were already using previously released unstable single-fetch types:
- Remove "@remix-run/react/future/single-fetch.d.ts" override from tsconfig.json > compilerOptions > types
- Remove defineLoader, defineAction, defineClientLoader, defineClientAction helpers from your route modules
- Replace UIMatch_SingleFetch type helper with UIMatch
- Replace MetaArgs_SingleFetch type helper with MetaArgs
Then you are ready for the new typesafety setup:
```
// vite.config.ts

declare module "@&#8203;remix-run/server-runtime" {
  interface Future {
    unstable_singleFetch: true; // 👈 enable _types_ for single-fetch
  }
}

export default defineConfig({
  plugins: [
    remix({
      future: {
        unstable_singleFetch: true, // 👈 enable single-fetch
      },
    }),
  ],
});
```
For more information, see Guides > Single Fetch in our docs.
Clarify wording in default HydrateFallback console warning (#9899)
Updated dependencies:
- @remix-run/server-runtime@2.12.0

`v2.11.2`

Compare Source

Patch Changes

Fog of War: Simplify implementation now that React Router handles slug/splat edge cases and tracks previously discovered routes (see remix-run/react-router#11883) (#9860)
- This changes the return signature of the internal __manifest endpoint since we no longer need the notFoundPaths field
Fog of War: Update to use renamed unstable_patchRoutesOnNavigation function in RR (see remix-run/react-router#11888) (#9860)
Single Fetch: Update turbo-stream to v2.3.0 (#9856)
- Stabilize object key order for serialized payloads
- Remove memory limitations payloads sizes
Updated dependencies:
- @remix-run/server-runtime@2.11.2

`v2.11.1`

Compare Source

Patch Changes

Revert #9695, stop infinite reload (a7cffe57)
Updated dependencies:
- @remix-run/server-runtime@2.11.1

`v2.11.0`

Compare Source

Minor Changes

Single Fetch: Add a new unstable_data() API as a replacement for json/defer when custom status/headers are needed (#9769)
Add a new replace(url, init?) alternative to redirect(url, init?) that performs a history.replaceState instead of a history.pushState on client-side navigation redirects (#9764)
Rename future.unstable_fogOfWar to future.unstable_lazyRouteDiscovery for clarity (#9763)
Single Fetch: Remove responseStub in favor of headers (#9769)
- Background
  - The original Single Fetch approach was based on an assumption that an eventual middleware implementation would require something like ResponseStub so users could mutate status/headers in middleware before/after handlers as well as during handlers
  - We wanted to align how headers got merged between document and data requests
  - So we made document requests also use ResponseStub and removed the usage of headers in Single Fetch
  - The realization/alignment between Michael and Ryan on the recent roadmap planning made us realize that the original assumption was incorrect
  - middleware won't need a stub - users can just mutate the Response they get from await next() directly
  - With that gone, and still wanting to align how headers get merged, it makes more sense to stick with the current headers API and apply that to Single Fetch and avoid introducing a totally new thing in RepsonseStub (that always felt a bit awkward to work with anyway)
- With this change:
  - You are encouraged to stop returning Response instances in favor of returning raw data from loaders and actions:
    - ~~return json({ data: whatever });~~
    - return { data: whatever };
  - In most cases, you can remove your json() and defer() calls in favor of returning raw data if they weren't setting custom status/headers
    - We will be removing both json and defer in the next major version, but both should still work in Single Fetch in v2 to allow for incremental adoption of the new behavior
  - If you need custom status/headers:
    - We've added a new unstable_data({...}, responseInit) utility that will let you send back status/headers alongside your raw data without having to encode it into a Response
  - The headers() function will let you control header merging for both document and data requests

Patch Changes

Single Fetch: Ensure calls don't include any trailing slash from the pathname (i.e., /path/.data) (#9792)
Single Fetch: Add undefined to the useRouteLoaderData type override (#9796)
Change initial hydration route mismatch from a URL check to a matches check to be resistant to URL inconsistencies (#9695)
Updated dependencies:
- @remix-run/server-runtime@2.11.0

`v2.10.3`

Compare Source

Patch Changes

Log any errors encountered loading a route module prior to reloading the page (#8932)
Single Fetch (unstable): Proxy request.signal through dataStrategy for loader calls to fix cancellation (#9738)
Single Fetch (unstable): Adopt React Router's stabilized future.v7_skipActionErrorRevalidation under the hood (#9706)
- This also stabilizes the shouldRevalidate parameter from unstable_actionStatus to actionStatus
Updated dependencies:
- @remix-run/server-runtime@2.10.3

`v2.10.2`

Compare Source

Patch Changes

Forward ref to Form (bdd04217)
Updated dependencies:
- @remix-run/server-runtime@2.10.2

`v2.10.1`

Compare Source

Patch Changes

Fog of War (unstable): Don't discover links/forms with reloadDocument (#9686)
Fog of War (unstable): Suppor

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate bot added dependencies devDependencies labels Jun 18, 2022

renovate bot force-pushed the renovate/remix-monorepo branch from fb0925e to b981960 Compare June 23, 2022 19:12

renovate bot changed the title ~~chore(dev-deps): update remix monorepo to v1.6.0~~ chore(dev-deps): update remix monorepo to v1.6.1 Jun 23, 2022

renovate bot force-pushed the renovate/remix-monorepo branch from b981960 to a0db5e8 Compare September 25, 2022 15:06

renovate bot changed the title ~~chore(dev-deps): update remix monorepo to v1.6.1~~ chore(dev-deps): update remix monorepo to v1.7.2 Sep 25, 2022

renovate bot force-pushed the renovate/remix-monorepo branch from a0db5e8 to 56755f0 Compare November 20, 2022 16:32

renovate bot changed the title ~~chore(dev-deps): update remix monorepo to v1.7.2~~ chore(dev-deps): update remix monorepo to v1.7.6 Nov 20, 2022

renovate bot force-pushed the renovate/remix-monorepo branch from 56755f0 to 8c053db Compare March 12, 2023 17:16

renovate bot changed the title ~~chore(dev-deps): update remix monorepo to v1.7.6~~ chore(dev-deps): update remix monorepo to v1.14.1 Mar 12, 2023

renovate bot force-pushed the renovate/remix-monorepo branch from 8c053db to 0522ae9 Compare March 14, 2023 21:03

renovate bot changed the title ~~chore(dev-deps): update remix monorepo to v1.14.1~~ chore(dev-deps): update remix monorepo to v1.14.2 Mar 14, 2023

renovate bot force-pushed the renovate/remix-monorepo branch from 0522ae9 to a066261 Compare March 16, 2023 10:38

renovate bot changed the title ~~chore(dev-deps): update remix monorepo to v1.14.2~~ chore(dev-deps): update remix monorepo to v1.14.3 Mar 16, 2023

renovate bot force-pushed the renovate/remix-monorepo branch from a066261 to df3023a Compare March 31, 2023 17:29

renovate bot changed the title ~~chore(dev-deps): update remix monorepo to v1.14.3~~ chore(dev-deps): update remix monorepo to v1.15.0 Mar 31, 2023

renovate bot force-pushed the renovate/remix-monorepo branch from df3023a to d04acc9 Compare May 28, 2023 11:48

renovate bot changed the title ~~chore(dev-deps): update remix monorepo to v1.15.0~~ chore(dev-deps): update remix monorepo to v1.16.1 May 28, 2023

renovate bot force-pushed the renovate/remix-monorepo branch from d04acc9 to d989a44 Compare June 6, 2023 23:11

renovate bot changed the title ~~chore(dev-deps): update remix monorepo to v1.16.1~~ chore(dev-deps): update remix monorepo to v1.17.0 Jun 6, 2023

renovate bot force-pushed the renovate/remix-monorepo branch from d989a44 to 105459b Compare June 15, 2023 17:24

renovate bot changed the title ~~chore(dev-deps): update remix monorepo to v1.17.0~~ chore(dev-deps): update remix monorepo to v1.17.1 Jun 15, 2023

renovate bot force-pushed the renovate/remix-monorepo branch from 105459b to ecd5fff Compare June 26, 2023 19:28

renovate bot changed the title ~~chore(dev-deps): update remix monorepo to v1.17.1~~ chore(dev-deps): update remix monorepo to v1.18.0 Jun 26, 2023

renovate bot force-pushed the renovate/remix-monorepo branch from ecd5fff to 4f93c97 Compare June 30, 2023 21:44

renovate bot changed the title ~~chore(dev-deps): update remix monorepo to v1.18.0~~ chore(dev-deps): update remix monorepo to v1.18.1 Jun 30, 2023

renovate bot force-pushed the renovate/remix-monorepo branch from 4f93c97 to 3ec57fa Compare July 19, 2023 20:11

renovate bot changed the title ~~chore(dev-deps): update remix monorepo to v1.18.1~~ chore(dev-deps): update remix monorepo to v1.19.0 Jul 19, 2023

renovate bot force-pushed the renovate/remix-monorepo branch from 3ec57fa to 8c7aecc Compare July 23, 2023 05:36

renovate bot changed the title ~~chore(dev-deps): update remix monorepo to v1.19.0~~ chore(dev-deps): update remix monorepo to v1.19.1 Jul 23, 2023

renovate bot force-pushed the renovate/remix-monorepo branch from 002b118 to 4929ac1 Compare June 25, 2024 14:53

renovate bot changed the title ~~fix(deps): update remix monorepo to v2.9.2~~ fix(deps): update remix monorepo to v2.10.0 Jun 25, 2024

renovate bot force-pushed the renovate/remix-monorepo branch from 4929ac1 to 762e05e Compare July 9, 2024 22:17

renovate bot changed the title ~~fix(deps): update remix monorepo to v2.10.0~~ fix(deps): update remix monorepo to v2.10.2 Jul 9, 2024

renovate bot force-pushed the renovate/remix-monorepo branch from 762e05e to ab6c6ec Compare July 16, 2024 15:01

renovate bot changed the title ~~fix(deps): update remix monorepo to v2.10.2~~ fix(deps): update remix monorepo to v2.10.3 Jul 16, 2024

renovate bot force-pushed the renovate/remix-monorepo branch from ab6c6ec to f11d07a Compare August 1, 2024 21:31

renovate bot changed the title ~~fix(deps): update remix monorepo to v2.10.3~~ fix(deps): update remix monorepo to v2.11.0 Aug 1, 2024

renovate bot force-pushed the renovate/remix-monorepo branch from f11d07a to 1fb58a8 Compare August 6, 2024 02:12

renovate bot changed the title ~~fix(deps): update remix monorepo to v2.11.0~~ fix(deps): update remix monorepo to v2.11.1 Aug 6, 2024

renovate bot force-pushed the renovate/remix-monorepo branch from 1fb58a8 to deda060 Compare August 15, 2024 20:29

renovate bot changed the title ~~fix(deps): update remix monorepo to v2.11.1~~ fix(deps): update remix monorepo to v2.11.2 Aug 15, 2024

renovate bot force-pushed the renovate/remix-monorepo branch from deda060 to c19a2db Compare August 28, 2024 06:31

renovate bot force-pushed the renovate/remix-monorepo branch from c19a2db to 9bdfbf5 Compare September 9, 2024 20:09

renovate bot changed the title ~~fix(deps): update remix monorepo to v2.11.2~~ fix(deps): update remix monorepo to v2.12.0 Sep 9, 2024

renovate bot force-pushed the renovate/remix-monorepo branch from 9bdfbf5 to d4e5e5d Compare September 19, 2024 19:24

renovate bot changed the title ~~fix(deps): update remix monorepo to v2.12.0~~ fix(deps): update remix monorepo to v2.12.1 Sep 19, 2024

renovate bot force-pushed the renovate/remix-monorepo branch 2 times, most recently from f00dab3 to 3882b20 Compare October 11, 2024 19:53

renovate bot changed the title ~~fix(deps): update remix monorepo to v2.12.1~~ fix(deps): update remix monorepo to v2.13.0 Oct 11, 2024

renovate bot force-pushed the renovate/remix-monorepo branch from 3882b20 to 578b9bc Compare October 11, 2024 22:02

renovate bot changed the title ~~fix(deps): update remix monorepo to v2.13.0~~ fix(deps): update remix monorepo to v2.13.1 Oct 11, 2024

renovate bot force-pushed the renovate/remix-monorepo branch from 578b9bc to 66e6aa7 Compare November 9, 2024 00:52

renovate bot changed the title ~~fix(deps): update remix monorepo to v2.13.1~~ fix(deps): update remix monorepo to v2.14.0 Nov 9, 2024

fix(deps): update remix monorepo to v2.15.0

ddd3226

renovate bot force-pushed the renovate/remix-monorepo branch from 66e6aa7 to ddd3226 Compare November 22, 2024 10:03

renovate bot changed the title ~~fix(deps): update remix monorepo to v2.14.0~~ fix(deps): update remix monorepo to v2.15.0 Nov 22, 2024

renovate bot changed the title ~~fix(deps): update remix monorepo to v2.15.0~~ fix(deps): update remix monorepo to v2.15.0 - autoclosed Dec 8, 2024

renovate bot closed this Dec 8, 2024

renovate bot deleted the renovate/remix-monorepo branch December 8, 2024 19:00

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update remix monorepo to v2.15.0 - autoclosed #32

fix(deps): update remix monorepo to v2.15.0 - autoclosed #32

renovate bot commented Jun 18, 2022 •

edited

Loading

fix(deps): update remix monorepo to v2.15.0 - autoclosed #32

fix(deps): update remix monorepo to v2.15.0 - autoclosed #32

Conversation

renovate bot commented Jun 18, 2022 • edited Loading

Release Notes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

renovate bot commented Jun 18, 2022 •

edited

Loading