fix(desktop): ensure NODE_ENV is set in t3-env runtimeEnv
Merged
SA
1y ago+5+5+0123456789-1-1-0123456789
Summary
- Fix t3-env not receiving the build-time NODE_ENV value
- Explicitly set
NODE_ENV: process.env.NODE_ENVin runtimeEnv so Vite's define can replace it
Root cause
Previous fix added Vite define for process.env.NODE_ENV, but t3-env uses runtimeEnv: process.env which passes the entire object. The spread doesn't trigger Vite's replacement - only direct property access does.
🤖 Generated with Claude Code
Summary by CodeRabbit
- Chores
- Refined environment variable configuration in desktop app builds to ensure consistent behavior across packaged releases.
✏️ Tip: You can customize this high-level summary in your review settings.