Update dependency @remix-run/dev to v2.14.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@remix-run/dev (source)	2.9.2 -> 2.14.0

---

Release Notes

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

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 "@​remix-run/fs-routes";
  import type { RouteConfig } from "@​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/[email protected]
  • @remix-run/[email protected]

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/[email protected]
  • @remix-run/[email protected]

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/[email protected]
  • @remix-run/[email protected]

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/[email protected]
  • @remix-run/[email protected]

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/[email protected]
  • @remix-run/[email protected]

v2.11.2

Compare Source

Patch Changes

• Updated dependencies:
  • @remix-run/[email protected]
  • @remix-run/[email protected]

v2.11.1

Compare Source

Patch Changes

• Updated dependencies:
  • @remix-run/[email protected]
  • @remix-run/[email protected]

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/[email protected]
  • @remix-run/[email protected]

v2.10.3

Compare Source

Patch Changes

• Updated dependencies:
  • @remix-run/[email protected]
  • @remix-run/[email protected]

v2.10.2

Compare Source

Patch Changes

• Updated dependencies:
  • @remix-run/[email protected]
  • @remix-run/[email protected]

v2.10.1

Compare Source

Patch Changes

• Updated dependencies:
  • @remix-run/[email protected]
  • @remix-run/[email protected]

v2.10.0

Compare Source

Patch Changes

• Upgrade express dependency to ^4.19.2 (#​9184)
• Updated dependencies:
  • @remix-run/[email protected]
  • @remix-run/[email protected]

---

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 this update again.

---

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

---

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