Always log from get-page-static as dev-turbo has log bug

Author: devjiwonchoi

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

@@ -768,8 +768,7 @@ export async function getPagesPageStaticInfo({
 
   let resolvedRuntime = config.runtime ?? config.config?.runtime
 
-  // Turbopack will handle error during compilation with better code frame.
-  if (!process.env.TURBOPACK && isProxyFile(page) && resolvedRuntime) {
+  if (isProxyFile(page) && resolvedRuntime) {
     const relativePath = relative(process.cwd(), pageFilePath)
     const resolvedPath = relativePath.startsWith('.')
       ? relativePath

test/e2e/app-dir/proxy-runtime/proxy-runtime.test.ts

@@ -24,11 +24,9 @@ describe('proxy-missing-export', () => {
       cliOutput = (await next.build()).cliOutput
     }
 
-    if (process.env.IS_TURBOPACK_TEST) {
-      if (isNextDev) {
-        // TODO: Investigate why in dev-turbo, the error is shown in the browser console, not CLI output.
-      } else {
-        expect(stripAnsi(cliOutput)).toContain(`proxy.ts:3:14
+    // TODO: Investigate why in dev-turbo, the error is shown in the browser console, not CLI output.
+    if (process.env.IS_TURBOPACK_TEST && !isNextDev) {
+      expect(stripAnsi(cliOutput)).toContain(`proxy.ts:3:14
 Next.js can't recognize the exported \`config\` field in route. Proxy does not support Edge runtime.
   1 | export default function () {}
   2 |
@@ -37,7 +35,6 @@ Next.js can't recognize the exported \`config\` field in route. Proxy does not s
   4 |
 
 The exported configuration object in a source file needs to have a very specific format from which some properties can be statically parsed at compiled-time.`)
-      }
     } else {
       expect(cliOutput).toContain(
         `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`