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 🙏

© 2021 – Pkg Stats / Ryan Hefner




Resolver for Lerna-based projects for eslint-plugin-import





eslint-import-resolver-lerna Build Status Built with GNU Make

This resolver can be used together with eslint-plugin-import package to help it find modules in your Lerna-based monorepo.

When you might need this

In general you might not even need this, since Lerna symlinks your monorepo packages into your node_modules directory where the resolver can pick it up using the standard Node.js resolution mechanism. You probably will need this if:

  • You compile your project with Babel, Flow, TypeScript or any other compilation pipeline
  • You compile your packages directory into a completely different directory, ie. from src/packages into dist/packages
  • You configure Lerna to do link your packages together in the dist/packages directory

This will cause your src/packages directory to not have node_modules folder, thus causing the plugin to be unable to find your other packages using the standard built-in Node.js module resolution mechanism. That's where this resolver will help you.

What this does

This plugin will look in your packages directory and generate a list of all the package names (as defined in their package.json files) that the monorepo contains. Then, when the import plugin tries to resolve any of those names it will be able to help the import plugin to locate the package.


This resolver accepts only one configuration option: packages (string or array of strings, required) which must be an absolute path to Lerna's packages directory or an array of such absolute paths.

// .eslintrc.js
const path = require('path')

module.exports = {
  settings: {
    'import/resolver': {
      'eslint-import-resolver-lerna': {
        packages: path.resolve(__dirname, 'src/packages')


See the LICENSE file for information.