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

react-pipeline-component

v1.1.0

Published

A solution for react provider hell (provider version of callback hell)

Downloads

201

Readme

React Pipeline Component

A component to declare really long nested components without going to component hell.

How to use

This code:

import {SomethingProvider, Something} from './something';
import {OtherthingProvider, Otherthing} from './otherthing';
import {ComplexProvider, Complex} from './complex';
import {MyLayout} from './layout';

function MyApp() {
    const mySomething = new Something()
    const myOtherthing = new Otherthing()
    const myFirstComplex = new Complex()
    const mySecondComplex = new Complex()

    return <SomethingProvider something={mySomething}>
        <OtherthingProvider otherthing={myOtherthing}>
            <Complex complex={myFirstComplex}>
                <Complex complex={mySecondComplex}>
                    {/* Ouch, too deep! */}
                    <MyLayout />
                </Complex>
            </Complex>
        </OtherthingProvider>
    </SomethingProvider>
}

Can be transformed into:

import {Pipeline, Pipe} from "react-pipeline-component";
import {SomethingProvider, Something} from './something';
import {OtherthingProvider, Otherthing} from './otherthing';
import {ComplexProvider, Complex} from './complex';
import {MyLayout} from './layout';

function MyApp() {
    const mySomething = new Something()
    const myOtherthing = new Otherthing()
    const myFirstComplex = new Complex()
    const mySecondComplex = new Complex()

    return <Pipeline components={[
        // You can write your providers in one line for each provider
        <SomethingProvider something={mySomething} children={<Pipe />} />,
        <OtherthingProvider otherthing={myOtherthing} children={<Pipe />} />,
        // or you could nest some and keep the rest oneliners
        <Complex complex={myFirstComplex}>
            <Complex complex={mySecondComplex}>
                {/* Pipe holds the next component in the list */}
                <Pipe />
            </Complex>
        </Complex>,
        // now your main component can be written with less indentation
        <MyLayout />
    ]} />
}

Alternatively, you can write it this way:

import {Pipeline, Pipe, pipe} from "react-pipeline-component";
import {SomethingProvider, Something} from './something';
import {OtherthingProvider, Otherthing} from './otherthing';
import {ComplexProvider, Complex} from './complex';
import {MyLayout} from './layout';

function MyApp() {
    const mySomething = new Something()
    const myOtherthing = new Otherthing()
    const myFirstComplex = new Complex()
    const mySecondComplex = new Complex()

    return <Pipeline>
        {/* You can write your providers in one line for each provider */}
        <SomethingProvider something={mySomething} {...pipe} />
        <OtherthingProvider otherthing={myOtherthing} {...pipe} />
        {/* or you could nest some and keep the rest oneliners */}
        <Complex complex={myFirstComplex}>
            <Complex complex={mySecondComplex}>
                {/* Pipe holds the next component in the list */}
                <Pipe />
            </Complex>
        </Complex>
        {/* now your main component can be written with less indentation */}
        <MyLayout />
    </Pipeline>
}

As you can see, the constant pipe is alternative to writing <Pipe />

<Component children={<Pipe />} />
<Component {...pipe} />

Also, passing your components as an array is alternative to passing them as children

<Pipeline components={[
    <Component children={<Pipe />} />,
    <Component children={<Pipe />} />,
]} />
<Pipeline>
    <Component children={<Pipe />} />
    <Component children={<Pipe />} />
</Pipeline>