chore(deps): update dependency @vercel/remix to v2.10.3 #321

renovate · 2024-08-03T13:17:13Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vercel/remix (source)	`2.9.1` -> `2.10.3`

Release Notes

vercel/remix (@vercel/remix)

`v2.10.3`

Date: 2024-07-16

Patch Changes

@remix-run/architect - Manually joining headers with semi-colons to avoid differences in Remix and node/undici Headers implementation (#9664)
@remix-run/react - Log any errors encountered loading a route module prior to reloading the page (#8932)
@remix-run/react - Single Fetch (unstable): Proxy request.signal through dataStrategy for loader calls to fix cancellation (#9738)
@remix-run/react - Single Fetch (unstable): Adopt React Router's stabilized future.v7_skipActionErrorRevalidation under the hood (#9706)
- This stabilizes the shouldRevalidate parameter from unstable_actionStatus to actionStatus
- ⚠️ This might be a breaking change for your app if you have opted into single fetch and the unstable_actionStatus parameter

Updated Dependencies

Changes by Package

Full Changelog: v2.10.2...v2.10.3

`v2.10.2`

Date: 2024-07-04

Patch Changes

@remix-run/react - Forward ref to Form (bdd04217)
@remix-run/server-runtime - Fix bug with immutable headers on raw native fetch responses returned from loaders (#9693)

Changes by Package

Full Changelog: v2.10.1...v2.10.2

`v2.10.0`

Date: 2024-06-25

What's Changed

Lazy Route Discovery (a.k.a. "Fog of War")

The "Fog of War" feature in Remix, now available through the future.unstable_fogOfWar flag, is an optimization to reduce the up front size of the Remix route manifest. In most scenarios the Remix route manifest isn't prohibitively large so as to impact initial perf metrics, but at scale we've found that some apps can generate large manifests that are expensive to download and execute on app startup.

When Fog of War is enabled, Remix will only include the initially server-rendered routes in the manifest and then it will fetch manifest "patches" for outgoing links as the user navigates around. By default, to avoid waterfalls Remix fetches patches for all rendered links, so that in the ideal case they've already been patched in prior to being clicked. If a user clicks a link before this eager discovery completes, then a small waterfall will occur to first "discover" the route, and then navigate to the route.

Enabling this flag should require no application code changes. For more information, please see the documentation.

Minor Changes

Add support for Lazy Route Discovery (a.k.a. Fog of War) (#9600, #9619)

Patch Changes

@remix-run/{dev|express|serve} - Upgrade express dependency to ^4.19.2 (#9184)
@remix-run/react - Don't prefetch server loader data when clientLoader exists (#9580)
@remix-run/react - Avoid hydration loops when Layout/ErrorBoundary renders also throw (#9566)
@remix-run/react - Fix a hydration bug when using child routes and HydrateFallback components with a basename (#9584)
@remix-run/{server-runtime|react} - Single Fetch: Update to [email protected] (#9562)
@remix-run/server-runtime - Single Fetch: Properly handle thrown 4xx/5xx response stubs (#9501)
@remix-run/server-runtime - Single Fetch: Change redirects to use a 202 status to avoid automatic caching (#9564)
@remix-run/server-runtime - Single Fetch: Fix issues with returning or throwing a response stub from a resource route in single fetch (#9488)
@remix-run/server-runtime - Single Fetch: Fix error when returning null from a resource route (#9488)

Updated Dependencies

Changes by Package

Full Changelog: v2.9.2...v2.10.0

`v2.9.2`

Compare Source

Date: 2024-05-10

What's Changed

Updated Type-Safety for Single Fetch

In 2.9.2 we've enhanced the type-safety when opting into the future.unstable_singleFetch feature. Previously, we added the response stub to LoaderFunctionArgs and used type overrides for inference on useLoaderData, etc., but we found that it wasn't quite enough.

With this release we're introducing new functions to assist the type-inference when using single fetch - defineLoader/defineAction and their client-side counterparts defineClientLoader and nd defineClientAction. These are identity functions; they don't modify your loader or action at runtime. Rather, they exist solely for type-safety by providing types for args and by ensuring valid return types.

export const loader = defineLoader(({ request }) => {
  //                                ^? Request
  return { a: 1, b: () => 2 };
  //           ^ type error: `b` is not serializable
});

Note that defineLoader and defineAction are not technically necessary for defining loaders and actions if you aren't concerned with type-safety:

// this totally works! and typechecking is happy too!
export const loader = () => {
  return { a: 1 };
};

This means that you can opt-in to defineLoader incrementally, one loader at a time.

Please see the Single Fetch docs for more information.

Patch Changes

@remix-run/dev - Vite: Fix dest already exists error when running remix vite:build (#9305)
@remix-run/dev - Vite: Fix issue resolving critical CSS during development when route files are located outside of the app directory (#9194)
@remix-run/dev - Vite: 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)
@remix-run/dev - Vite: Clean up redundant ?client-route=1 imports in development (#9395)
@remix-run/dev - Vite: Ensure Babel config files are not referenced when applying the react-refresh Babel transform within the Remix Vite plugin (#9241)
@remix-run/react - Type-safety for single-fetch: defineLoader, defineClientLoader, defineAction, defineClientAction (#9372)
@remix-run/react - Single Fetch: Add undefined to useActionData type override (#9322)
@remix-run/react - Single Fetch: Allow a nonce to be set on single fetch stream transfer inline scripts via <RemixServer> (#9364)
@remix-run/server-runtime - Single Fetch: Don't log thrown response stubs via handleError (#9369)
@remix-run/server-runtime - Single Fetch: Automatically wrap resource route naked object returns in json() for back-compat in v2 (and log deprecation warning) (#9349)
@remix-run/server-runtime - Single Fetch: Pass response stub to resource route handlers (#9349)

Updated Dependencies

Changes by Package

Full Changelog: v2.9.1...v2.9.2

Configuration

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

🚦 Automerge: Enabled.

♻ 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.

vercel · 2024-08-03T13:17:17Z

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
boston-ts-website	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 3, 2024 4:42pm

renovate bot added the dependencies label Aug 3, 2024

renovate bot enabled auto-merge (squash) August 3, 2024 13:17

vercel bot deployed to Preview August 3, 2024 13:17 View deployment

renovate bot force-pushed the renovate/vercel-remix-2.x-lockfile branch from 38d6215 to dde4b8e Compare August 3, 2024 16:24

vercel bot deployed to Preview August 3, 2024 16:25 View deployment

renovate bot force-pushed the renovate/vercel-remix-2.x-lockfile branch from dde4b8e to cfef353 Compare August 3, 2024 16:32

vercel bot deployed to Preview August 3, 2024 16:33 View deployment

chore(deps): update dependency @vercel/remix to v2.10.3

52f523b

renovate bot force-pushed the renovate/vercel-remix-2.x-lockfile branch from cfef353 to 52f523b Compare August 3, 2024 16:41

renovate bot merged commit d4f8bd5 into main Aug 3, 2024
11 of 12 checks passed

renovate bot deleted the renovate/vercel-remix-2.x-lockfile branch August 3, 2024 16:42

vercel bot deployed to Preview August 3, 2024 16:42 View deployment

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency @vercel/remix to v2.10.3 #321

chore(deps): update dependency @vercel/remix to v2.10.3 #321

renovate bot commented Aug 3, 2024 •

edited

Loading

vercel bot commented Aug 3, 2024 •

edited

Loading

chore(deps): update dependency @vercel/remix to v2.10.3 #321

chore(deps): update dependency @vercel/remix to v2.10.3 #321

Conversation

renovate bot commented Aug 3, 2024 • edited Loading

Release Notes

v2.10.3

Patch Changes

Updated Dependencies

Changes by Package

v2.10.2

Patch Changes

Changes by Package

v2.10.0

What's Changed

Lazy Route Discovery (a.k.a. "Fog of War")

Minor Changes

Patch Changes

Updated Dependencies

Changes by Package

v2.9.2

What's Changed

Updated Type-Safety for Single Fetch

Patch Changes

Updated Dependencies

Changes by Package

Configuration

vercel bot commented Aug 3, 2024 • edited Loading

renovate bot commented Aug 3, 2024 •

edited

Loading

`v2.10.3`

`v2.10.2`

`v2.10.0`

`v2.9.2`

vercel bot commented Aug 3, 2024 •

edited

Loading