nextjs - 💡(How to fix) Fix infinite rebuild hmr when rename middleware.ts to proxy.ts [1 comments, 2 participants]

TL;DR

Renaming a file in the project triggers an infinite rebuild in the Next.js development server, suggesting a potential issue with file watching or caching.

Guidance

• Verify if the issue persists when using a different file name or location to isolate if the problem is specific to the middleware.ts or proxy.ts name.
• Check for any circular imports or dependencies that could be causing the infinite rebuild.
• Try deleting the .next directory and restarting the development server to ensure it's not a caching issue.
• Investigate if there are any known issues with file watching in Next.js version 16.0.0 or if there's an update available that addresses this problem.

Example

No specific code example is provided as the issue seems related to the development server's behavior rather than a specific code snippet.

Notes

The exact cause of the infinite rebuild is unclear without further information about the project's structure or the contents of middleware.ts. This issue might be specific to the combination of Next.js version, Node version, or the project's configuration.

Recommendation

Apply workaround: Try renaming the file to a different name that doesn't seem to trigger the infinite rebuild, or attempt to update Next.js to a newer version if available, to see if the issue persists. The reason is to avoid potential issues with the current file name or version incompatibilities.