StartXKit docs

Roadmap

What StartXKit supports today and what is planned next.

StartXKit is focused on a TypeScript backend scaffolding MVP. The current goal is to make the generated projects predictable, easy to inspect, and useful as a starting point for real APIs.

Available Now

  • Interactive project creation with npm create @startxkit@latest
  • Framework choices: Express, Fastify, Hono
  • Architecture choices: minimal, modular, layered
  • Generated health endpoint
  • API prefix configuration
  • Module generation with npx @startxkit/cli add module
  • Module layer choices:
    • Route + Controller
    • Route + Controller + Service
    • Route + Controller + Service + Repository
    • Full
  • Optional CORS setup
  • Optional env config
  • Optional Zod validation dependency
  • Optional Pino logging
  • Optional error handler
  • Optional dependency injection wiring
  • Optional Vitest setup
  • Optional Docker files
  • Package manager selection: pnpm, npm, yarn, bun
  • Project commands: doctor and info

Not In The MVP

These are intentionally not part of the current MVP:

  • Authentication
  • Database setup
  • ORM setup
  • JavaScript templates
  • GraphQL
  • WebSockets
  • gRPC
  • Deployment templates

Keeping these out of the MVP makes the generated projects smaller and easier to understand.

Planned Areas

AreaPossible additions
AuthenticationJWT, sessions, OAuth starter flows
DatabasesPostgreSQL, MySQL, SQLite, MongoDB
ORMsDrizzle, Prisma
API docsOpenAPI or Swagger generation
More runtimesServerless and deployment templates
More languagesJavaScript templates

Design Principle

StartXKit should generate code that developers can understand on day one.

That means new features should not only add files. They should also preserve clear folder structure, readable generated code, and working TypeScript checks.

Have a feature request? Open an issue on GitHub.