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

saas-init

v1.1.0

Published

CLI scaffolding tool that generates production-ready SaaS projects with Next.js, auth, payments, database, and email — configured and ready to ship.

Readme

saas-init

npm version npm downloads CI License: MIT Node.js >= 18

CLI scaffolding tool that generates production-ready SaaS projects on top of Next.js.

Install

npm install -g saas-init

Or use directly without installing:

npx saas-init init

Usage

saas-init init

The CLI walks you through a short prompt sequence:

  1. Project name (lowercase, npm-valid, e.g. my-app)
  2. Output directory (default: ./<project-name>)
  3. Auth provider
  4. Database
  5. Payments (optional)
  6. Email (optional)
  7. Summary — confirm before any files are written

After confirming, saas-init generates the project files and optionally runs pnpm install in the output directory.

What's Included

Every generated project comes with:

  • Landing Page: Production-ready landing page with multiple sections (hero, problem agitate, value proposition, social proof, transformation, CTA, footer). Fully customizable via template variables.
  • Docker: Pre-configured Dockerfile and docker-compose.yml for easy containerization.
  • GitHub Actions: Automated CI workflow for testing and linting on every push and PR.

Supported Stack Options

| Category | Options | |-----------|-------------------------------------| | Auth | Clerk, NextAuth, Supabase Auth | | Database | Postgres (Drizzle), SQLite (Drizzle), Supabase | | Payments | Stripe, Lemon Squeezy, None | | Email | Resend, Postmark, None |

Adding a New Provider

  1. Add templates under templates/<category>/<provider>/. Use {{key}} placeholders for variables that come from ProjectConfig.

  2. Create a generator at src/generators/<category>/<provider>.ts that exports:

    export async function generate(config: ProjectConfig, outDir: string): Promise<void>

    Inside it, use the file utilities to copy templates and merge dependencies:

    import path from 'path'
    import fs from 'fs-extra'
    import { writeTemplate, appendEnv } from '../../utils/files.js'
    import { mergeDeps } from '../../utils/deps.js'
    import { TEMPLATES_ROOT } from '../../utils/paths.js'
    
    const TEMPLATES_DIR = path.join(TEMPLATES_ROOT, '<category>/<provider>')
    
    export async function generate(config: ProjectConfig, outDir: string): Promise<void> {
      await writeTemplate(
        path.join(TEMPLATES_DIR, 'lib/client.ts'),
        path.join(outDir, 'lib/client.ts'),
        {}
      )
      const pkgPath = path.join(outDir, 'package.json')
      const pkg = await fs.readJson(pkgPath)
      pkg.dependencies = mergeDeps(pkg.dependencies ?? {}, { '<package>': '^1.0.0' })
      await fs.writeJson(pkgPath, pkg, { spaces: 2 })
      await appendEnv(outDir, { MY_API_KEY: '' })
    }
  3. Register the generator in src/generators/index.ts by adding it to the relevant map (e.g. authGenerators, databaseGenerators, etc.).

  4. Add the new value to the relevant union type in src/types.ts and the matching zod enum in projectConfigSchema.

  5. Add a prompt option in src/prompts/<category>.ts.

  6. Write tests in tests/generators/<category>/<provider>.test.ts following the patterns of existing generator tests.

Requirements

  • Node.js >= 18
  • pnpm (for generated projects)