redux-devtools-extension
rtk-query
Our great sponsors
redux-devtools-extension | rtk-query | |
---|---|---|
10 | 47 | |
13,473 | 579 | |
- | - | |
0.0 | 8.7 | |
6 months ago | almost 3 years ago | |
JavaScript | TypeScript | |
MIT License | 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.
redux-devtools-extension
-
State Management Nx React Native/Expo Apps with TanStack Query and Redux
Dev tools: @redux-devtools/extension
-
WHAT THE REDUX
As alternative to redux devtools extension in our store. I posted a link to ComposewithDevTools. Which can be use in place of the redux devtools line in our store. Check section 1.3 for more details. ComposeWithDevTools
-
Stop Overcomplicating your State – Try Zustand
With the middleware functionality, we can easily actually use an amazing extension created for Redux, Redux DevTools link. We just need to import the devtools middleware, and attach it to our store.
-
Part 2: Redux-React
Redux DevTools, https://github.com/zalmoxisus/redux-devtools-extension React Developer Tools, https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi/related?hl=ko
-
Redux boilerplate was never the problem
FWIW, I added an "action stack trace" feature to the Redux DevTools a couple years ago. Click on any action in the left list, and then click the "Trace" tab in the upper right to view the exact stack trace where it was dispatched from.
-
Developer Tools & Debugging in NgRx
When working on a complex software solution, we often find ourselves scratching our heads over a bug that was reported to us. It's essential to have proper tools to trace the issues which like to hide in our code execution paths. Luckily for the devs using NgRx in their project, the application state is kept in a single location and all the actions that can modify it are easily traceable with some great DevTools. As NgRx adheres to the redux pattern, we can use the same Redux DevTools as we would use for any other Redux base application. This tool is essential for me when debugging an NgRx based application.
-
React Common Tools and Practices: State Management Overview
If any react noobs are reading this, the best React state management setup for you is Redux+Immer. After some setup, it's easy to use, and the docs are very good and up to date.
When I was learning React, I kept putting off Redux because youtube said it was complicated and you didn't need it after useContext. Big mistake. Our app became more complicated because our state management(useState/useContext) was so simple. Switching to Redux dramatically simplified our most complicated components.
Also, the Redux dev tools extension is a game changer. It lets you see every state change, in order, with traces and diffs.
https://github.com/zalmoxisus/redux-devtools-extension
Pros can obviously make up their own mind. I’ve tried Mobx and the tooling just wasn’t there, but I hear their diffing algos are good.
-
Advanced Blazor State Management Using Fluxor, part 2
Fluxor also supports the ReduxDevTools browser extension. To enable it, first install the NuGet package Fluxor.Blazor.Web.ReduxDevTools:
- Does Redux state populate after useEffect() ?
-
Learn redux-toolkit in 10 steps
Redux devtools chrome extension: https://github.com/zalmoxisus/redux-devtools-extension
rtk-query
-
What I Learned as a Web Dev on My First React Native Project
The Redux library is quite a common choice thanks to its broad ecosystem. Luckily, there is now a very useful Redux Toolkit that mitigates the amount of boilerplate you have to usually write. RTK Query is a very new Redux solution for data fetching and caching, hopefully making our lives even easier. Though the web seems to slowly be moving away from Redux to React Query, SWR or other solutions, mobile is a different story; Redux is holding on to its popularity, as it integrates well with libraries that persist and rehydrate the global state for users when they relaunch the app.
-
Is there an effective solution for implementing data-fetching logic while keeping the codebase DRY?
rtk query is built-in to the redux toolkit starting from v 1.6
-
Using Redux vs Regular States?
For api data. Check out rtk query https://rtk-query-docs.netlify.app/ It is supposed to better for api data with redux. I have not yet tried it.
-
Kea: Production Ready React State Management
I haven't looked at Kea in a while, but I'll toss out some comparisons based on my knowledge of RTK and what I remember about Kea + looking at its docs.
Kea's main selling point is that it lets you define self-contained chunks of Redux logic. Initially, this is similar to RTK's `createSlice`, in that you're writing a set of "case reducers" + action creators. However, it also build in Redux-Saga as a general-purpose side effects approach, and lets you write "listeners" that respond to dispatched actions.
Where it particularly differs from RTK is in the amount of abstraction included. RTK tries to stay "visibly Redux" [0], and the abstractions are fairly thin - the focus is on simplifying the typical Redux code patterns, without hiding the fact that you're using Redux. Kea is much more heavily abstracted. It does use a number of Redux terms ("actions", "reducers", etc), but the code that you write looks noticeably different than a "typical" Redux app. Also, RTK focuses on thunks as the default async approach, rather than sagas [1]
I believe Kea also has some mechanisms for combining together those "logic" chunks in various ways, including doing so dynamically at runtime, and it appears to have some "lifecycle"-type callbacks for handling when those chunks get mounted and unmounted.
RTK Query [2] [3], on the other hand, is a purpose-built data-fetching abstraction, most similar to React Query and Apollo. Its only purpose is to fetch data from whatever URL endpoints you've defined, handle the loading state, update the cache with the results, and re-render whatever components care about that data.
I haven't actually used Kea myself, but it does appear to have some meaningful thought and development put into it. I would still recommend RTK as the default approach for anyone wanting to use Redux (and of course I'm biased there), but Kea has some interesting approaches.
[0] https://blog.isquaredsoftware.com/2019/10/redux-starter-kit-...
[1] https://blog.isquaredsoftware.com/2020/02/blogged-answers-wh...
[2] https://rtk-query-docs.netlify.app
[3] https://github.com/reduxjs/redux-toolkit/releases/tag/v1.6.0...
-
Redux Toolkit v1.6 alpha.1: RTK Query APIs integrated and smaller bundles with Redux 4.1!
https://github.com/rtk-incubator/rtk-query/issues/215#issuecomment-826344927
-
Apollo or redux for state?
tl;dr Apollo, URQL, SWR, react-query, nor even RTK Query are meant to be wholesale replacements for Redux which is meant for global state.
- RTK Query 0.3 Final Beta: custom query functions, lazy queries, and more!
-
Use case for redux-thunk?
You may want to look into our upcoming "RTK Query" API, which is specifically designed to abstract the process of fetching and caching data for Redux. We've got one more alpha release coming up that we're finalizing now, and then we'll be merging the APIs back into Redux Toolkit itself and releasing it.
-
Cousins playing nicely: Experimenting with NgRx Store and RTK Query
Redux provides state management that has been widely used across many different web ecosystems for a long time. NgRx provides a more opinionated, batteries-included framework for managing state and side effects in the Angular ecosystem based on the Redux pattern. Redux Toolkit provides users of Redux the same batteries-included approach with conveniences for setting up state management and side effects. The Redux Toolkit (RTK) team has recently released RTK Query, described as "an advanced data fetching and caching tool, designed to simplify common cases for loading data in a web application", built on top of Redux Toolkit and Redux internally. When I first read the documentation for RTK Query, it immediately piqued my interest in a few ways:
-
Need help in choosing state management library.
Check out RTK Query since you are already using Redux.
What are some alternatives?
zustand - 🐻 Bear necessities for state management in React
redux-saga - An alternative side effect model for Redux apps
nami - Nami Wallet is a browser based wallet extension to interact with the Cardano blockchain. Support requests: https://iohk.zendesk.com/hc/en-us/requests/new
react-query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]
redux-toolkit-example
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
msw - Seamless REST/GraphQL API mocking library for browser and Node.js.
BlazorWithFluxor - A demo of Blazor Wasm using Fluxor as application state management
Recoil - Recoil is an experimental state management library for React apps. It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.
Android Debug Bridge - ADB
redux-persist - persist and rehydrate a redux store