chore: Update version for release (pre) #7780
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
[email protected]
Minor Changes
Unstable Vite support for Node-based Remix apps (#7590)
remix build
👉vite build && vite build --ssr
remix dev
👉vite dev
Other runtimes (e.g. Deno, Cloudflare) not yet supported.
Custom server (e.g. Express) not yet supported.
See "Future > Vite" in the Remix Docs for details.
Patch Changes
Support local tarballs with
.tgz
extension (#7649)It allows to directly support
pnpm pack
tarballs.Set default Remix version to match the version of
create-remix
being used. This most notably enables easier usage of tags, e.g.npm create remix@nightly
. (#7670)@remix-run/[email protected]
Minor Changes
Add a new
future.v3_fetcherPersist
flag to change the persistence behavior of fetchers. Instead of being immediately cleaned up when unmoutned in the UI, fetchers will persist until they return to anidle
state (RFC) (#7704)useFetchers()
API was always supposed to only reflect in-flight fetcher information for pending/optimistic UI -- it was not intended to reflect fetcher data or hang onto fetchers after they returned to anidle
stateuseFetchers()
. They served effectively no purpose in there since you can access the data viauseFetcher().data
).idle
state. They will remain exposed viauseFetchers
while in-flight so you can still access pending/optimistic data after unmount.Unstable Vite support for Node-based Remix apps (#7590)
remix build
👉vite build && vite build --ssr
remix dev
👉vite dev
Other runtimes (e.g. Deno, Cloudflare) not yet supported.
Custom server (e.g. Express) not yet supported.
See "Future > Vite" in the Remix Docs for details.
Patch Changes
@remix-run/[email protected]
@remix-run/[email protected]
@remix-run/[email protected]
@remix-run/[email protected]
Minor Changes
Add a new
future.v3_fetcherPersist
flag to change the persistence behavior of fetchers. Instead of being immediately cleaned up when unmoutned in the UI, fetchers will persist until they return to anidle
state (RFC) (#7704)useFetchers()
API was always supposed to only reflect in-flight fetcher information for pending/optimistic UI -- it was not intended to reflect fetcher data or hang onto fetchers after they returned to anidle
stateuseFetchers()
. They served effectively no purpose in there since you can access the data viauseFetcher().data
).idle
state. They will remain exposed viauseFetchers
while in-flight so you can still access pending/optimistic data after unmount.Unstable Vite support for Node-based Remix apps (#7590)
remix build
👉vite build && vite build --ssr
remix dev
👉vite dev
Other runtimes (e.g. Deno, Cloudflare) not yet supported.
Custom server (e.g. Express) not yet supported.
See "Future > Vite" in the Remix Docs for details.
Patch Changes
Fix warning that could be logged when using route files with no
default
export (#7745)default
which we can then end up passing toReact.createElement
, triggering the console warning, but generally no UI issuesComponent: undefined
off to the React Router layer@remix-run/react
layer and hopefully disappears in a Vite worldUpdated dependencies:
@remix-run/[email protected]
@remix-run/[email protected]
Minor Changes
Unstable Vite support for Node-based Remix apps (#7590)
remix build
👉vite build && vite build --ssr
remix dev
👉vite dev
Other runtimes (e.g. Deno, Cloudflare) not yet supported.
Custom server (e.g. Express) not yet supported.
See "Future > Vite" in the Remix Docs for details.
@remix-run/[email protected]
Minor Changes
Unstable Vite support for Node-based Remix apps (#7590)
remix build
👉vite build && vite build --ssr
remix dev
👉vite dev
Other runtimes (e.g. Deno, Cloudflare) not yet supported.
Custom server (e.g. Express) not yet supported.
See "Future > Vite" in the Remix Docs for details.
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]
Patch Changes
Allow the
@remix-run/express
adapter to work behind a proxy when usingapp.enable('trust proxy')
(#7323)req.get('host')
to construct the RemixRequest
, but that does not respectX-Forwarded-Host
req.hostname
which will respectX-Forwarded-Host
Updated dependencies:
@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]
remix
See the
CHANGELOG.md
in individual Remix packages for all changes.@remix-run/[email protected]
@remix-run/[email protected]
[email protected]
Minor Changes
Unstable Vite support for Node-based Remix apps (#7590)
remix build
👉vite build && vite build --ssr
remix dev
👉vite dev
Other runtimes (e.g. Deno, Cloudflare) not yet supported.
Custom server (e.g. Express) not yet supported.
See "Future > Vite" in the Remix Docs for details.