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-reducer-effects

v2.0.3

Published

Redux enhancer which adds support for **managed effects** to the reducer, allowing you to return **side effects as data** in your reducer function.

Downloads

24

Readme

redux-reducer-effects

Redux enhancer which adds support for managed effects to the reducer, allowing you to return side effects as data in your reducer function.

Reducer

  • Pure function as before, returning state and tasks
  • Task: description of a side effect, to be ran by the task runner

(state: State, action: Action) => [State, Task]

Task runner

  • Impure function to perform all side effects for incoming tasks
  • Input: an Observable of tasks
  • Output: an Observable of actions for the enhancer to dispatch

(tasks$: Observable<Task>) => Observable<Action>

Example

See an example of what this looks like in practice.

Inspiration

redux-observable allows you to interpret incoming actions as a stream (Observable), performing side effects when the stream emits a new value and returning a stream of new actions to be dispatched (see “Epics”). The Observable interface makes it easy to manage complex asynchronous tasks without maintaining lots of internal state (e.g. debounce, cancellation).

In Elm, it is easy to reason about when and which new actions will be dispatched as a result of any asynchronous work by simply looking inside the reducer (also known as update) function, which returns a tuple of the next state and side effects to be ran (returned as data). In redux-observable, epics are provided to the store at initialisation along with the reducer, making it much harder to trace where and when asynchronous actions will be dispatched.

Last but not least, we wanted the ability to easily write declarative tests for all our business logic: when an action occurs, what should happen now (state) and what should happen next (tasks).

This is why we decided all business logic should have a single source of truth: the reducer.

Also:

Usage

TODO: Improve example using ping/pong

import {createEnhancer} from './enhancer';
import {createStore} from 'redux';

const enhancer = createEnhancer({
    createSubject: () => new Subject(),
    taskRunner,
})
const store = createStore(reducer, initialState, enhancer);

Development

npm install
npm run compile
# run local HTTP server against ./target dir, e.g. http-server CLI `http-server -c-1 ./target`
npm test