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

@matthewbub/init-formatters

v0.2.0

Published

Scaffold a repo onto the @matthewbub/toolshed ESLint + Prettier configs: patches package.json and writes the config files, predictably and idempotently.

Readme

@matthewbub/init-formatters

Scaffold a repo onto the @matthewbub/toolshed ESLint + Prettier configs. It patches your package.json and drops the config files needed to consume the toolshed presets — predictably and idempotently. It does not run an install.

Run it

pnpm dlx @matthewbub/init-formatters --preset vite
# or: npx @matthewbub/init-formatters --preset vite

By default it targets ./package.json. Pass a path (file or directory) to target another:

pnpm dlx @matthewbub/init-formatters ./apps/web/package.json --preset next

[!NOTE] The bare npm init @matthewbub/… / pnpm create @matthewbub/… shorthand resolves to a create--prefixed package name, so use the dlx/npx form above.

Options

init-formatters [options] [packageJsonPath]

  packageJsonPath       target package.json, or a directory containing one (default: package.json)
  --preset <preset>     ESLint preset: base | react | vite | astro | next | hono | storybook (prompted if omitted)
  --no-prettier-ignore  do not write a .prettierignore
  -y, --yes             non-interactive; requires --preset
  -f, --force           overwrite existing config files
  -V, --version         print version
  -h, --help            print help

When --preset is omitted (and not --yes), you're prompted to pick one. When a config file already exists, you're asked before overwriting unless --force (or skipped under --yes).

What it does

  • package.json scripts — adds lint, lint:fix, format, format:check (existing scripts are left as-is).

  • package.json devDependencies — adds @matthewbub/toolshed, eslint, prettier as exact pins matching the toolshed version + catalog this CLI was built against.

  • package.json "prettier" — set to @matthewbub/toolshed/prettier-config (left as-is if already present).

  • eslint.config.mjs — wires the chosen preset, e.g.:

    import {vite} from "@matthewbub/toolshed/eslint-config/vite";
    
    export default vite({tsconfigRootDir: import.meta.dirname});
  • .prettierignore — common build/generated globs (skip with --no-prettier-ignore).

Re-running is safe: existing scripts, dependencies, and the prettier field are never clobbered, and existing config files are skipped unless --force.

Afterward, install the new devDependencies (pnpm install, or npm/yarn).

Extending

Each capability is a self-contained, idempotent Step (src/steps/*) listed in src/commands/init.ts. Adding a new one (a tsconfig.json, a CI workflow, a .gitignore) is a new module appended to that list.