Core Features | Nuxt Auto CRUD

Explore the Nuxt Auto CRUD ecosystem. Dynamic RESTful APIs, Drizzle-Zod validation, and Agentic-ready logic for high-performance Nuxt 4 applications.

Core Engine Features

📡 Dynamic API Mapping & Agentic Tools

Leverage Nitro Dynamic Routing and Runtime Reflection to resolve RESTful endpoints directly from your Drizzle schemas. By bypassing traditional code generation, the API stays synchronized with your database layer—making it natively compatible with LLM Tooling and MCP (Model Context Protocol) agents.

MethodEndpoint PathRuntime Logic
GET/api/:resourceDynamic pagination, and search.
POST/api/:resourceAutomated Zod-backed payload validation and insertion.
GET/api/:resource/:idPrecision record resolution via schema metadata.
PATCH/api/:resource/:idPartial updates with strict system-field protection.
DELETE/api/:resource/:idValidated record removal

🔐 Auth & RBAC

  • Authentication: Production-ready flows for Login/Registration, Social OAuth (Google/GitHub), and Secure Password Resets.
  • Authorization: Fine-grained Role-Based Access Control (RBAC) defined via database state and app.config.ts seeding, ensuring multi-instance security.

🖥️ Adaptive Headless UI Components

  • Dynamic Data Tables: High-performance grids featuring Search, Pagination, and Multi-format Export (Excel/PDF).
  • Inferred Forms: UI inputs are derived from Drizzle schema types, ensuring zero-drift between the database and the frontend.

⚡ Real-time Updates (SSE)

  • Zero-Config Broadcasting: All CRUD operations (create, update, delete) automatically broadcast events to connected clients.
  • Instant Synchronization: The useAutoCrudSSE composable ensures UI state remains strictly consistent with the server database, including computed fields like updatedAt.
  • Atomic Reliability: Updates are broadcast only after successful database commitment, ensuring the frontend never displays a false positive.

🛡️ Data Integrity & System Security

  • Drizzle-Zod Validation: Payloads are strictly validated at runtime against your schema definitions for type-safe operations.
  • Immutable Field Protection: System-critical fields (id, createdAt, updatedAt, deletedAt) are automatically shielded from external mutation by the NAC core.
  • Delete Logic: Standard Hard-Deletes. System fields are recognized and protected from client-side manipulation to maintain audit trail integrity.

⚙️ Centralized Instance Configuration

Manage global behavior or per-resource overrides via app.config.ts. This architecture allows the specific App to seamlessly customize.

// app.config.ts - Centralized CRUD Governance
export default defineAppConfig({
  crud: {
    // Automated Role Seeding on deployment
    rolesToSeed: ['moderator', 'customer'],
    
    // Global Runtime Visibility Controls
    globalHide: ['updatedAt', 'deletedAt', 'createdBy', 'updatedBy'],

    exports: {
      pdf: {
        globalExclude: ['avatar', 'resetToken'],
        resourceExclude: {
          users: ['password', 'googleId'],
        },
      },
      excel: {
        globalExclude: [],
        resourceExclude: {
          users: ['password'],
        },
      },
    },
  },
})