Modules
Module catalog
Add only the infrastructure and product foundations your application needs.
How modules work
Each module declares its source templates, dependencies, environment variables, compatibility rules, and optional lifecycle hooks. During generation, Nextron resolves requirements first and then applies modules in dependency order.
Database
Drizzle or Prisma with provider-aware configuration.
Authentication
Better Auth, Clerk, or NextAuth routes and clients.
Dashboard
Protected routes, responsive navigation, overview, and settings.
Integrations
tRPC, AI, Stripe, Polar, and Inngest foundations.
Generation guarantees
- A selected module receives only files whose conditions match the project configuration.
- A missing declared template stops generation instead of producing a partial feature.
- Module dependencies are merged into
package.json. - Environment variables are consolidated into
src/env.tsand.env.example. - Generated templates never retain unresolved
{{variable}}placeholders.
Add modules later
npx @edwinfom/nextron@latest add <module>The add command preserves existing destination files. When a file conflicts, Nextron warns and leaves the existing file untouched.