Troubleshooting
Resolve common generation, installation, environment, and build problems.
Generation reports a missing template
Nextron treats a declared but unavailable module template as a generation error. The message includes the module name, source template, and searched directory. Rebuild or reinstall the CLI package before retrying.
Dashboard is not available
Dashboard routes require an authentication provider. Choose Better Auth, Clerk, or NextAuth before selecting Dashboard. Existing projects with auth: "none" cannot add the Dashboard module until authentication is configured.
Environment validation fails
Compare the reported keys with .env.example, then ensure the values are placed in .env.local rather than only in your shell history.
Common requirements include:
DATABASE_URLfor database-backed modules.BETTER_AUTH_SECRETandBETTER_AUTH_URLfor Better Auth.- Clerk secret and publishable keys for Clerk.
AUTH_SECRETfor NextAuth.
Dependencies install with the wrong package manager
The selected package manager is recorded in nextron.config.ts. Run its install command from the generated project root, or update the recorded packageManager before using nextron add.
A generated file already exists
nextron add does not overwrite existing files. It prints the skipped destination so you can merge the new module template manually without losing project changes.
The app builds but authentication warns about a secret
Production compilation can complete without runtime secrets, but the deployed application still validates its environment when it starts. Set real secrets in the deployment platform before serving traffic.