nestjs-crud-v1

Configure nestjs-crud v1 CRUD controllers, filters, pagination, and Swagger in NestJS.

9|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/kodjunkie/nestjs-crud --skill nestjs-crud-v1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nestjs-crud-v1
Source: https://github.com/kodjunkie/nestjs-crud/tree/main/skills/nestjs-crud-v1
Command: npx skills add https://github.com/kodjunkie/nestjs-crud --skill nestjs-crud-v1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers integrate and maintain legacy nestjs-crud v1.x within NestJS projects by providing setup guidance for CRUD controllers, query filters, pagination, and scoped authentication with @CrudAuth, plus troubleshooting tips for common v1 issues.

Core Features & Use Cases

  • Guided setup for CRUD controllers, query parsing, pagination, and Swagger integration in v1 projects.
  • Troubleshooting and migration guidance for common v1 symptoms (e.g., flat arrays from getManyBase, misapplied filters, maxLimit concerns) and how to upgrade to v2.
  • Best-practice patterns for auth scoping, route overrides, and interoperability with adapters (TypeORM, Drizzle, MikroORM).
  • Real-world scenarios and step-by-step decision guidance for maintaining, debugging, and upgrading legacy v1 implementations.

Quick Start

Follow the steps to add v1 to your NestJS project, configure @Crud, enable CrudAuth scoping, and verify endpoints and Swagger behavior.

Frequently Asked Questions about nestjs-crud-v1

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure CRUD controllers and query filters in a legacy NestJS app?▼

To configure CRUD controllers and query filters in a legacy NestJS app, you apply the v1 @Crud decorator, parse query parameters, and set up pagination to ensure endpoints return properly scoped data.

Why does getManyBase return a flat array instead of paginated results in nestjs-crud?▼

The getManyBase method returns a flat array instead of paginated results due to specific v1 query configuration behaviors. Adjusting query parameter parsing and checking maxLimit settings resolves this common symptom.

How do I apply @CrudAuth scoping to secure routes in NestJS?▼

Applying @CrudAuth scoping secures routes in NestJS by injecting authentication rules directly into the CRUD controller configuration, ensuring users only access authorized data based on their session.

Can I use nestjs-crud v1 with TypeORM, Drizzle, or MikroORM adapters?▼

Yes, nestjs-crud v1 works with TypeORM, Drizzle, and MikroORM adapters. The skill provides best-practice patterns for interoperability, ensuring query filters and pagination function correctly across these adapters.

What are the steps to migrate from nestjs-crud v1 to v2?▼

Migrating from nestjs-crud v1 to v2 involves installing updated dependencies, referencing known v1 issues like misapplied filters, and following step-by-step upgrade guidance to adapt controllers and Swagger integration.

How do I override default CRUD routes and enable Swagger in NestJS?▼

Overriding default CRUD routes and enabling Swagger in NestJS requires customizing the base controller methods within the v1 configuration and verifying that API documentation accurately reflects the modified endpoints.