chore: Update version for release #13422
Merged
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release-next, this PR will be updated.
Releases
[email protected]
Patch Changes
Fix single fetch bug where no revalidation request would be made when navigating upwards to a reused parent route (#13253)
When using the object-based
route.lazy
API, theHydrateFallback
andhydrateFallbackElement
properties are now skipped when lazy loading routes after hydration. (#13376)If you move the code for these properties into a separate file, you can use this optimization to avoid downloading unused hydration code. For example:
Properly revalidate prerendered paths when param values change (#13380)
UNSTABLE: Add a new
unstable_runClientMiddleware
argument todataStrategy
to enable middleware execution in customdataStrategy
implementations (#13395)UNSTABLE: Add better error messaging when
getLoadContext
is not updated to return aMap
" (#13242)Do not automatically add
null
tostaticHandler.query()
context.loaderData
if routes do not have loaders (#13223)undefined
from loaders, our prior check ofloaderData[routeId] !== undefined
was no longer sufficient and was changed to arouteId in loaderData
check - thesenull
values can cause issues for this new checkcreateStaticHandler()
/<StaticRouterProvider>
, and usingcontext.loaderData
to control<RouterProvider>
hydration behavior on the clientFix prerendering when a loader returns a redirect (#13365)
UNSTABLE: Update context type for
LoaderFunctionArgs
/ActionFunctionArgs
when middleware is enabled (#13381)Add support for the new
unstable_shouldCallHandler
/unstable_shouldRevalidateArgs
APIs indataStrategy
(#13253)@react-router/[email protected]
Patch Changes
[email protected]
@react-router/[email protected]
@react-router/[email protected]
Patch Changes
[email protected]
@react-router/[email protected]
Patch Changes
[email protected]
@react-router/[email protected]
@react-router/[email protected]
[email protected]
Patch Changes
[email protected]
@react-router/[email protected]
Patch Changes
[email protected]
@react-router/[email protected]
@react-router/[email protected]
Patch Changes
@react-router/[email protected]
@react-router/[email protected]
Patch Changes
[email protected]
@react-router/[email protected]
Patch Changes
@react-router/[email protected]
@react-router/[email protected]
Patch Changes
[email protected]
@react-router/[email protected]
@react-router/[email protected]
[email protected]