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-dynamic-context-provider

v1.0.5

Published

An easy way to config multiple contexts in React application

Downloads

8

Readme

react-dynamic-context-provider

Provides an easy way to manage react contexts.

Problem to solve

Following is a simple example of implementation of multiple dynamic contexts in React.

import React from 'react';

export const UserContext = React.createContext(null);
export const SetUserContext = React.createContext(() => {}));
export const ThemeContext = React.createContext('light');
export const SetThemeContext = React.createContext(() => {}));
export const AnotherContext = React.createContext('another value');
export const SetAnotherContext = React.createContext(() => {});

const App = () => {
    const [user, setUser] = React.useState(null);
    const [theme, setTheme] = React.useState('light');
    const [another, setAnother] = React.useState(null);
    return (
        <UserContext.Provider value={user}>
            <SetUserContext.Provider value={setUser}>
                <ThemeContext.Provider value={theme}>
                    <SetThemeContext.Provider value={setTheme}>
                        <AnotherContext.Provider value={another}>
                            <SetAnotherContext.Provider value={setAnother}>
                                ...
                                <MainComponent />
                                ...
                            </SetAnotherContext.Provider>
                        </AnotherContext.Provider>
                    </SetThemeContext.Provider>
                </ThemeContext.Provider>
            </SetUserContext.Provider>
        </UserContext.Provider>
    )
}

export default App;

Note that the contexts of value (e.g. user) and setter (e.g. setUser) are separated to prevent re-render of component that needs to call setUser but doesn't depend on user.

The problem with the approach above is there is too much boilerplate code. When you need to add a new context, what you will need to do is:

  1. Create and export a new context with React.createContext().
  2. Create a new state in App or other HOC for the new context value.
  3. Wrap the App component with two context providers, e.g. NewContext.Provider and SetNewContext.Provider.
  4. Import the context with it's name e.g. import { NewContext } from 'SomeModule'.

This is hard to manage especially when you need to remove or change the name of the context. Afterall, what you really have to provide is just the name and value of the context. Other codes are just boilerplate codes which should be automatically generated or managed.

Usage

This package manages the above boilerplate for you. With this package the above code becomes

import React from 'react';
import { getContextProvider } from 'react-dynamic-context-provider';

const contexts = [
    { name: 'User', value: null },
    { name: 'Theme', value: 'light' },
    { name: 'Another', value: 'another value' }
];
const ContextProvider = getContextProvider(contexts);

const App = () => (
    <ContextProvider>
        <MainComponent />
    </ContextProvider>
)

export default App;

When you need to add a new context (e.g. MyValue), simply add a new name-value pair in the array of contexts. Then two contexts will be automatically created MyValueContext and SetMyValueContext. You can import and use them like

import React from 'react';
import { getContexts } from 'react-dynamic-context-provider';
...
const myValue = React.useContext(getContexts().MyValueContext);
const setMyValue = React.useContext(getContexts().SetMyValueContext);

When you need to remove a context, simply remove the context from the array contexts. When you need to change the name or default value, you only need to change it in the same array.

Installation

yarn add react-dynamic-context-provider