Let me check if the dev server started properly and look for any errors:
The Vite dev server is running successfully on port 3000. I added host: true and allowedHosts: "all" to the Vite config, which allows requests from any host including the v0 preview iframe. The server is now accessible and the preview should be visible with your luxury lehenga landing page.
An error occurred during deployment. Please fix:
Running build in Washington, D.C., USA (East) – iad1
Build machine configuration: 4 cores, 8 GB
Retrieving list of deployment files...
Previous build caches not available.
Downloading 99 deployment files...
...
at async CAC.<anonymous> (file:///vercel/path0/node_modules/.pnpm/vite@8.0.10_@types+node@22.19.11_jiti@2.6.1/node_modules/vite/dist/node/cli.js:778:3) {
errors: [Getter/Setter]
}
ELIFECYCLE Command failed with exit code 1.
Error: Command "pnpm run build" exited with 1
The issue is that the components are in src/components/ but the @/ alias in Vite points to the root, not to src/. Let me check the vite config and fix the path aliases:
I see the issue. The components are in src/components/ but the imports use @/components/ which resolves to the root components/ folder (which has the shadcn UI components). Let me read the Home.tsx and fix the imports to use the correct path:
Now let me also check and fix the imports in the src/components files that may reference @/components/ui/*:
I see the issue. The App.tsx uses @/src/pages/ paths which are incorrect. Let me fix all the imports:
Now let me run the build again to verify it works:
The build is now successful. I fixed the import paths in three files:
src/pages/Home.tsx - Changed @/components/ imports to relative ../components/ paths for the landing page componentssrc/App.tsx - Changed @/components/ui/ to ../components/ui/ and @/src/pages/ to ./pages/ for correct relative resolutionsrc/pages/not-found.tsx - Changed @/components/ui/button to ../../components/ui/buttonThe issue was that the @/ alias in Vite points to the project root, but the imports were assuming @/ pointed to the src/ directory. Using relative paths ensures all modules resolve correctly during both development and production builds.
An error occurred during deployment. Please fix:
Running build in Washington, D.C., USA (East) – iad1
Build machine configuration: 4 cores, 8 GB
Retrieving list of deployment files...
Previous build caches not available.
Downloading 99 deployment files...
...
at async CAC.<anonymous> (file:///vercel/path0/node_modules/.pnpm/vite@8.0.10_@types+node@22.19.11_jiti@2.6.1/node_modules/vite/dist/node/cli.js:778:3) {
errors: [Getter/Setter]
}
ELIFECYCLE Command failed with exit code 1.
Error: Command "pnpm run build" exited with 1