redux-essentials-example-app
devtools
Our great sponsors
redux-essentials-example-app | devtools | |
---|---|---|
37 | 44 | |
291 | 651 | |
1.7% | 1.1% | |
0.0 | 9.8 | |
2 months ago | 3 days ago | |
CSS | TypeScript | |
- | GNU General Public License v3.0 or later |
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-essentials-example-app
- Redux vs Zustand
- Designing an async app as a long time backend engineer dedicated to synchronous pages. Help!
-
I was struggling with MVx architectures for years and now I can explain why
You're right, it is related. But I think that Flux- and ELM-like architectures are making it even worse by forcing any "external" interaction to became the gap. Look how they suffer when it comes to executing any async operation like network request. Initially we have this relatively simple framework, but then we had to add "Middleware" to just run network request (which is a good example of the Remainder issue). I love the idea behind these architectures, which makes logic more predictable and testing way easier. I even was using them by myself. But now they looks like something turned inside out for me. I believe we could do better. I'm finishing my proposal right now. It will take couple more weeks to edit and translate it, but soon I'll show what I mean.
-
JavaScript State Machines and Statecharts
Hi, I maintain Redux and wrote most of our docs (including our current tutorials).
Can you give some details on which parts of our docs you feel are "incomprehensible"? I'm curious which specific pages you've been looking at, and for what purpose.
We've tried to organize the docs using the "Documentation System" approach described at [0]: Tutorials for teaching step-by-step, Explanations and How-To guides for specific topics, and References for API details.
Generally we want people to go through our "Redux Essentials" tutorial [1] as the primary way to learn how to use Redux correctly. It teaches "modern Redux" patterns with Redux Toolkit as the standard way to write Redux logic (including RTK Query for handling data fetching), and React-Redux hooks in components.
I'm genuinely interested in feedback on what explanations aren't clear and how we can improve things!
[0] https://documentation.divio.com/
[1] https://redux.js.org/tutorials/essentials/part-1-overview-co...
- Best React Course 2023 (intermediate / advanced)
- Redux vs Redux toolkit
-
Redux, RTK, React Query, Typescript resources
https://redux.js.org/tutorials/essentials/part-1-overview-concepts (covers how to use Redux Toolkit and RTK Query)
- I don't get why I should use Redux
- What library or tool is causing you the most pain right now?
- Beginner’s guide to Redux
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...
- https://github.com/Replayio/Protocol-Examples
-
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:
-
Replay.io: announcing our new Replay for Test Suites feature! Time-travel debug Cypress (and Playwright) tests in CI
Hiya folks! In addition to all my free time spent working on Redux, answering questions, and modding this sub, my day job is working on Replay.io. Today we're thrilled to announce our new Replay for Test Suites feature, which lets you record and time-travel debug Cypress (and Playwright) E2E tests as they ran in CI!
-
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.
-
The 2023 guide to React debugging | Raygun Blog
I currently work for Replay.io, where we're building a true time-travel debugger for JS apps. If you haven't seen it, check it out - it makes debugging so much easier, and I've solved many bugs that would have been impossible otherwise
-
Ask HN: Is debugging TypeScript worse then JavaScript?
That's not a "TypeScript" problem. That's a "JS being transpiled and bundled" problem (of which TS is just one possible example of "transpiling").
JS debuggers (browsers, VS Code, etc) normally use sourcemaps to show you what the original source looked like so you can debug that.
Also, I'll put in a plug for my day job, Replay ( https://replay.io ). Our app is meant to help simplify debugging scenarios by making it easy to record, reproduce and investigate your code.
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.
Note that Replay also works best when you have sourcemaps, same as the other debugger tools.
What are some alternatives?
zustand - 🐻 Bear necessities for state management in React
legend-state - Legend-State is a super fast and powerful state library that enables fine-grained reactivity and easy automatic persistence
redux-eggs - Add some Eggs to your Redux store.
hookstate - The simple but very powerful and incredibly fast state management for React that is based on hooks
jotai - 👻 Primitive and flexible state management for React
scaffold-eth - 🏗 forkable Ethereum dev stack focused on fast product iterations [Moved to: https://github.com/scaffold-eth/scaffold-eth]
rr - Record and Replay Framework
scaffold-eth - 🏗 forkable Ethereum dev stack focused on fast product iterations
dark - Darklang main repo, including language, backend, and infra
react-redux - Official React bindings for Redux