Update dependency remix-run/react-router to v6.23.0 #136
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:
6.22.0->6.23.0Release Notes
remix-run/react-router (remix-run/react-router)
v6.23.0Compare Source
Date: 2024-04-23
What's Changed
Data Strategy (unstable)
The new
unstable_dataStrategyAPI is a low-level API designed for advanced use-cases where you need to take control over the data strategy for yourloader/actionfunctions. The default implementation is today's behavior, to fetch all loaders in parallel, but this option allows users to implement more advanced data flows including Remix "Single Fetch", user-land middleware/context APIs, automatic loader caching, and more. Please see the docs for more information.Note: This is a low-level API intended for advanced use-cases. This overrides React Router's internal handling of
loader/actionexecution, and if done incorrectly will break your app code. Please use with caution and perform the appropriate testing.Skip Action Error Revalidation (unstable)
Currently, all active
loader's revalidate after anyactionsubmission, regardless of theactionresult. However, in the majority of cases a4xx/5xxresponse from anactionmeans that no data was actually changed and the revalidation is unnecessary. We've introduced a newfuture.unstable_skipActionErrorRevalidationflag that changes the behavior here, and we plan to make this the default in future version of React Router.With this flag enabled,
action's that return/throw a4xx/5xxresponse status will no longer automatically revalidate. If you need to revalidate after a4xx/5xxresult with this flag enabled, you can still do that via returningtruefromshouldRevalidate- which now also receives a newunstable_actionStatusargument alongsideactionResultso you can make decision based on the status of theactionresponse without having to encode it into the action data.Minor Changes
unstable_dataStrategyconfiguration option (#11098, #11377)@remix-run/router- Add a newfuture.unstable_skipActionRevalidationfuture flag (#11098)@remix-run/router- SSR: Added a newskipLoaderErrorBubblingoptions to thestaticHandler.querymethod to disable error bubbling by the static handler for use in Remix's Single Fetch implementation (#11098, (#11377))Full Changelog:
v6.22.3...v6.23.0v6.22.3Compare Source
Date: 2024-03-07
Patch Changes
future.v7_partialHydrationbug that would re-run loaders below the boundary on hydration if SSR loader errors bubbled to a parent boundary (#11324)future.v7_partialHydrationbug that would consider the router uninitialized if a route did not have a loader (#11325)Full Changelog:
v6.22.2...v6.22.3v6.22.2Compare Source
Date: 2024-02-28
Patch Changes
Full Changelog:
v6.22.1...v6.22.2v6.22.1Compare Source
Date: 2024-02-16
Patch Changes
Full Changelog:
v6.22.0...v6.22.1Configuration
📅 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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.