npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

make-ca

v1.0.10

Published

CLI tool for generating Clean Architecture templates for NestJS & TypeORM

Readme

make-ca

A powerful CLI tool that generates a complete Clean Architecture boilerplate for NestJS projects with TypeORM integration. Designed to accelerate your development workflow by automating the creation of properly structured TypeScript code following Clean Architecture principles.

What is Clean Architecture?

Clean Architecture is a software design philosophy that separates concerns into distinct layers, making your codebase more maintainable, testable, and adaptable to change. The layers include:

  • Domain Layer: Contains business logic, entities, and interfaces
  • Application Layer: Orchestrates the flow of data between domain and infrastructure
  • Infrastructure Layer: Handles external concerns like databases, frameworks, and external services

Features

  • Project Scaffolding: Initialize a complete NestJS project with proper Clean Architecture structure
  • Entity Generation: Create fully-featured entities with all necessary layers:
    • Domain layer (entities, repositories, use cases, exceptions)
    • Service layer (use case implementations)
    • Infrastructure layer (TypeORM entities, mappers, repositories)
    • Application layer (controllers, DTOs, modules)
  • Selective Generation: Skip specific layers based on your needs
  • Convention Enforcement: Follows Clean Architecture best practices
  • TypeORM Integration: Built-in database access patterns
  • Dependency Injection: Proper DI setup with NestJS modules
  • API Documentation: Auto-generated Swagger endpoints
  • Type Safety: Fully typed TypeScript implementation

Installation

# Install globally
npm install -g make-ca

# Or use directly with npx
npx make-ca <command>

Quick Start

Initialize a new project

# Create a new project
npx make-ca init -p my-clean-app

# Or initialize in the current directory
npx make-ca init

Generate an entity

# Generate in the current directory
npx make-ca generate product

Selective Generation

# Skip specific layers
npx make-ca generate order --skip-domain
npx make-ca generate customer --skip-infrastructure
npx make-ca generate category --skip-application

# Generate only specific layers
npx make-ca generate invoice --only-domain
npx make-ca generate payment --only-infrastructure

Project Structure

The generated project follows a clean architecture pattern:

src/
├── core/
│   ├── domain/         # Business logic, entities, interfaces
│   │   └── user/       # Domain layer for 'user' entity
│   ├── shared/         # Shared code across entities
│   │   ├── type/       # Common types
│   │   ├── exception/  # Base exceptions
│   │   └── util/       # Utilities
│   └── service/        # Use case implementations
│       └── user/       # Service layer for 'user' entity
├── infrastructure/
│   └── persistence/
│       └── typeorm/    # TypeORM implementation
│           └── feature/
│               └── user/ # TypeORM entities for 'user'
└── application/
    ├── api/
    │   └── rest/       # REST API controllers
    │       ├── shared/ # Shared API components
    │       └── user/   # Controllers for 'user' entity
    └── di/             # Dependency injection modules
        └── feature/
            └── UserModule.ts # DI module for 'user' entity

Entity Naming Rules

  • Entity names must be in kebab-case (e.g., user, blog-post)
  • Must be at least 3 characters long
  • Must start with a letter
  • Can only contain letters, numbers, and hyphens

Important Note

After generating a project, you need to create a config.yaml file based on the provided config.yaml.example template to ensure your project works correctly.

Once your project is running, you can test the API endpoints through Swagger documentation at /docs.

License

make-ca is MIT Licensed