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




Add any path to node's require path





Part of the [nodeutils package]

Add any path to node's require path

Simple straightforward tool to allow you to require locally


Install the package via npm:

$ npm install @nodeutils/reqhere --save


Wherever you want to be a module root:


And everything from there down will be included.


│   yourApp.js
    │   index.js
    │   itemA.js
    │   │   itemA.js
    │   │   itemB.js
    │   │   ...
    │   index.js

If myModules/index.js is given: require("@nodeutils/reqhere")(); Then everything in that directory is added to the path, and the following will work from ANYWHERE in the application:

require("itemA"); //myModules/itemA.js
require("directoryA/itemA"); //myModules/directoryA/itemA.js
require("directoryA/itemB"); //myModules/directoryA/itemB.js
require("directoryB"); //myModules/directoryV/index.js

What if I want to add multiple paths?

Not an issue. Add require("@nodeutils/reqhere")(); as many times as you like, and it will append (both Unix and Windows tested).

Can I namespace?

You sure can, and it's a good idea too, so you can spot the difference between an installable module and a local one.

  1. Make yourself a folder called something like components.

  2. In there make a file called index.js containing

    "use strict"; require("@nodeutils/reqhere")();

  3. Add a folder inside components called, for example, app.

  4. Inside app put all your modules and files.

  5. Done! From anywhere you can now `require("app/someModuleYouMade");

Need more help, found a bug? Raise an issue