feat(modules): add nuxt-nats

[lithqube]

Summary

Lists lithqube/nuxt-nats (3rd-party) in the Nuxt modules registry.

NATS and JetStream integration for Nuxt: publish/subscribe messaging, durable JetStream streams, consumers, and server-side event-driven workflows for Nitro. Includes typed consumers, server-side publish, KV, Object Store, stream provisioning, and rotating credentials (Infisical, Synadia Control Plane, or a custom provider). Bun-ready; tested on Nuxt 3 and Nuxt 4.

• Repo: https://github.com/lithqube/nuxt-nats
• npm: https://www.npmjs.com/package/nuxt-nats
• Icon: icons/nuxt-nats.png (512×512 PNG, 128 KB)
• Category: Database (KV / streams / object store are data-plane primitives; matches how Appwrite, Convex, EdgeDB are listed)
• Type: 3rd-party
• Compat: Nuxt 3 / Nuxt 4 (>=3.0.0)

How this was generated

pnpm install
pnpm sync nats lithqube/nuxt-nats

Then I corrected the auto-inferred category from Devtools to Database, tightened the description to match the upstream README framing (publish/subscribe + durable streams + event-driven workflows), cleared website (no separate homepage), and pointed learn_more at https://docs.nats.io/.

Icon

Initially committed as a 920 KB SVG, but on inspection it turned out to be a 1254×1254 PNG embedded as base64 inside an SVG wrapper (not a vector). Replaced with a properly-sized 512×512 PNG (128 KB, ~86% smaller) in icons/nuxt-nats.png. pnpm build validates the icon file exists.

Checklist

• Repo is public
• nuxt-nats is published on npm
• pnpm build passes (schema validated; icon file exists)
• Category chosen from lib/categories.ts
• All CI checks passing (autofix, check-provenance, ci, CodeRabbit, Socket Security)

resolves #1615

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 4334e291-4bc4-49f2-a261-322a2038b346

📥 Commits

Reviewing files that changed from the base of the PR and between 849c161 and 9eb7db7.

📒 Files selected for processing: 1

• modules/nuxt-nats.yml

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 2 remain after this review.

📝 Walkthrough

Adds a nuxt-nats module listing. The entry includes integration details, links, category, maintainer, and Nuxt compatibility information.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 9eb7d

The proposed change is a module catalog listing; no actionable merge-blocking risk is identified in the supplied review context.

Pre-merge checks: 4 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Linked Issues check		Issue #1615 requests a registry listing for lithqube/nuxt-nats with NATS JetStream features including server-side publish, typed consumers, KV storage, and Object Store, plus repository/npm links an…	Update the module description to include typed consumers, KV storage, and Object Store. Confirm that the compatibility declaration satisfies the repository schema for both Nuxt 3 and Nuxt 4, or represent both versions explicitly if required…

Passed checks: 4 passed

Check name	Status	Explanation
Title check		The title clearly identifies the primary change: adding the nuxt-nats module listing.
Description check		The description is detailed and on-topic. It explains the module, links the issue, documents metadata and icon changes, and records validation results. It uses a Summary heading instead of the templat…
Out of Scope Changes check		The whole-PR diff adds only the nuxt-nats registry metadata and its referenced icon. The metadata and icon directly support the requested module listing. No unrelated repository change is shown.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…

Full details: Linked Issues check

Explanation

Issue #1615 requests a registry listing for lithqube/nuxt-nats with NATS JetStream features including server-side publish, typed consumers, KV storage, and Object Store, plus repository/npm links and Nuxt 3 and Nuxt 4 compatibility. modules/nuxt-nats.yml provides the listing, links, publish/subscribe messaging, consumers, and >=3.0.0 compatibility. The description does not identify typed consumers, KV storage, or Object Store. The file also does not explicitly declare Nuxt 4 compatibility beyond the broad version range.

Resolution

Update the module description to include typed consumers, KV storage, and Object Store. Confirm that the compatibility declaration satisfies the repository schema for both Nuxt 3 and Nuxt 4, or represent both versions explicitly if required.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

[lithqube]

Added the icon: icons/nuxt-nats.png (512×512 PNG, 128 KB) and wired it into modules/nats.yml via icon: nuxt-nats.png. pnpm build passes (schema validator confirms the file exists).

[lithqube]

@danielroe, hope I did it properly, thank you for your support

[lithqube]

🙇🏻