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

shadyt-gen

v1.0.1

Published

CLI tool to scaffold Next.js and .NET project structures.

Readme

npm version license .NET Build

shadyt-gen

CLI tool to scaffold Next.js and .NET project structures.

Installation

npm install -g shadyt-gen

Usage

Basic Command Structure

shadyt-gen <next|dotnet> [options]

Options (for both next and dotnet)

  • -a, --all     Enable all features and use sensible defaults (no prompts)
  • -p, --path <path>     Path to create/find the project directory (default: current directory)
  • -n, --name <name>     Name of the project (used for folder creation or lookup)

Example: Scaffold a Next.js Project with All Features

shadyt-gen next -a -p C:\Projects -n MyNextApp

Example: Scaffold a .NET Project with All Features

shadyt-gen dotnet -a -p C:\Projects -n MyDotnetApp

Interactive Mode (Prompt for Each Option)

If you omit -a, shadyt-gen will prompt you for each feature:

shadyt-gen next -n MyNextApp
shadyt-gen dotnet -n MyDotnetApp

Help

shadyt-gen --help
shadyt-gen <next|dotnet> --help

Features & Generated Files

Next.js

  • App directory structure (app/, components/, lib/, etc.)
  • Optional: MDX, NextAuth, Prisma, Tailwind CSS
  • Database setup (Postgres, with sensible defaults if -a is used)
  • .env, config, and utility files

.NET

  • Layered solution structure (Controllers, Models, Services, Data, etc.)
  • General-use enums (StatusCode, UserRole)
  • Response classes (BaseResponse, ErrorResponse, SuccessResponse, ItemResponse, ItemsResponse)
  • IResponse interface
  • Sample controllers (AIModelsController, AuthController, HealthController, VersionedController)
  • Sample unit tests (Xunit)
  • .editorconfig, .gitignore, Dockerfile, docker-compose.yml (if Docker enabled)
  • Docs/Swagger/swagger.json (starter OpenAPI spec)
  • .github/workflows/dotnet.yml (GitHub Actions CI)
  • .prettierrc (for JS/TS formatting)

Customizing Swagger UI (for .NET projects)

A starter swagger.json is generated in Docs/Swagger/. You can:

  • Edit this file to document your API endpoints.
  • Use the Swagger Editor for a visual interface.
  • In your .NET project, ensure Swagger is enabled (see Extensions/SwaggerServiceExtensions.cs).
  • To customize the UI, edit the UseCustomSwagger method or add options in SwaggerServiceExtensions.cs.

For more, see: Swagger/OpenAPI docs.


Docker & Docker Compose

If Docker is enabled, a Dockerfile and docker-compose.yml are generated for API + Postgres orchestration.


GitHub Actions

A starter workflow is generated at .github/workflows/dotnet.yml for .NET CI/CD.


Release Process

A helper script is provided at scripts/release-helper.ps1 to:

  • Show the current published NPM version and git tags
  • Walk you through git add, commit, tag, push, and npm publish

Run in PowerShell:

pwsh scripts/release-helper.ps1

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Submit a pull request

License

MIT