Add support for Next.js 16 in peerDependencies

[diogocapela]

This PR updates package.json peerDependencies to include compatibility with Next.js v16.

"next": "^14.0.0 || ^15.0.0 || ^16.0.0"

Without this update, projects using Next.js 16 encounter peer dependency resolution failures during installation. This update ensures users can install @ant-design/nextjs-registry without needing to use --force or --legacy-peer-deps.

Summary by CodeRabbit

版本更新

• Chores
  • 扩展框架兼容性，新增对 Next.js 16.x 的支持；更新依赖、开发依赖和同伴依赖以兼容 Next.js 14/15/16 三个主要版本系列，提升与最新框架的兼容性与构建稳定性。无用户界面变更。

[coderabbitai]

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

📝 Walkthrough

Walkthrough

在 package.json 中将 Next.js 的三个依赖条目版本从 ^15.0.0 升级为 ^16.0.0，并将 peerDependencies 的允许范围扩展为包含 ^16.0.0。

Changes

Cohort / File(s)	变更摘要
依赖版本更新 package.json	将顶层 dependencies.next 从 ^15.0.0 更新为 ^16.0.0；将 devDependencies.next 从 ^15.0.0 更新为 ^16.0.0；将 peerDependencies.next 从 `^14.0.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 分钟

Poem

🐰 兔子的小诗

新版来了轻轻跳，
十六号门已敞开，
依赖一行微改绕，
兼容多了步更快，
项目轻盈向前跑 🌿

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	PR标题"Add support for Next.js 16 in peerDependencies"准确地反映了该拉取请求的主要目标。根据PR目标描述，该PR的核心目的是在peerDependencies中添加Next.js 16支持，以防止使用Next.js 16的项目在安装时出现对等依赖解析失败。虽然原始总结显示也更新了顶级依赖和devDependency，但根据PR目标，peerDependencies的更新是此次变更的主要焦点和驱动因素。标题清晰、具体且有意义，能够帮助团队成员理解主要变更内容。

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b7454d9 and d0150e6.

📒 Files selected for processing (1)

• package.json (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• package.json

---

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.}

[gemini-code-assist]

Summary of Changes

Hello @diogocapela, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the package.json file to officially declare compatibility with Next.js v16. By extending the next peer dependency range, it resolves installation issues for users leveraging the latest Next.js version, ensuring a smoother development workflow.

Highlights

• Next.js 16 Compatibility: The package.json has been updated to include support for Next.js v16 in its peerDependencies.
• Improved Developer Experience: This change prevents peer dependency resolution failures for users on Next.js 16, eliminating the need to use --force or --legacy-peer-deps during package installation.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly updates the peerDependencies in package.json to add support for Next.js v16, which will resolve installation issues for users on the new version. My review includes one suggestion to also update the next version in devDependencies. This will ensure the project's examples and tests are run against Next.js 16, providing confidence that the package is fully compatible.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eb07ba1 and b7454d9.

📒 Files selected for processing (1)

• package.json (1 hunks)

⏰ 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: Socket Security: Pull Request Alerts