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

@starci/prettier-config

v1.0.3

Published

The one StarCi Prettier config: 120 columns, 4 spaces, no semicolons, double quotes, trailing commas everywhere.

Readme

@starci/prettier-config

The one StarCi Prettier config, for back end and front end. Prettier is the only formatter: the ESLint layout rules (indent, quotes, semi, object-curly-newline, array-element-newline, function-call-argument-newline) are removed from the canon and never come back.

{ "prettier": "@starci/prettier-config" }

Install it from the npm registry at the exact version in knowledge/hfs/canon-pins.yaml (see packages/README.md).

The choice

printWidth: 120, tabWidth: 4, semi: false, singleQuote: false, trailingComma: "all"; JSON, YAML and Markdown use 2 spaces.

None of the StarCi monorepo repositories carries a Prettier file today. Their layout came from ESLint: the largest back end enforces indent: 4, quotes: "double", semi: "never", and the front-end sources already follow the same four rules. The largest repository's dialect produces the smallest reformat diff. What changes is the one-binding-per-line imports and exports and the one-argument-per-line calls those ESLint rules forced; Prettier collapses them to the width. endOfLine is auto so a Windows checkout with core.autocrlf is not flagged.

Applying it to a large repository is one commit in a quiet window, listed in .git-blame-ignore-revs.