chore: Update version for release (pre) #7780
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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-nextis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonrelease-next.Releases
create-remix@2.2.0-pre.0
Minor Changes
Unstable Vite support for Node-based Remix apps (#7590)
remix build👉vite build && vite build --ssrremix dev👉vite devOther 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
.tgzextension (#7649)It allows to directly support
pnpm packtarballs.Set default Remix version to match the version of
create-remixbeing used. This most notably enables easier usage of tags, e.g.npm create remix@nightly. (#7670)@remix-run/dev@2.2.0-pre.0
Minor Changes
Add a new
future.v3_fetcherPersistflag 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 anidlestate (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 anidlestateuseFetchers(). They served effectively no purpose in there since you can access the data viauseFetcher().data).idlestate. They will remain exposed viauseFetcherswhile 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 --ssrremix dev👉vite devOther 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/server-runtime@2.2.0-pre.0@remix-run/serve@2.2.0-pre.0@remix-run/node@2.2.0-pre.0@remix-run/react@2.2.0-pre.0
Minor Changes
Add a new
future.v3_fetcherPersistflag 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 anidlestate (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 anidlestateuseFetchers(). They served effectively no purpose in there since you can access the data viauseFetcher().data).idlestate. They will remain exposed viauseFetcherswhile 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 --ssrremix dev👉vite devOther 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
defaultexport (#7745)defaultwhich we can then end up passing toReact.createElement, triggering the console warning, but generally no UI issuesComponent: undefinedoff to the React Router layer@remix-run/reactlayer and hopefully disappears in a Vite worldUpdated dependencies:
@remix-run/server-runtime@2.2.0-pre.0@remix-run/server-runtime@2.2.0-pre.0
Minor Changes
Unstable Vite support for Node-based Remix apps (#7590)
remix build👉vite build && vite build --ssrremix dev👉vite devOther 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/testing@2.2.0-pre.0
Minor Changes
Unstable Vite support for Node-based Remix apps (#7590)
remix build👉vite build && vite build --ssrremix dev👉vite devOther 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/react@2.2.0-pre.0@remix-run/node@2.2.0-pre.0@remix-run/architect@2.2.0-pre.0
Patch Changes
@remix-run/node@2.2.0-pre.0@remix-run/cloudflare@2.2.0-pre.0
Patch Changes
@remix-run/server-runtime@2.2.0-pre.0@remix-run/cloudflare-pages@2.2.0-pre.0
Patch Changes
@remix-run/cloudflare@2.2.0-pre.0@remix-run/cloudflare-workers@2.2.0-pre.0
Patch Changes
@remix-run/cloudflare@2.2.0-pre.0@remix-run/deno@2.2.0-pre.0
Patch Changes
@remix-run/server-runtime@2.2.0-pre.0@remix-run/express@2.2.0-pre.0
Patch Changes
Allow the
@remix-run/expressadapter to work behind a proxy when usingapp.enable('trust proxy')(#7323)req.get('host')to construct the RemixRequest, but that does not respectX-Forwarded-Hostreq.hostnamewhich will respectX-Forwarded-HostUpdated dependencies:
@remix-run/node@2.2.0-pre.0@remix-run/node@2.2.0-pre.0
Patch Changes
@remix-run/server-runtime@2.2.0-pre.0@remix-run/serve@2.2.0-pre.0
Patch Changes
@remix-run/express@2.2.0-pre.0@remix-run/node@2.2.0-pre.0remix@2.2.0-pre.0
remixSee the
CHANGELOG.mdin individual Remix packages for all changes.@remix-run/css-bundle@2.2.0-pre.0
@remix-run/eslint-config@2.2.0-pre.0
integration-tests@0.0.0-pre.0
Minor Changes
Unstable Vite support for Node-based Remix apps (#7590)
remix build👉vite build && vite build --ssrremix dev👉vite devOther 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.