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 toGo to
Ask how to do somethingGitHub Discussions
Report a bug you can reproduceGitHub issues, bug report template
Request a featureGitHub issues, feature request template
Report a security vulnerabilityA private security advisory
Contribute codeCONTRIBUTING.md
Fund the workSponsor 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:

  1. The nestjs-drizzle-crud version, the dialect, and your Node, NestJS and Drizzle versions.
  2. The Drizzle table definition for the entity, trimmed to the relevant columns.
  3. The forRoot and forFeature config for that entity.
  4. The call you made and what came back, including the exception class and HTTP status.
  5. The SQL, if you have it. Drizzle logging (drizzle(client, { logger: true })) prints the statement the service built.
  6. 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.

QuestionAnswer
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

Next steps

Last updated View change history

On this page