-
Notifications
You must be signed in to change notification settings - Fork 10
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.15.2 #475
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/remix-monorepo
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
added
dependencies
Pull requests that update a dependency file
javascript
labels
Dec 10, 2024
✅ Deploy Preview for remix-serverless ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
❌ Deploy Preview for remix-edge failed. Why did it fail? →
|
github-actions
bot
added
the
type: chore
work needed to keep the product and development running smoothly
label
Dec 10, 2024
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
December 13, 2024 14:41
b6db28a
to
91b401c
Compare
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
December 13, 2024 16:04
91b401c
to
6650f50
Compare
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
December 17, 2024 18:03
6650f50
to
4b542dd
Compare
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
December 19, 2024 00:13
4b542dd
to
bea1750
Compare
renovate
bot
changed the title
chore(deps): update remix monorepo to v2.15.1
chore(deps): update remix monorepo
Dec 19, 2024
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
December 20, 2024 22:25
bea1750
to
c3b8730
Compare
renovate
bot
changed the title
chore(deps): update remix monorepo
chore(deps): update remix monorepo to v2.15.2
Dec 20, 2024
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
December 21, 2024 00:46
c3b8730
to
da7799f
Compare
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
December 21, 2024 04:13
da7799f
to
1d4628f
Compare
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
December 23, 2024 03:40
1d4628f
to
aa8cf65
Compare
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
December 23, 2024 07:44
aa8cf65
to
72922cc
Compare
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
January 6, 2025 05:12
72922cc
to
910d3e8
Compare
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
January 22, 2025 11:38
910d3e8
to
04ac8fa
Compare
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
January 23, 2025 19:08
04ac8fa
to
be39f04
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dependencies
Pull requests that update a dependency file
javascript
type: chore
work needed to keep the product and development running smoothly
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.12.0
->2.15.2
2.12.0
->2.15.2
2.12.0
->2.15.2
2.12.0
->2.15.2
2.12.0
->2.15.2
2.12.0
->2.15.2
2.12.0
->2.15.2
Release Notes
remix-run/remix (@remix-run/css-bundle)
v2.15.2
Compare Source
v2.15.1
Compare Source
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.remix-run/remix (@remix-run/dev)
v2.15.2
Compare Source
Patch Changes
false
(#10358)9c35c5fbc
)@remix-run/node@2.15.2
@remix-run/server-runtime@2.15.2
v2.15.1
Compare Source
Patch Changes
@remix-run/node@2.15.1
@remix-run/server-runtime@2.15.1
v2.15.0
Compare Source
Patch Changes
Stabilize the
future.v3_routeConfig
future flag, replacingfuture.unstable_routeConfig
. This enables support forroutes.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 inapp/routes.ts
is no longer defined via theroutes
export and must now be defined via the default export.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
behindfuture.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 forroutes.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 inroutes.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:A minimal
routes.ts
file to support Remix's built-in file system routing looks like this:Log deprecation warnings for v3 future flags (#10126)
@deprecated
annotations tojson
/defer
utilitiesPatch Changes
@remix-run/server-runtime@2.14.0
@remix-run/node@2.14.0
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/node@2.13.1
@remix-run/server-runtime@2.13.1
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/server-runtime@2.13.0
@remix-run/node@2.13.0
v2.12.1
Compare Source
Patch Changes
request.signal
duringvite dev
when the node response is closed (#9976)?inline
,?inline-css
and?raw
are no longer incorrectly injected during SSR in development (#9910)@remix-run/server-runtime@2.12.1
@remix-run/node@2.12.1
remix-run/remix (@remix-run/eslint-config)
v2.15.2
Compare Source
v2.15.1
Compare Source
v2.15.0
Compare Source
v2.14.0
Compare Source
Minor Changes
@remix-run/eslint-config
(#10174)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.remix-run/remix (@remix-run/node)
v2.15.2
Compare Source
Patch Changes
@remix-run/server-runtime@2.15.2
v2.15.1
Compare Source
Patch Changes
@remix-run/server-runtime@2.15.1
v2.15.0
Compare Source
Patch Changes
@remix-run/server-runtime@2.15.0
v2.14.0
Compare Source
Patch Changes
@remix-run/server-runtime@2.14.0
v2.13.1
Compare Source
Patch Changes
@remix-run/server-runtime@2.13.1
v2.13.0
Compare Source
Patch Changes
@remix-run/server-runtime@2.13.0
v2.12.1
Compare Source
Patch Changes
interface Future
through@remix-run/node
/@remix-run/cloudflare
/@remix-run/deno
packages so thatpnpm
doesn't complain about@remix-run/server-runtime
not being a dependency (#9982)@remix-run/server-runtime@2.12.1
remix-run/remix (@remix-run/react)
v2.15.2
Compare Source
Patch Changes
@remix-run/server-runtime@2.15.2
v2.15.1
Compare Source
Patch Changes
@remix-run/server-runtime@2.15.1
v2.15.0
Compare Source
Patch Changes
@remix-run/server-runtime@2.15.0
v2.14.0
Compare Source
Patch Changes
defaultShouldRevalidate
value when using single fetch (#10139)@remix-run/server-runtime@2.14.0
v2.13.1
Compare Source
Patch Changes
@remix-run/server-runtime@2.13.1
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/server-runtime@2.13.0
v2.12.1
Compare Source
Patch Changes
@remix-run/server-runtime@2.12.1
remix-run/remix (@remix-run/serve)
v2.15.2
Compare Source
Patch Changes
@remix-run/express@2.15.2
@remix-run/node@2.15.2
v2.15.1
Compare Source
Patch Changes
@remix-run/express@2.15.1
@remix-run/node@2.15.1
v2.15.0
Compare Source
Patch Changes
@remix-run/express@2.15.0
@remix-run/node@2.15.0
v2.14.0
Compare Source
Patch Changes
@remix-run/node@2.14.0
@remix-run/express@2.14.0
v2.13.1
Compare Source
Patch Changes
@remix-run/express@2.13.1
@remix-run/node@2.13.1
v2.13.0
Compare Source
Patch Changes
@remix-run/express@2.13.0
@remix-run/node@2.13.0
v2.12.1
Compare Source
Patch Changes
@remix-run/node@2.12.1
@remix-run/express@2.12.1
remix-run/remix (@remix-run/server-runtime)
v2.15.2
Compare Source
v2.15.1
Compare Source
v2.15.0
Compare Source
v2.14.0
Compare Source
Minor Changes
SerializeFrom
in favor of generics because it will be removed in React Router v7 (#10173)Patch Changes
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
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
v2.12.1
Compare Source
Patch Changes
loader
,action
,clientLoader
, orclientAction
return a mixture of bare objects,json(...)
,defer(...)
, andunstable_data(...)
. (#9999)interface Future
through@remix-run/node
/@remix-run/cloudflare
/@remix-run/deno
packages so thatpnpm
doesn't complain about@remix-run/server-runtime
not being a dependency (#9982)Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (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.
This PR was generated by Mend Renovate. View the repository job log.