Closed domosedov closed 3 weeks ago
Nice catch, thanks @domosedov 🙏 Seems NextJS canary not working is caused by https://github.com/swc-project/swc/issues/8613. I'll rebuild the plugin with the fixed SWC version now.
I've published a fix in v0.2.2 with the updated SWC library. Can you check if that fixes the issue for you on next@14.1.1-canary.47
?
I've published a fix in v0.2.2 with the updated SWC library. Can you check if that fixes the issue for you on
next@14.1.1-canary.47
?
I've updated the compatibility table
swc_core update
https://github.com/vercel/next.js/pull/61976
Plugin version | Next.js canary version | Status |
---|---|---|
0.2.2 | 14.1.1-canary.54 | 🔴 |
0.2.2-swc1.3.63 | 14.1.1-canary.54 | 🔴 |
0.2.2-swc1.3.106 | 14.1.1-canary.54 | 🔴 |
0.2.2-swc1.4.0 | 14.1.1-canary.54 | 🔴 |
Seems this is a bug of NextJS: https://github.com/vercel/next.js/issues/62081
14.1.2
works as well with "effector-swc-plugin": "0.3.0-swc1.3.63",
I added an "official" compatibility table in NextJS-specific doc. That table is checked with a bunch of integration tests that I run on each release, so it should be very accurate and you should refer to it
If you find an issue with incompatible Next versions, feel free to open a new issue 🙏
My test