Remove "Restart the dev server if the error persists."

Author: devjiwonchoi

crates/next-core/src/middleware.rs

@@ -201,8 +201,7 @@ impl Issue for MiddlewareMissingExportIssue {
              - There's a syntax error preventing the export from being recognized.\n\n\
              To fix it:\n\
              - Check your \"{}\" file.\n\
-             - Ensure it has either a default or \"{}\" function export.\n\
-             - Restart the dev server if the error persists.\n\n\
+             - Ensure it has either a default or \"{}\" function export.\n\n\
              Learn more: https://nextjs.org/docs/messages/middleware-to-proxy",
             type_description,
             migration_bullet,

packages/next/errors.json

@@ -900,5 +900,7 @@
   "899": "Both \"%s\" and \"%s\" files are detected. Please use \"%s\" instead. Learn more: https://nextjs.org/docs/messages/middleware-to-proxy",
   "900": "Both %s file \"./%s\" and %s file \"./%s\" are detected. Please use \"./%s\" only. Learn more: https://nextjs.org/docs/messages/middleware-to-proxy",
   "901": "The file \"%s\" must export a function, either as a default export or as a named \"%s\" export.\\nThis function is what Next.js runs for every request handled by this %s.\\n\\nWhy this happens:\\n- The file exists but doesn't export a function.\\n- The export is not a function (e.g., an object or constant).\\n- There's a syntax error preventing the export from being recognized.\\n\\nTo fix it:\\n- Check your \"%s\" file.\\n- Ensure it has either a default or \"%s\" function export.\\n- Restart the dev server if the error persists.\\n\\nLearn more: https://nextjs.org/docs/messages/middleware-to-proxy",
-  "902": "The file \"%s\" must export a function, either as a default export or as a named \"%s\" export.\\nThis function is what Next.js runs for every request handled by this %s.\\n\\nWhy this happens:\\n%s- The file exists but doesn't export a function.\\n- The export is not a function (e.g., an object or constant).\\n- There's a syntax error preventing the export from being recognized.\\n\\nTo fix it:\\n- Check your \"%s\" file.\\n- Ensure it has either a default or \"%s\" function export.\\n- Restart the dev server if the error persists.\\n\\nLearn more: https://nextjs.org/docs/messages/middleware-to-proxy"
+  "902": "The file \"%s\" must export a function, either as a default export or as a named \"%s\" export.\\nThis function is what Next.js runs for every request handled by this %s.\\n\\nWhy this happens:\\n%s- The file exists but doesn't export a function.\\n- The export is not a function (e.g., an object or constant).\\n- There's a syntax error preventing the export from being recognized.\\n\\nTo fix it:\\n- Check your \"%s\" file.\\n- Ensure it has either a default or \"%s\" function export.\\n- Restart the dev server if the error persists.\\n\\nLearn more: https://nextjs.org/docs/messages/middleware-to-proxy",
+  "903": "The file \"%s\" must export a function, either as a default export or as a named \"%s\" export.\\nThis function is what Next.js runs for every request handled by this %s.\\n\\nWhy this happens:\\n- The file exists but doesn't export a function.\\n- The export is not a function (e.g., an object or constant).\\n- There's a syntax error preventing the export from being recognized.\\n\\nTo fix it:\\n- Check your \"%s\" file.\\n- Ensure it has either a default or \"%s\" function export.\\n\\nLearn more: https://nextjs.org/docs/messages/middleware-to-proxy",
+  "904": "The file \"%s\" must export a function, either as a default export or as a named \"%s\" export.\\nThis function is what Next.js runs for every request handled by this %s.\\n\\nWhy this happens:\\n%s- The file exists but doesn't export a function.\\n- The export is not a function (e.g., an object or constant).\\n- There's a syntax error preventing the export from being recognized.\\n\\nTo fix it:\\n- Check your \"%s\" file.\\n- Ensure it has either a default or \"%s\" function export.\\n\\nLearn more: https://nextjs.org/docs/messages/middleware-to-proxy"
 }

packages/next/src/build/analysis/get-page-static-info.ts

@@ -411,8 +411,7 @@ function validateMiddlewareProxyExports({
         `- There's a syntax error preventing the export from being recognized.\n\n` +
         `To fix it:\n` +
         `- Check your "${relativeFilePath}" file.\n` +
-        `- Ensure it has either a default or "${fileName}" function export.\n` +
-        `- Restart the dev server if the error persists.\n\n` +
+        `- Ensure it has either a default or "${fileName}" function export.\n\n` +
         `Learn more: https://nextjs.org/docs/messages/middleware-to-proxy`
     )
   }

packages/next/src/build/templates/middleware.ts

@@ -37,8 +37,7 @@ if (typeof handler !== 'function') {
       `- There's a syntax error preventing the export from being recognized.\n\n` +
       `To fix it:\n` +
       `- Check your "${resolvedRelativeFilePath}" file.\n` +
-      `- Ensure it has either a default or "${fileName}" function export.\n` +
-      `- Restart the dev server if the error persists.\n\n` +
+      `- Ensure it has either a default or "${fileName}" function export.\n\n` +
       `Learn more: https://nextjs.org/docs/messages/middleware-to-proxy`
   )
 }

test/e2e/app-dir/proxy-missing-export/proxy-missing-export.test.ts

@@ -14,7 +14,6 @@ Why this happens:
 To fix it:
 - Check your "./proxy.ts" file.
 - Ensure it has either a default or "proxy" function export.
-- Restart the dev server if the error persists.
 
 Learn more: https://nextjs.org/docs/messages/middleware-to-proxy`