Migrating to Vite + React

Introduction

When Google introduced Firebase Studio for "vibe coding", Next.js was established as the primary framework due to its seamless integration of front-end and back-end logic.

• While this unified design is compelling, it carries a hidden cost: a heavy reliance on server-side post-processing and Cloud Functions to serve even basic assets.
• For many developers, this architecture introduces unnecessary complexity and overhead for projects that don't require a persistent server.

The Migration

While exploring alternative configurations, I discovered that Google Antigravity suggests app setups tailored to specific functional needs.

• The PWAs (Progressive Web Apps) I designed for personal use - an offline-first budget tracker, a QR code suite, and a "Sheet-to-Database" utility - are primarily static applications.
• They rely almost entirely on local client-side execution ('use client') and do not require Server-Side Rendering (SSR).

Antigravity recommended a Vite + React setup over Next.js.

• This approach is significantly more lightweight and reduces the attack surface; by removing the server-side component, vulnerabilities like SSR injection, Server-Side Request Forgery (SSRF), and Node.js runtime exploits are eliminated entirely.
• Transitioning to Vite allowed me to move from Firebase App Hosting to the simpler Firebase Hosting, which is more cost-effective and avoids the mandatory Blaze Plan subscription.

Driven by further cost-consciousness, I eventually migrated the apps to Cloudflare Pages for maximum deployment efficiency.

Technical Implementation

Despite my limited coding background, the migration was relatively smooth.

• The core workflow remained intuitive: whenever I encountered a hurdle, I fed the error logs into the natural language prompt, allowing Google Antigravity to troubleshoot the issues.

I gained hands-on experience with vite-plugin-pwa for offline capabilities and wrangler for Cloudflare Pages deployments.

Moving away from the fully integrated environment of Firebase Studio helped me better appreciate the standard development lifecycle:

• npm run dev: Essential for real-time local testing and rapid iteration.
• npm run build: A critical step to ensure the production bundle is free of conflicts before deployment.
• Dependency Management: I learned that migrating away from a heavy framework often requires downgrading specific dependencies or rewriting logic to remove proprietary framework hooks.

Summary

While Firebase Studio offers impressive cloud computing power, its rigid reliance on Next.js can lead to unnecessary server costs.

• Furthermore, its tendency to push complex Genkit AI integrations can be overkill for simple tools.

The flexibility and precision offered by Google Antigravity proved more effective and cost-conscious for my requirements, making it the superior choice for lightweight, client-focused applications.