How to exclude a third-party package from swcMinify in Next.js 14.2.23?

[PPDEMOone]

Summary

I am using Next.js 14.2.23 and would like to know how to avoid a specific third-party package from the swcMinify process.

When swcMinify is enabled, variables in the same scope within the package are incorrectly overwritten by other variables with the same name, causing runtime errors. However, I still want to keep using swcMinify for the rest of my application.

Is there a way to exclude a particular package from the minification process while enabling swcMinify?

For example：

Before and after Enable swcMinify

Additional information

No response

Example

No response

[quasimodo-tech]

Currently, SWC minification (swcMinify: true) does not have a built-in way to exclude specific third-party packages from minification.

Alternatively you can use Use transpilePackages in next.config.js.
You can transpile the package manually using Next.js’ built-in transpilePackages option.
This ensures the package is compiled separately and may help avoid SWC minification conflicts.
module.exports = {
transpilePackages: ["package-name"],
swcMinify: true,
};

[PPDEMOone]

Thanks, but is not working for me : (

[Jimmydalecleveland]

We've had the same problem with a troublesome package (The various SpreadJS packages like @mescius/spread-sheets-io) and adding it to transpilePackages does not solve the issue either. If I swap in Terser for the minifier, it works correctly, and I've confirmed it's a minification issue by globally setting config.optimization.minimize = false; in the webpack property of the Next.js config, which fixes the issue as well.