feat(nextjs): Add support for Next 16

[davecarlson]

Description

Checklist

• pnpm test runs as expected.
• pnpm 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:

Summary by CodeRabbit

• Chores
  • Extended Next.js version compatibility to include Next.js 16.

[changeset-bot]

🦋 Changeset detected

Latest commit: 8d6fb13

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

This PR includes changesets to release 1 package

Name	Type
@clerk/nextjs	Minor

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

[vercel]

@davecarlson is attempting to deploy a commit to the Clerk Production Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Caution

Review failed

The head commit changed during the review from e3c9128 to 8d6fb13.

Walkthrough

Updated the Next.js package's peer dependency constraint to include Next.js version 16. The allowed version range now explicitly supports Next.js 13.5.7, 14.2.25, 15.2.3, and 16, enabling compatibility with the latest major release.

Changes

Cohort / File(s)	Change Summary
Next.js peer dependency update packages/nextjs/package.json	Added Next.js 16 to the peer dependency version constraint: `"^13.5.7

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop and a bound, version 16 is found!
Next.js takes flight, our peers align just right,
From thirteen to sixteen, the smoothest we've seen,
With || and ^ we dance in harmony! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Title Check	✅ Passed	The pull request title "feat(nextjs): Add support for Next 16" directly and accurately describes the main change in the changeset, which is updating the peerDependencies in packages/nextjs/package.json to include Next.js version 16 in the allowed range. The title is concise, clear, and uses conventional commit formatting without unnecessary noise or vague language. A teammate reviewing the pull request history would immediately understand that this change enables compatibility with Next.js 16.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 911ccbb and e23a7eb.

📒 Files selected for processing (1)

• packages/nextjs/package.json (1 hunks)

🧰 Additional context used

📓 Path-based instructions (2)

**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

• packages/nextjs/package.json

packages/*/package.json

📄 CodeRabbit inference engine (.cursor/rules/global.mdc)

All publishable packages should be placed under the packages/ directory

packages/*/package.json: All publishable packages must be located in the 'packages/' directory.
All packages must be published under the @clerk namespace on npm.
Semantic versioning must be used across all packages.

Files:

• packages/nextjs/package.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: semgrep-cloud-platform/scan

🔇 Additional comments (2)

packages/nextjs/package.json (2)

1-104: Verify PR testing and Next.js 16 compatibility before merge.

Per the PR checklist, all testing items are unchecked (pnpm test, pnpm build). Before merging a peer dependency expansion, ensure:

1. The package has been tested with Next.js 16 (not just 14.2.33)
2. No breaking changes in Next.js 16 affect this SDK
3. All CI checks pass with the new version constraint
4. If applicable, document any Next.js 16–specific behavior or known limitations

Additionally, the PR description is empty. Please provide context: Is this driven by a customer request, an internal need, or proactive Next.js 16 support? Any related issue or discussion link would strengthen the rationale.

---

93-97: Confirm Prettier formatting compliance.

Per the coding guidelines, JSON files should be formatted with Prettier. Lines 95–96 show trailing space annotations. Ensure the file passes Prettier formatting checks (pnpm format:check) before merge.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
clerk-js-sandbox	Ready	Preview	Comment	Oct 22, 2025 5:12pm

[wobsoriano]

Thanks!

[pkg-pr-new]

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@7051

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@7051

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@7051

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@7051

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@7051

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@7051

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@7051

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@7051

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@7051

@clerk/express

npm i https://pkg.pr.new/@clerk/express@7051

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@7051

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@7051

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@7051

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@7051

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@7051

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@7051

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@7051

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@7051

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@7051

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@7051

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@7051

@clerk/types

npm i https://pkg.pr.new/@clerk/types@7051

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@7051

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@7051

commit: 8d6fb13

[wobsoriano]

Closing in favor of #7055