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 🙏

© 2024 – Pkg Stats / Ryan Hefner

redux-elm-subscriptions

v0.6.0

Published

A tiny, zero-dependency package to listen to global events in an Elm Architecture manner.

Downloads

2

Readme

Redux Elm Subscriptions

Listen to global events Elm Style.

npm i -S redux-elm-subscriptions

Why?

When creating components you most likely wanna keep your components dumb and not use lifecycle hooks which couples rendering to functionality. This package revolves around the idea that some of the events you listen to are global and come from a world "outside" of your application like:

  • global mouse events
  • timers and animation frame callbacks
  • window focus and blur etc.
  • listening to websocket messages

So instead of this in a component file ...

componentDidMount() {
  document.addEventListener('keydown', handlekeyDown);
}


componentWillUnmount() {
  document.removeEventListener('keydown', handlekeyDown);
}

you can do this in a central place in your code ...

import { createSubsriptions, subNone } from 'redux-elm-subscriptions';

...

// will be called every time the state changes
const mapStateToSubs = (state, dispatch) => {

  // each subscription function needs to set up the subscription and return
  // a function to unsubscribe
  const arrowKeysSub = () => {
    const handler = e => {
      if (e.keyCode === 32) {
        dispatch({ action: 'SPACE_PRESS' });
      }
    };
    document.addEventListener('keydown', handler);
    return () => {
      document.removeEventListener('keydown', handler);
    };
  };

  const listenToClicks = () => {
    const handler = () => { dispatch({ type: 'DOCUMENT_CLICK' }); };
    document.addEventListener('click', handler);
    return () => { document.removeEventListener('click', handler); };
  };

  // return an object of subscriptions
  return {
    arrowKeys: arrowKeysSub,
    anotherSubscriptions: () => {
      // subscribe here
      return () => {
        // unsubscribe here
      };
    },
    // only listen to clicks when the modal is open
    documentClick: state.modalOpen ? listenToClicks : subNone,
  };
};

// add them to the store
store.subscribe(createSubscriptions(store)(mapStateToSubs));

Also check out the example.

Some Details

The API is designed so you can control listening behavior based on your state. Your subscription function receives the state and dispatch as parameters and should start listening to some event in the world. After that it needs to return a function to unsubscribe from the event you just started listening to. The function will be called every time the state changes. If a subscription is no longer present in the returned object, the unsubscribe function will be called automatically.

As long as yo make sure that your functions return functions to unsubscribe, everything should be handled automatically for you.

What not to use it for?

This lib was build to listen events which happen outside the scope of your app. Don't use it for one-time things are things that involve performing other work. Those will be better served by a library like redux-loop. Examples that are not subscriptions but effects include:

  • making http requests
  • reading from the localStorage

Also, of course the subscriptions are only for global events. DOM Events that happen within the virtual DOM that is managed by your app, should be handled directly in your components.

How does it work?

Check out the source. It's very simple, less than 30 LOC and needs no dependencies.