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

woolly

v0.6.9

Published

A tool for building and using simple node.js backends

Readme

woolly

A tool for building and using simple node.js backends.

The basic idea comes from an observation that most of the screens I write in my apps can be broken down into:

  1. state
  2. actions on that state

Given the above, I sought to find the simplest interface that would suffice.

To that end, Woolly has two parts. WoollyClient and WoollyServer.

Example Usage

server.js

// Woolly Server
const app = require('express')()
const server = app.listen(3000)

let w = WoollyServer(server)

// This example stores all messages in an in memory map of topicName => [messages...]
let messages = {}

const route = '/topics/:topic'
const getState = ({topic}) => messages[topic] || []
const actions = {
  addMessage: (message) => {
    // Modify the state
    messages[topic] = (messages[topic] || []).concat([message])
  }
}

w.handler(route, getState, actions)

client.js

const WoollyClient = require('woolly/lib/WoollyClient.js')

const client = WoollyClient('/topics/testing', (messages) => {
  //Update the view here
  console.log('topic messages:', messages)
})

client.actions.addMessage({text: `Tick ${new Date()}`})

WoollyServer

API

WoollyServer(server)

Returns a WoollyServer attached to the HTTP server.

WoollyServer.handler(route, getState, actions) : WoollyServer

Makes a resource available at the given route. When a client connects to it, they start receiving its current state as determined by calling getState()

actions is a map of action names to handler functions. After an action is completed, the state is considered updated, and all connected clients will receive the new state.

WoollyClient(uri, onChange) : WoollyClient

Generates a WoollyClient and connects it to the uri provided. When a state change occurs, the onChange handler will be called.

WoollyClient.do(action, params = {}) : Promise

Sends a request for the server to perform the action with the provided params (if any)

WoollyClient.actions.ACTION_NAME(params = {}) : Promise

Each action defined in the server is available by name here and can be invoked.

WoollyClient.on(event:string, callback:function)

Allows clients to register for the events 'ready', 'connected', 'disconnected', and 'error'. Until the ready event is fired, the actions map will be empty.

WoollyClient.disconnect()

Disconnects the client from the WoollyServer