I'm having a strange deployment issue with a Next.js 16 project on Vercel.
The project works perfectly locally:
pnpm buildsucceedspnpm startsucceedslocalhost:3000loads the application normallyapp/page.tsxexists and is the root/route
The Vercel deployment also reports a successful build. The build output shows:
Creating an optimized production build ...✓ Compiled successfully in 6.0sSkipping validation of typesFinished TypeScript config validation in 21ms ...Collecting page data using 1 worker ...Generating static pages using 1 worker (0/3) ...✓ Generating static pages using 1 worker (3/3) in 220msFinalizing page optimization ...
Route (app)┌ ○ /└ ○ /_not-found
○ (Static) prerendered as static content
Build Completed in /vercel/output [35s]Deploying outputs...Deployment completedCreating build cache..However, when I open the Vercel deployment URL, I get: this url => https://teklu-azure.vercel.app/
i get this response 404: NOT_FOUND Code: NOT_FOUND
My project structure is: N-Portfolio/ └── client-v3/ ├── app/ │ ├── page.tsx │ ├── layout.tsx │ └── ... ├── components/
├── public/ ├── package.json ├── next.config.mjs └── ...
I have configured client-v3 as the Vercel Root Directory.
The same application works correctly when built and started locally.
I have also tried a fresh Vercel deployment, but I'm still investigating the issue.
Could anyone help me understand why Vercel is generating the / route successfully during the build but returning a platform-level 404: NOT_FOUND when I actually visit the deployed URL?
Any suggestions on what I should check next would be appreciated.
