Version Packages (next) - #361
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
September 11, 2026 17:01
a760639 to
dcfc55a
Compare
commit: |
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.43
Patch Changes
resolve.noExternalpatterns when adding vitefu's externals to the SSR environment. The plugin already refused to re-externalize anythingnoExternalinlines, but it compared literal names only, while Vite treats string entries as picomatch patterns and RegExp entries as tests (createFilter(undefined, noExternal, { resolve: false })). Since 3.0.0-next.41 the crawl also reaches the packages that consume the Solid runtime, and their non-Solid dependencies land inssr.external— so a host that inlines its packages by pattern (TanStack Start's@tanstack/start**, whose@tanstack/start-server-coreresolves its#tanstack-*imports only when Vite processes it) saw them re-externalized, andvite devfailed withERR_PACKAGE_IMPORT_NOT_DEFINED: Package import specifier "#tanstack-router-entry" is not defined. The externals are now filtered with the same matcher Vite uses, and a single string or RegExpnoExternalvalue is kept instead of being dropped.observeoption: resolve Solid's observe builds for production observability.observe: trueadds theobserveexport condition to every environment — client and server, inlined and externalized (resolve.externalConditions), inlining the core runtime and its consumers for server builds the way the dev posture already does so one build is loaded end to end — and turns on the compiler'scomponentNamesoption, so component owner labels (<Home>) survive minification in diagnostics and attribution paths.componentNamesis also enabled under the dev posture, wherelazy()and HMR wrappers otherwise hide the tag name. Requires@solidjs/compiler/@solidjs/babel-plugin≥ 2.0.0-rc.8 (the release that adds the option).