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

tide-fire-namespace-middleware

v0.0.1

Published

Namespace middleware for tide-fire

Readme

Tide Fire Namespace middleware

What?

Middleware for tide-fire that allows for namespaced action handlers.

Why?

For some applications it's natural to separate different parts of the app into namespaces. Since tide-fire is built specifically for large apps, it makes sense to also support namespaces.

How?

Install by adding tide-fire-namespace-middleware to your middleware array when you init fide-fire.

import namespaceMiddleware from 'tide-fire-namespace-middleware'

/*
Assume the following state shape:
const state = {
  bar: {
    beer: 'Singha',
  },
  weather: 'Rainy',
}
*/

init(tide, actionHandlers, [namespaceMiddleware])

If you want to set a namespace for a set of action handlers, define a __namespace prop on that part of the actionHandlers object.

const actionHandlers = {
  bar: {
    setBeer: (data, {get, set}) => set(['beer'], data),
    __namespace: ['bar'],
  },
}

In the example above, set(['beer', data]) will set data on the path ['bar', 'beer']. Similarly, get(['beer']) would get from ['bar', 'beer'].

Action handlers also have access to getGlobal and setGlobal functions.

const actionHandlers = {
  bar: {
    getWeather: (_, {getGlobal}) => getGlobal(['weather']),
    setWeather: (data, {setGlobal}) => setGlobal(['weather', data]),
    __namespace: ['bar'],
  },
}

Reporting issues

Issues should be filed here on github.