nextjs - 💡(How to fix) Fix Proxy misleading outdated errors about Edge runtime when custom page extension is used [1 participants]

I get the following error: Ecmascript file had an error I shouldn’t receive this error, because proxy don’t run on Edge Runtime according to the documentation: Runtime, Error Handling, Middleware, Not sure

TL;DR

• The issue can be resolved by modifying the proxy.universal.ts file to avoid using Node.js APIs not supported in the Edge Runtime or by adjusting the next.config.js to exclude universal.ts from the Edge Runtime.

Guidance

• Review the proxy.universal.ts file and identify any Node.js APIs that are not supported in the Edge Runtime, such as process.versions.
• Consider using a different approach that does not rely on Node.js APIs, or use a runtime check to ensure the code is running in a supported environment.
• Adjust the next.config.js file to exclude universal.ts from being executed in the Edge Runtime, potentially by removing it from the pageExtensions array or using a custom configuration to handle this file type differently.
• Verify that the custom pageExtensions configuration is the root cause of the issue by testing with the default configuration.

Example

// next.config.js
import type { NextConfig } from "next";

const nextConfig: NextConfig = {
  // Remove or modify the custom pageExtensions to avoid the issue
  pageExtensions: ['tsx', 'ts']
};

export default nextConfig;

Notes

• The issue is specific to the next dev and next build stages, and is reproducible only when a custom pageExtensions is configured and used.
• The universal.ts file is likely intended to run in a Node.js environment, but is being executed in the Edge Runtime due to the custom configuration.

Recommendation

• Apply workaround: Modify the next.config.js file to exclude universal.ts from the Edge Runtime or adjust the proxy.universal.ts file to avoid using unsupported Node.js APIs. This approach allows for a quick resolution without requiring significant changes to the codebase.