Fix Blank Screen on Vercel by Using Correct Environment Variable Syntax#2
Fix Blank Screen on Vercel by Using Correct Environment Variable Syntax#2google-labs-jules[bot] wants to merge 1 commit intomainfrom
Conversation
Updated services/geminiService.ts to use import.meta.env.VITE_API_KEY instead of process.env.API_KEY. This resolves the "white screen" issue on Vercel deployments caused by process.env being undefined in the browser.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This change fixes the blank white screen issue on Vercel by correcting how the Google Gemini API key is accessed. It replaces the Node.js-specific
process.env.API_KEYwith Vite's client-sideimport.meta.env.VITE_API_KEY. For this fix to work, you must add aVITE_API_KEYenvironment variable to your Vercel project settings.PR created automatically by Jules for task 13111806713070375795 started by @orbiscode-ops