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-easy-shared-state

v1.0.16

Published

The most easiset solution to share state across many components. Every component can read and write the state like any other JS object. No need to use provider or context.

Downloads

2

Readme

react-easy-shared-state

The most easiset solution to share state across many components. Every component can read and write the state like any other JS object. No need to use provider or context.

It is fully supported every version of React (including v18), it's working really fast. You do not need to create actions and reducers. The truth is that you almost not feel it.

Let's take the Redux todo example. (https://github.com/reduxjs/redux/tree/master/examples/todos) When implemented in react-easy-shared-state (https://github.com/Aminadav/react-easy-shared-state-todo) it's saving about 90% of the code.

Why react-easy-shared-state?

  • Very easy to refactor.
  • Great for agility. Let you easily refactor.
  • Mutable. You don't need to clone object and array's before changing.
  • It's working fast.
  • You can read and change in part of your state easily from any component.
  • Supporting all smart features of VSCode. Including auto-complete, find all-refreneces, and rename symbols!
  • I'm not a big fun of Redux. Too many code to write, hard to refactor, and not supporting auto-complete.

Compare to Redux

  • 90% less code to write in compare to Redux.
  • Very easy to learn. Contain only three methods.
  • I like to write code as little as possible. I'm not like to develop reducers, action builders, connectors, and containers.
  • I want to change the state directly - without calling other actions, dispatching, or making any other change.
  • Sometimes I need to access specific part of the store Buy I don't want to changing anything in the code-
  • I Like JSON. And the component should use the store's property like any other JSON object. And without using or creating selectors.
  • I wouldn't say I like immutable objects. I prefer to push, pull, and change arrays and objects without cloning.
  • I don't like that sometimes I'm getting previous store values because of cloning, and I'm not particularly eager to fix it using useRef and similar fixes. I prefer to have one state ojbect.
  • In Redux all IDE smart features like "Find all references" or "rename symbol" doesn't work for keys in the store (unless your spend more time to create type definitaions). In react-easy-shared-state it's working out of the box, so my code always have the naming I wish and I don't afraid to refactor.

How to use react-easy-shared-state?

Create a new file (store.js) and call the react-easy-shared-state newStore function with your initial store. And export the result.

const store = NewStore({
  todos:[],
  filter:'ALL',
})
export default store

Suppport all smart IDE's features such as autocomplete for keys in your store, rename symbols and find all references

react-easy-shared-state will create one store for your whole app. You can read any part of the store easily by importing the store.js file. This is a simple JSON file.

import store from './store'

console.log(store.filter)
store.todos.push("My First Todo")
function Component(){
  return <div>{store.filter></div>
}

Each time you updating the store you have to call the updateStore function, it will render the componets that are depneded on the store.

import store from './store'
<div onClick={()=>{ store.counter++; store.updaterStore() }>
  Increase counter
</div>

To know which components should re-render you have to use the react-easy-shared-state hook useRerenderIfChange and tell it which part of the store this component is dependent on.

import store from './store'
function MyComponent(){
  store.useRerenderIfChange(()=>[store.counter]) // Each time counter change re-render this component
  <div onClick={()=>{ store.counter++; store.updaterStore() }>
    Increase counter
  </div>
}

That it! You know everything about react-easy-shared-state.

  • createStore - called once.
  • updateStore - called every time you want to rerender your UI.
  • useRerenderIfChange - called on every component that depended on specific part of the store.

Demo App:

Please see the full working demo app: https://github.com/Aminadav/react-easy-shared-state/tree/master/examples/todo

See the website: https://react-easy-shared-state.js.org

Link to the first Reddit post about it: https://www.reddit.com/r/reactjs/comments/m27hqm/globux_a_global_state_manager_that_let_you_read/

Installation

npm i react-easy-shared-state

Demo:

// First you should creating the store.
// Usually you will create one store for each app and share this variable.
// Usually you will put this in separate file.
import {newStore} from "react-easy-shared-state"

const store = newStore({
  key1:0,
  key2:0,
})

function App(){
  // This component will automatically re-render when store.key1 will change.
  store.useRerenderIfChange(()=>[store.key1])
  function incrementKey1(){
    store.key1++
    store.updateStore() // This will check which component should re-render since the last update.
  }
  return <div onClick={incrementKey1}>
    Store key1: {store.key1}
    <ChildComponent />
    </div>
}

function ChildComponent() {
  // This component will automatically re-render when store.key2 or store.key1 will change.
  store.useRerenderIfChange(()=>[store.key2,store.key1])
  function incrementKey2(){
    store.key2++
    store.updateStore()
  }
  return <div onClick={incrementKey2}>
    Store key1: {store.key1}
    Store key2: {store.key2}
    </div>
}