chore: Update version for release (pre) #9402
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/architect@2.9.2-pre.0
Patch Changes
@remix-run/node@2.9.2-pre.0
@remix-run/cloudflare@2.9.2-pre.0
Patch Changes
Typesafety for single-fetch: defineLoader, defineClientLoader, defineAction, defineClientAction (#9372)
defineLoader
anddefineAction
are helpers for authoringloader
s andaction
s.They are identity functions; they don't modify your loader or action at runtime.
Rather, they exist solely for typesafety by providing types for args and by ensuring valid return types.
Note that
defineLoader
anddefineAction
are not technically necessary for defining loaders and actions if you aren't concerned with typesafety:This means that you can opt-in to
defineLoader
incrementally, one loader at a time.You can return custom responses via the
json
/defer
utilities, but doing so will revert back to the old JSON-based typesafety mechanism:You can also continue to return totally custom responses with
Response
though this continues to be outside of the typesystem since the built-inResponse
type is not genericUpdated dependencies:
@remix-run/server-runtime@2.9.2-pre.0
@remix-run/cloudflare-pages@2.9.2-pre.0
Patch Changes
@remix-run/cloudflare@2.9.2-pre.0
@remix-run/cloudflare-workers@2.9.2-pre.0
Patch Changes
@remix-run/cloudflare@2.9.2-pre.0
@remix-run/deno@2.9.2-pre.0
Patch Changes
Typesafety for single-fetch: defineLoader, defineClientLoader, defineAction, defineClientAction (#9372)
defineLoader
anddefineAction
are helpers for authoringloader
s andaction
s.They are identity functions; they don't modify your loader or action at runtime.
Rather, they exist solely for typesafety by providing types for args and by ensuring valid return types.
Note that
defineLoader
anddefineAction
are not technically necessary for defining loaders and actions if you aren't concerned with typesafety:This means that you can opt-in to
defineLoader
incrementally, one loader at a time.You can return custom responses via the
json
/defer
utilities, but doing so will revert back to the old JSON-based typesafety mechanism:You can also continue to return totally custom responses with
Response
though this continues to be outside of the typesystem since the built-inResponse
type is not genericUpdated dependencies:
@remix-run/server-runtime@2.9.2-pre.0
@remix-run/dev@2.9.2-pre.0
Patch Changes
dest already exists
error when runningremix vite:build
(#9305)@remix-run/node
from Vite plugin'soptimizeDeps.include
list since it was unnecessary and resulted in Vite warnings when not depending on this package. (#9287)?client-route=1
imports in development (#9395)react-refresh
Babel transform within the Remix Vite plugin (#9241)@remix-run/react@2.9.2-pre.0
@remix-run/server-runtime@2.9.2-pre.0
@remix-run/node@2.9.2-pre.0
@remix-run/serve@2.9.2-pre.0
@remix-run/express@2.9.2-pre.0
Patch Changes
@remix-run/node@2.9.2-pre.0
@remix-run/node@2.9.2-pre.0
Patch Changes
Typesafety for single-fetch: defineLoader, defineClientLoader, defineAction, defineClientAction (#9372)
defineLoader
anddefineAction
are helpers for authoringloader
s andaction
s.They are identity functions; they don't modify your loader or action at runtime.
Rather, they exist solely for typesafety by providing types for args and by ensuring valid return types.
Note that
defineLoader
anddefineAction
are not technically necessary for defining loaders and actions if you aren't concerned with typesafety:This means that you can opt-in to
defineLoader
incrementally, one loader at a time.You can return custom responses via the
json
/defer
utilities, but doing so will revert back to the old JSON-based typesafety mechanism:You can also continue to return totally custom responses with
Response
though this continues to be outside of the typesystem since the built-inResponse
type is not genericUpdated dependencies:
@remix-run/server-runtime@2.9.2-pre.0
@remix-run/react@2.9.2-pre.0
Patch Changes
Add
undefined
touseActionData
type override (#9322)Allow a nonce to be set on single fetch stream transfer inline scripts (#9364)
Typesafety for single-fetch: defineLoader, defineClientLoader, defineAction, defineClientAction (#9372)
defineLoader
anddefineAction
are helpers for authoringloader
s andaction
s.They are identity functions; they don't modify your loader or action at runtime.
Rather, they exist solely for typesafety by providing types for args and by ensuring valid return types.
Note that
defineLoader
anddefineAction
are not technically necessary for defining loaders and actions if you aren't concerned with typesafety:This means that you can opt-in to
defineLoader
incrementally, one loader at a time.You can return custom responses via the
json
/defer
utilities, but doing so will revert back to the old JSON-based typesafety mechanism:You can also continue to return totally custom responses with
Response
though this continues to be outside of the typesystem since the built-inResponse
type is not genericUpdated dependencies:
@remix-run/server-runtime@2.9.2-pre.0
@remix-run/serve@2.9.2-pre.0
Patch Changes
@remix-run/node@2.9.2-pre.0
@remix-run/express@2.9.2-pre.0
@remix-run/server-runtime@2.9.2-pre.0
Patch Changes
Don't log thrown response stubs via
handleError
in Single Fetch (#9369)Automatically wrap resource route naked object returns in
json()
for back-compat in v2 (and log deprecation warning) (#9349)Typesafety for single-fetch: defineLoader, defineClientLoader, defineAction, defineClientAction (#9372)
defineLoader
anddefineAction
are helpers for authoringloader
s andaction
s.They are identity functions; they don't modify your loader or action at runtime.
Rather, they exist solely for typesafety by providing types for args and by ensuring valid return types.
Note that
defineLoader
anddefineAction
are not technically necessary for defining loaders and actions if you aren't concerned with typesafety:This means that you can opt-in to
defineLoader
incrementally, one loader at a time.You can return custom responses via the
json
/defer
utilities, but doing so will revert back to the old JSON-based typesafety mechanism:You can also continue to return totally custom responses with
Response
though this continues to be outside of the typesystem since the built-inResponse
type is not genericPass
response
stub to resource route handlerså when single fetch is enabled (#9349)@remix-run/testing@2.9.2-pre.0
Patch Changes
@remix-run/react@2.9.2-pre.0
@remix-run/node@2.9.2-pre.0
create-remix@2.9.2-pre.0
remix@2.9.2-pre.0
remix
See the
CHANGELOG.md
in individual Remix packages for all changes.@remix-run/css-bundle@2.9.2-pre.0
@remix-run/eslint-config@2.9.2-pre.0