Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .changeset/pre.json
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,7 @@
"drop-vite-lt-6",
"empty-dragons-grow",
"external-dev-styles",
"fetchable-start-handler",
"fix-runnable-environment-check",
"fix-ssr-stream-abort-crash",
"handler-edge-commit-fold",
Expand Down Expand Up @@ -65,6 +66,7 @@
"turnkey-ssr",
"turnkey-start-option",
"virtual-manifest-types-subpath",
"vitest-browser-mode-no-jsdom-default",
"vitest-client-posture",
"vitest-server-posture-opt-out"
]
Expand Down
18 changes: 18 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,23 @@
# Changelog

## 3.0.0-next.26

### Patch Changes

- 6dbb7e8: Start mode's generated request handler now default-exports a Fetchable
`{ fetch(request) }` object alongside its named `handleRequest` export.
Deployment integrations that follow the web-standard Fetchable convention
can consume the virtual handler or built server entry without a wrapper.
The `fetch` method intentionally ignores provider arguments after the request
instead of forwarding them as Solid handler options.

The normal `ssr` environment now exposes that handler as its `index` service
entry. Provider Vite plugins can adopt the same environment for development
and production without `start.external`, a custom source entry, or explicit
Rollup input. Standalone builds continue to emit `dist/server/server.js`.

- 06aadc6: Don't default `test.environment` to 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.

## 3.0.0-next.25

### Patch Changes
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "vite-plugin-solid",
"version": "3.0.0-next.25",
"version": "3.0.0-next.26",
"description": "solid-js integration plugin for vite 6/7/8",
"type": "module",
"files": [
Expand Down