chore: Update version for release #10636
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]
Minor Changes
Add support for
application/json
andtext/plain
encodings foruseSubmit
/fetcher.submit
. To reflect these additional types,useNavigation
/useFetcher
now also containnavigation.json
/navigation.text
andfetcher.json
/fetcher.text
which include the json/text submission if applicable. (#10413)Patch Changes
submitter
element, prefer the built-innew FormData(form, submitter)
instead of the previous manual approach in modern browsers (those that support the newsubmitter
parameter). For browsers that don't support it, we continue to just append the submit button's entry to the end, and we also add rudimentary support fortype="image"
buttons. If developers want full spec-compliant support for legacy browsers, they can use theformdata-submitter-polyfill
. (#9865)typescript
to 5.1 (#10581)window.history.pushState/replaceState
before updating React Router state (instead of after) so thatwindow.location
matchesuseLocation
during synchronous React 17 rendering. However, generally apps should not be relying onwindow.location
and should always referenceuseLocation
when possible, aswindow.location
will not be in sync 100% of the time (due topopstate
events, concurrent mode, etc.) (#10448) (#10211)tsc --skipLibCheck:false
issues on React 17 (#10622)[email protected]
@remix-run/[email protected]
@remix-run/[email protected]
Minor Changes
Add support for
application/json
andtext/plain
encodings forrouter.navigate
/router.fetch
submissions. To leverage these encodings, pass your data in abody
parameter and specify the desiredformEncType
: (#10413)Patch Changes
unstable_useBlocker
key issues inStrictMode
(#10573)shouldRevalidate
for fetchers that have not yet completed a data load (#10623)typescript
to 5.1 (#10581)basename
from thelocation
provided to<ScrollRestoration getKey>
to match theuseLocation
behavior (#10550)window.history.pushState/replaceState
before updating React Router state (instead of after) so thatwindow.location
matchesuseLocation
during synchronous React 17 rendering. However, generally apps should not be relying onwindow.location
and should always referenceuseLocation
when possible, aswindow.location
will not be in sync 100% of the time (due topopstate
events, concurrent mode, etc.) (#10448) (#10211)[email protected]
Patch Changes
unstable_useBlocker
key issues inStrictMode
(#10573)generatePath
when passed a numeric0
value parameter (#10612)typescript
to 5.1 (#10581)basename
from locations provided tounstable_useBlocker
functions to matchuseLocation
(#10573)tsc --skipLibCheck:false
issues on React 17 (#10622)@remix-run/[email protected]
[email protected]
Patch Changes
typescript
to 5.1 (#10581)[email protected]
[email protected]
[email protected]
Patch Changes
typescript
to 5.1 (#10581)[email protected]