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-render-prop

v0.8.1

Published

Redux with render props. Typescript friendly.

Downloads

102

Readme

redux-render-prop

Greenkeeper badge

Redux with render props. Alternative to the connect() higher order component.

Read an introductory blog post here.

Very TypeScript friendly. It heavily leverages type inference to avoid manual typing of props.

Install

For react-redux 6.x

npm install redux-render-prop react-redux@6 # has peer dep of react-redux 6.x

For react-redux 5.x you must use pre 0.7 versions

npm install [email protected] react-redux@5 # has peer dep of react-redux 5.x

For Typescript you will need the types too

npm install @types/react-dom @types/react @types/react-redux

Usage

import {makeConnector} from "redux-render-prop";
import {bindActionCreators} from "redux";

// Define state as a single type
interface State {
    counters: {
        [name: string]: {count: number};
    };
}

// Define some actions creators
const ActionCreators = {
    incrementByName: (name: string) => {
        return {type: "INC", name};
    },
};

// Create render prop component creator with app specific types.
// There is usually only one of these per app
const createAppConnect = makeConnector({
    // Component creators infer the state type from here.
    //
    // It is possible to return only part of the state here
    // which can be handy if you have a large app and want multiple
    // more specific component creators.
    //
    // You can also return here something other than the state
    // itself. For example you could wrap it with selector helpers.
    prepareState: (state: State) => state,

    // Actions are prepared similarly.
    prepareActions: dispatch => bindActionCreators(ActionCreators, dispatch),
});

// Create render prop component for counters.
const CounterConnect = createAppConnect({
    // State type is infered from the prepareState return value
    mapState: (state, ownProps: {name: string}) => ({
        count: state.counters[ownProps.name].count,
    }),

    // Actions type is infered from the prepareActions and
    // ownProps type is from the mapState ownProps
    mapActions: (actions, ownProps) => ({
        inc() {
            actions.incrementByName(ownProps.name);
        },
    }),
});

// Must be wrapped with <Provider store={store} />
const App = () => (
    <div>
        <CounterConnect
            // required by the ownProps type
            name="foo"
        >
            {(data, actions) => (
                // Fully typed data and actions
                <button onClick={actions.inc}>{data.count}</button>
            )}
        </CounterConnect>
    </div>
);

Flattening render props

If you find yourself nesting too much you can flatten the render callbacks type safely with the MappedState, MappedActions and MappedStateAndActions type helpers like so:

import {MappedState, MappedActions} from "redux-render-prop";

class MyComponent {
    renderCounter(
        data: MappedState<typeof CounterConnect>,
        actions: MappedActions<typeof CounterConnect>,
    ) {
        return <button onClick={actions.inc}>{data.count}</button>;
    }

    render() {
        return <CounterConnect name="foo">{this.renderCounter}</CounterConnect>;
    }
}

You can also use it to pass the props to class components if you need to access the mapped state or actions from lifecycle methods.

class ClassComponent extends React.Component<
    MappedStateAndActions<typeof CounterConnect>
> {
    componentDidMount() {
        // do something with this.props.count
    }

    render() {
        return <div>{this.props.count}</div>;
    }
}

export default () => (
    <CounterConnect name="wrapped">
        {data => <ClassComponent {...data} />}
    </CounterConnect>
);

Memoizing

For advanced high performance you may use memoizeMapState() to create memoized selectors on component mount.

const FooConnect = createComponent({
    // The initialState is the state at the time of the component
    // mount and it won't change during the component lifetime.
    // Same goes for the initialOwnProps.
    memoizeMapState: (initialState, initialOwnProps) => {
        // using the reselect module
        const selectFoosOnly = createSelector(
            (s: typeof initialState) => s.list,
            list =>
                list.map(obj => ({
                    foo: obj.foo,
                })),
        );

        // Return the actual mapState function
        return (state, ownProps) => {
            return {
                foos: selectFoosOnly(state),
            };
        };
    },
});

Examples

Here's a more complete example with immer-reducer:

https://github.com/epeli/typescript-redux-todoapp