chore(deps): update remix monorepo to v2.13.1 #286

renovate · 2024-10-28T00:19:22Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@remix-run/dev (source)	`2.11.2` -> `2.13.1`
@remix-run/eslint-config (source)	`2.11.2` -> `2.13.1`
@remix-run/node (source)	`2.11.2` -> `2.13.1`
@remix-run/react (source)	`2.11.2` -> `2.13.1`
@remix-run/serve (source)	`2.11.2` -> `2.13.1`

Release Notes

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

`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]

remix-run/remix (@remix-run/eslint-config)

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

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

`v2.13.1`

Compare Source

Patch Changes

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

`v2.13.0`

Compare Source

Patch Changes

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

`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/[email protected]

`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/[email protected]

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

`v2.13.1`

Compare Source

Patch Changes

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

`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/[email protected]

`v2.12.1`

Compare Source

Patch Changes

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

`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/[email protected]

remix-run/remix (@remix-run/serve)

`v2.13.1`

Compare Source

Patch Changes

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

`v2.13.0`

Compare Source

Patch Changes

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

`v2.12.1`

Compare Source

Patch Changes

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

`v2.12.0`

Compare Source

Patch Changes

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

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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 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.

netlify · 2024-10-28T00:19:37Z

✅ Deploy Preview for kpop-upgrade ready!

Name	Link
🔨 Latest commit	`6cefc38`
🔍 Latest deploy log	https://app.netlify.com/sites/kpop-upgrade/deploys/671ed88dc2f4320008c8454a
😎 Deploy Preview	https://deploy-preview-286--kpop-upgrade.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

netlify · 2024-10-28T00:19:43Z

✅ Deploy Preview for kpop-stack ready!

Name	Link
🔨 Latest commit	`6cefc38`
🔍 Latest deploy log	https://app.netlify.com/sites/kpop-stack/deploys/671ed88df22dd00008d5c63b
😎 Deploy Preview	https://deploy-preview-286--kpop-stack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

chore(deps): update remix monorepo to v2.13.1

6cefc38

renovate bot added dependencies javascript labels Oct 28, 2024

renovate bot merged commit 1bd9c97 into main Oct 28, 2024
8 checks passed

renovate bot deleted the renovate/remix-monorepo branch October 28, 2024 04:52

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update remix monorepo to v2.13.1 #286

chore(deps): update remix monorepo to v2.13.1 #286

renovate bot commented Oct 28, 2024

netlify bot commented Oct 28, 2024 •

edited

Loading

netlify bot commented Oct 28, 2024 •

edited

Loading

chore(deps): update remix monorepo to v2.13.1 #286

chore(deps): update remix monorepo to v2.13.1 #286

Conversation

renovate bot commented Oct 28, 2024

Release Notes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor 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

Configuration

netlify bot commented Oct 28, 2024 • edited Loading

✅ Deploy Preview for kpop-upgrade ready!

netlify bot commented Oct 28, 2024 • edited Loading

✅ Deploy Preview for kpop-stack ready!

netlify bot commented Oct 28, 2024 •

edited

Loading

netlify bot commented Oct 28, 2024 •

edited

Loading