feat: add antdv-next module

[darkingtail]

Summary

• Add antdv-next (Ant Design for Vue) to the Nuxt modules list
• Add module icon (SVG)

Module Info

Field	Value
Name	antdv-next
NPM	@antdv-next/nuxt
Category	UI
Compatibility	Nuxt >= 4.0.0
Website	https://www.antdv-next.com
Repository	https://github.com/antdv-next/nuxt

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces a new manifest file modules/antdv-next.yml that defines metadata for the Ant Design Vue Nuxt integration. The file includes configuration properties such as name, description, repository reference, npm package details, icon, URLs (GitHub and website), learning resources, category, type designation, maintainer information, and version constraints requiring Nuxt 4.0.0 or higher. This is a configuration and metadata addition with no functional code implementation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat: add antdv-next module' clearly and accurately describes the main change: adding a new Ant Design Vue module to the Nuxt modules list.
Description check	✅ Passed	The description is directly related to the changeset, providing a clear summary of the module being added and relevant metadata about the antdv-next integration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

---

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]

🧹 Nitpick comments (2)

modules/antdv-next.yml (2)

16-16: Consider omitting the empty requires field.

The requires: {} field is currently an empty object. Based on learnings, the requires field is primarily used for bridge compatibility properties (e.g., bridge: true/false/optional). If no such requirements exist, this field can be omitted entirely for cleaner configuration.

♻️ Proposed cleanup

 compatibility:
   nuxt: '>=4.0.0'
-  requires: {}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@modules/antdv-next.yml` at line 16, Remove the empty requires field from the
modules/antdv-next.yml manifest: locate the top-level "requires: {}" entry and
delete it so the file omits the empty requirements block (the manifest should
not include a blank requires key when there are no bridge/compatibility
properties).

---

7-8: Consider differentiating learn_more from website.

Both website and learn_more point to the same URL. If the project has dedicated documentation (e.g., /docs or /guide), consider pointing learn_more to that specific resource for better user guidance.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@modules/antdv-next.yml` around lines 7 - 8, The YAML currently sets both keys
website and learn_more to the same URL; update the learn_more value to point at
a dedicated docs or guide page (e.g., append /docs or /guide or the project’s
actual documentation URL) so users land directly on learning resources; locate
the website and learn_more entries in the YAML and change only the learn_more
value to the documentation URL while keeping website as the main site.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@modules/antdv-next.yml`:
- Line 16: Remove the empty requires field from the modules/antdv-next.yml
manifest: locate the top-level "requires: {}" entry and delete it so the file
omits the empty requirements block (the manifest should not include a blank
requires key when there are no bridge/compatibility properties).
- Around line 7-8: The YAML currently sets both keys website and learn_more to
the same URL; update the learn_more value to point at a dedicated docs or guide
page (e.g., append /docs or /guide or the project’s actual documentation URL) so
users land directly on learning resources; locate the website and learn_more
entries in the YAML and change only the learn_more value to the documentation
URL while keeping website as the main site.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2515b5a and e661304.

⛔ Files ignored due to path filters (1)

• icons/antdv-next.svg is excluded by !**/*.svg

📒 Files selected for processing (1)

• modules/antdv-next.yml