CNA Templates

This repository contains official templates and extensions for create-awesome-node-app.

Quick start

Browse templates and extensions on the official site, then scaffold locally:

# Interactive mode
npx create-awesome-node-app

# With template and extensions
npx create-awesome-node-app --template react-vite-boilerplate --addons material-ui zustand

Available templates

Template	Type	Use Case
React Vite	`react`	Frontend apps
Next.js	`nextjs`	Full-stack apps
NestJS	`nestjs-backend`	Backend APIs
Remix / React Router v7	`remix`	Full-stack apps
Astro	`astro`	Content sites
Hono	`hono`	Lightweight APIs
Turborepo	`monorepo`	Monorepos
WebdriverIO	`webdriverio`	E2E testing
WebExtension	`webextension-react`	Browser extensions

Documentation

File	Contents
docs/ARCHITECTURE.md	System overview, type system, generation flow
docs/AUTHORING.md	File conventions, EJS variables, `package/` system
docs/TESTING.md	Local testing and CI workflow
docs/MAINTENANCE_RUNBOOK.md	Operational procedures for maintaining templates, extensions, CI, dependencies, security, and releases
CONTRIBUTING.md	How to add templates and extensions

CI compatibility matrix

The badges above reflect the CI workflows:

Workflow	Trigger	Scope
Test Combinations	Push to `main`, PR, weekly	Randomized & full matrix of template × extension combinations
Smoke Test	PRs to `main`	Quick end-to-end validation of scaffolded projects

On push to main: a randomized subset of template × extension combinations
On every PR: a randomized subset + smoke test of scaffolded projects
Weekly (Sunday UTC): full matrix — every template with all compatible extensions

See the Actions tab for the latest run results.

For AI assistants: copy-paste to start a maintenance session

If you are an AI agent beginning work on this repository, paste the following prompt exactly (after reading any prior conversation context the user provides):

You are maintaining the Create-Node-App ecosystem: the `create-node-app` CLI monorepo and the `cna-templates` template/extension bank.

Follow the maintenance runbook at `docs/MAINTENANCE_RUNBOOK.md` and its companion guides (`docs/MAINTENANCE_TEMPLATES.md`, `docs/MAINTENANCE_DEPENDENCIES.md`, `docs/MAINTENANCE_SECURITY.md`, `docs/MAINTENANCE_CI.md`, `docs/MAINTENANCE_RELEASE.md`).

Always:
1. Run the pre-flight checklist in `docs/MAINTENANCE_RUNBOOK.md` Section 3 before changing code.
2. Start every significant task with a GitHub issue. If the solution is not obvious, use the issue to analyze options before writing code.
3. Scope work to one fix per PR with a `Closes #<issue>` link when applicable.
4. Open PRs as **ready for review** (not drafts) and wait for automated AI reviewers such as CodeRabbit to finish before merging.
5. Write commits, PRs, issues, and docs in English.
6. Validate locally with `file://` URLs before pushing (see `docs/MAINTENANCE_TEMPLATES.md` Section 9).
7. Run the relevant full CI workflow manually after risky merges and watch it to completion.
8. Update `knowledge/processes/create-node-app-maintenance.md` in the workspace if you discover a new pattern or decision.

Current known constraints:
- Storybook extension is pinned to `^8.6.18` with `legacy-peer-deps=true` in `extensions/storybook/.npmrc`; do not upgrade to Storybook v10 without resolving issue #161 first.
- The `test-combinations.yml` generator uses JS variables `repoDir` and `tplDir` unescaped; never prefix them with a backslash inside the heredoc.
- `create-node-app` releases use npm Trusted Publishing via OIDC; do not use a manual `NPM_TOKEN`.

If the user only says "continue" or asks "what should I do next", summarize the current CI/issues state and propose the next action.

cna-templates

Live repository statistics

README preview