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

component-connector

v1.0.5

Published

Easily and cleanly connect your components to many higher order components

Downloads

1

Readme

react-component-connector

Easily and cleanly connect your components to many higher order components. This package was created to provide a cleaner way to connect a component to many higher order components (HoC). For example consider a component connected to a redux store

The Problem

import connect from 'react-redux';

class MyConnectedComponent extends React.Component {
    static propTypes: {
        storeValue1: PropTypes.number
    }
    ...
}

export default connect(
    (state) => ({
        storeValue1: state.value1
    }), 
    (dispatch) => ({
        ...
    }))(MyConnectedComponent);

This by itself isn't too bad, but consider if you wanted to pass this store connected component to another higher order component that extended its functionality.

...

class MyConnectedComponent extends React.Component {
    static propTypes: {
        ....
        myExtendedFunctionality: PropTypes.func
    }
    ....
}


export default extendFunctionality({
    doAwesomeStuff: true
}, connect(
   (state) => ({
       storeValue1: state.value1
   }), 
   (dispatch) => ({
       ...
   }))(MyConnectedComponent));

notice we keep the pattern of taking config and returning a function that takes a component with only two connections this is already getting pretty hard to read.

The solution

...
export default connectComponent(MyConnectedComponent)
    .toStore(
       (state) => ({
           storeValue1: state.value1
       }), 
       (dispatch) => ({
           ...
       }))
    .toExtendedFunctionality({
        doAwesomeStuff: true
    });

Use a function that is pre-configured with the connectors that your app uses, and provides a declarative api for connecting. toStore and toExtendedFunctionality are names for connectors. We keep the pattern of connectors which are functions that take configuration and return a function that takes a component (and probably wraps the component in an HoC)

Usage

You first need to configure you connectComponent function with the connectors your app uses

/* connectComponent.js */
import componentConnector from 'react-component-connector';
import { connect } from 'react-redux';
import extendedConnector from './extendedConnector';

// Ordering of connectors DOES matter
const myConnectors = [
    {
        name: 'toStore',
        connector: connect
    },
    {
        name: 'toExtendedFunctionality',
        connector: extendedConnector
    },
    ...
];

export default componentConnector(myConnectors);

connectComponent will apply connectors in order they show up in your connectors list this is important because some HoC may expect some piece of data to be on props that another connector supplied