eliminate top-level await from the generated virtual:env/server module — boot validation used to conditionally await each Standard Schema validate() result, putting a TLA in the server env chunk whenever the schema had server keys, and any downstream bundler below esnext (Nitro's node-server preset in real deploys) rejects a TLA chunk, forcing the documented build-target-esnext workaround. Validation is now fully synchronous with identical boot semantics (same process.env read at module init, same per-key report, fail-loud before any importer's body runs, frozen env export) — synchronous init is the only shape that keeps "validated before first use", since user server modules read env.KEY at their own top level. Tradeoff made explicit: async validators are rejected for server keys at config/build time with the fix in the message (boot backstops with the same report when async-ness only surfaces on real values); client keys keep async support (baked at build time, where the plugin awaits). start-env suite: async-server-validator guard fixture + every server chunk must transform under esbuild target es2020 (rejects TLA at parse time — the exact downstream-bundler check). Patch changeset on the 3.0.0-next line. · solidjs/solid-vite-plugin@ca4d221

3m 13s

23s

3m 36s

Navigation Menu