Version Packages (next) - #378
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
September 27, 2026 09:50
b67ff77 to
8ea38ce
Compare
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
September 27, 2026 10:16
8ea38ce to
b8ec7b9
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.46
Patch Changes
engines.nodeis now>=22.12.0(was^20.19.0 || >=22.12.0), matching thesolid-js,@solidjs/weband@solidjs/signals2.0 runtime packages, which have been ESM-only with that floor since rc.8; the README says the same. Underserve,@solidjs/signalsjoinssolid-jsand@solidjs/webinresolve.dedupewhen the app root can reach a copy of it (node_modules/@solidjs/signals, walking up — an npm-style hoist or a direct dependency):@solidjs/diagnostics/browserandsolid-js/attributionimport the signals core directly, so a nested/duplicated install yielded a second engine beside the onesolid-jsloads. The entry is gated on the root copy becauseresolve.deduperesolves the listed package from the root and Vite's Node-side resolver (fetchModulefor externalized SSR imports, and the externalize decision) has no importer fallback when that misses — under pnpm's isolated layout, where signals exists only assolid-js's transitive dependency, an unconditional entry turnedimport "@solidjs/signals"from the inlinedsolid-jsintoERR_MODULE_NOT_FOUNDonce anything externalized it (vitefu does, when a semi-framework package such as@solidjs/diagnosticslists it underdependencies). With no root copy there is nothing to dedupe to, so the gate loses nothing. Signals does not joinoptimizeDeps.include: the optimizer already reaches it throughsolid-js, and an include entry that doesn't resolve from the root warns on every start.vite dev. NewperformanceTracksoption (boolean | PerformanceTracksOptions, defaulttrue): the plugin injects a client module that calls@solidjs/web/performance-tracks'enablePerformanceTracks()ahead of the app's entry — a<head>module script forindex.htmlapps, the first import of the (generated or authored) client entry in start mode — so hydration and the first interaction land on the timeline without the app enabling the tracks itself. An object passes the adapter's options through (minMs,rich,attribution, serialized into the module);falseopts out. Dev serve only: never onvite build(dev: trueandobservebuilds included), preview, or in test mode. The dev server already writes itsServer-Timingmetrics, which the tracks read back. Skipped with a startup warning if the installed@solidjs/weblacks the./performance-trackssubpath.vite devfailing in dependency optimization for apps using a Solid library that ships build-time code in the same package (vite dev: semi-framework crawl pre-bundles a library's node-only dependencies (@yak/solid > @swc/core) since next.44 #375). Since the semi-framework classification landed (any package withsolid-js/@solidjs/webindependenciesorpeerDependenciesisssr.noExternalso it shares the app's runtime copy), vitefu's crawl also deep-included every CJS dependency of such a package into the browser'soptimizeDeps.include, exactly as it does for framework packages. For@yak/solidthat is@swc/core, and rolldown failed on its native.nodebinding (UNLOADABLE_DEPENDENCY … stream did not contain valid UTF-8) before the dev server served a page. Sharing the runtime needs nothing pre-bundled, so include chains that pass through a semi-framework package are dropped; a browser-side CJS dependency of one is discovered and optimized on first use, as before the package was classified. Framework packages (asolidexport condition) keep vitefu's full treatment.