Repository navigation
chore: release - #2344
Merged
Merged
chore: release#2344
Conversation
github-actions
Bot
force-pushed
the
changeset-release/1.x
branch
4 times, most recently
from
October 15, 2026 19:52
dd6ae8d to
cc135b7
Compare
github-actions
Bot
force-pushed
the
changeset-release/1.x
branch
from
October 15, 2026 20:10
cc135b7 to
28b1f20
Compare
commit: |
birkskyum
approved these changes
Oct 15, 2026
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 1.x, this PR will be updated.
Releases
@solidjs/start@1.4.0
Minor Changes
ssr: "data-only". The app renders on the client without hydration, as withssr: false, but the server runs the requested page's routepreloads and streams their query results with the HTML shell, so the client doesn't fetch that data again.Patch Changes
92d9603: Let a
clientOnlyloader resolve to the component itself, so a named export works without wrapping it in{ default }:Destructuring the export inside the loader also lets the bundler leave the module's other exports out of the chunk.
8f03760: Add an
earlyHintsoption that sends the page's assets as103 Early Hints, so the browser can start downloading them while the server is still rendering. It covers the app's entry assets and the assets of the routes being rendered. On runtimes other than Node, the same hints are added asLinkheaders on the response. Off by default, and only applies to production builds.e36e23c: Make
event.request.signalabort when the client disconnects on Node. The request was built without a signal tied to the connection, so it never aborted and API routes kept running after the client went away. On web runtimes the platform signal still applies.95ca993: Reload the page once when a route's code fails to load during client-side navigation, such as when a deploy replaced it while the page was open. Before, the navigation ended on an error page until the user refreshed by hand. The page now reloads at the destination and loads the new version. A route that still fails right after the reload shows the error instead of reloading again. This only applies to production builds, and can be turned off with
reloadOnRouteChunkError: false.273496b: Serve pages in SPA mode (
ssr: false) when a route file exports both a page and an API handler, such as a[...404].tsxwith aGET. The server treated those routes as API-only, so aGETthat returned nothing gave a 404 for every URL the route matched.