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-react-observable

v0.1.1

Published

Efficient and descriptive Redux React bindings

Downloads

5

Readme

Redux React Observable

npm version Circle CI

This is an experiment

Efficient and descriptive Redux React binding.

Why & Benefits

Unlike connect in react-redux, redux-react-observable will update tree leaf component directly, rather than passing down props at each level. This way we can skip middle level components and directly update deeply nested components. Also the selector is kinda descriptive. In the future, we might be able to add data dependency deceleration and fetch data automatically without writing any additional code.

Usage

npm i -S redux-react-observable

redux-react-observable requires react and redux (no need of react-redux) to work

npm i -S react react-dom redux
'use strict';

const React = require('react');
const ReactDOM = require('react-dom');
const {createStore} = require('redux')
const {StoreObserverProvider, observe} = require('redux-react-observable');

function counter(state = {count: 0}, action) {
  switch (action.type) {
  case 'INCREMENT':
    return {count: state.count + 1};
  case 'DECREMENT':
    return {count: state.count - 1};
  default:
    return state;
  }
}

const store = createStore(counter);

// Create pure function component
const Counter = (props) => (
  <div>{props.num}</div>
);

// Wrap Counter with higher order component
const HigherOrder = observe(
  function () {
    // This is our store path selector
    return {
      num: ['count']
    };
  },
  Counter
);

// If you know react-redux's <Provider>, you know <StoreObserverProvider>
ReactDOM.render(
  <StoreObserverProvider store={store}>
    <HigherOrder/>
  </StoreObserverProvider>,
  document.getElementById('app')
);

setInterval(() => {
  store.dispatch({type: 'INCREMENT'})
}, 100);

API

<StoreObserverProvider store>

  • store Redux store instance

observe(selector, Component): Component

  • selector: (props: any) => {[key: string]: string[]} Return higher order component. Props passed to higher order component will pass to selector function as first argument. Must return an object. Object keys will become the props' name of wrapped component. Object values must be an array of string or number, a.k.a. key path. Those key paths will be used to get values from the Redux store. The value related to key path will be assigned to props of the wrapped component. New props will be passed to wrapped component only when key path related value has changed by using a deep equal comparison.
  • Component: React.Component A wrapped component