[backport request] Backport fix of an already-fixed bug of next-swc about next.js HOT 7 OPEN

Yeap I understood. If we want to publish a new version that uses react@18 and recent SWC, we need to revert many commits before publishing and it should be a backport

from next.js.

So you are requesting a backport?

from next.js.

@kdy1 I recently upgrade my company project next from 12 to 14, next12 no this bug. The latest nextjs still has this bug but canary version had fixed it.

I don't know when the next will release the new version to fix it, But now there is no good way to fix it.

from next.js.

I see that issue is related with swc loose setting, any way to config swc not to use losse?

ref: swc-project/swc#8830 (comment)

from next.js.

next-swc does not use loose mode

from next.js.

@kdy1 I see there is a new 14.x update, but this issue is still not fixed

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

from next.js.

https://github.com/vercel/next.js/blob/v14.2.4/Cargo.lock#L5431

It's 0.90.30 and but the fix is 0.90.31

from next.js.