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

alley

v2.0.2

Published

action logger and effects library

Readme

alley

Tree-based action logger and effects library

Motivation

Reduxes middleware is popular and generic, but quite underpowered. Actions like making AJAX requests, connecting websockets, and setting cookies often need to be asynchronous. While you can do certainly do these things in Redux's middleware, it's flow is mind-bending because Redux's middleware is synchronous, so you need to internally re-dispatch to achieve asynchronous behavior.

Let's take some of the lessons we learned on the server with asynchronous http frameworks like Koa and make them compatible on the wider web using Promises. This will give us more powerful middleware to work with in the browser.

Example

const Alley = require('alley')
const { send, use } = Alley()

// root middleware for things like logging
use(async (action, next) => {
  console.log('->', action.type, action.payload)
  await next()
  console.log('<-', action.type, action.payload)
})

// any sort of http request specifc logging, timing, etc.
use('http', async (action, next) => {
  console.time('request')
  await next()
  console.timeEnd('request')
})

// perform a POST request
use('http:post', async (action, next) => {
  // ...
})

// perform a GET request
use('http:get', async (action, next) => {
  let res = await fetch(action.payload.url)
  action.payload.response = res
  await next()
})

// send an action
// steps: root -> http -> http:get -> http -> root
let action = await send('http:get', {
  url: 'http://google.com'
})

Install

npm install alley

Documentation

use([namespace], fn)

Create an action handler with an optional namespace.

The namespaces are arranged in a tree structure, separated by colons.

send(namespace|action, [payload])

Send an action down, then back up the tree. The flow is conceptionally similar to Koa, so understanding Koa's model would be a good place to start.

Send supports a couple different formats and automatically handles error types. For now, it's best to look at the tests for usage examples.

Send returns a Promise that will resolve after the flow completes or there's an error that's thrown.

Test

npm test

License

MIT