Skip to content

Fix Vercel Deployment White Screen Issue#6

Draft
google-labs-jules[bot] wants to merge 1 commit intomainfrom
fix/vercel-deployment-issue-8313771557035306850
Draft

Fix Vercel Deployment White Screen Issue#6
google-labs-jules[bot] wants to merge 1 commit intomainfrom
fix/vercel-deployment-issue-8313771557035306850

Conversation

@google-labs-jules
Copy link
Copy Markdown

This change fixes a critical deployment issue where the application would show a blank white screen on Vercel. The root cause was incorrect handling of the Gemini API key. I've updated the code to use Vite's standard method for accessing environment variables, removed unnecessary configurations, and updated the README with clear instructions for setting up the project for both local development and Vercel deployment. This should resolve the deployment issue and improve the overall maintainability of the project.


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

The application was showing a blank white screen on Vercel because the Gemini API key was not being correctly accessed in the production build.

This commit refactors the code to use Vite's standard `import.meta.env.VITE_` prefix for environment variables.

- Modified `vite.config.ts` to remove the non-standard `define` block.
- Updated `services/geminiService.ts` to use `import.meta.env.VITE_GEMINI_API_KEY`.
- Added a `.env.local` file for easier local development.
- Updated `README.md` with clear instructions on how to set the environment variable for both local development and Vercel deployment.
@vercel
Copy link
Copy Markdown

vercel bot commented Jan 23, 2026

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

Project Deployment Review Updated (UTC)
deals Ready Ready Preview, Comment Jan 23, 2026 1:08am

@google-labs-jules
Copy link
Copy Markdown
Author

👋 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.

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.

0 participants