Subject: Next.js 15 ENOENT Error - Local Build Succeeds, Vercel Fails

Help
,
1

Priority: High - Blocking Production Deployment

Issue Type: Build Failure / Next.js Compatibility

-–

TIMELINE:

- Issue Started: October 17, 2025

- First Reported: October 20, 2025 (ticket still open)

- Duration: 5+ days of blocked deployments

- Current Status: Still unresolved, affecting production

PROBLEM SUMMARY:

Our Next.js 15 application builds successfully locally but fails on Vercel with an ENOENT file system error during static generation.

ERROR DETAILS:

[Error: ENOENT: no such file or directory, rename ‘/vercel/path0/coinbase/fc-minikit/.next/export/500.html’ → ‘/vercel/path0/coinbase/fc-minikit/.next/server/pages/500.html’]

EVIDENCE - LOCAL vs VERCEL:

:white_check_mark: LOCAL BUILD (SUCCESS):

- Next.js 15.5.3 + React 19.2.0

- Build completes successfully in 10.9s

- 48 static pages generated without errors

- All TypeScript strict mode errors resolved

- No ENOENT error

:cross_mark: VERCEL BUILD (FAILURE):

- Same codebase, same dependencies

- ENOENT error during static generation

- Build progresses much further than before (compilation succeeds)

- Fails at static page generation phase

TECHNICAL SPECIFICATIONS:

- Next.js: 15.5.3

- React: 19.2.0

- Node.js: Latest LTS

- Framework: Next.js App Router

- Repository: Public GitHub repository (available upon request)

TROUBLESHOOTING ATTEMPTED:

1. :white_check_mark: Disabled static generation - `experimental: { staticGenerationRetryCount: 0 }`

2. :white_check_mark: Created custom 500.tsx - Dynamic error handling

3. :white_check_mark: Pre-build scripts - Attempted to create missing files

4. :white_check_mark: Provider configuration - Fixed wallet integration

5. :white_check_mark: TypeScript strict mode - Resolved all compilation errors

RELATED GITHUB ISSUES:

- [vercel/next.js#84283]( [Bug] Next.js 15.5.3 + React 19 RC - Build fails with React error #31 during static generation · Issue #84283 · vercel/next.js · GitHub ) - React error #31 with React 19 RC and Next.js 15

- [vercel/next.js#39952]( Serverless function error with custom 500 page · Issue #39952 · vercel/next.js · GitHub ) - ENOENT error with 500 page

REQUEST:

Since this appears to be a Vercel-specific Next.js 15 compatibility issue, we need:

1. Immediate workaround for Next.js 15 + React 19 deployments

2. Timeline for when this will be resolved

3. Alternative deployment configuration if needed

IMPACT:

Our production application is ready but blocked by this Vercel deployment issue. The local build success confirms our code is correct.

4

This is not a Vercel platform issue

You have successful builds on your main branch and are getting this issue due to code changes in your PR. I suspect it’s the force-dynamic export in your error.tsx that is responsible for this specific error, but you can further debug by removing changes from the PR until you get successful compilations again and checking what went wrong

I will also note that all of your API keys are publicly available in your GIthub and need to be revoked. There are automated scrapers online that check every repo for this, so the odds that they are compromised already is very high