[3.0 Beta] Using Next.js version 14.2.1 results in an error

[todor0v]

Link to reproduction

No response

Describe the Bug

When trying to log in after installing Payload using npx create-payload-app@beta on an existing project with Next.js version 14.2.1 I get the following error:

createContext only works in Client Components. Add the "use client" directive at the top of the file to use it. Read more: https://nextjs.org/docs/messages/context-in-server-component

Then I get a GET /api/users/me returning 500.

The error is not present if I use Next.js 14.2.0-canary.23 like the 3.0 Demo.

To Reproduce

Install Payload on an existing project using Next.js 14.2.1 and try to login or register a user.

Payload Version

3.0.0-beta.10

Adapters and Plugins

db-mongodb, next, richtext-lexical

[jmikrut]

Tracked on Next.js repo already here:

vercel/next.js#64412

This is only using Turbopack, right?

[todor0v]

@jmikrut That is correct. The issue is only present if I use next dev --turbo.

[jmikrut]

Hey @todor0v — looks like they fixed the issue, but the fix has not yet been released as a canary. I'll keep this open until we see confirmation that the fix works in a released Next.js canary.

[todor0v]

@jmikrut Thank you so much! 🙏

[KnotScientific]

@jmikrut @todor0v was this fixed in 14.3.0-canary.8 or 14.3.0-canary.7? I see the fix as part of the commits, but after installing 14.3.0-canary.8 and running next dev --turbo. I'm still running into the same issue.

[luochuanyuewu]

@jmikrut @todor0v was this fixed in 14.3.0-canary.8 or 14.3.0-canary.7? I see the fix as part of the commits, but after installing 14.3.0-canary.8 and running next dev --turbo. I'm still running into the same issue.

Me on the same page.

[todor0v]

@luochuanyuewu @KnotScientific As far as I can see not yet. I still get the same error using Payload 3.0.0-beta.10 (or 11) and Next.js 14.3.0-canary-11

[paulpopus]

We've updated the original issue in Nextjs vercel/next.js#64412 regarding this, it looks like turbo is still not fully functioning with client side components

[jmikrut]

Happy to report that this is now fixed!