Hm we ran into an interesting regression | Next.js | Page 1

eternal thistle May 14, 2024, 10:10 PM

#

It looks like this only occurs in production builds after upgrading to 14.2.3. If we set swcMinify: false in our next config it fixes it. Downgrading to 14.1.4 also fixes it.

drowsy rivet May 15, 2024, 1:53 AM

#

I haven't seen it yet and I use a lot of lazy-loaded components with ssr: false, we just updated to the latest version so I will keep it in mind and let you know in case I ever see this behavior bighmm

eternal thistle May 15, 2024, 8:41 PM

#

I think it turns out to be due to a regression with the swc compiler and swcMinify: true: https://github.com/vercel/next.js/issues/46887#issuecomment-2111778234

#

I put together a reproduction of the bug we were experiencing: https://github.com/kcrwfrd/next-swc-minify-bug-reproduction

#

It involves another dependency so it's not especially well-isolated.

#Hm we ran into an interesting regression