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 🙏

© 2025 – Pkg Stats / Ryan Hefner

ploader

v2.0.1

Published

Plugin Loader - Dynamically requires plugins from a directory when their source code has been updated

Readme

PLoader

This project is a dynamic plugin loader module for node.js

Originally written for an IRC bot

It allows a directory of plugins to be reloaded on code change, or when files are added or removed. Below is an example of usage:

var fs = require('fs');
var ploader = require('ploader');

var plugins = {};
var loader = ploader.attach('./plugins', {
    add: function(plugin, file) {
        plugins[file] = plugin;
        console.log('Loaded plugin:', file);
    },
    read: function(plugin, file) {
        // Reread callback
        plugins[file] = plugin;
        console.log('Reread plugin:', file);
    },
    remove: function(file) {
        // Remove plugin on deletion
        delete plugins[file];
        console.log('Unloaded plugin:', file);
    },
    error: function(file, e) {
        console.log('Error in plugin:', file, e);
    }
});

// Reload with watch, or manually
fs.watch('./plugins', function() {
    loader.reload();
});

Now the plugin hash can be used async and will always contain fresh plugins

Changes

The fs.watch api is ridiculously buggy which forced me to remove it from the module, opting to instead have an option to rescan the plugins manually. At least this way is slightly more reliable than watching every file.

You will now have to keep the loader closure somewhere to be able to call reload on it