nextjs - 💡(How to fix) Fix mismatched turbopack source maps [2 comments, 3 participants]

TL;DR

Enabling webpack with next build --webpack may serve as a temporary workaround to ensure source maps match js files.

Guidance

• The issue seems to be related to Turbopack in Next.js version 16, as enabling webpack resolves the mismatch between source maps and js files.
• To verify the issue, build the app and compare the source maps in the /.next/static directory with the expected output.
• Try using the --webpack flag with next build to see if it produces the expected behavior, as it has worked for the reporter.
• Investigate if there are any open issues or discussions related to Turbopack and source map generation in Next.js version 16.

Example

No specific code snippet is provided as the issue seems to be related to the build process and configuration rather than a specific code block.

Notes

The provided information suggests that this issue is specific to Next.js version 16 and Turbopack. The workaround using --webpack flag may not be a permanent solution and might have performance implications.

Recommendation

Apply workaround: Use next build --webpack as a temporary solution until the issue is resolved in a future version of Next.js, as it currently ensures source maps match js files.