nextjs - 💡(How to fix) Fix Next 16.0: Route segment config is not allowed in Proxy file [2 comments, 2 participants]

Build error occurred Error: Route segment config is not allowed in Proxy file at "./proxy.ts". Proxy always runs on Node.js runtime. Learn more: https://nextjs.org/docs/messages/middleware-to-proxy

TL;DR

• The build error can likely be resolved by updating the proxy.ts file to be compatible with the Edge Runtime, as indicated by the Next.js documentation.

Guidance

• Review the Middleware to Proxy migration guide to understand the requirements for Proxy files in Next.js.
• Verify that the proxy.ts file does not contain any route segment configurations, which are not allowed in Proxy files.
• Check the Next.js version and ensure that it is up-to-date, as the issue might be related to a version mismatch.
• Consider testing the build process with a minimal proxy.ts file to isolate the issue and identify any specific configurations that might be causing the error.

Example

No specific code example can be provided without modifying the original code, but reviewing the proxy.ts file for any route segment configurations and ensuring compatibility with the Edge Runtime is a good starting point.

Notes

The discrepancy between the error message and the documentation suggests that there might be a version-specific issue or a misunderstanding of the Proxy configuration requirements. Further investigation into the Next.js version and the proxy.ts file configuration is necessary to resolve the issue.

Recommendation

• Apply workaround: Update the proxy.ts file to be compatible with the Edge Runtime, and review the Next.js documentation to ensure that the configuration meets the requirements for Proxy files. This approach is recommended because it allows for a targeted fix without requiring a version upgrade, which might not be feasible in all environments.