chore: Update version for release (pre) #9808
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.
release-next
is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exit
onrelease-next
.Releases
@remix-run/[email protected]
Minor Changes
unstable_data()
API for usage with Remix Single Fetch (#9769)replace(url, init?)
alternative toredirect(url, init?)
that performs ahistory.replaceState
instead of ahistory.pushState
on client-side navigation redirects (#9764)Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
Minor Changes
unstable_data()
API for usage with Remix Single Fetch (#9769)replace(url, init?)
alternative toredirect(url, init?)
that performs ahistory.replaceState
instead of ahistory.pushState
on client-side navigation redirects (#9764)Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
Minor Changes
future.unstable_fogOfWar
tofuture.unstable_lazyRouteDiscovery
for clarity (#9763)Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
@remix-run/[email protected]
@remix-run/[email protected]
@remix-run/[email protected]
Minor Changes
unstable_data()
API for usage with Remix Single Fetch (#9769)replace(url, init?)
alternative toredirect(url, init?)
that performs ahistory.replaceState
instead of ahistory.pushState
on client-side navigation redirects (#9764)Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
Minor Changes
Add a new
unstable_data()
API for usage with Remix Single Fetch (#9769)Add a new
replace(url, init?)
alternative toredirect(url, init?)
that performs ahistory.replaceState
instead of ahistory.pushState
on client-side navigation redirects (#9764)Rename
future.unstable_fogOfWar
tofuture.unstable_lazyRouteDiscovery
for clarity (#9763)Single Fetch: Remove
responseStub
in favor ofheaders
(#9769)Background
middleware
implementation would require something likeResponseStub
so users could mutatestatus
/headers
inmiddleware
before/after handlers as well as during handlersheaders
got merged between document and data requestsResponseStub
and removed the usage ofheaders
in Single Fetchmiddleware
won't need a stub - users can just mutate theResponse
they get fromawait next()
directlyheaders
get merged, it makes more sense to stick with the currentheaders
API and apply that to Single Fetch and avoid introducing a totally new thing inRepsonseStub
(that always felt a bit awkward to work with anyway)With this change:
Response
instances in favor of returning raw data from loaders and actions:return json({ data: whatever });
return { data: whatever };
json()
anddefer()
calls in favor of returning raw data if they weren't setting customstatus
/headers
json
anddefer
in the next major version, but both should still work in Single Fetch in v2 to allow for incremental adoption of the new behaviorstatus
/headers
:unstable_data({...}, responseInit)
utility that will let you send backstatus
/headers
alongside your raw data without having to encode it into aResponse
headers()
function will let you control header merging for both document and data requestsPatch Changes
undefined
to theuseRouteLoaderData
type override (#9796)@remix-run/[email protected]
@remix-run/[email protected]
Minor Changes
Add a new
unstable_data()
API for usage with Remix Single Fetch (#9769)Add a new
replace(url, init?)
alternative toredirect(url, init?)
that performs ahistory.replaceState
instead of ahistory.pushState
on client-side navigation redirects (#9764)Rename
future.unstable_fogOfWar
tofuture.unstable_lazyRouteDiscovery
for clarity (#9763)Single Fetch: Remove
responseStub
in favor ofheaders
(#9769)Background
middleware
implementation would require something likeResponseStub
so users could mutatestatus
/headers
inmiddleware
before/after handlers as well as during handlersheaders
got merged between document and data requestsResponseStub
and removed the usage ofheaders
in Single Fetchmiddleware
won't need a stub - users can just mutate theResponse
they get fromawait next()
directlyheaders
get merged, it makes more sense to stick with the currentheaders
API and apply that to Single Fetch and avoid introducing a totally new thing inRepsonseStub
(that always felt a bit awkward to work with anyway)With this change:
Response
instances in favor of returning raw data from loaders and actions:return json({ data: whatever });
return { data: whatever };
json()
anddefer()
calls in favor of returning raw data if they weren't setting customstatus
/headers
json
anddefer
in the next major version, but both should still work in Single Fetch in v2 to allow for incremental adoption of the new behaviorstatus
/headers
:unstable_data({...}, responseInit)
utility that will let you send backstatus
/headers
alongside your raw data without having to encode it into aResponse
headers()
function will let you control header merging for both document and data requestsPatch Changes
@remix-run/[email protected]
Minor Changes
future.unstable_fogOfWar
tofuture.unstable_lazyRouteDiscovery
for clarity (#9763)Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
[email protected]
[email protected]
remix
See the
CHANGELOG.md
in individual Remix packages for all changes.@remix-run/[email protected]
@remix-run/[email protected]