Skip to content

Fix Vercel White Screen by Correctly Accessing Environment Variables#10

Open
orbiscode-ops wants to merge 1 commit intomainfrom
fix/vercel-white-screen-13031513397253770569
Open

Fix Vercel White Screen by Correctly Accessing Environment Variables#10
orbiscode-ops wants to merge 1 commit intomainfrom
fix/vercel-white-screen-13031513397253770569

Conversation

@orbiscode-ops
Copy link
Copy Markdown
Owner

This change fixes the white screen issue on Vercel by correctly accessing the Gemini API key using Vite's import.meta.env and the VITE_ prefix. It also improves the developer experience by adding a .env.local file and updating the README.md with clear instructions for Vercel deployment.


PR created automatically by Jules for task 13031513397253770569 started by @orbiscode-ops

- Modified `services/geminiService.ts` to use `import.meta.env.VITE_GEMINI_API_KEY` instead of `process.env.API_KEY` to correctly access the environment variable in a Vite project.
- Created a `.env.local` file with a dummy API key to prevent crashes during local development.
- Updated `README.md` with clear instructions on how to set the `VITE_GEMINI_API_KEY` for both local development and Vercel deployment.

This fixes the white screen issue on Vercel caused by the app failing to initialize the Gemini API client due to a missing API key.

Co-authored-by: orbiscode-ops <233809675+orbiscode-ops@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@vercel
Copy link
Copy Markdown

vercel bot commented Jan 27, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
deals Ready Ready Preview, Comment Jan 27, 2026 0:37am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant