npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2023 – Pkg Stats / Ryan Hefner




Generic eslint configuration for web development - ESLint Shareable Config





Build Status

Quick start

  1. Install the following dev-dependencies:

    yarn add -D \
      @benjaminsimode/eslint-config-benjamin \
      eslint \
  2. Extend the @benjaminsimode/eslint-config-benjamin config in your .eslintrc (or eslintConfig key in your package.json):

    "eslintConfig": {
      "extends": "@benjaminsimode/eslint-config-benjamin"
  3. Specify the version of Node.js your project uses by setting .engines.node in your package.json.

    "engines": {
      "node": ">=8"
  4. Run eslint on your project as part of your lint:js scripts:

    "scripts": {
      "lint:js": "yarn run eslint --cache --ext .js --ignore-path .gitignore ./resources/",


The "Quick start" above exemplifies usage of this package with standard Node.js code.

Depending on the ECMAScript version of your code, whether you are using non-standard syntax like Flow and React's JSX, or other considerations, you may want to extend a variety of configurations provided by this package. @benjaminsimode/eslint-config-benjamin exposes several configurations targeting specific ESLint plugins, each named after the plugin it targets.

To use each plugin-specific configuration, you'll need to do the following:

  • Install as dev-dependencies @benjaminsimode/eslint-config-benjamin, eslint, and any plugins that are used by the configuration(s) you are extending, such as @benjaminsimode/eslint-plugin-node or @benjaminsimode/eslint-plugin-promise.

  • Add the configuration(s) you are using to the "extends" array in your project's ESLint configuration, like this:

      "extends": [

Plugin-specific configurations

With Prettier

If you are using Prettier to format your JS, install eslint-config-prettier and add it at the end of your "extends" array. It will turn off all ESLint rules related to the code-style preferences that Prettier already addresses.