clerk not compatible nextjs 15

[metacop]

Preliminary Checks

• I have reviewed the documentation: https://clerk.com/docs

• I have searched for existing issues: https://github.com/clerk/javascript/issues

• I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)

• This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.

Reproduction

xxxxxx

Publishable key

pk_test_bmF0dXJhbC1zYXdmaXNoLTc1LmNsZXJrLmFjY291bnRzLmRldiQ

Description

I am creating a new project and I have the latest version of clerk, but it is not compatible with nextjs 15.
@clerk/nextjs": "^5.7.5",

Environment

xxx

[drosi94]

I think in the next major version this will be an actual issue

https://nextjs.org/docs/app/building-your-application/upgrading/version-15#recommended-async-usage

As they said they will throw an error now so you can fix it, but it will still works for the this version

[ChristianIvicevic]

To add to this, the stack trace shows that this is very like caused by the implementation of auth(), in my case used within a SignedOut component:

at new Request (node:internal/deps/undici/undici:9267:34)
at new NextRequest (.next/server/chunks/ssr/5a2f6_next_2cb2f2._.js:3350:14)
at buildRequestLike (.next/server/chunks/ssr/_2a1227._.js:48:16)
at auth (.next/server/chunks/ssr/_2a1227._.js:853:443)
at SignedOut (.next/server/chunks/ssr/_2a1227._.js:1043:433)

@drosi94 We as consumers of the Clerk SDK cannot fix it with the workaround, it's a problem the Clerk team has to fix since we receive the error to their underlying sync access.

[drosi94]

Yes you are right they are working on it #4366

edit: As I see they changing everything to be async which may introduce more time migrating as testing it would be needed. An option would be to use the workaround for now with the sync way and migrate afterwards to the async APIs

[eifo]

Clerk provider not awaiting headers throws error per @clerk/nextjs": "^5.7.5" and "next": "^15.0.1-canary.1" next --turbo.

[ChristianIvicevic]

@eifo As drosi pointed out, the fix is part of #4366 and will most likely be shipped in a major update anytime soon.

[eifo]

@eifo As drosi pointed out, the fix is part of #4366 and will most likely be shipped in a major update anytime soon.

This got worst with latest next canary, it's critical at this point.

[ChristianIvicevic]

Given that Next 15 just released with massive breaking changes it's not surprise. If you have a critical application you shouldn't migrate the same day and wait for a few days until the ecosystem catches up.

[LekoArts]

Hello!

We've merged #4366 to provide compatibility with the latest Next.js release and it'll be released soon. You'll hear about that in our changelog (https://clerk.com/changelog) and once #4358 is merged it'll be released by our CI.

Thank you for your patience 🙏

[ChristianIvicevic]

@LekoArts I just tried out the latest canary and at first glance it looks to be working well with all the relevant changes, but I had to apply the changes manually. I couldn't get your @clerk/upgrade codemods to work, but chances are it's a just an issue of me trying to use it.

[zaiiche]

@LekoArts I just tried out the latest canary and at first glance it looks to be working well with all the relevant changes, but I had to apply the changes manually. I couldn't get your @clerk/upgrade codemods to work, but chances are it's a just an issue of me trying to use it.

same, I guess it's down for now...?