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

@rpappa/create

v0.3.2

Published

Personalized TypeScript project template, includes the following:

Readme

@rpappa/create

Personalized TypeScript project template, includes the following:

  • TypeScript
  • Opinionated linting / formatting
  • Testing, with vitest
  • Monorepo support with npm workspaces

Usage

From the directory where you want package.json to be, run npm init @rpappa

To pass arguments use npx @rpappa/create [args] or npm init @rpappa -- [args]

If an arugment is not specified the CLI will prompt for it. Allowed arguments:

  • --yes or -y will pass through to initial npm init if ran
  • --monorepo or -m will create a monorepo
  • --scope= (ex --scope=@foo) will use the specified scope when creating packages
  • --workspace=[package] (ex --workspace=packages/foo) or -w [package] will define a new workspace at the specified path. This allows for re-running the script after project creation to initialize a new workspace.

For example:

npx @rpappa/create -y -m --scope=@foo

This will produce a monorepo with scope @foo without any intervention.

Or

npx @rpappa/create -w packages/newLib

To create a new workspace after the first npm init.

You may even want to npm i -D @rpappa/create after setting up a project, so further uses via npx have their version controlled by the root package.json.

Goals

Goals for this project:

  1. Reduce setup time for personal TypeScript projects
  2. Get more in the habit of using linting and testing for personal projects

Long term I'd like to migrate the TypeScript and eslint configs to their own packages, but this will do for now.