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-immersive

v0.6.3

Published

Simple state management for react on top of immer

Downloads

163

Readme

react-immersive

Simple state management for react on top of immer

  1. Define the state.
  2. Define actions that will modify the state (it uses immer, so mutate it all you want).
  3. Use the hooks to access the state and actions.
  4. Use local updates to prioritize user input response.

Installation

Install via yarn:

yarn add immer react-immersive

Or npm:

npm install --save immer react-immersive

Usage

Pass your initial state as the first argument, followed by an actions creator on the second argument. An actions creator accepts a modifier function that lets you modify the state (I prefer to call it draftState) directly inside each of actions that you create.

Please head to immer's documentation if you haven't heard of it.

Initialization

todo.js

import { createContext } from "react-immersive";

const todo = createContext(
  { tasks: [{ task: "hello", done: false }] },
  (modify) => ({
    addTask: (task) => {
      modify((draft) => {
        draft.tasks.push({ done: false, task });
      });
    },
    removeTask: (index) => {
      modify((draft) => {
        draft.tasks.splice(index, 1);
      });
    },
  })
);

export default todo;

main.jsx

ReactDOM.render(
  <todo.Provider>
    <YourApp />
  </todo.Provider>
);

Accessing actions

import todo from "./todo";

const SomeComponent = () => {
  const actions = todo.useActions();
  const handleAddNewTask = () => {
    actions.addTask("Test");
  };

  const handleRemoveTask = () => {
    actions.removeTask(0);
  };

  return <div></div>;
};

Accessing state

useSelectState accepts a function that selects the state target, allowing your component to focus only on what matters.

import todo from "./todo";

const OtherComponent = () => {
  const firstTask = todo.useSelectState((state) => state.tasks[0]);
  return <div></div>;
};

Using local updates

This is an experimental feature that lets you prioritize the rendering of the closest component to the user input in order to improve the user-perceived performance of your large application. This feature relies on the presence of window.requestIdleCallback, therefore you need to add the polyfill at the beginning of your application entrypoint.

import todo from "./todo";

const SomeComponent = () => {
  const localUpdates = todo.useLocalUpdates();
  const actions = localUpdates.useActions();
  const handleAddNewTask = () => {
    actions.addTask("Test");
  };

  const handleRemoveTask = () => {
    actions.removeTask(0);
  };

  const firstTask = localUpdates.useSelectState((state) => state.tasks[0]);

  return <div></div>;
};

In this example, SomeComponent will maintain a copy of the global state in localUpdates. Each changes that happen to localUpdates will be emitted to the global state after the SomeComponent completes re-rendering.