Skip to main content


import { useGlobalState } from '@dr.pogodin/react-global-state';

useGlobalState(path, initialValue): [any, function];

The primary hook for interacting with the global state, modeled after the standard React's useState(). It subscribes a component to a given path of global state, and provides a function to update it. Each time the value at path changes, the hook triggers re-render of its host component.


For performance, the library does not copy objects written to / read from global state paths. You MUST NOT manually mutate returned state values, or change objects already written into the global state, without explicitly clonning them first yourself.


State update notifications are asynchronous. When your code does multiple global state updates in the same React rendering cycle, all state update notifications are queued and dispatched together, after the current rendering cycle. In other words, in any given rendering cycle the global state values are "fixed", and all changes becomes visible at once in the next triggered rendering pass.


  • path - string - Dot-delimitered state path. It can be undefined to subscribe for entire state. Under-the-hood state values are read and written using Lodash's _.get() and _.set() methods, thus it is safe to access state paths which have not been created before.
  • initialValue - any - Initial value to set at the path, or its factory:
    • If a function is given, it will act similar to the lazy initial state of the standard React's useState(). only if the value at path is undefined, the function will be executed, and the value it returns will be written to the path.
    • Otherwise, the given value itself will be written to the path, if the current value at path is undefined.


It returs an array with two elements: [value, setValue]:

  • value - any - The current value at the given path.

  • setValue - function - The setter function to update the value at path.

    Similar to the standard React's useState(), it supports functional value updates: if setValue() is called with a function as argument, that function will be called and its return value will be written to path. Otherwise, the argument of setValue() itself is written to path.

    Also, similar to the standard React's state setters, setValue() is stable function: it does not change between component re-renders.