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

rinter

v2.1.1

Published

Minimalist state container based on reactive extensions

Downloads

25

Readme

Rinter

Rinter is a minimalist state container based on reactive extensions.

Installation

yarn add rinter rxjs

Getting Started

Rinter is similar to Redux, MobX or Vuex: it handles the application state in a centralized and predictable way.

To get started we are going to follow the usual example of incrementing or decrementing a number (aka "Counter").

An immutable object describes the application state. And the actions generate a new instance of the application state:

Rinter represents this architecture with an object called Controller. A controller has a state property that returns the current state value. It also has methods to modify the state. The view is able to detect changes by the changes property.

Code (using the controller function):

const counter = controller({
  initialState: { count: 0 },

  mutators: {
    increment: state => ({ count: state.count + 1 }),
    decrement: state => ({ count: state.count - 1 }),
  },
});

const appCounter = counter();

appCounter.changes.subscribe(state => {
  // renderView is an example of how the view will respond to state
  // changes and send callbacks to update the state
  renderView(state, {
    onIncrementClick: appCounter.increment,
    onDecrementClick: appCounter.decrement,
  });
});

The controller function is a shortcut to write less code. If you prefer ES6 classes you can create a Controller by sub-classing DefaultController:

class Counter extends DefaultController {
  constructor(initialValue = { count: 0 }) {
    super(initialValue);
  }

  increment() {
    this.set({ count: this.state.count + 1 });
  }

  decrement() {
    this.set({ count: this.state.count - 1 });
  }
}

const appCounter = counter();

appCounter.changes.subscribe(state => {
  renderView(state, {
    onIncrementClick: () => appCounter.increment(),
    onDecrementClick: () => appCounter.decrement(),
  });
});

Controller Composition

As your application grows, you may want to compose multiple controllers into one. The compose function does that:

const twoCounters = compose({
  a: counter,
  b: counter,
});

const controller = twoCounters();
console.log(controller.state); // {a: {count: 0}, b: {count:0}}

controller.a.increment();
console.log(controller.state); // {a: {count: 1}, b: {count:0}}

API Reference

Functions

Classes

Troubleshooting

Log State Changes

The Observable returned by the changes property can be used to trace state changes:

controller.changes.subscribe(state => console.log(state));

However, setting up this in an app can be annoying. The good news is that you can use the debug utility function to trace state changes:

import { debug } from 'rinter';
//...
debug(controller);

By default, debug will log every state change, but you can mute it:

debug(controller, debug.SILENT);

Also you may want to customize the logging behavior:

debug(controller, {
  stateChange(value) {
    myCustomLogFunction(value);
  },
});

The debug function returns the controller that you pass to it:

const controller = debug(createController());

If you pass a controller factory function, debug will detect it and return a factory function too:

const createController = debug(initialCreateController);
const controller = createController();

Which is handy when using compose:

const twoCounters = compose({
  a: debug(counter),
  b: counter,
});

Bundle Size

Rinter itself is small, but RxJS is a big module. If your bundle size is big, make sure to use a bundler that supports ES6 modules and does tree-shaking to remove unnecessary code. For example, Webpack 4+ or Rollup supports that, but Webpack 3 doesn't.

License

MIT