feat(nextjs): Next.js@15 compatibility

[jacekradko]

Description

Next.js@15 compatibility integration branch

Checklist

• npm test runs as expected.
• npm run build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

[changeset-bot]

🦋 Changeset detected

Latest commit: 9b8cccd

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 7 packages

Name	Type
@clerk/nextjs	Major
@clerk/upgrade	Minor
@clerk/clerk-react	Minor
@clerk/chrome-extension	Patch
@clerk/clerk-expo	Patch
@clerk/remix	Patch
@clerk/tanstack-start	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[drosi94]

Is there anything to be done? We could help to push it on main as the Next.JS just released v15

[jacekradko]

!allow-major

[BRKalow]

🚢

[ChristianIvicevic]

I have tested the canary for this with 6.0.0-canary.va0204a8 and noticed that the types for the clerkMiddleware aren't correct yet.

export default clerkMiddleware(async (auth, request) => {
  const { sessionClaims } = await auth() // auth() is not a Promise over here and causes TS and eslint to complain
  // ...
  if (!isPublicRoute(request)) {
    try { await auth.protect() } // works as expected
    catch (e) { unstable_rethrow(e) }
  }
})

Do you want me to open a separate issue to track this?

[dstaley]

@ChristianIvicevic Thanks for reporting this! It was fixed in 6.0.0-canary.vee453d8.