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 🙏

© 2026 – Pkg Stats / Ryan Hefner

react-providers-flattener

v1.0.0

Published

A simple way to flatten providers so you aren't building a sideways mountain

Downloads

348

Readme

react-providers-flattener

A simple way to flatten providers so you aren't building a sideways mountain.

The Problem

When building React applications, you often end up with deeply nested providers that create a "sideways mountain" or "pyramid of doom":

<ThemeProvider>
  <AuthProvider>
    <RouterProvider>
      <QueryProvider>
        <NotificationProvider>
          <ModalProvider>
            <App />
          </ModalProvider>
        </NotificationProvider>
      </QueryProvider>
    </RouterProvider>
  </AuthProvider>
</ThemeProvider>

This is hard to read, maintain, and refactor.

The Solution

react-providers-flattener provides a clean, declarative way to compose multiple providers:

<ProviderComposer
  providers={[
    ThemeProvider,
    AuthProvider,
    RouterProvider,
    QueryProvider,
    NotificationProvider,
    ModalProvider,
  ]}
>
  <App />
</ProviderComposer>

Installation

npm install react-providers-flattener

or

yarn add react-providers-flattener

or

pnpm add react-providers-flattener

Usage

Basic Usage

import { ProviderComposer } from 'react-providers-flattener';
import { ThemeProvider, AuthProvider, RouterProvider } from './providers';

function Root() {
  return (
    <ProviderComposer
      providers={[ThemeProvider, AuthProvider, RouterProvider]}
    >
      <App />
    </ProviderComposer>
  );
}

With Provider Props

If your providers need props, pass them as tuples:

import { ProviderComposer } from 'react-providers-flattener';

function Root() {
  return (
    <ProviderComposer
      providers={[
        [ThemeProvider, { theme: darkTheme }],
        [AuthProvider, { initialUser: currentUser }],
        [RouterProvider, { router: appRouter }],
        // Providers without props can be passed directly
        NotificationProvider,
      ]}
    >
      <App />
    </ProviderComposer>
  );
}

Creating Reusable Provider Compositions

Use composeProviders to create a reusable provider component:

import { composeProviders } from 'react-providers-flattener';

// Create your composed provider
const AppProviders = composeProviders([
  ThemeProvider,
  AuthProvider,
  RouterProvider,
  QueryProvider,
]);

// Use it anywhere in your app
function Root() {
  return (
    <AppProviders>
      <App />
    </AppProviders>
  );
}

With Props in Composed Providers

import { composeProviders } from 'react-providers-flattener';

const AppProviders = composeProviders([
  [ThemeProvider, { theme: darkTheme }],
  [QueryProvider, { client: queryClient }],
  AuthProvider,
]);

function Root() {
  return (
    <AppProviders>
      <App />
    </AppProviders>
  );
}

API

ProviderComposer

A component that composes multiple providers into a single wrapper.

Props:

  • providers: ProviderEntry[] - Array of providers to compose
  • children: React.ReactNode - Children to render inside all providers

ProviderEntry Types:

  • Provider - A React component without props
  • [Provider, props] - A tuple of component and its props (excluding children)

composeProviders(providers)

Creates a composed provider component from an array of providers.

Parameters:

  • providers: ProviderEntry[] - Array of providers to compose

Returns:

  • A React component that accepts children prop

TypeScript Support

This package is written in TypeScript and includes full type definitions. All types are exported for your convenience:

import type {
  Provider,
  ProviderEntry,
  ProviderComposerProps,
} from 'react-providers-flattener';

Examples

Real-world Example

import { ProviderComposer } from 'react-providers-flattener';
import { QueryClient, QueryClientProvider } from '@tanstack/react-query';
import { ThemeProvider } from '@mui/material';
import { AuthProvider } from './auth';
import { RouterProvider } from 'react-router-dom';

const queryClient = new QueryClient();
const theme = createTheme();

function Root() {
  return (
    <ProviderComposer
      providers={[
        [QueryClientProvider, { client: queryClient }],
        [ThemeProvider, { theme }],
        AuthProvider,
        [RouterProvider, { router: appRouter }],
      ]}
    >
      <App />
    </ProviderComposer>
  );
}

Migration Example

Before:

function Root() {
  return (
    <QueryClientProvider client={queryClient}>
      <ThemeProvider theme={theme}>
        <AuthProvider>
          <RouterProvider router={router}>
            <NotificationProvider>
              <App />
            </NotificationProvider>
          </RouterProvider>
        </AuthProvider>
      </ThemeProvider>
    </QueryClientProvider>
  );
}

After:

function Root() {
  return (
    <ProviderComposer
      providers={[
        [QueryClientProvider, { client: queryClient }],
        [ThemeProvider, { theme }],
        AuthProvider,
        [RouterProvider, { router }],
        NotificationProvider,
      ]}
    >
      <App />
    </ProviderComposer>
  );
}

Why Use This?

  • Cleaner Code: No more deeply nested provider trees
  • Better Readability: See all your providers in a flat list
  • Easier Refactoring: Add, remove, or reorder providers easily
  • Type Safe: Full TypeScript support with type inference
  • Tiny: Minimal bundle size with zero dependencies (except React peer dependency)
  • Flexible: Works with any React provider pattern

Requirements

  • React >= 16.8.0

License

MIT