Version Packages (next) - #264
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
July 9, 2026 04:24
faf8293 to
3fde1a6
Compare
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
July 10, 2026 21:47
3fde1a6 to
2e730a7
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
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 next, this PR will be updated.
nextis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonnext.Releases
vite-plugin-solid@3.0.0-next.6
Minor Changes
compiler: "native"JSX transform path powered by@dom-expressions/jsx-compiler.Patch Changes
5250437: Harden SSR asset resolution for
lazy()modules.preserveSignature: "exports-only"), so it always gets a manifest entry keyed by its source path and a stabledefaultexport — even whenmanualChunksor dual static/dynamic imports would otherwise fold it facade-less into a shared chunk. This also coversimport.meta.globtargets that never pass through thelazy()moduleUrl transform.isEntrytoisDynamicEntryin the virtual manifest so the runtime's entry-asset detection can't pick a lazy facade instead of the real client entry.$$moduleUrlexport carrying the module's client-manifest key. Server-sidelazy()(solid-js ≥ 2.0.0-beta.17) reads it off the resolved module when the callsite has no static import specifier — enabling asset resolution and hydration preloading for glob-based lazy routes. Client builds are untouched.