Version Packages (next)#280
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/next
branch
3 times, most recently
from
July 23, 2026 08:52
b408226 to
e820bf7
Compare
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
July 23, 2026 20:08
e820bf7 to
f61e9a7
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.16
Minor Changes
vitepeer dependency is now^6.0.0 || ^7.0.0 || ^8.0.0and the legacy pre-environment-API code pathsare gone: the plugin now always configures
resolve.conditionsand SSRnoExternal/externalper environment throughconfigEnvironment(insteadof the old top-level
resolve.conditions/ssrconfig placement), and theturnkey SSR object form no longer needs a Vite-version guard. The
vite-3,vite-4andvite-5examples were removed. If you are on Vite 3–5, stay onan earlier release of this plugin or upgrade Vite.
serverFunctions: { components: true }(experimental): server components ride server functions with zero extra plugin config — the dev middleware and production handler serve component responses automatically, and turnkey SSR's generated entries emit the document wiring (render plugin, bootstrap script, clientinstallServerComponents()call)Patch Changes
flash of unstyled content. The dev middleware walks the SSR module graph
from the root entry (the app + document for generated entries, the authored
server entry otherwise), compiles each transitively imported stylesheet
through the client environment, and SSRs them as
<style data-asset data-vite-dev-id>tags in<head>— the same shape thelazy-asset system emits, so Vite's client adopts them on startup (CSS HMR
updates the adopted tag in place) and the dev style patch dedupes any
late-injected twin. Previously entry CSS only arrived when the client entry
JS executed, so server-painted markup flashed unstyled in dev; production
was always fine (manifest-driven
<link rel="stylesheet">).vite-plugin-solid/virtual-solid-manifestambient typedeclarations through a package
exportssubpath so"types": ["vite-plugin-solid/virtual-solid-manifest"]resolves undermoduleResolution: "bundler"/node16too (previously only classicnoderesolution found the shipped
.d.ts).