feat: add @nuxt-drizzle/module

[Myshkouski]

🔗 Linked issue

Resolves #1391

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Nuxt Drizzle is a Nuxt module for automating Drizzle ORM setup with support for multiple datasources and conditional database driver imports.

Key Features:

• 🚅 Multiple Datasources - Support for multiple named database connections
• 📦 Conditional imports - Avoid bundling unused database drivers
• 🔧 Seamless Nuxt integration - Auto-discovers Drizzle configs in subdirectories
• 🛠️ Migration support - Built-in migration handling with hooks
• ✅ Multi-database support - SQLite, PostgreSQL, and MySQL

The module simplifies Drizzle ORM integration in Nuxt/Nitro applications by:

• Auto-configuring database connections from nuxt.config.ts
• Providing useDrizzle(event, name) composable for accessing datasources
• Supporting auto-discovery of Drizzle config files in subdirectories
• Integrating with Nitro's experimental database feature
• Providing lifecycle hooks for migrations and seeding

Target Users:

• Nuxt developers who want to use Drizzle ORM

• Projects requiring multiple database connections

• Applications needing type-safe database operations with schema awareness

[coderabbitai]

📝 Walkthrough

Walkthrough

A new YAML manifest file for the Drizzle ORM Nuxt module has been added to the modules directory. The file declares metadata for a third-party Nuxt module named "drizzle," including its description, repository, npm package reference, icon, GitHub URL, website, category, type, a single maintainer entry, and Nuxt version compatibility requirements (>=3.0.0).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: adding the @nuxt-drizzle/module to the Nuxt modules registry, which is directly reflected in the YAML manifest file added.
Description check	✅ Passed	The description is well-detailed and directly related to the changeset, explaining the purpose, features, and benefits of the @nuxt-drizzle/module being added.
Linked Issues check	✅ Passed	The PR successfully addresses issue #1391 by adding the modules/drizzle.yml manifest file with all required metadata for module listing including repository, npm package, Nuxt compatibility, and module description.
Out of Scope Changes check	✅ Passed	All changes in the PR are in-scope: the single file added (modules/drizzle.yml) is a module descriptor directly addressing the module listing request in issue #1391 with no extraneous modifications.
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.}