devtools
react-redux
Our great sponsors
devtools | react-redux | |
---|---|---|
44 | 82 | |
648 | 23,221 | |
1.9% | 0.5% | |
9.9 | 9.1 | |
1 day ago | 6 days ago | |
TypeScript | 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.
devtools
-
Is Something Bugging You?
Exactly - that's what we've already built for web development at https://replay.io :)
I did a "Learn with Jason" show discussion that covered the concepts of Replay, how to use it, and how it works:
- https://www.learnwithjason.dev/travel-through-time-to-debug-...
Not only is the debugger itself time-traveling, but those time-travel capabilities are exposed by our backend API:
- https://static.replay.io/protocol/
Our entire debugging frontend is built on that API. We've also started to build new advanced features that leverage that API in unique ways, like our React and Redux DevTools integration and "Jump to Code" feature:
- https://blog.replay.io/how-we-rebuilt-react-devtools-with-re...
- https://blog.isquaredsoftware.com/2023/10/presentations-reac...
-
Weird Debugging Tricks the Browser Doesn't Want You to Know
Replay's founders originally worked as engineers on the Firefox DevTools (and in fact our debugger client UI started as a fork of the FF Devtools codebase, although at this point we've rewritten basically every single feature over the last year and a half). So, the original Replay implementation started as a feature built into Firefox, and thus the current Replay recording browser you'd download has been our fork of Firefox with all the recording capabilities built in.
But, Chromium is the dominant browser today. It's what consumers use, it's devs use for daily development, and it's what testing tools like Cypress and Playwright default to running your tests in. So, we're in the process of getting our Chromium fork up to parity with Firefox.
Currently, our Chromium for Linux fork is fully stable in terms of actual recording capability, and we use it extensively for recording E2E tests for ourselves and for customers. (in fact, if you want to, all the E2E recordings for our own PRs are public - you could pop open any of the recordings from this PR I merged yesterday [0] and debug how the tests ran in CI.)
But, our Chromium fork does not yet have the UI in place to let a user manually log in and hit "Record" themselves, the way the Firefox fork does. It actually automatically records each tab you open, saves the recordings locally, and then you use our CLI tool to upload them to your account. We're actually working on this "Record" button _right now_ and hope to have that available in the next few weeks.
Meanwhile, our Chrome for Mac and Windows forks are in early alpha, and the runtime team is focusing on stability and performance.
Our goal is to get the manual recording capabilities in place ASAP so we can switch over and make Chromium the default browser you'd download to make recordings as an individual developer. It's already the default for configuring E2E test setups to record replays, since the interactive UI piece isn't necessary there.
Also, many of the new time-travel-powered features that we're building rely on capabilities exposed by our Chromium fork, which the Firefox fork doesn't have. That includes the improved React DevTools support I've built over the last year, which relies on our time-travel backend API to extract React component tree data, and then does post-processing to enable nifty things like sourcemapping original component names even if you recorded a production app. I did a talk just a couple weeks ago at React Advanced about how I built that feature [1]. Meanwhile, my teammate Brian Vaughn, who was formerly on the React core team and built most of the current React DevTools browser extension UI, has just rebuilt our React DevTools UI components and started to integrate time-travel capabilities. He just got a working example of highlighting which props/hooks/state changed for a selected component, and we've got some other neat features like jumping between each time a component rendered coming soon. All that relies on data extracted from Chromium-based recordings.
[0] https://github.com/replayio/devtools/pull/9885#issuecomment-...
[1] https://blog.isquaredsoftware.com/2023/10/presentations-reac...
- Evading JavaScript Anti-Debugging Techniques
-
Why does the `useSyncExternalStore`docs example call `getSnapshot` 6 times on store update?
I made a Replay recording of the sandbox:
-
Firefox displayed a pop-up ad for Mozilla VPN over an unrelated page
FWIW, the Firefox devs who were doing the WebReplay time travel debugging POC weren't, as far as I know, fired. Instead, they left and started Replay ( https://replay.io ), a true time-traveling debugger for JavaScript.
I joined Replay as a senior front-end dev a year ago. It's real, it works, we're building it, and it's genuinely life-changing as a developer :)
Not sure how well this would have fit into Firefox as a specific feature, given both the browser C++ runtime customizations and cloud wizardry needed to make this work. But kinda like Rust, it's a thing that spun out of Mozilla and has taken on a life of its own.
Obligatory sales pitch while I'm writing this:
The basic idea of Replay: Use our special browser to make a recording of your app, load the recording in our debugger, and you can pause at any point in the recording. In fact, you can add print statements to any line of code, and it will show you what it would have printed _every time that line of code ran_!
From there, you can jump to any of those print statement hits, and do typical step debugging and inspection of variables. So, it's the best of both worlds - you can use print statements and step debugging, together, at any point in time in the recording.
See https://replay.io/record-bugs for the getting started steps to use Replay, or drop by our Discord at https://replay.io/discord and ask questions.
-
What is not taught in React courses, but is commonly used in a real job and overlooked?
I also recently did a Learn with Jason show episode based on this, where we went through many of the same topics, and also looked at the Replay.io time-traveling debugger that I build as my day job:
-
Dan Abramov responds to React critics
My day job is working at a company called Replay ( https://replay.io ), and we're building a true "time traveling debugger" for JS. Our app is meant to help simplify debugging scenarios by making it easy to record, reproduce and investigate your code.
-
Introducing Suspense: APIs to simplify data loading and caching, for use with React Suspense.
Not directly, no. Brian used to be part of the React core team, but he (and I) both joined https://replay.io last year. We've built up these utils as we've been refactoring our codebase, and Brian extracted them into their own package.
-
Omniscient Debugging
Yep, my day job is working on the Replay time-traveling debugger for JS ( https://replay.io/ ).
Also saw someone post an indie gaming company's TTD development environment yesterday:
https://www.reddit.com/r/programming/comments/11a2meo/tomorr...
-
Tomorrow Corporation's time travelling debugger, including debugging other people's play sessions, hot asset reloading, live compilation on every keystroke and more
I actually work for Replay ( https://replay.io ), where we're building a time-traveling debugger for JS apps. It's interesting to hear some of the similarities and differences in approaches and usages, since this is the kind of thing I work with on a daily basis myself.
react-redux
-
Free Resources Every Web Developer Should Know About
React Redux (https://react-redux.js.org/)
-
Get out of state management hell with automatic revalidation
You add the current user state to a React Context or state management library, read from it on the top bar, and write to it after a user signs in. Done. No big deal, right?
- Redux 101
- Redux Toolkit 2.0: new features, faster perf, smaller bundle sizes (plus major versions for all Redux family packages!)
-
Redux Toolkit 2.0: new features, faster perf, smaller bundle sizes, and more
- Throws better errors in an RSC environment
- https://github.com/reduxjs/react-redux/releases/tag/v9.0.0
## Reselect 5.0:
- Switches to a new `weakMapMemoize` memoizer as default
- Renames `defaultMemoize` to `lruMemoize`
- Allows passing memoizer options direct to `createSelector`
- Many TS improvements
- https://github.com/reduxjs/reselect/releases/tag/v5.0.1
## Redux Thunk 3.0:
- Drops the default export and switches to named exports ( `{thunk, withExtraArgument}` )
- https://github.com/reduxjs/redux-thunk/releases/tag/v3.1.0
This has been a _huge_ year-long development effort!
We're thrilled to get these improvements out. The tooling and bundle improvements will help all users, and we think the features and TS changes will improve the Redux dev experience significantly.
Thank you SO MUCH to everyone who has contributed or helped test out the work!
Please file bug reports for the inevitable issues that pop up post-release!
but now I'm going off on a conf trip and going to take a very well-earned break from Redux work for December :)
-
45 NPM Packages to Solve 16 React Problems
redux with react-redux
-
Easy Shared Reactive State in React without External Libraries
Redux
-
20 Essential Parts Of Any Large Scale React App
react-redux : Integration with React
-
I am making a pizza app and I want that whenever I click on add my cart gets updated which is at the bottom of the page. Can anyone please help
You should think about using some client state management libraries like Redux. Redux gives you the possibility to encapsulate states and manipulate it through functions. https://react-redux.js.org/
-
What Are Signals?
`useSyncExternalStore` was shipped live in React 18.0 and is fully ready for production use.
Source: I'm the primary Redux maintainer, and worked with Andrew Clark of the React team to nail down the semantics and behavior needed by `useSyncExternalStore` in practice. They had the idea, but discussed a lot of the necessary use cases with us and other lib maintainers, and a lot of its internal implementation is directly related to how React-Redux's `useSelector` hook was implemented already.
I built the first working code that used it by prototyping React-Redux v8's switch from our own internal subscription handling to `useSyncExternalStore` instead and gave Andrew feedback:
What are some alternatives?
axios - Promise based HTTP client for the browser and node.js
Express - Fast, unopinionated, minimalist web framework for node.
recompose - A React utility belt for function components and higher-order components.
reselect - Selector library for Redux
kea - Batteries Included State Management for React
redux - Predictable state container for JavaScript apps
cerebral - Declarative state and side effects management for popular JavaScript frameworks
react-final-form - 🏁 High performance subscription-based form state management for React
valtio - 💊 Valtio makes proxy-state simple for React and Vanilla
redux-batched-subscribe - store enhancer for https://github.com/reactjs/redux which allows batching subscribe notifications.
effector-react - Business logic with ease ☄️
alt - Isomorphic flux implementation