[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [v0](/c/v0/59) # V0 project not building on vercel 193 views · 0 likes · 4 posts Hp Heli Uscom (@hp-heli-uscom) · 2024-10-30 I created a UI using v0.dev which has a few .tsx files. Uploaded it to a git project and trying to run it on vercel. If I choose "other" frameworks in settings, the deploy goes through - but when I open the app the files are downloaded to the browser as .dms files. If I choose "Next.js" framework in settings, I get this deployment error [13:06:26.243] Running build in Washington, D.C., USA (East) – iad1 [13:06:26.392] Cloning <hidden> [13:06:26.408] Skipping build cache, deployment was triggered without cache. [13:06:26.851] Cloning completed: 458.076ms [13:06:27.273] Running "vercel build" [13:06:28.967] Vercel CLI 37.13.0 [13:06:29.352] Your application is being built using `next build`. If you need to define a different build step, please create a `vercel-build` script in your `package.json` (e.g. `{ "scripts": { "vercel-build": "npm run prepare && next build" } }`). [13:06:29.357] Installing dependencies... [13:06:30.019] [13:06:30.020] up to date in 484ms [13:06:30.026] Warning: Could not identify Next.js version, ensure it is defined as a project dependency. [13:06:30.031] Error: No Next.js version could be detected in your project. Make sure `"next"` is installed in "dependencies" or "devDependencies" [13:06:30.883] would love some advice. thanks Amy Egan (@amyegan) · 2024-10-30 Hey @hp-heli-uscom. Are you able to share the project or chat here? Hp Heli Uscom (@hp-heli-uscom) · 2024-10-30 thanks. How do I privately share the project? I am able to now build it. I was missing the config files. I thought the vercel platform would add them. I am now typing to see why my css wont load. Amy Egan (@amyegan) · 2024-11-15 I hope you already found a solution. If not, I have a few ideas. - Check your browser's dev tools for errors and other clues about why the styles are missing. There could be a 404 on a CSS file, an error logged in the console, or other clues in the page source. - Append the [special path](https://vercel.com/docs/deployments/build-features#special-paths) `/_src` to your deployment and check the **Source** and **Output** to verify the CSS file exists where you expected it. - Use the [Debugging 404 Errors](https://community.vercel.com/t/debugging-404-errors/437) tips to investigate further.