Skip to content

Conversation

akashraj9828
Copy link
Owner

Restructure repository for Vercel deployment by moving frontend to root and refactoring backend to a serverless API.

The original setup had separate frontend and backend directories, with the frontend using a custom Express server and the backend running a persistent Express server. This PR adapts both to Vercel's serverless model: the frontend is now a static build served directly by Vercel, and the backend Express app is exported as a module in the api/ directory to function as a serverless API. This allows for a single Vercel deployment.


Open Background Agent:
Web · Cursor

Learn more about Background Agents

Copy link

vercel bot commented Jul 22, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
gitstats ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 27, 2025 7:27am

Copy link

vercel bot commented Jul 22, 2025

Deployment failed with the following error:

The `vercel.json` schema validation failed with the following message: should NOT have additional property `engines`

Learn More: https://vercel.com/docs/concepts/projects/project-configuration

…mproved error handling

feat: add start script for backend in package.json and enhance dev scripts
fix: update API base URL logic in config to support Vercel and localhost
chore: update dependencies in yarn.lock for better compatibility
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.

2 participants