-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update remix monorepo to v2.13.1 #1023
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[misspell] reported by reviewdog 🐶
"optimise" is a misspelling of "optimize"
suddenlygiovanni.dev/pnpm-lock.yaml
Line 412 in 8b6b127
'@babel/[email protected]': |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[misspell] reported by reviewdog 🐶
"optimise" is a misspelling of "optimize"
suddenlygiovanni.dev/pnpm-lock.yaml
Line 6197 in 8b6b127
'@babel/helper-optimise-call-expression': 7.22.5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[misspell] reported by reviewdog 🐶
"optimise" is a misspelling of "optimize"
suddenlygiovanni.dev/pnpm-lock.yaml
Line 6231 in 8b6b127
'@babel/[email protected]': |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[misspell] reported by reviewdog 🐶
"optimise" is a misspelling of "optimize"
suddenlygiovanni.dev/pnpm-lock.yaml
Line 6242 in 8b6b127
'@babel/helper-optimise-call-expression': 7.22.5 |
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@remix-run/[email protected], npm/@remix-run/[email protected], npm/@remix-run/[email protected], npm/@remix-run/[email protected], npm/@remix-run/[email protected], npm/[email protected] |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1023 +/- ##
======================================
Coverage ? 3.29%
======================================
Files ? 41
Lines ? 2702
Branches ? 44
======================================
Hits ? 89
Misses ? 2613
Partials ? 0 ☔ View full report in Codecov by Sentry. |
This PR contains the following updates:
2.12.1
->2.13.1
2.12.1
->2.13.1
2.12.1
->2.13.1
2.12.1
->2.13.1
2.12.1
->2.13.1
Release Notes
remix-run/remix (@remix-run/dev)
v2.13.1
Compare Source
Patch Changes
future.v3_optimizeDeps
back tofuture.unstable_optimizeDeps
as it was not intended to stabilize in Remix v2 (#10099)@remix-run/[email protected]
@remix-run/[email protected]
v2.13.0
Compare Source
Minor Changes
future.unstable_optimizeDeps
flag intofuture.v3_optimizeDeps
(#10092)unstable_dataStrategy
->dataStrategy
unstable_patchRoutesOnNavigation
->patchRoutesOnNavigation
unstable_data()
->data()
unstable_viewTransition
->viewTransition
(Link
,Form
,navigate
,submit
)unstable_flushSync>
-><Link viewTransition>
(Link
,Form
,navigate
,submit
,useFetcher
)future.unstable_singleFetch
->future.v3_singleFetch
future.unstable_lazyRouteDiscovery
->future.v3_lazyRouteDiscovery
Patch Changes
Stop passing
request.signal
as therenderToReadableStream
signal
to abort server rendering for cloudflare/deno runtimes because by the time thatrequest
is aborted, aborting the rendering is useless because there's no way for React to flush down the unresolved boundaries (#10047)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 closedReadableStream
.request.signal
on successful rendersentry.server
files no longer pass asignal
torenderToReadableStream
because adding a timeout-based abort signal to the default behavior would constitute a breaking changeentry.server
viaremix reveal entry.server
, and the template entry.server files have been updated with an example approach for newly created Remix appsFix adapter logic for aborting
request.signal
so we don't incorrectly abort on theclose
event for successful requests (#10046)Updated dependencies:
@remix-run/[email protected]
@remix-run/[email protected]
remix-run/remix (@remix-run/node)
v2.13.1
Compare Source
Patch Changes
@remix-run/[email protected]
v2.13.0
Compare Source
Patch Changes
@remix-run/[email protected]
remix-run/remix (@remix-run/react)
v2.13.1
Compare Source
Patch Changes
@remix-run/[email protected]
v2.13.0
Compare Source
Minor Changes
unstable_dataStrategy
->dataStrategy
unstable_patchRoutesOnNavigation
->patchRoutesOnNavigation
unstable_data()
->data()
unstable_viewTransition
->viewTransition
(Link
,Form
,navigate
,submit
)unstable_flushSync>
-><Link viewTransition>
(Link
,Form
,navigate
,submit
,useFetcher
)future.unstable_singleFetch
->future.v3_singleFetch
future.unstable_lazyRouteDiscovery
->future.v3_lazyRouteDiscovery
Patch Changes
clientLoader.hydrate
in a layout route when hydrating with bubbled errors (#10063)@remix-run/[email protected]
remix-run/remix (@remix-run/serve)
v2.13.1
Compare Source
Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
v2.13.0
Compare Source
Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
remix-run/remix (@remix-run/testing)
v2.13.1
Compare Source
Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
v2.13.0
Compare Source
Patch Changes
@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: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.