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

Help
,
1

Priority: High - Blocking Production Deployment

Issue Type: Build Failure / Next.js Compatibility

-–

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: `https://github.com/cc-deployments/deployment-01/tree/sohey-testing\`

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 most likely related to the ongoing AWS outage

Ongoing incident: elevated errors across multiple services

5

Next.js 15 ENOENT Error Persisting Since October 17 - Not Related to AWS Outage

Hi Vercel Team,

I’m experiencing the exact same ENOENT error mentioned in the related topics: “Next.js 15 ENOENT Error - Local Build Succeeds, Vercel Fails”

Timeline:

  • October 17: ENOENT errors began after fixing React error #31

  • October 17-19: Multiple fix attempts, error persists

  • October 20: AWS outage occurred (separate issue)

  • October 21: ENOENT error still occurring

[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’]

Key Points:

  1. Local builds succeed - this is a Vercel-specific issue

  2. Error persists despite multiple Next.js config changes

  3. Started before AWS outage - not related to infrastructure issues

  4. Affects Next.js 15 static generation - appears to be a platform bug

What I’ve Tried:

  • Dynamic error pages with force-dynamic

  • Disabling static generation completely

  • Webpack optimization changes

  • Multiple Next.js config variations

Request: Can Vercel engineering team investigate this Next.js 15 ENOENT error? It’s affecting multiple users and appears to be a platform-specific issue with static generation.

Status Page: Incident #5m5fd7ljhf26

This is clearly part of the same platform incident affecting multiple services. The ENOENT error is a Vercel build system issue, not a code issue.

6

Closed as duplicate of