Skip to content

Commit 8c1f62a

Browse files
Version Packages (next) (#305)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
1 parent 6dbb7e8 commit 8c1f62a

3 files changed

Lines changed: 21 additions & 1 deletion

File tree

.changeset/pre.json

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@
3131
"drop-vite-lt-6",
3232
"empty-dragons-grow",
3333
"external-dev-styles",
34+
"fetchable-start-handler",
3435
"fix-runnable-environment-check",
3536
"fix-ssr-stream-abort-crash",
3637
"handler-edge-commit-fold",
@@ -65,6 +66,7 @@
6566
"turnkey-ssr",
6667
"turnkey-start-option",
6768
"virtual-manifest-types-subpath",
69+
"vitest-browser-mode-no-jsdom-default",
6870
"vitest-client-posture",
6971
"vitest-server-posture-opt-out"
7072
]

CHANGELOG.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,23 @@
11
# Changelog
22

3+
## 3.0.0-next.26
4+
5+
### Patch Changes
6+
7+
- 6dbb7e8: Start mode's generated request handler now default-exports a Fetchable
8+
`{ fetch(request) }` object alongside its named `handleRequest` export.
9+
Deployment integrations that follow the web-standard Fetchable convention
10+
can consume the virtual handler or built server entry without a wrapper.
11+
The `fetch` method intentionally ignores provider arguments after the request
12+
instead of forwarding them as Solid handler options.
13+
14+
The normal `ssr` environment now exposes that handler as its `index` service
15+
entry. Provider Vite plugins can adopt the same environment for development
16+
and production without `start.external`, a custom source entry, or explicit
17+
Rollup input. Standalone builds continue to emit `dist/server/server.js`.
18+
19+
- 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.
20+
321
## 3.0.0-next.25
422

523
### Patch Changes

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "vite-plugin-solid",
3-
"version": "3.0.0-next.25",
3+
"version": "3.0.0-next.26",
44
"description": "solid-js integration plugin for vite 6/7/8",
55
"type": "module",
66
"files": [

0 commit comments

Comments
 (0)