Isolate compiler WASI test forcing.

Apply the NAPI WASI override inside Vitest workers so it validates the compiler binding without forcing the test runner's own Rolldown binding.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: ryansolid

.github/workflows/compiler-binaries.yml

@@ -137,7 +137,7 @@ jobs:
 
       - name: Test WASI binary
         working-directory: packages/compiler
-        run: NODE_NO_WARNINGS=1 NAPI_RS_FORCE_WASI=error pnpm exec vitest run --exclude '**/binding-loader.test.js'
+        run: NODE_NO_WARNINGS=1 SOLID_COMPILER_TEST_WASI=1 pnpm exec vitest run --exclude '**/binding-loader.test.js'
 
       # Authenticates via OIDC trusted publishing (id-token: write above) —
       # no npm token. Each platform package must have this repo + workflow

packages/compiler/__tests__/force-wasi.js

@@ -0,0 +1 @@
+process.env.NAPI_RS_FORCE_WASI = "error";

packages/compiler/vite.config.mjs

@@ -8,6 +8,7 @@ export default defineConfig({
     pool: "threads",
     globals: true,
     include: ["__tests__/**/*.test.js"],
-    exclude: ["**/node_modules/**"]
+    exclude: ["**/node_modules/**"],
+    setupFiles: process.env.SOLID_COMPILER_TEST_WASI ? ["./__tests__/force-wasi.js"] : []
   }
 });