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

@10stars/config

v22.0.0

Published

Readme

@10stars/config

Shareable Configs

React Compiler rules (browser config)

react/globals, react/immutability, react/preserve-manual-memoization, react/refs and react/set-state-in-effect are off. They encode React Compiler semantics, and we build with Vite — nothing is auto-memoized, so render-time ref reads, idempotent module-scope caches and prop-ref writes are load-bearing house patterns rather than mistakes. preserve-manual-memoization reports that hand-written memoization stopped the compiler from optimizing, which cannot apply with no compiler in the pipeline — and hand-written useCallback/useMemo is required house style here.

react/purity stays on: an impure call during render is unstable under any build.

Install

  • Not intended for global installation
  • Use it as part of your project's devDependencies

Commands

Single-repository commands:

  • bunx config ts: typecheck one tsconfig.json in watch mode.
  • bunx config typecheck: typecheck one tsconfig.json once.
  • bunx config lint: format and lint one repository.

Run these commands from a parent directory containing repositories as immediate children:

  • bunx config tsAll: watch the root and immediate-child tsconfig.json files in one TypeScript build process. The latest complete cycle is written atomically to .typecheck-diagnostics.json. TypeScript build caches are stored under each project's ignored node_modules/.cache directory.
  • bunx config typecheckAll: typecheck the same projects once in one TypeScript build process.

Oxfmt and Oxlint discover nested tool configs. Child repository VCS ignore files are not guaranteed to apply from the parent process. Put required Oxfmt exclusions in formatIgnore of the repository's 10stars.config.ts (prepare regenerates .oxfmtrc.json from them) and Oxlint exclusions in .oxlintrc.json.

prepare writes a .husky/pre-commit that runs bun fmt --staged. List generated files a commit must not take stale (e.g. screenshot baselines) in generatedPaths of 10stars.config.ts, as git pathspecs, and the hook also blocks a commit when one of them changed after it was staged.