Community
Get Involved
- GitHub Discussions - Questions, ideas, and general discussion
- GitHub Issues - Bug reports and feature requests (per-package repos)
- npm - All published packages
Contributing
We welcome contributions to any nestarc package. Here's how to get started:
1. Pick a package
Each package lives in its own repository under the nestarc organization:
| Package | Repository |
|---|---|
| tenancy | nestarc/nestjs-tenancy |
| safe-response | nestarc/nestjs-safe-response |
| audit-log | nestarc/nestjs-audit-log |
| feature-flag | nestarc/nestjs-feature-flag |
| soft-delete | nestarc/nestjs-soft-delete |
| pagination | nestarc/nestjs-pagination |
| idempotency | nestarc/idempotency |
| outbox | nestarc/outbox |
| webhook | nestarc/webhook |
| api-keys | nestarc/api-keys |
| rbac | nestarc/rbac |
| data-subject | nestarc/data-subject |
| jobs | nestarc/jobs |
Labs and developer tooling live separately from the main SaaS package list:
| Tool | Repository |
|---|---|
| mcp-guard | nestarc/mcp-guard |
2. Development workflow
bash
# Clone the repo
git clone https://github.com/nestarc/<repo>.git
cd <repo>
# Install dependencies
npm install
# Run tests
npm test
# Build
npm run build3. Submit a PR
- Fork the repository
- Create a feature branch from
main - Write tests for your changes
- Ensure all tests pass
- Submit a pull request with a clear description
Roadmap
Roadmap items are grouped by current product focus. Nestarc core stays focused on SaaS backend primitives; experimental developer tools live under Labs until they are proven enough to become part of the main product direction.
| Stage | Items |
|---|---|
| Now | @nestarc/rbac, Webhooks Cloud beta, generated API reference refresh |
| Next | Webhooks onboarding, examples, access-control recipes, docs localization parity |
| Later | metering, quota, entitlements |
| Exploring | Additional Labs developer tools |
Core vs Labs
Core roadmap items are packages, docs, examples, and Cloud workflows that directly support production SaaS backends. Labs items, including @nestarc/mcp-guard, are useful developer tools, but they are intentionally separate from the core package roadmap until their fit is clear.