Repository navigation
chore: release - #2381
Open
github-actions[bot] wants to merge 1 commit into
Open
chore: release#2381github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
✅ Deploy Preview for solid-start-landing-page ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 14, 2026 16:36
9f93de4 to
6e6d4e1
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
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 main, this PR will be updated.
Releases
@solidjs/start@2.2.3
Patch Changes
@solidjs/startout of server pre-bundling, so that server functions no longer fail with "invalid server function" in dev with plugins that pre-bundle server dependencies, such as the Cloudflare Vite plugin.fetchnever rejected: with Nitro, theerrorhook and theerrorHandlernever ran for it, and SolidStart's own dev server never showed its error overlay. An h3HTTPErrornot marked unhandled, or a status thrown as a number, is answered as before. A server that calls the handler'sfetchitself now gets a rejected promise for such an error and answers it; headers set for the error response withevent.res.errHeadersare not part of that answer.