react-community-tools-practices-cheatsheet
react-redux-links
react-community-tools-practices-cheatsheet | react-redux-links | |
---|---|---|
10 | 10 | |
325 | 22,520 | |
- | - | |
0.0 | 0.0 | |
over 1 year ago | 6 months ago | |
JavaScript | ||
- | - |
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.
react-community-tools-practices-cheatsheet
- State Management in React Applications
-
How I write React after 8 years
Eh, there was entirely valid reasons for the backlash :)
Redux _was_ overused in the first couple years. The original patterns _were_ very boilerplate-y. There _are_ a lot of other good tools for varying use cases that overlap with things that people have used Redux for: Context for prop drilling, React Query / Apollo for data fetching, Zustand/Jotai/Mobx/five-million-other-libs for state management.
Redux will never be the "must use this" lib again the way it was there for a couple years.
And that's a _good_ thing, because folks should take time to think about what problems they actually need to solve in their apps and pick the tools that work best for those problems.
But it's also true that Redux _is_ still a useful tool, and that RTK has addressed the pain points in using Redux. So, still very much a viable choice today, and the positive feedback we get on RTK daily shows that.
Really, the bigger issue today is that a lot of folks don't seem to understand the technical differences, tradeoffs, and intended use cases between a lot of these tools.
I wrote an extensive post describing the differences between Context and Redux to try to help with that:
- https://blog.isquaredsoftware.com/2021/01/context-redux-diff...
I've also been trying to start up a community-driven site to list common tools for various use cases (state management, styling, build tools, data fetching, etc), to act as a resource to help clarify this sort of confusion:
- https://github.com/markerikson/react-community-tools-practic...
Sadly I haven't had time to push it forward myself due to all the other responsibilities and tasks on my todo list, but hopefully at some point we can get enough info filled in for it to be a real resources that we can point people to.
-
Redux is Poison
In fact, I am literally trying to put together a community-driven site that would list commonly used tools for use cases like state management and styling, and describe their tradeoffs, specifically because I want people to make informed decisions.
-
UIs are not pure functions of the model
Good question!
The really short answer is: mostly looking at NPM download stats, Github "depended by" numbers, and random polls on Twitter.
Which are all _horribly_ flawed metrics, but they're also all we have to go by.
I wrote a couple longer comments on Reddit a while back that went into more details on some of the numbers and the potential flaws in using them:
- https://www.reddit.com/r/reactjs/comments/lcgqnd/state_manag...
- https://www.reddit.com/r/reactjs/comments/skbyb1/the_most_po...
and unfortunately you asking me about this is tempting me to turn those comments into a blog post with some additional thoughts :)
I'll definitely agree that Redux usage has peaked in _relative_ terms, although as you can see from the download numbers it seems to still be growing in _absolute_ terms. Also it's entirely possible that fewer new projects are choosing Redux.
Then again, how do we even count "usage" in the first place? I've seen Web3 app boilerplate repos that include Redux Toolkit. If 1000 people clone that repo and play with it, how do we compare that usage conceptually vs one app using Mobx that's been around for years and has a bunch of developers working on it daily?
As I've pointed out in a number of podcasts and articles: I'm not trying to convince people they _must_ use Redux, or even that they _should_ use Redux. I just want people to be aware that modern Redux is way easier than legacy Redux, that Redux _is_ still widely used and is a viable choice, and what some of the tradeoffs are when using Redux or any other state management library.
I've actually been trying to get the community to come together and work on a centralized site that would list tools in different use cases and categories such as state management, styling, data fetching, and build tooling, describe purpose / use cases / tradeoffs for each tool, and have that as a recognized resource for people to use when researching what to use for a project. You can see the original RFC discussion and prototype site here:
- https://github.com/markerikson/react-community-tools-practic...
- https://react-community-tools-practices-cheatsheet.netlify.a...
Sadly I haven't had time to push this forward, and it needs to have more people involved and helping fill out content on the various topics (not just me).
-
Building first React project, and lost on State Management
Fortunately, we're starting to make some headway on https://github.com/markerikson/react-community-tools-practices-cheatsheet/discussions/1 ! We recently got a PR adding a page covering the three Poimandres libs (Zustand/Jotai/Valtio), someone's filling out pages on styling approaches, etc.
-
Recap from Reactathon, if you missed the conference
(I will say this is the exact kind of guidance I'd like to have in the "React Community Tools" site I still want to build out as a resource, and I'm hopeful that we can get some content filled out and momentum behind that site later this year.)
-
Should we be teaching Redux in 2022?
Early last year, I proposed creating a "React Community Tools and Practices" resource site. The idea was to provide curated written guidance on the different tools and techniques that React devs commonly use to solve various problems, describe the purpose and tradeoffs of each tool, and give some general guidance on how to decide on what tool best solves your use case.
-
React State Management
Background: https://github.com/markerikson/react-community-tools-practices-cheatsheet/discussions/1
- What are the biggest issues you see with React in its current form?
- Top libraries to know about
react-redux-links
-
ReactJS Good Practices
React-Redux Links - List of tutorials and resources for React/Redux.
-
State Management in React Applications
btw, not sure if you're referring to https://www.reactiflux.com/learning specifically, or the Discord as a whole . I did come up with the links in that "Learning" page myself (it's an updated version of the much older https://github.com/markerikson/react-redux-links repo that I had to stop updating in 2018 because it was sucking up time and burning me out), but agreed that this is also now somewhat outdated as well. Which is admittedly the problem with any resource :) tools, practices, and patterns all change, and keeping up to date with them is a full-time job by itself.
-
7 Really Helpful GitHub Repositories for React Developers🚀🎯
Link: https://github.com/markerikson/react-redux-links
-
16 Github Repos to master React
16-) Compiled tutorials and resource links on React, Redux, ES6 and more react-redux-links
-
useState under the hood question
I strongly recommend reading/watching /u/swyx 's talk and post Getting Closure on React Hooks to see how this actually works under the hood. I've also got some additional links on hooks concepts and implementation here.
- A selected list of tutorials, articles, and resources on Javascript, React, Redux, and related topics. Brought to you by Mark Erikson
-
Would Redux survive without its maintainers high level of engagement?
For the next several months, I just sorta did issue triage and cleanup. I really didn't feel like I had the right to say anything about how the library worked or to mess with the source code. At the same time, I'd been putting together a "React/Redux Links List" repo, and answering a lot of Redux questions in Reactiflux.
-
Ultimate React Resources
3.React Redux Links
-
How to not learn Javascript
First because, there were always some more resources or links to go through. I kinda felt depressed to find Mark Erikson awesome list or resources. as I felt like I should go through it .
-
How do custom hooks really work under the hood?
For more details, see this list of articles explaining how React hooks actually work internally.
What are some alternatives?
redux - A JS library for predictable global state management
30-Days-Of-React - 30 Days of React challenge is a step by step guide to learn React in 30 days. These videos may help too: https://www.youtube.com/channel/UC7PNRuno1rzYPb1xLa4yktw
use-context-selector - React useContextSelector hook in userland
usehooks - Easy to understand React Hook code recipes
ducks-modular-redux - A proposal for bundling reducers, action types and actions when using Redux
awesome-react-components - Curated List of React Components & Libraries.
egui - egui: an easy-to-use immediate mode GUI in pure Rust
awesome-react-hooks - A curated list about React Hooks
react-handbook - ⚛🤌 Modern approaches to architecture and feature development in React apps.
youtube-clone - The repository helps you learn React and Redux by building Youtube :star:
freeCodeCamp - freeCodeCamp.org's open-source codebase and curriculum. Learn to code for free.
didact - A DIY guide to build your own React