$ pnpm build

@ build /project/workspace next build

Attention: Next.js now collects completely anonymous telemetry regarding usage. This information is used to shape Next.js' roadmap and prioritize features. You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: https://nextjs.org/telemetry

▲ Next.js 16.0.2-canary.27 (Turbopack)

Creating an optimized production build ... ✓ Compiled successfully in 2.7s ✓ Finished TypeScript in 2.3s
Collecting page data using 3 workers ..Error: Could not parse module '[project]/node_modules/.pnpm/next@[email protected]_react@19.2.0/node_modules/next/dist/server/route-modules/app-route/vendored/contexts/app-router-context.js', file not found at instantiateModule (.next/server/chunks/[turbopack]_runtime.js:715:9) at getOrInstantiateModuleFromParent (.next/server/chunks/[turbopack]_runtime.js:738:12) at Context.commonJsRequire [as r] (.next/server/chunks/[turbopack]_runtime.js:249:12) at instantiateModule (.next/server/chunks/[turbopack]_runtime.js:715:9) at getOrInstantiateModuleFromParent (.next/server/chunks/[turbopack]_runtime.js:738:12) at Context.commonJsRequire [as r] (.next/server/chunks/[turbopack]_runtime.js:249:12) at instantiateModule (.next/server/chunks/[turbopack]_runtime.js:715:9) { code: 'MODULE_UNPARSABLE' }

Build error occurred Error: Failed to collect page data for /a at ignore-listed frames { type: 'Error' }  ELIFECYCLE  Command failed with exit code 1.

TL;DR

The issue can be resolved by using a try-catch block to handle the notFound() function from next/navigation in the Route Handler GET function body, allowing Turbopack to build without errors.

Guidance

• Verify that the notFound() function is being used correctly in the Route Handler GET function body.
• Try using a try-catch block to handle any potential errors thrown by the notFound() function.
• Check the Next.js documentation for any known issues or limitations with using notFound() with Turbopack.
• Compare the build configurations for Turbopack and webpack to identify any differences that may be contributing to the issue.

Example

import { notFound } from 'next/navigation';

export async function GET() {
  try {
    // code that may throw an error
    return notFound();
  } catch (error) {
    // handle the error
    console.error(error);
    return new Response('Error occurred', { status: 500 });
  }
}

Notes

The issue appears to be specific to Turbopack and may be related to how it handles errors thrown by the notFound() function. The try-catch block example provided is a potential workaround, but the root cause of the issue may require further investigation.

Recommendation

Apply workaround: Using a try-catch block to handle the notFound() function can allow Turbopack to build without errors, providing a temporary solution until the root cause of the issue is identified and addressed.