Devtools Alternatives

Similar projects and alternatives to devtools

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better devtools alternative or higher similarity.

devtools reviews and mentions

Posts with mentions or reviews of devtools. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-09-19.
  • The Hate around Redux and co?
    3 projects | reddit.com/r/reactjs | 19 Sep 2022
    I also recently wrote a proof of concept Suspense cache backed by RTK Query, proving that it's possible to do that, and we've got some experimental PRs playing with ways to add Suspense support directly into RTK Query's hooks.
  • I am sick and tired of react-redux. Who has some good alternatives?
    18 projects | reddit.com/r/reactjs | 11 Sep 2022
    To be honest, it's hard. The day job app I work on ( https://github.com/replayio/devtools ) still has a bunch of "setter actions", and I've even written a few of those myself.
  • Reverse Debugging and Other Stories
    2 projects | news.ycombinator.com | 23 Aug 2022
    Yep, this is why we're building a time-travel debugger for JS at https://replay.io .

    The basic idea of Replay: Use our special browser or Node forks 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.

    We record the OS-level syscalls from the browser, and replay those in the cloud against hundreds of process forks of the exact browser version while you're debugging. When you step backwards, evaluate a print statement that ran many times, or jump to a different pause point, the backend is using those many forked processes to evaluate those results and ship the info to the debugging client.

    I can say that we personally use Replay to debug our own dev work on Replay on a daily basis, and it makes a _huge_ difference. I recently used Replay to debug an obscure E2E test failure ( https://twitter.com/acemarke/status/1547682026181996554 ), and a bug with React-Redux v8's `connect` and React's experimental `` ( https://twitter.com/acemarke/status/1559643125865390083 ).

    See https://replay.io/record-bugs for the getting started steps to use Replay, and we've got some neat articles about some of the technology at https://docs.replay.io/docs/how-replay-works-2adcccaf8f7743f... .

    If you've got any questions, please come by our Discord and ask! https://replay.io/discord

  • Do I need old Redux.
    4 projects | reddit.com/r/reactjs | 13 Aug 2022
    Ironically, my current day job ( https://replay.io ) is itself an old React + Redux app - most of the original code was written 2015-2016. So, I've been doing a lot of work to modernize that code over the last few months :)
    4 projects | reddit.com/r/reactjs | 13 Aug 2022
  • Slices vs APIs - Redux Toolkit
    6 projects | reddit.com/r/reactjs | 12 Aug 2022
    Also, I'm happy to chat about how to handle the migration! I've been doing a lot of that work myself over in https://github.com/replayio/devtools - you can see a lot of the PRs I've merged have been about migrating React+Redux to RTK and TS. Best place to chat would be the #redux channel over in the Reactiflux Discord ( https://www.reactiflux.com ).
  • what's the most complex issue you've had to use a state management library (redux) for
    3 projects | reddit.com/r/reactjs | 8 Aug 2022
    I currently work for https://replay.io, which is a true time-traveling debugger for JS apps. We use Redux to manage all the state related to the debugger itself, which includes a lot of code to sync behavior with our backend via an SDK client. For example, every time you add a print statement, we tell the backend to run "analysis" on that line at various points in time, then display the results. We also store data on all the source files in the recording so we can show the sources folder tree, fetch the text contents of the current source file, hit counts for each line, and a lot more. The app actually makes heavy use of thunks for imperative control flow.
    3 projects | reddit.com/r/reactjs | 8 Aug 2022
    The Replay codebase is fully open source - you can see it at https://github.com/replayio/devtools , including all the work Brian Vaughn and I have been doing for the last few months to refactor and clean up the internals from the original legacy Firefox Devtools codebase the app started from.
  • Launch HN: DeploySentinel (YC S22) – End-to-end tests that don't flake
    2 projects | news.ycombinator.com | 2 Aug 2022
    Obligatory alternative tool plug / comparison:

    I work for https://replay.io , which is a true time-traveling debugger for JS. We have forks of Firefox, Chrome, and Node, instrumented to capture syscalls at the OS level. Those recordings are uploaded to the cloud, and devs can then use our web client (effectively the Firefox DevTools as an app + a bunch of new features) to debug the recording at _any_ point in time, including adding print statements after the fact that show values every time a line was hit, step debugging, network requests, React + Redux DevTools integration, DOM inspection, and more.

    Currently, our main usage is manually recorded replays, but we're actually working on similar test integration features as well. We can record Playwright and Cypress tests, upload recordings of test runs, show results per test in our dashboard, and let you debug the full recordings of each successful and failed test. The test suite feature is early closed beta atm - we've been dogfooding it ourselves and it's _really_ helpful!

    Based on your description + a quick glance at your home page, sounds like we're addressing the same use case in similar ways, with some differences in the underlying recording technology nadi mplementations

  • The new wave of React state management
    23 projects | news.ycombinator.com | 2 Jul 2022
    Depends on what you mean here specifically :)

    I'll agree that the Redux DevTools "skip action" and "jump back to action" features are not all that commonly used in practice. I _maintain_ Redux, and I don't even use them that often.

    On the other hand, the ability to see a written list of all dispatched action type names is valuable by itself. So is the ability to click one of the listed actions and see the action contents, state diff, and final state. _That_ is very powerful.

    Beyond that... I now work 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 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.

    I actually recently implemented a POC version of support for the Redux DevTools in our Replay debugging app, so that if you do record a Redux app (or Jotai, or Zustand, or NgRx), you can use that same Redux DevTools UI to see the action history.

    So, yes, time travel debugging _is_ an amazingly powerful concept. It's just ironic that that particular aspect of Redux didn't end up getting used that much... but the Redux DevTools themselves are still valuable, and Replay is actually a far superior "time travel debugger" overall.

  • A note from our sponsor - SonarQube
    www.sonarqube.org | 29 Sep 2022
    Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free. Learn more →

Stats

Basic devtools repo stats
24
346
0.0
about 22 hours ago

replayio/devtools is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.

Truly a developer’s best friend
Scout APM is great for developers who want to find and fix performance issues in their applications. With Scout, we'll take care of the bugs so you can focus on building great things 🚀.
scoutapm.com
Find remote jobs at our new job board 99remotejobs.com. There are 5 new remote jobs listed recently.
Are you hiring? Post a new remote job listing for free.