Add nuxt-c15t

[matt-rolley]

Adds nuxt-c15t to the catalogue.

Nuxt module for GDPR / CMP consent management: headless components, reactive composables, Nuxt Scripts integration for consent-gated script loading, and a vendor cookie registry covering 16+ common third parties (Google Analytics, Meta Pixel, Hotjar, YouTube, Stripe, Directus, Medusa, etc.).

Links

• npm: https://www.npmjs.com/package/nuxt-c15t
• docs: https://nuxt-c15t.rolley.io
• playground: https://playground.nuxt-c15t.rolley.io
• GitHub: https://github.com/rolleyio/nuxt-c15t

Category `Extensions` to match `cookie-control` (the existing cookie-consent entry). Type `3rd-party`.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new module metadata manifest file modules/c15t.yml was added, defining configuration for the c15t Nuxt module. The manifest contains 18 lines of declarative metadata including module identification (name, description), repository references (repo, github, npm, website), visual assets (icon), categorization fields (category, type), maintainer information, and Nuxt compatibility constraints (nuxt ≥3.0.0 with an empty requires object). No functional code implementation is included.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add nuxt-c15t' directly corresponds to the main change: adding a new module metadata file for the nuxt-c15t Nuxt module to the catalogue.
Description check	✅ Passed	The description clearly explains what nuxt-c15t is, its features, provides relevant documentation links, and specifies the requested categorization—all directly related to the changeset.
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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

🧹 Nitpick comments (2)

modules/c15t.yml (2)

18-18: Consider removing empty compatibility.requires.

requires: {} is harmless, but if the schema doesn’t require it, omitting it keeps the manifest cleaner.
Based on learnings, requires in this registry is intended for Nuxt-specific/bridge compatibility metadata, not npm dependency declaration.

🤖 Prompt for AI Agents

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

In `@modules/c15t.yml` at line 18, Remove the empty compatibility.requires entry
from the module manifest: delete the line containing "requires: {}" (the
compatibility.requires key in modules/c15t.yml) so the manifest omits an
unnecessary empty field and only includes compatibility metadata when values are
present.

---

10-10: Avoid empty learn_more value.

Prefer either omitting learn_more or setting it to the docs/playground URL to avoid shipping an empty metadata field.

🤖 Prompt for AI Agents

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

In `@modules/c15t.yml` at line 10, The YAML metadata currently includes an empty
learn_more value; either remove the learn_more entry entirely from
modules/c15t.yml or set learn_more to a valid docs or playground URL (e.g., the
component's documentation link) so the metadata isn't empty — locate the
learn_more key in modules/c15t.yml and either delete that line or replace the
empty string with the appropriate URL.

🤖 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/c15t.yml`:
- Line 18: Remove the empty compatibility.requires entry from the module
manifest: delete the line containing "requires: {}" (the compatibility.requires
key in modules/c15t.yml) so the manifest omits an unnecessary empty field and
only includes compatibility metadata when values are present.
- Line 10: The YAML metadata currently includes an empty learn_more value;
either remove the learn_more entry entirely from modules/c15t.yml or set
learn_more to a valid docs or playground URL (e.g., the component's
documentation link) so the metadata isn't empty — locate the learn_more key in
modules/c15t.yml and either delete that line or replace the empty string with
the appropriate URL.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: dde1f309-dc4d-4537-a528-e4b27993f6bb

📥 Commits

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

⛔ Files ignored due to path filters (1)

• icons/c15t.svg is excluded by !**/*.svg

📒 Files selected for processing (1)

• modules/c15t.yml

[KayleeWilliams]

Hey, co-author of c15t here. We're actively working on an official version of c15t for Vue & Nuxt. I think this is a great start however it's missing a lot of features / polish it needs. For example a11y is very important in consent solutions and I am pretty sure it's missing in this area.

Very glad to see that it's wanted on Vue & Nuxt!

[matt-rolley]

Hey, thanks for commenting! I was about to reach out to you guys, I saw the great work you were doing and thought I'd try help out with the port!

I'm more than happy to transfer this over to you or pull it down so you guys can take over.

I just wanted to use the project with nuxt and thought it might be useful for others.

Happy to do whatever works best, just let me know :)