Nightmarish Pawnshop Mystic
Share your code. npm Orgs help your team discover, share, and reuse code. Create a free org »


0.1.0 • Public • Published


ReactN is a extension of React that includes global state management.

Frequently Asked Questions

What version of React does ReactN come with?

ReactN does not come bundled with React. You must install React alongside it. ReactN piggybacks off whatever version of React that you choose to use.

What version(s) of React does ReactN support?

You may use any version of React with ReactN. You may freely upgrade or downgrade to any version of React without impacting your ReactN installation.

What if my project requires a clean copy of React also?

ReactN does not mutate the React package or object. It extends a copy of it. You can use React and ReactN in the same project, even in the same file!

Your react package and its imports are completely unmodified by the use of ReactN.

import React from 'react';
import ReactN from 'reactn';
assert(React.Component !== ReactN.Component);

Is my create-react-app project supported?

Yes! ReactN supports projects bootstrapped with create-react-app.


No Boilerplate!

For functional components, import { useGlobal } from 'reactn'; to harness the power of React Hooks!

For class components, simply change import React from 'react'; to import React from 'reactn';, and your React class components will have global state built in!

If you prefer class decorators, you can continue to import React from 'react'; for your components and additionally import reactn from 'reactn'; for access to the @reactn decorator!


Global state in functional components behaves almost identically to local state. Instead of [ value, setValue ] = useState(defaultValue), you can use [ value, setValue ] = useGlobal(key) where key is the key of the global state from which you want to read and to which you want write.

Global state in class components behaves exactly like local state! Instead of this.state and this.setState to read and write to the local state, you can use and this.setGlobal to read from and write to the global state object.

You may alternatively use [ global, setGlobal ] = useGlobal() to access the entire global object.

If you prefer Redux's connect functionality, pure functions, or are dealing with deeply nested objects, a withGlobal higher-order component is also available.


  • npm install reactn --save or
  • yarn add reactn

Example (Class Component)

The below example reads an array of cards from the global state. The cards are deleted from the global state via the Card component and added to the global state via the AddCard comonent. Despite this, the Cards component can still access them and will re-render whenever either other component updates the cards in the global state.

import React from 'reactn'; // uses reactn for built-in global state on components
import AddCard from '../add-card/add-card';
import Card from '../card/card';
// Render all cards in the global state, plus an additional Add Card button.
export default class Cards extends React.PureComponent {
  // For each card in the global state, render a Card component.
  get cards() {
    // returns the global state,
    //   much the same way this.state returns the local state.
    return =>
  render() {
    return (
      <div className="cards">
        <AddCard />

Example (Functional Component)

Using React Hooks in React v16.7, you can harness useGlobal to access the global state.

The above component is re-written below as a functional component.

import React from 'react';
import { useGlobal } from 'reactn';
import AddCard from '../add-card/add-card';
import Card from '../card/card';
import './cards.scss';
// Render all cards in the global state, plus an additional Add Card button.
const Cards = () => {
  const [ cards ] = useGlobal('cards');
  // For each card in the global state, render a Card component.
  return (
    <div className="cards">
      { =>
      <AddCard />
export default Cards;

Updating the Component (Re-Rendering)

When a component's local state changes, that component "updates" or re-renders.

It would not be performant to update every component when the global state changes. Instead, a component only updates if a global state root key that that component has accessed has changed.

If your component accesses, it will not re-render when changes.

If your component accesses, it will re-render when changes, because the root key myObject has changed. You should take this into consideration when nesting objects in your global state.

If you strongly desire to circumvent this behavior, you may use the withGlobal higher-order component to wrap a React.memo functional component or PureComponent.

import React, { memo } from React;
import { withGlobal } from 'reactn';
const Me = memo(
  ({ age, name }) =
    <p>My name is {name}, and I am {age}!</p>
export default withGlobal(
  (global, props) => ({
    age: global.people[props.person].age,
    name: global.people[props.person].name




npm i reactn

Downloadsweekly downloads









last publish


  • avatar
Report a vulnerability