@solidjs/vite-plugin 3.0.0-next.28 → 3.0.0-next.29

package/dist/types/src/ssr/index.d.ts

@@ -119,6 +119,11 @@ export interface StartOptions {
      * only), so platform-injected vars work and secrets rotate without a
      * rebuild — no secret exists in any dist artifact. Build-time server
      * failures are a deferred-to-boot warning; dev failures stay hard.
+     * Boot validation is synchronous — the generated module carries no
+     * top-level await, so server bundles work on non-esnext targets
+     * (Nitro's node-server preset needs no `esnext` override) — which is
+     * why async validators are rejected for `server` keys at config time
+     * (`client` keys may stay async: they are awaited at build time).
      *
      * `true` requires the conventional file (error when missing); a string
      * is an explicit schema path; `false` disables even the probing.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@solidjs/vite-plugin",
-  "version": "3.0.0-next.28",
+  "version": "3.0.0-next.29",
   "description": "solid-js integration plugin for vite 6/7/8",
   "type": "module",
   "files": [

package/virtual-solid-manifest.d.ts

@@ -17,7 +17,17 @@ declare module "virtual:solid-server-function-handler" {
   export const endpoint: string;
   export function handleServerFunctionRequest(
     request: Request,
-    options?: Record<string, unknown>,
+    options?: {
+      /**
+       * Extra fields spread into the request event at creation — the public
+       * wrapper→event extension seam, same as the SSR handler's
+       * `handleRequest`. Conventionally `nativeEvent` carries the platform's
+       * raw request object (the plugin's dev middleware and a Node server
+       * entry pass the Node `IncomingMessage`); read it back with
+       * `getRequestEvent()`.
+       */
+      event?: Record<string, unknown>;
+    } & Record<string, unknown>,
   ): Promise<Response>;
 }
 
@@ -39,6 +49,16 @@ declare module "virtual:solid-ssr-handler" {
       context?: Record<string, unknown>;
       /** Status/headers for the HTML response. */
       responseInit?: ResponseInit;
+      /**
+       * Extra fields spread into the request event at creation — the public
+       * wrapper→event extension seam. Conventionally `nativeEvent` carries
+       * the platform's raw request object; the plugin's dev/preview
+       * middlewares (and, by convention, a custom Node server entry) pass
+       * the Node `IncomingMessage` here, so `getRequestEvent().nativeEvent`
+       * answers the same on every surface. Read it back anywhere inside the
+       * request scope with `getRequestEvent()`.
+       */
+      event?: Record<string, unknown>;
       /** Options forwarded to the server-function handler for endpoint requests. */
       serverFunctions?: Record<string, unknown>;
     },