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

@hackthedev/socket-tools

v1.0.4

Published

This small and awesome library was made to simplify a basic socket.io setup by using an existing express server. In this example the express server will be setup with the [express-starter](#) library. The library will scan a directory for files that inclu

Readme

Socket Toolbox

This small and awesome library was made to simplify a basic socket.io setup by using an existing express server. In this example the express server will be setup with the express-starter library. The library will scan a directory for files that include socket.io handlers to keep everything modular without pain. Files inside the scanned directory that do not have the required socket handler block will fail to load and cause an error.

import ExpressStarter from "@hackthedev/express-starter"
import SocketTools from "@hackthedev/socket-tools"

// express setup
let starter = new ExpressStarter()
starter.registerErrorHandlers();
starter.registerTemplateMiddleware();
starter.app.use(starter.express.static(starter.dirname + "/public"));
starter.startHttpServer(5000);

// Socket.io Setup
let socketTools = new SocketTools({expressHttpServer: starter.server});
socketTools.listen();

Setting up socket events

On default the socket library will recursively scan for .mjs files inside the ./modules/sockets folder relative from what process.cwd() returns. These files at a very minimum are required to have this structure:

export default (io) => (socket) => {
    socket.on('hello', function (data, response) {
        response({ error: null, message: "Hi " + data.name })
    });
}

You can define multiple socket events and even functions inside or outside of the required export default (io) => (socket) => {} block. You can do literally anything as long as the required block is present, because otherwise it will abort loading that file and logging it as error.

function getLeftMessage(){
    return ", have a great time!";
}

export default (io) => (socket) => {
    socket.on('hello', function (data, response) {
        response({ error: null, message: "Hi " + data.name })
    });
    
    socket.on('bye', function (data, response) {
        response({ error: null, message: "Bye " + data.name + getLeftMessage() })
    });
}

Custom sockets directory

You can also specify a custom directory path to scan that for files instead. The default will always be path.join(process.cwd(), "modules/sockets")

let socketTools = new SocketTools({expressHttpServer: starter.server, modulesDir: path.join(process.cwd(), "sockets")});

Non-socket files in scan directory

If you have files inside the "scan directory" aka modulesDir then you can add the following line to the file to avoid the socket toolbox from reporting errors: export default (io) => (socket) => {}

By leaving it empty it wont have any real effect and avoids errors and possible crashes.