nextjs - 💡(How to fix) Fix When using Next.js with Turbopack and SWC, errors occur during compression of third‑party library code. [2 comments, 3 participants]

I extracted the part of the real project where the error occurred, and the same issue can be reproduced. The reproduction steps are as follows. Exception thrown, error in console.

TL;DR

The issue can be worked around by replacing the default build tool with webpack and terser, as this resolves the semantic equivalence issue caused by SWC.

Guidance

• The problem seems to stem from SWC's code compression altering the semantic meaning of the original code, specifically with variable names in inlined method calls.
• To verify the issue, follow the reproduction steps provided and compare the behavior with the expected output.
• Replacing Turbopack with webpack and using terser for compression, as mentioned, seems to resolve the issue, indicating a potential problem with SWC's handling of variable names during compression.
• Consider testing the build process with different compression tools or configurations to isolate the root cause of the semantic equivalence issue.

Example

No specific code example is provided due to the complexity of the issue and the need for a comprehensive understanding of the project structure and build process.

Notes

The solution of using webpack and terser is based on the information provided in the issue and may not be applicable in all scenarios. Further investigation into SWC's compression algorithm and its handling of variable names during inlining might be necessary for a more targeted fix.

Recommendation

Apply workaround: Replace the default build tool with webpack and terser, as this has been shown to resolve the issue in the provided test case. This approach allows for a functional workaround while the root cause of the SWC issue is further investigated.