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-providers-tree-builder

v0.0.1

Published

A React library that focuses on making provider trees more readable

Downloads

3

Readme

react-providers-tree-builder 🧗‍♀️

Introduction ⚙️

This library provides a simple and efficient way to manage multiple React providers, solving the "Provider Hell" problem by allowing you to wrap all providers into a single, manageable component. This makes your app structure cleaner and more readable.

The Problem:

"Provider Hell" occurs when there are numerous nested providers in a React application, resulting in a cumbersome and difficult-to-maintain and read component hierarchy.

Example:

const App = () => {
  // ... some code
  return (
    <>
      <ReduxProvider value={store}>
        <ThemeProvider value={theme}>
          <OtherProvider value={otherValue}>
            <OtherOtherProvider value={otherOtherValue}>
              {/** ... other providers*/}
              <HellProvider value={hell}>
                <HelloWorld />
              </HellProvider>
              {/** ... other providers*/}
            </OtherOtherProvider>
          </OtherProvider>
        </ThemeProvider>
      </ReduxProvider>
    </>
  );
};

How react-providers-tree-builder Solves It:

Installation

To install the library, use npm or yarn:

npm install react-providers-tree-builder

or

yarn add react-providers-tree-builder

Usage ⚡

import { BuildProviderTree } from "react-providers-tree-builder";

const App = () => {
  const Providers = BuildProviderTree([
    { Provider: ThemeContext.Provider, props: { value: themeValue } },
    {
      Provider: AuthContext.Provider,
      props: { value: userData },
    },
    {
      //Provider without any props
      Provider: OtherContext.Provider,
    },
  ]);
  return (
    <Providers>
      <HelloWorld />
    </Providers>
  );
};

export default App;

Output react tree 🙌

<ThemeContext value={themeValue}>
  <AuthContext value={userData}>
    <OtherContext>
      <HelloWorld />
    </OtherContext>
  </AuthContext>
</ThemeContext>

Contribution 🤝

We welcome contributions! Feel free to open issues or submit pull requests for any improvements.

License 📄

This project is licensed under the MIT License - see the LICENSE for details.