Skip to content
Efficient and simple to use global state management for React, implemented with hooks, and spiced by useful data management functions (async retreival, caching, etc.)
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.


Type Name Latest commit message Commit time
Failed to load latest commit information.

Master Build Status Dev Build Status Latest NPM Release NPM Downloads

React Global State

Efficient and simple global state management for React, implemented with hooks, and spiced by useful data management functions (asyncroneous retrieval, caching, etc.), and the server-side rendering (SSR) support.



The motivation, and the vision, is to bring to the table all useful features of Redux, without related development overheads, like the amount of required boilerplate code, and the efforts needed to design, and mainaint actions, and reducers.

With this library, the introduction of a datum (data piece), shared across different application components, is as easy as using the local React state:

function SampleReactComponent() {
  const [data, setData] = useGlobalState('', initialValue);

  /* `data` value can be updating by calling `setData(newData)` anywhere inside
   * the component code, including inside hooks like `useEffect(..)` or some
   * event handlers. */

  return /* Some JSX markup. */;

Relying on async data, e.g. loading into the state data from a 3-rd party API, is similarly easy:

async function loader() {

  /* Some async operation to get data, like a call to a 3-rd party API. */

  return data;

function SampleReactComponent() {
  const { data, loading, timestamp } = useAsyncData('data.envelop.path', loader);

  /* `data` holds the data loaded into the global state, if they are fresh enough;
   * `loading` signals that data loading (or silent re-loading) is in-progress;
   * `timestamp` is the timestamp of currently loaded `data`. */

  return /* Some JSX markup. */

⇑ Behind the scene, the library takes care about updating the component when the data loading starts, and ends; as well as about the timestamps, automatic reloading, and garbage collection of aged data.

Related closely to async data is the server-side rendering (SSR). This library takes it into account, and provides a flexible way to implement SSR with loading of some, or all async data at the server side.


  1. The base setup is simple: just wrap your app into the <GlobalStateProvider> component, provided by this library, and you'll be able to use any library hooks within its child hierarchy.

    /* The minimal example of the library setup and usage. */
    import React from 'react';
    import {
    } from '@dr.pogodin/react-global-state';
    /* Example of component relying on the global state. */
    function SampleComponent() {
      const [value, setValue] = useGlobalState('sample.component', 0);
      return (
        <button onClick={() => setValue(1 + value)}>
    /* Example of component relying on async data in the global state. */
    async function sampleDataLoader() {
      return new Promise((resolve) => {
        setTimeout(() => resolve('Sample Data'), 500);
    function SampleAsyncComponent() {
      const { data, loading } = useAsyncData('sample.async-component', sampleDataLoader);
      return data;
    /* Example of the root app component, providing the state.  */
    export default function SampleApp() {
      return (
          <SampleComponent />
          <SampleAsyncComponent />

    Multiple, or nested <GlobalStateProvider> instances are allowed, and they will provide independent global states to its children (shadowing parent ones, in the case of nesting). However, the current SSR implementation assumes a single <GlobalStateProvider> at the app root. Multiple providers won't break it, but won't be a part of SSR data loading either.

    This setup is fine to run both at the client, and at the server-side, but in the case of server-side rendering, the library won't run any async data fetching, thus rendering pages with the initial global state; e.g. in the example above the <SampleAsyncComponent> will be rendered as an empty node, as data will be undefined, and loading will be false. To handle SSR better, and to have <SampleAsyncComponent> rendered as Sample Data even at the server-side, you need the following, a bit more complex, setup.

  2. Advanced setup with the server-side rendering support is demonstrated below, assuming that <SampleComponent>, sampleDataLoader(..), and <SampleAsyncComponent> are defined the same way as in the previous example, and <SampleApp> component itself does not include the <GlobalStateProvider>, i.e.

    export default function SampleApp() {
      return (
          <SampleComponent />
          <SampleAsyncComponent />

    The server-side rendering code becomes:

    /* Server-sider rendering. */
    import React from 'react';
    import ReactDOM from 'react-dom/server';
    import { GlobalStateProvider } from '@dr.pogodin/react-global-state';
    import SampleApp from 'path/to/app';
    async function renderServerSide() {
      let render;
      const ssrContext = { state: {} };
      for (let round = 0; round < 3; round += 1) {
        render = ReactDOM.renderToString((
            <SampleApp />
        if (ssrContext.dirty) {
          await Promise.allSettled(ssrContext.pending);
        } else break;
      return { render, state: ssrContext.state };

    ⇑ When ssrContext property is passed into the <GlobalStateProvider>, the corresponding global state object switches into the SSR mode. In this mode, if the app rendering modifies the state, the ssrContext.dirty flag is set true, and for any async operations, triggered by the library hooks, corresponding promises are added into the ssrContext.pending array. Thus, the block of code

    if (ssrContext.dirty) {
      await Promise.allSettled(ssrContext.pending);
    } else break;

    in the case when last rendering pass triggered async operations, it waits for them to complete, and repeats allows the rendering pass to be redone with the new initial value of the global state, which is written to ssrContext.state in this case. If no updates to the state happened in the last rendering pass, this block breaks out of the loop, giving you in the render variable the HTML markup to send to the client, and in the ssrContext.state the initial value of the global state to use for app initialization at the client side.

    The outer for loop serves to protect against possible long re-rendering loops: if after several re-renders the state has not become stable, it is fine to send to the client side the latest render and state results, and finalize the rest of rendering at the client side.

    In case when some async operations are too long to wait for them during SSR, the async hooks accept noSSR option, to be ignored during SSR. Additional option is to wrap the rendering cycle into a timeout race codition, and if the desired rendering time has bit hit, the rendering loop can be interrupted, and the latest render and state can be sent to the client side.

    The corresponding client-side rendering is simple, just pass the state calculated during the server-side rendering into the initialState prop of <GlobalStateProvider> at the client side:

    /* Client-side rendering. */
    import React from 'react';
    import ReactDOM from 'react-dom';
    import { GlobalStateProvider } from '@dr.pogodin/react-global-state';
    import SampleApp from 'path/to/app';
    function renderClientSide(stateFromServerSide) {
        <GlobalStateProvider initialState={stateFromServerSide}>
          <SampleApp />
      ), document.getElementById('your-react-view'));


  • <GlobalStateProvider /> – Provides global state to its children. The Missing GlobalStateProvider error is thrown if a library function is used inside a component which cannot find a provider up in the component hierarchy. Multiple providers can be used, and nested, in the same code. In such case a component will see the global state from the closest provider up in the component hierarchy.

    Children are optional, and they are rendered at the component place.


    • [initialState] (Any) – Optional. Initial global state.

    • [ssrContext] (Object) – Optional. Switches provided state into the SSR mode. In this state, async operations will be executed in the optimal way, and the following fields will be written to ssrContext on the exit from the rendering pass:

      • ssrContext.dirty (Boolean) – Will be set true, if the state was altered during the pass, including some async operations started.
      • ssrContext.pending (Promise[]) – Array of promises which will resolve or reject once all async operations triggered by the render pass, are completed. Do await Promise.allSettled(ssrContext.pending) to wait until the rendering pass can be repeated with the updated state.
      • ssrContext.state (Any) – Will contain the resulting state after the rendering pass, including the results of async operations.
    • [stateProxy] (Boolean | GlobalState) – Optional. If set true, the provider will act as proxy, i.e. it will re-use the state from a parent provider, instead of creating a new one. If set an instance of the global state object, that global state will be used. This is useful for code-splitting with SSR support.

  • useGlobalState(path, [initialValue]) – Base global state hook, similar to React's useState hook for the local state. It subscribes the component to the data located at the given state path, and also exposes the data update method.


    • path (String) – State path. It can be undefined to subscribe for entire state, though for most practical applications components should subscribe for relevant state paths.

      Internally, the state is a single object, and data are read and written to paths using lodash's _.get(..) and _.set(..) methods. Thus, it is safe to read, and set paths which have not been set in the state yet.

    • [initialValue] (Any) – Optional. Initial value. If given, it will be set at the path, if the current value at the path is undefined.

    Returns [value, setValue(newValue)] – Array with two elements. The first one is the value at the path. The second one is the function to update the path value.

    Notifications on state updates are async, in the sence that if you update the state multiple times from the same syncroneous code, the updates are propagated to other components once the current code exits.

    ⇑ This requires a better explanation!

  • useAsyncData(path, loader, [options]) – Hook for storing async data in the global state and the specified path. When different components in your application rely on the same async data (e.g. fetched from a remote API), this hook simplifies loading, and reusing these data among the components (i.e. load just once, refresh if stale, etc.)

    Given async data loader (a function which returns a Promise resolving to some data), this hook loads data to the specified global state path, ensuring that loader is triggered a single time even if the hook is called from different components (it is assumed that all calls of useAsyncData(..) for the same path rely on the same loader). It remembers the timestamp of data retrieval, and the number of components relying on the data. If hook is used when data are already present in the state, it reloads the data only if existing ones are older than the specified maximum age. It clears stale data from the state, when the last component relying on them is dismounted.


    • path (String) – State path, where all related information will be kept.
    • loader (Function) – Async function with resolves to the data of interest.
    • [options] (Object) – Optional. Additional parameters.
      • [options.maxage] (Number) – Optional. Maximum age of data acceptable to the caller. If data in the state are older than this time [ms], the reloading will be initiated.
      • [options.refreshAge] (Number) – Optional. Maximum age of data which will not trigger data update. Defaults to the maxage value.
      • [options.garbageCollectAge] (Number) – Optional. Maximum age of data after which they will be dropped from the state, if no objects reference to them.
      • [options.noSSR] (Boolean) – Optional. If true this async operation will be ignored during the SSR rendering.

    Returns object with the following fields:

    • data (Any) – current data stored at the state.
    • loading (Boolean) – true if the data are being loaded.
    • timestamp (Number) – Timestamp of the data currently loaded into the state [ms]. Defaults 5 min.
  • getSsrContext([throwWithoutSsrContext=true]) – Hook to access SSR context from React components.

    In most use cases you don't need to access SSR context directly from your components. For SSR you just provide SSR context to the state provider, and read its resulting state directly after the render (see SSR example above). This hook is introduced to implement code-splitting with full SSR support, in a scenario when some components need additional data to be passed to them during SSR.

    Returns the SSR context, or throws if it does not exist. The optional throwWithoutSsrContext argument can be set to false to not throw if the context does not exist. In any case, this hook still throws if entire global state (i.e. <GlobalStateProvider>) is missing.

  • getGlobalState() – Hook to get the actual GlobalState instance. In all practical usecases you want to use useGlobalState(..) hook instead. This one is only intended for advanced usecases, like code-splitting, and SSR support, where the same global state instance should be shared between independently rendered React trees.


P.S.: Mind the early version! As of now it is a proof-of-concept, which works great in my tests, but lacks some features, and optimizations I have in my mind.

You can’t perform that action at this time.