chore: Update version for release #8031
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}
github-actions
bot
force-pushed
the
changeset-release/release-next
branch
from
36aa960
to
5bbdfab
Compare
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.
Releases
@remix-run/[email protected]
Minor Changes
unstable_prefix from theuseBlockerhook as it's been in use for enough time that we are confident in the API. We do not plan to remove the prefix fromunstable_usePromptdue to differences in how browsers handlewindow.confirmthat prevent React Router from guaranteeing consistent/correct behavior. (#7882)Patch Changes
LiveReloadcomponent afterScriptsin Vite dev (#7919)LiveReloadcomponent in Vite dev (#7919)@remix-run/[email protected]@remix-run/[email protected]
Minor Changes
cookiedependency from0.4.1to0.5.0to inherit support forPriorityattribute in Chrome (#6770)@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
Support rendering of
LiveReloadcomponent afterScriptsin Vite dev (#7919)fix(vite): fix "react-refresh/babel" resolution for custom server with pnpm (#7904)
Support JSX usage in
.jsxfiles without manualReactimport in Vite (#7888)Support optional rendering of
LiveReloadcomponent in Vite dev (#7919)Fix Vite production builds when plugins that have different local state between
developmentandproductionmodes are present, e.g.@mdx-js/rollup. (#7911)Cache resolution of Remix Vite plugin options (#7908)
Support Vite 5 (#7846)
Allow
process.env.NODE_ENVvalues other than"development"in Vite dev (#7980)Attach CSS from shared chunks to routes in Vite build (#7952)
fix(vite): Let Vite handle serving files outside of project root via
/@fs(#7913)This fixes errors when using default client entry or server entry in a pnpm project
where those files may be outside of the project root, but within the workspace root.
By default, Vite prevents access to files outside the workspace root
(when using workspaces) or outside of the project root (when not using
workspaces) unless user explicitly opts into it via Vite's
server.fs.allow.Improve performance of LiveReload proxy in Vite dev (#7883)
fix(vite): deduplicate
@remix-run/react(#7926)Pre-bundle Remix dependencies to avoid Remix router duplicates.
Our remix-react-proxy plugin does not process default client and
server entry files since those come from within
node_modules.That means that before Vite pre-bundles dependencies (e.g. first time dev server is run)
mismatching Remix routers cause
Error: You must render this element inside a <Remix> element.Fix React Fast Refresh error on load when using
deferin Vite dev server (#7842)Handle multiple "Set-Cookie" headers in Vite dev server (#7843)
Fix flash of unstyled content on initial page load in Vite dev when using a custom Express server (#7937)
Emit assets that were only referenced in the server build into the client assets directory in Vite build (#8031)
Populate
process.envfrom.envfiles on the server in Vite dev (#7958)Fix
FutureConfigtype (#7895)Updated dependencies:
@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]@remix-run/[email protected]
Patch Changes
@remix-run/[email protected]@remix-run/[email protected][email protected]
[email protected]
remixSee the
CHANGELOG.mdin individual Remix packages for all changes.@remix-run/[email protected]
@remix-run/[email protected]