Skip to content

Fix: Resolve Vercel White Screen by Correcting Environment Variable Handling#11

Open
orbiscode-ops wants to merge 1 commit intomainfrom
fix/vercel-white-screen-env-vars-18284001224368641293
Open

Fix: Resolve Vercel White Screen by Correcting Environment Variable Handling#11
orbiscode-ops wants to merge 1 commit intomainfrom
fix/vercel-white-screen-env-vars-18284001224368641293

Conversation

@orbiscode-ops
Copy link
Copy Markdown
Owner

This change addresses a critical issue where the application would show a blank white screen when deployed to Vercel. The root cause was the improper handling of the GEMINI_API_KEY environment variable. The fix aligns the project with Vite's standard practices for environment variables, improves application resilience, and enhances project documentation to prevent future issues.


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

This commit fixes a critical bug that caused a blank white screen to appear after deploying the application to Vercel.

The key changes include:
- Modified vite.config.ts to remove the non-standard define block and rely on Vite's built-in environment variable handling.
- Updated services/geminiService.ts to use import.meta.env.VITE_GEMINI_API_KEY to access the API key, which is the correct method for Vite projects.
- Added a check in geminiService.ts to prevent the application from crashing if the API key is not set, instead logging a warning to the console.
- Created a .env.example file to document the required environment variables.
- Updated the README.md with clear instructions in Arabic on how to set up the environment variables for both local development and Vercel deployment.

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 28, 2026

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

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

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