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

@shanedg/trshcmpctr

v1.0.0

Published

All build config, no substance.

Readme

trshcmpctr

Build Status

"all build config, no substance"

Install

Prefer to install from the lockfile.

npm ci

Build

Build the project in development mode.

npm run build

Build the project with production optimizations applied.

npm run build:production

Start

Start webpack-dev-server to serve the project, in-memory. Launch project in browser. Watch files, rebuilding and reloading incremental changes.

npm start

Watch

Build the project in development mode and watch files, rebuilding incremental changes.

npm run watch

Lint

Lint JavaScript files with ESLint.

npm run lint

A Note on Choice of ESLint Parser

This project compiles TypeScript with Babel, not the TypeScript compiler. Babel discards all type information during transpilation but supports a wider range of syntax than the TypeScript compiler. For this reason, we use the babel-eslint parser instead of the parser provided by @typescript-eslint. For more context, see What about Babel and babel-eslint:

The key trade-off can be summarized as: babel-eslint supports additional syntax which TypeScript itself does not, but typescript-eslint supports creating rules based on type information, which is not available to Babel because there is no type-checker.

Test

Run Jest tests.

npm run test

Type Check

This project compiles TypeScript with Babel, not the TypeScript compiler. For additional context, see the note on choice of ESLint parser above.

Run tsc against the project's TS files to catch type errors.

npm run type-check

TODO

  • Add styles, CSS and some preprocessor
    • Add linting for styles
  • Add auto versioning via conventional commits
    • Also publishing for fun? via Github actions maybe?
  • React strict mode
  • Acceptance tests
  • E2E tests