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

rxsc

v0.6.0

Published

RxSC (ReactiveX State Container) uses the phenomenal RxJS library to provide a Redux-like state container, but with the power of RxJS. Thus the amount of boilerplate code required to get up and running is greatly reduced (see [example](#example)).

Downloads

12

Readme

RxSC

RxSC (ReactiveX State Container) uses the phenomenal RxJS library to provide a Redux-like state container, but with the power of RxJS. Thus the amount of boilerplate code required to get up and running is greatly reduced (see example).

Add-ons

Installation

With npm

$ npm install --save rxsc

With yarn

$ yarn add rxsc

Terms

Since some concepts of Redux has been merged, or does not translate directly we use some different terms for RxSC.

Transformer

A transformer takes care of mapping actions to state changes. You define both the action and its effect on the state in the transformer unlike Redux, where this is separated into actions, action creators and reducers.

The Transformer class constructor takes three arguments Transformer(name: string, initialState: any, transforms: Function).

  • name scope name of the transformer, will be the key for the transformer's state
  • initialState the initialState of the transformer before any action has been performed
  • transforms a function which takes an action creator and returns a list of transforms

Example

// transformer.js

import { Transformer } from 'rxsc';

export default new Transformer('counter', 0, action => [
    action('increment').map(amount => state => state + amount),
]);

Container

The Container class takes an array of Transformers and merges them into a single observable. It also provides a nice mapping of all the transformer actions under the container.actions$ object.

Example

// container.js

import { Container } from 'rxsc';
import counterTransformer from './transformer';

const container = new Container([counterTransformer]);

// performing actions
container.actions$.increment(1);

Example

Putting it all together, it might look something like this

import { Transformer, Container } from 'rxsc';


const transformer = new Transformer('count', 0, action => [
    action('increment').map(amount => state => state + amount),
    action('decrement').map(amount => state => state - amount),
]);

const container = new Container([transformer]);

container.subscribe(console.log);

container.actions$.increment(1);
container.actions$.increment(2);
container.actions$.decrement(2);

Which should give you the following output

{ count: 0 }
{ count: 0 }
{ count: 1 }
{ count: 3 }
{ count: 1 }