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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@giansandoval/screaming-arch

v0.1.0

Published

CLI tool to generate feature-first project structures inspired by Screaming Architecture.

Readme

@giansandoval/screaming-arch

A TypeScript CLI to generate feature-first project structures inspired by Screaming Architecture and Clean Architecture.

The goal is simple: your project structure should scream the business domain first, not the framework.

Links

Installation

Run it directly with npm:

npx @giansandoval/screaming-arch create auth

Or install it globally:

npm install -g @giansandoval/screaming-arch
screaming-arch create products

Usage

screaming-arch create <feature-name>

Examples:

screaming-arch create auth
screaming-arch create products
screaming-arch create orders
screaming-arch create payments

Generated structure

src/
  features/
    auth/
      domain/
        entities/
          Auth.ts
        repositories/
          AuthRepository.ts
        usecases/
          GetAuthUseCase.ts
      application/
        dtos/
          AuthDTO.ts
        services/
          AuthService.ts
      infrastructure/
        datasources/
        repositories/
          AuthRepositoryImpl.ts
      presentation/
        components/
        hooks/
          useAuth.ts
        screens/
      index.ts

Example

npx @giansandoval/screaming-arch create auth

Generates:

src/features/auth

with domain, application, infrastructure, and presentation boundaries already separated.

Why Screaming Architecture?

Screaming Architecture makes the business capability visible from the top-level structure. Instead of organizing code around tools, frameworks, or delivery mechanisms, each feature owns its domain model, use cases, adapters, and presentation pieces.

This keeps the feature easy to scan, test, replace, and evolve as the project grows.

Commands

screaming-arch --help
screaming-arch -h
screaming-arch create <feature-name>

Feature names are normalized to kebab-case:

screaming-arch create user-profile
screaming-arch create "user profile"
screaming-arch create UserProfile

Publishing

Build and test before publishing:

npm run build
npm test

Publish the package publicly under the @giansandoval scope:

npm login
npm publish --access public

License

This project is released under the MIT License.