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

shazamjs-core

v1.0.0

Published

Creates a socket.io application to communicate across all applications.

Readme

shazamjs-core

Each client establishes a connection to this socket server, any client can connected to the server as it is not password protected.

Client Implementation

Clients need to handle the following events emitted by the server:

socket-client.on("Refresh!", (currentAppState) => {//Handle the current appState});

On "Refresh!" the app state is transmitted to the client to update itself.

socket-client.on("Transform!", (currentAppState) => {//Handle the current appState});

On "Transform!" the app state is transmitted to the client to update itself, but it is expected the client does something special to signify the app state is changing state between Billy and Shazam.

Clients should emit the follow information to the server:

socket.emit("Shazam!", {location: "A location string"})

Client tells server someone has clicked Shazam a long with the current location of where the event occured.

socket.emit("Who am I?")

Client requests the server send the current state. The server only broadcasts the state via the Refresh event. The server only broadcasts the Refresh event to the current socket, not globally.

Server Implementation

The server handles the following events:

socket.on("Who am I?", () => { //emit "Refresh Event!"});

Emit a Refresh event only to the current socket that emitted the "Who Am I?" event.

socket.on("Shazam!", () => { //update the app state then emit "Transform!"});

The server increments the proper app state based upon the location string sent.

Possible Location Strings

"coreApp", "websiteApp", "desktopApp", "hardwareApp", "consoleApp", "mobileApp"