clay / claycli / 26614528197

87%

master: 87%

Build Type

Pull #252

github

Committed by jjpaulino

Commit Message

🍕 Match Browserify env handling in Vite: inline build vars + runtime fallback

buildClientEnvDefines now reproduces the legacy dotenv-webpack
({ path: './.env', systemvars: true }) behaviour and adds a runtime safety
net so the Vite pipeline stops regressing where the build env is bare:

- Layer 1 (Browserify parity): overlay ./.env with the build process env and
  inline every NON-EMPTY process.env.<VAR> as a string literal — exactly what
  the old pack pipeline shipped (a local container build started with env_file
  bakes the real values in).
- Layer 2 (runtime catch-all): define process.env -> window.process.env so any
  var the build can't see (the bare Docker image build) resolves to the object
  .clay/_env-init.js hydrates from window.kiln.preloadData._envVars instead of a
  pVt={} stub.

Fixes the Vite-only image/product picker break: the prior build-time inline
baked "" for client vars (the Docker build has no PYXIS_HOST/AGORA_HOST), and
master's `window.process.env.X = process.env.X` then clobbered the hydrated
value with "". Empty/absent vars now fall through to the runtime read, turning
that line into a harmless self-assign. process.env.NODE_ENV stays a literal so
guards still tree-shake.

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

Pull Request Pull Request #252: 🍕 Add Kiln plugin init diagnostics for Vite

Coverage Stats

766 of 951 branches covered (80.55%)

Branch coverage included in aggregate %.

54 of 59 new or added lines in 2 files covered. (91.53%)

57 existing lines in 1 file now uncovered.

1634 of 1809 relevant lines covered (90.33%)

14.9 hits per line