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

@glowing-fishstick/generator

v0.1.3

Published

CLI template generator for glowing-fishstick applications

Readme

@glowing-fishstick/generator

CLI tool for scaffolding new glowing-fishstick applications and APIs.

Installation

npm install -g @glowing-fishstick/generator

Usage

Interactive mode

fishstick-create

Prompts for project name, template type, description, port, git, and npm install.

With arguments

fishstick-create my-app
fishstick-create my-api --template api
fishstick-create my-app --port 8080 --no-install

Options

| Flag | Description | Default | | ------------------- | ----------------------------- | --------------------------- | | --template <type> | Template type: app or api | app | | --port <number> | Override default port | 3000 (app) / 3001 (api) | | --no-install | Skip npm install | runs install | | --no-git | Skip git init | runs git init | | --force | Overwrite existing directory | false | | --version | Show version | — | | --help | Show help | — |

Generated Output

App template (--template app)

my-app/
├── package.json
├── README.md
└── src/
    ├── server.js        — thin entrypoint
    ├── app.js           — plugin (routes + lifecycle hooks)
    ├── config/
    │   └── env.js       — config overrides
    ├── routes/
    │   └── router.js    — example route
    ├── views/
    │   ├── my-feature.eta
    │   └── layouts/
    │       ├── header.eta
    │       └── footer.eta
    └── public/
        ├── css/
        └── js/

Generated app uses @glowing-fishstick/app and starts on port 3000.

API template (--template api)

my-api/
├── package.json
├── README.md
└── src/
    ├── server.js        — thin entrypoint
    ├── api.js           — plugin (routes + lifecycle hooks)
    ├── config/
    │   └── env.js       — config overrides
    └── routes/
        └── router.js    — example route

Generated API uses @glowing-fishstick/api and starts on port 3001.

Local Development

# From the monorepo root
npm install

# Run a test scaffold (no install, no git)
node core/generator/bin/cli.js test-output --template app --no-install --no-git

# Verify the output
cd test-output && npm install && node src/server.js

When scaffolding into a directory inside this monorepo, generated package.json dependencies use local file: links to core/web-app, core/service-api, and core/shared so npm install works even before packages are published. Outside this repo, generated dependencies use semver ranges (for example ^0.1.0) against published @glowing-fishstick/* packages.