V2 Version Packages (beta)#8418
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/build/v2
branch
from
486d0c2 to
273918b
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 build/v2, this PR will be updated.
build/v2is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonbuild/v2.Releases
@qwik.dev/core@2.0.0-beta.28
Minor Changes
✨ the Vite environment API is now better supported. This means that you can build multiple environments simultaneously without Qwik having a problem, with
vite build --app. (by @wmertens in #6903)However, Qwik Router adapters still require running
build.serverseparately for now because they use a different vite configuration file.The minimum supported version of Vite is now 6.0.0.
✨ Hot Module Replacement (HMR) support. You now get instant updates in the browser when you change your source code, without losing state. This happens without forcing a resume at load, so everything is fast. (by @wmertens in #8421)
The slight disadvantage is that all components now send their state during development (because now they can always rerender on the client). You can disable HMR and fall back to full page reloads by setting
{devTools: {hmr: false}}in theqwikVite()plugin configuration.@qwik.dev/router@2.0.0-beta.28
Minor Changes
✨ the Vite environment API is now better supported. This means that you can build multiple environments simultaneously without Qwik having a problem, with
vite build --app. (by @wmertens in #6903)However, Qwik Router adapters still require running
build.serverseparately for now because they use a different vite configuration file.The minimum supported version of Vite is now 6.0.0.
✨ Hot Module Replacement (HMR) support. You now get instant updates in the browser when you change your source code, without losing state. This happens without forcing a resume at load, so everything is fast. (by @wmertens in #8421)
The slight disadvantage is that all components now send their state during development (because now they can always rerender on the client). You can disable HMR and fall back to full page reloads by setting
{devTools: {hmr: false}}in theqwikVite()plugin configuration.Patch Changes
640e8d3,d304830]:@qwik.dev/react@2.0.0-beta.28
Patch Changes
640e8d3,d304830]:create-qwik@2.0.0-beta.28
eslint-plugin-qwik@2.0.0-beta.28