Version Packages (next)#278
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
July 20, 2026 20:21
7bcc085 to
8bc0e3a
Compare
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
July 20, 2026 20:25
8bc0e3a to
ab64441
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 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.14
Patch Changes
b2b9979: update to solid 2.0.0-beta.21 and @dom-expressions/compiler 0.50.0-next.24
5828a6e: Turnkey SSR: the object form of the
ssroption (even empty:ssr: {})adds a serving layer on top of the SSR transforms so a plain Vite app gets
streaming server-side rendering with zero wiring — no entry files, no
index.html, no dev server script (requires Vite 6+;
ssr: truekeeps thetransform-only behavior unchanged).
HTML-accepting GET requests through the SSR environment, scoping each
request with
provideRequestEventand injecting the Vite client and thedev style patch into
<head>; SSR errors flow (stack-fixed) to Vite'serror page with the overlay.
viteis the whole dev story.vite buildproduces both bundles via theenvironments/builder API — client assets and manifest to
dist/client,the server bundle to
dist/server/server.js(vite build --appand theclassic two-step
vite build+vite build --ssralso work).virtual:solid-ssr-handler,whose
handleRequest(request)export maps a web-standardRequestto astreamed
Response— adapter-agnostic, one line to mount on any server.Hashed client assets are resolved through
virtual:solid-manifest.ssr.entryServer/ssr.entryClient; conventionalsrc/entry-server.*/src/entry-client.*(the server entry exportsrender(request?, context?); authored/src/entry-client.tsxscriptreferences are rewritten to the hashed asset in prod); else both entries
are generated from a root component (
ssr.app, defaultsrc/App.*)wrapped in a document shell (
ssr.document, defaultsrc/Document.*,else a built-in one).
serverFunctionsenabled the two compose: the dev server-functionmiddleware runs ahead of SSR, and the production
handleRequestservesthe endpoint before rendering.
client build's persisted manifest at manifest load time as well, so
builder-mode (single-invocation) builds keep registrations for functions
only client code references.