blacksheepcode
hookstate
blacksheepcode | hookstate | |
---|---|---|
10 | 16 | |
2 | 1,632 | |
- | - | |
8.1 | 4.8 | |
about 2 months ago | 6 months ago | |
MDX | TypeScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
blacksheepcode
- [Question] Recommendations for an agnostic state management?
-
REDUX or ZUSTAND?.
My workaround has been to adopt a scaffold, , which I call a 'Hook Provider' pattern, essentially injecting your data selectors/updaters via context. See here for details.
-
Replacing redux with custom hooks and react hooks
I have a blog post and code repo with specific details here.
-
How to test custom useFetch hook in Jest
Now, for testing components that use this useDataFetch function, you would also want to be able to not use the real data fetching functions. In order to do that, those functions should be provided via context, in a pattern called dependency injection. I write about it here
-
What is the best state management library?
I write about it here and here
- Best practices for writing good unit tests for components?
-
Dependency injection when using Redux - am I overthinking it?
Full post here but here's the main gyst.
-
Form elements in your design system - uncontrolled components are the way to go?
Full post is here.
-
What's best practice for managing state without Redux?
I recommend accessing your state via a hook..
-
Agnostic state and service management in React.
Here's a article written about service and state management. It's on github here if you want to submit PRs for it.
hookstate
-
A Comprehensive Guide to React State Management
Hookstate
-
ReactJS Good Practices
Avoid using complex state structures to make it easier to manage and debug. There are multiple libraries to help manage complex state management such as Redux, Hookstate, etc.
-
What is React State Management?
Link: https://hookstate.js.org/
- 2022: Best State management libraries in React JS
-
The new wave of React state management
As you stumble on this post and article, do check out one library not mentioned in this list: hookstate. I'm a big fan, the API is very simple and it offers lots of extendability options.
-
As a beginner which is better Redux or useContext() API?
Why don't you try out hook state
-
Redattolo, un gioco per ████████ in React (Next.js)
Lo stack tecnologico è abbastanza standard per il 2022: il core è Next.js (quindi React, 18), di store managemente se ne occupa Hookstate e per un po' di collante in più c'è l'event emitter / pubsub Mitt.
-
React state management libraries in 2022
I have been using Hookstate, curiously aanbidt never mentioned in lists like this.
-
What's best practice for managing state without Redux?
I've never understood why Hookstate (https://hookstate.js.org/) doesn't get more love. It's super-simple (no boilerplate), modern (hook-based), performant (works great for all size apps) and even works outside of components beautifully. It's somewhat similar to context, but more robust and feature-rich (because it's a true state management solution, which context really isn't meant to be). It's basically the only way I've done state in React for a couple of years now and I wouldn't trade it for the world.
-
Noob question, Nextjs vs CRA?
If your data requirements aren't particularly mutating / don't mutate regularly then the newer context api would be your friend it essentially variable that is scoped to your react tree which components can subscribe to changes of, but it is important to know that: unfortunately the current useContext hook (and by extension the rest of the context api) doesn't have any means of specifically "choosing" / "selecting" a part of that context state which is where it falls behind redux etc... - even though they technically operate very very similarly - both redux and context api make use of "subscriptions" to track state updates, just that the context api was designed as a means of "dependency injection" whereas redux was designed for managing state across an entire application. Passing data through props is practically the same, as before the hooks api - avoid prop drilling etc... if you're simply looking at avoiding prop-drilling and just passing some stateful value to another component thats deeply nested then context is your friend - as for redux, I personally am further inclined to hookstate as I think their api is really strong.
What are some alternatives?
redux - A JS library for predictable global state management
zustand - 🐻 Bear necessities for state management in React
jotai - 👻 Primitive and flexible state management for React
msw - Seamless REST/GraphQL API mocking library for browser and Node.js.
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
react-hook-form - 📋 React Hooks for form state management and validation (Web + React Native)
unstated-next - 200 bytes to never think about React state management libraries ever again
particule - Fine-grained atomic React state management library
valtio - 💊 Valtio makes proxy-state simple for React and Vanilla
mitt - 🥊 Tiny 200 byte functional event emitter / pubsub.
redux-essentials-example-app - Example app for the Redux Essentials tutorial