Closed MatteoGauthier closed 1 year ago
Hi @MatteoGauthier! This looks like an issue with next-superjson-plugin
, so I transferred the issue there. @orionmiz could you take a look?
The plugin is broken in the new version of Next.Js v13 (which is expected to happen). Not sure if you are getting this error on the new version tho, but this is happening to me on the new version.
The plugin is broken in the new version of Next.Js v13 (which is expected to happen). Not sure if you are getting this error on the new version tho, but this is happening to me on the new version.
It might have been, but I'm on 12.3.2
@MatteoGauthier Hi, maybe it seems like a version issue of next.
next info
above indicates v12.3.1 which is not compatible with the plugin.
Would you mind using the plugin with next@canary?
Hey @orionmiz, I just updated to 12.3.2-canary.43
and it works ! Thanks for your help, a mention of the issue in the readme could save time for some people like me 😁
@MatteoGauthier Actually, It requires an issue template form including Next.js canary verification to submit a bug report for this plugin. Since this issue was transferred from other repository, you skipped that issue template form. But I updated README once again by your advice to avoid similar situation to be happened.
@Skn0tt Hey Simon, How about suggesting users to create a new issue rather than transferring the issue?
@tavindev Next.js 13 uses the older version of @swc/core
as a dependency.
I'll ask SWC team to update it, so please wait for the patch to be applied.
@orionmiz Great, thanks!
@tavindev
Unfortunately, swcPlugins
option is not supported for Next.js 13 in--turbo
dev mode currently.
However, if the same error above is occuring, I could guess that the build cache is used.
Have you tried to remove .next
directory?
@tavindev Unfortunately,
swcPlugins
option is not supported for Next.js 13 in--turbo
dev mode currently. However, if the same error above is occuring, I could guess that the build cache is used. Have you tried to remove.next
directory?
Working now on the latest version 0.4.8
. Thanks!
Here is my full stacktrace
And my
next info