Version Packages (next) - #355
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
September 10, 2026 00:20
1e13cf2 to
8a039cf
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
@solidjs/vite-plugin@3.0.0-next.41
Patch Changes
buildInputs(regression in 3.0.0-next.40) #353, a regression of 3.0.0-next.40 / Keep genuine configured entries when reclassifying emitted lazy facades #347). With filesystem-routing'sfileRoutes({ routers: { client }, buildInputs: 'client' })every route module is abuild.rollupOptions.input, and since Keep genuine configured entries when reclassifying emitted lazy facades #347 those records rightly keepisEntryinvirtual:solid-manifest. The generated handler resolved the client entry by scanning for the firstisEntryrecord, so a route key sorting ahead of the plugin's ownvirtual:solid-ssr-entry-client.tsxwon: the document's<script type="module">pointed at the route chunk (the page never hydrated) and<head>linked that route's CSS while the entry graph's global stylesheet was never linked. The manifest module now names the client entry explicitly —_entrycarries its key (the entry start mode injects, or the single configured input outside start mode) and its record is serialized first — and the handler reads_entrybefore falling back to theisEntryscan for hand-rolled manifests.@solidjs/web'sregisterEntryAssets, which links the entry graph's stylesheets and modulepreloads by the firstisEntryrecord, therefore agrees on the same chunk. Other configured inputs keepisEntry; they are genuine entries, just not the one the document boots.solidexport condition are now inlined in dev server environments too, closing the remaining half of the two-instance split. Inliningsolid-jsand@solidjs/webfixes every resolution those two perform, and vitefu inlines packages that advertise asolidexport condition — but a package that does neither is still externalized, and Node resolves its ownimport "solid-js"without thedevelopmentcondition, so it loads the production server build while the inlined graph holds the dev one.@solidjs/metais the first-party example: it has nosolidcondition, so under solid-js 2.0.0-rc.7 an app rendering a<Title>still died inuseContexton a secondsharedConfigeven with the core packages inlined. The crawl now also classifies any package declaringsolid-jsor@solidjs/webin itsdependenciesorpeerDependenciesas a semi-framework package —ssr.noExternalwithoutoptimizeDeps.exclude, since these hold no raw Solid components — so third-party component libraries and metadata helpers reach the same copy as everything else. Gated on the dev-condition swap (and off under vitest, which manages inlining itself), leaving builds unchanged. Two guards keep the rule narrow: tooling that declaressolid-jsas a peer but never runs inside the SSR module runner —@solidjs/vite-pluginitself,vite,vitest,eslint-plugin-*,vite-plugin-*,prettier-plugin-*,@types/*— is skipped entirely (classifying the plugin would also crawl its dependencies and pre-bundle@babel/coreand@solidjs/babel-plugininto the browser'soptimizeDeps, several megabytes of dead weight per cold start); and thessr.externallist vitefu derives from framework packages' non-frameworkdependenciesis filtered against the finalnoExternallist, because Vite givesexternalprecedence — a framework package listing@solidjs/webunderdependencies(e.g.@tanstack/solid-router) would otherwise re-externalize a core the plugin just inlined and split the runtime again.