Getting help with nestjs-drizzle-crud
Get help with nestjs-drizzle-crud. Ask in GitHub Discussions, report bugs as issues, report security issues privately, and include what to send.
To get help with nestjs-drizzle-crud, ask usage questions in GitHub Discussions, report a bug you can reproduce as a GitHub issue, and report a security vulnerability privately through a GitHub security advisory. A report that includes the package version, the table definition, the entity config and the exact call gets answered fastest.
Never report a vulnerability in public
Do not put a security problem in an issue, a discussion or a pull request. Use the private advisory form described under the security question below, which only the maintainers can see.
Where do I ask?
Pick the channel by what you need; each one is watched.
| You want to | Go to |
|---|---|
| Ask how to do something | GitHub Discussions |
| Report a bug you can reproduce | GitHub issues, bug report template |
| Request a feature | GitHub issues, feature request template |
| Report a security vulnerability | A private security advisory |
| Contribute code | CONTRIBUTING.md |
| Fund the work | Sponsor nestjs-drizzle-crud |
Blank issues are turned off, so every issue starts from the bug report or feature request template.
What should a bug report include?
A report with a reproduction usually gets fixed in one round trip. The bug report template asks for most of this; fill in all of it:
- The
nestjs-drizzle-crudversion, the dialect, and your Node, NestJS and Drizzle versions. - The Drizzle table definition for the entity, trimmed to the relevant columns.
- The
forRootandforFeatureconfig for that entity. - The call you made and what came back, including the exception class and HTTP status.
- The SQL, if you have it. Drizzle logging (
drizzle(client, { logger: true })) prints the statement the service built. - The stack trace, if there is one.
Search the existing issues first; the template asks you to confirm the bug is not a duplicate.
How do I report a security vulnerability?
Report it privately through GitHub's security advisory form, as the security policy says. Include:
- What the vulnerability is and what an attacker could do with it.
- Steps to reproduce, ideally a minimal proof of concept.
- The affected version or versions.
The maintainers acknowledge reports within 72 hours, work with you on a fix and agree a disclosure date. Reporters are credited in the advisory unless they prefer otherwise.
| Question | Answer |
|---|---|
| What is in scope? | The published npm package, packages/nestjs-drizzle-crud. |
| What is out of scope? | apps/api and apps/docs, the private example app and this docs site. Report problems there as normal issues. |
| Which versions get security fixes? | 3.x. Versions before 3.0 do not. |
Need paid help?
Community help stays free. If you want the package integrated, a migration done, a feature built or your services reviewed on your own schedule, see commercial support and custom development.
Common questions
findAll returns { data, total, page, limit } because every list is paginated. total comes from a count query with the same filters and search, so it stays correct as you page.
like and ilike use the wildcards you supply, so { name: { ilike: "jo" } } only matches jo. Write { name: { ilike: "jo%" } }, or use startsWith, which adds and escapes the wildcard for you.
Soft delete and timestamps are on by default and expect deleted_at, created_at and updated_at. Turn them off with defaults: { softDelete: false, timestamps: false }, or point them at your column keys.
No. forFeature builds the service and hands it the config, Drizzle instance included. Adding @Injectable() or an @Inject(DRIZZLE_DB) constructor breaks that registration.
Yes. Pass a mysql:// connection string or your own Drizzle MySQL instance as db, and the package reads written rows back because MySQL has no RETURNING. Full-text search and the array and JSON operators are PostgreSQL only.
Next steps
Error handling in NestJS with Drizzle
What each exception means and the status it returns.
nestjs-drizzle-crud facts for AI agents
Condensed rules and gotchas, checked against the source.
Sponsor nestjs-drizzle-crud
Fund the fixes, the docs and the next release.
Changelog
The nestjs-drizzle-crud changelog, every release since 3.0.0 with what was added, changed, fixed and deprecated, newest first, mirroring CHANGELOG.md.
Commercial support and custom development
Hire NestJS and Drizzle consultants from Avytrix Technologies, the team that maintains nestjs-drizzle-crud, to integrate, migrate, extend or review your API.