@alexkroman1/aai-cli 1.9.2 → 1.11.0

package/dist/_vite-env-CmXG4ZAu.mjs

@@ -1,31 +0,0 @@
-#!/usr/bin/env node
-//#region _vite-env.ts
-/**
-* Run a Vite build without letting it mutate the calling process's env.
-*
-* Vite's `build()` sets `process.env.NODE_ENV = "production"` when NODE_ENV is
-* unset — a global, permanent side effect on whatever process invoked it. That
-* is fine for a one-shot `aai build`, but both long-lived callers are broken by
-* it:
-*
-* - `aai dev` rebuilds on every file change, so the first rebuild would flip
-*   the dev server into production mode.
-* - The platform studio builds inside the server process, where flipping
-*   NODE_ENV makes the sandbox demand gVisor ("gVisor (runsc) is required in
-*   production but not found on PATH") and refuse every subsequent deploy on a
-*   dev machine.
-*
-* Snapshot and restore rather than pinning a value: callers that legitimately
-* run with NODE_ENV=production must keep it.
-*/
-async function withPreservedNodeEnv(fn) {
-	const saved = process.env.NODE_ENV;
-	try {
-		return await fn();
-	} finally {
-		if (saved === void 0) delete process.env.NODE_ENV;
-		else process.env.NODE_ENV = saved;
-	}
-}
-//#endregion
-export { withPreservedNodeEnv as t };

package/dist/types.mjs

@@ -1,2 +0,0 @@
-#!/usr/bin/env node
-export {};