Bumping now that NextJS 15 is out.

Facing this issue with Next 15.

Next changed metadata causing this plugin to no longer work for page router
bump this issue vercel/next.js#72019

You can use this plugin instead as a temporary workaround https://github.com/remorses/next-superjson

This package always uses the same version of @swc/core so the SWC plugins continues to work, even if Next.js upgrades it, the plugin ships his own frozen version of SWC

You can use this plugin instead as a temporary workaround https://github.com/remorses/next-superjson

This package always uses the same version of @swc/core so the SWC plugins continues to work, even if Next.js upgrades it, the plugin ships his own frozen version of SWC

Doesn't work for me. Throws the exact same errors as next-superjson-plugin with "next": "^15.0.1", which is actually 15.0.3 according to yarn.lock.

@Andkoo you have to remove the swc plugins section in your next.config.js

@Andkoo you have to remove the swc plugins section in your next.config.js

That was exactly the issue, figured it out right after posting the comment. It works now, thanks 🙏

@Andkoo you have to remove the swc plugins section in your next.config.js

This.

https://github.com/remorses/next-superjson throws error Couldn't find a 'pages' directory. Please create one under the project root". Is app router not supported?

$ npx next dev
C:\Programming2\fantasy-snooker\node_modules\next-superjson\dist\index.js:68
    throw new Error("Couldn't find a `pages` directory. Please create one under the project root");
          ^

Error: Couldn't find a `pages` directory. Please create one under the project root
    at findPagesDir ({some path}\node_modules\next-superjson\dist\index.js:68:11)
    at applyTurbopackOptions ({some path}\node_modules\next-superjson\dist\index.js:78:20)
    at {some path}\node_modules\next-superjson\dist\index.js:24:9

App router already supports passing Dates and other non JSON values to client components, you don’t need this plugin

App router already supports passing Dates and other non JSON values to client components, you don’t need this plugin

Thanks, good to know! I seem to have issues with the native serializer/deserializer of Next.js though which I didn't experience when using next-superjson-plugin, might have something to do with me using Map for a bunch of stuff. I'm pursuing the issue on Discord at https://discord.com/channels/752553802359505017/1318956577931137114 (and it's supposedly mirrored to https://nextjs-forum.com/post/1318956577931137114).

Edit:) those links above are worthless, nobody pursued the issue. I created a discussion here vercel/next.js#75976

App router already supports passing Dates and other non JSON values to client components, you don’t need this plugin

Is this true for custom types like Decimal used by prisma? This is the main reason why we need superjson at the moment.

I guess it's only supporting the types listed at https://react.dev/reference/rsc/use-server#serializable-parameters-and-return-values

App router already supports passing Dates and other non JSON values to client components, you don’t need this plugin

Is this true for custom types like Decimal used by prisma? This is the main reason why we need superjson at the moment.

I guess it's only supporting the types listed at https://react.dev/reference/rsc/use-server#serializable-parameters-and-return-values

Please stop using decimals in postgres & prisma, use Float instead with 24 precision.

Any update on this?

App router already supports passing Dates and other non JSON values to client components, you don’t need this plugin

Some of us probably will be stuck with the pages router forever. Didn't understand this being ported there.

I'll close this since, as mentioned a couple times already, the app router already supports non-json values, making this plugin obsolete.

So people using the pages router have to write their own or should it work for static/server side props out of the box too?

You can use this library instead which works with Next 15 https://github.com/remorses/next-superjson

@aplr: I'll close this since, as mentioned a couple times already, the app router already supports non-json values, making this plugin obsolete.

Please reopen this! Until Next.js fully deprecates and removes the Pages Router, it is a core part of the framework. Therefore, this plugin is not obsolete. Quite the opposite, it is of great value to Pages Router projects. 🙇🏻

@remorses unfortunately, your library is not an effective drop-in replacement for this plugin (while keeping it as a runtime dependency). I tried it on a large codebase back in November and it appeared to interfere with project config, with numerous routes malfunctioning.

Besides that, and I sincerely mean no offense by this, its existence shouldn't be necessary.

I'll close this since, as mentioned a couple times already, the app router already supports non-json values, making this plugin obsolete.

While this is true for most common types like Dates this is not true for any custom js types out there (e.g. Prisma Decimals which we heavily rely on). For me the use case of superjson combined with this plugin has always been to address exactly this - serializing any custom/niche types. That's why I'm very surprised about this decision.

You can use this library instead which works with Next 15 https://github.com/remorses/next-superjson

I am not sure if this is true. For one, this plugin is still needed and its package.json does require next 14 as a peer. If you ignore that, you'll still "failed to invoke plugin" errors like in the OP. Or am I misunderstanding something?