Skip to content

feat: add lucide-motion-vue module#1458

Open
tr-evo wants to merge 2 commits intonuxt:mainfrom
tr-evo:add-lucide-motion-vue
Open

feat: add lucide-motion-vue module#1458
tr-evo wants to merge 2 commits intonuxt:mainfrom
tr-evo:add-lucide-motion-vue

Conversation

@tr-evo
Copy link
Copy Markdown

@tr-evo tr-evo commented Apr 22, 2026

Description

Adds @respeak/lucide-motion-vue to the modules database.

The module exposes a Nuxt 3 integration at @respeak/lucide-motion-vue/nuxt that auto-registers <AnimateIcon> and all 535 animated Lucide icons as components. Default naming is Animated-suffixed (<HeartAnimated>, <Link2Animated>, …) so the module coexists cleanly with lucide-vue-next's static names; the suffix/prefix is configurable via nuxt.config's lucideMotion key. Per-icon tree-shaking is preserved under Nuxt's component loader.

Icon variants are adapted from animate-ui and pqoqubbw/icons (see the project's ATTRIBUTIONS.md).

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 22, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 14d464cf-5bf0-4d62-a3f3-e593057841c5

📥 Commits

Reviewing files that changed from the base of the PR and between aa65128 and a1cd815.

📒 Files selected for processing (1)
  • modules/lucide-motion-vue.yml
✅ Files skipped from review due to trivial changes (1)
  • modules/lucide-motion-vue.yml

📝 Walkthrough

Walkthrough

Adds a new Nuxt module manifest file modules/lucide-motion-vue.yml containing metadata for the lucide-motion-vue module: name and description, links to source and distribution (repo, npm, github, website), category and type, maintainer listed as Tim Rietz (GitHub: tr-evo), and compatibility declaring Nuxt support ^3.0.0 with no additional requires specified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The PR title 'feat: add lucide-motion-vue module' directly and clearly describes the main change: adding a new module to the database.
Description check ✅ Passed The PR description provides detailed information about the module being added, including package details, repository links, functionality, and compatibility constraints.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

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

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
modules/lucide-motion-vue.yml (1)

5-8: Consider populating the icon and learn_more fields.

While these fields appear to be optional, providing values could enhance the module's presentation:

  • icon: Adding an icon URL would improve visibility in the Nuxt modules directory.
  • learn_more: If additional resources or documentation exist beyond the website, this field could link to them.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@modules/lucide-motion-vue.yml` around lines 5 - 8, Populate the empty YAML
fields `icon` and `learn_more` in the module manifest: set `icon` to a publicly
accessible URL pointing to the module's logo or SVG (e.g., the project's repo or
GitHub Pages asset) and set `learn_more` to a helpful documentation or resources
URL (if none beyond `website`, you can reuse the `website` or point to the
README on GitHub); update the `icon` and `learn_more` keys in the existing
manifest (the `icon:` and `learn_more:` entries) with these values.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@modules/lucide-motion-vue.yml`:
- Around line 14-16: The compatibility entry currently lists "nuxt: '>=3.0.0'"
but your package peerDependency requires "@nuxt/kit: ^3.0.0", so update the
compatibility constraint to exactly reflect Nuxt 3.x by changing the "nuxt"
value from ">=3.0.0" to "^3.0.0" (i.e., replace nuxt: '>=3.0.0' with nuxt:
'^3.0.0').

---

Nitpick comments:
In `@modules/lucide-motion-vue.yml`:
- Around line 5-8: Populate the empty YAML fields `icon` and `learn_more` in the
module manifest: set `icon` to a publicly accessible URL pointing to the
module's logo or SVG (e.g., the project's repo or GitHub Pages asset) and set
`learn_more` to a helpful documentation or resources URL (if none beyond
`website`, you can reuse the `website` or point to the README on GitHub); update
the `icon` and `learn_more` keys in the existing manifest (the `icon:` and
`learn_more:` entries) with these values.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fd424311-3eee-4bc9-83c3-d4922dd453e8

📥 Commits

Reviewing files that changed from the base of the PR and between da52820 and aa65128.

📒 Files selected for processing (1)
  • modules/lucide-motion-vue.yml

Comment thread modules/lucide-motion-vue.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant