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

reactive-rx-redux-js

v1.2.5

Published

Rx-based Redux implementation.

Downloads

17

Readme

reactive-rx-redux-js

License: MIT npm version Build Status Coverage Status

Rx-based Redux implementation, inspired by https://github.com/Holmusk/HMReactiveRedux-iOS.git.

Rx store

The first implementation of the store is the RxStore, which can be accessed with:

ReduxStore.Rx.create(...reducers: Observable<RxReducer<any>>[]);

In order to use this store, we define BehaviorSubject instances as action creators, as follows:

let action1 = BehaviorSubject<number>(0);
let action2 = BehaviorSubject<string>('');
let action3 = BehaviorSubject<boolean>(false);

Then map these BehaviorSubject objects to emit RxReducer whose type signature is as follows:

type RxReducer<T> = (state: State.Type<T>): State.Type<T>;

Which is a function to be called when new value arrives for a stream. A sample setup is as follows:

let pureReducer1: (state: State.Type<any>, value: any) => State.Type<any> = v => {
  return v.updatingValue('a.b.c', value);
};

let reducer1: Observable<RxReducer<any>> = action1.map(v => {
  return (state: State.Type<any>) => pureReducer(state, v);
});

let reducer2 = ...;
let reducer3 = ...;

let store = new reduxstore.rx.Self(reducer1, reducer2, reducer3);
let wrapper = store.toWrapper();

wrapper.numberAtNode('a.b.c').pipe(doOnNext(console.log)).subscribe();

action1.next(1);
action2.next(2);
action3.next(3);

Every time the Subject pushes a value, it will be pushed onto the state stream and used to compute the next state.

Dispatch store

The second implementation is the same as normal Redux store, whereby the store is responsible for dispatching actions.