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 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.