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

saasblast

v1.1.0

Published

SaaSBlast CLI to scaffold SaaS projects for maximum development speed

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

pixtanepixtane

Keywords

Readme

SaaSBlast CLI (packages/cli)

The saasblast CLI scaffolds a new SaaS app from curated templates and optional features.

Installation

Global install (after publish):

npm i -g saasblast

Usage

npx saasblast@latest

or (if you have saasblast in your PATH)

saasblast

Options:

  • --name <string>: Project name (folder will be created if needed)
  • --dir <path>: Target directory (defaults to the project name)
  • --apiKey <string>: SaaSBlast API key (aliases: --apikey, --api-key)
  • Feature flags:
    • --trpc
    • --drizzle
    • --biome
    • --eslint-prettier
  • --help: Show help

You can pass feature flags to skip the interactive prompts for the corresponding choices. If any feature flags are provided, the linter defaults to Biome unless you explicitly pass --eslint-prettier.

API key resolution order: flag → SAASBLAST_API_KEY environment variable → saved config → prompt. When provided or entered, your API key is saved to a per-user config file so future runs won’t ask again.

The CLI will:

  1. Verify your API key against the SaaSBlast site
  2. Scaffold the base template
  3. Prompt for and apply optional features (tRPC, Drizzle, lint/format)
  4. Optionally initialize git and run npm install

Features

  • trpc: Adds tRPC wiring
  • drizzle: Adds Drizzle ORM and example schema
  • biome | eslint-prettier: Lint/format presets

How templates resolve

Locally, the CLI first tries to resolve @saasblast/templates from node_modules. If not present, it falls back to the monorepo path packages/templates/templates. When running against production, it downloads feature tarballs from the SaaSBlast site.