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

package/dist/types/src/http.d.ts

@@ -4,7 +4,14 @@ import type { IncomingMessage, ServerResponse } from 'node:http';
  * different URL than the one node saw — the dev middlewares use it to
  * restore the configured Vite `base` that the dev/preview base middleware
  * stripped, so the handler always sees production-shaped URLs.
+ *
+ * Handles plain HTTP/1 *and* the HTTP/2 compat API: Vite's dev server uses
+ * `http2.createSecureServer({ allowHTTP1: true })` whenever `server.https`
+ * is set without a proxy, so under https the middlewares receive
+ * `Http2ServerRequest`s. The h2/protocol/abort techniques here are
+ * reimplemented from srvx's Node adapter (github.com/h3js/srvx,
+ * src/adapters/_node) — reference, not copied code.
  */
-export declare function webRequestFromNode(req: IncomingMessage, urlPath?: string): Request;
+export declare function webRequestFromNode(req: IncomingMessage, urlPath?: string, res?: ServerResponse): Request;
 export declare function sendWebResponse(res: ServerResponse, response: Response): Promise<void>;
 export declare function joinBase(base: string, pathname: string): string;

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.30",
   "description": "solid-js integration plugin for vite 6/7/8",
   "type": "module",
   "files": [
@@ -50,7 +50,7 @@
   "dependencies": {
     "@ampproject/remapping": "^2.3.0",
     "@babel/core": "^7.23.3",
-    "@dom-expressions/compiler": "0.50.0-next.40",
+    "@dom-expressions/compiler": "^0.50.0-next.43",
     "@types/babel__core": "^7.20.4",
     "babel-preset-solid": "^2.0.0-rc.0",
     "merge-anything": "^5.1.7",

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>;
     },