Version Packages (next) - #305
Merged
Merged
Conversation
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.26
Patch Changes
6dbb7e8: Start mode's generated request handler now default-exports a Fetchable
{ fetch(request) }object alongside its namedhandleRequestexport.Deployment integrations that follow the web-standard Fetchable convention
can consume the virtual handler or built server entry without a wrapper.
The
fetchmethod intentionally ignores provider arguments after the requestinstead of forwarding them as Solid handler options.
The normal
ssrenvironment now exposes that handler as itsindexserviceentry. Provider Vite plugins can adopt the same environment for development
and production without
start.external, a custom source entry, or explicitRollup input. Standalone builds continue to emit
dist/server/server.js.06aadc6: Don't default
test.environmentto jsdom for vitest browser-mode projects (test.browser.enabled): vitest 4 probes for the environment's package at startup and sets a failing exit code when jsdom isn't installed, even though the suite runs (and passes) in the real browser. Browser-mode projects now fall back to vitest's own node default, which has no package probe — mirroring the existing jest-dom gate. Non-browser projects keep the jsdom default.