nextjs - 💡(How to fix) Fix Proxy.ts file not included on build with webpack - Next 16.01 [2 comments, 3 participants]

Error: ENOENT: no such file or directory, lstat '/vercel/path0/apps/dikaioai/.next/server/proxy.js'

TL;DR

The issue can likely be fixed by updating the build configuration to reference the renamed proxy.ts file instead of the original middleware.ts file.

Guidance

• Verify that the proxy.ts file is correctly referenced in the build configuration and that there are no remaining references to middleware.ts.
• Check the Vercel build settings to ensure that the --webpack flag is correctly configured to handle the renamed file.
• Consider updating the next.config.js file to include a custom webpack configuration that accounts for the renamed proxy.ts file.
• Review the file system and build output to ensure that the proxy.js file is being generated correctly during the build process.

Example

No code example is provided as the issue does not include sufficient code context.

Notes

The solution may depend on the specific build configuration and Vercel settings used in the project. Additional debugging may be required to identify the root cause of the issue.

Recommendation

Apply workaround: Update the build configuration to reference the renamed proxy.ts file, as this is likely to resolve the issue without requiring a version upgrade.