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-javascript Not only is the debugger itself time-traveling, but those time-travel capabilities are exposed by our backend API: -... - Source: Hacker News / 2 months ago
I made a Replay recording of the sandbox:. Source: 11 months ago
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! Source: 11 months ago
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... - Source: Hacker News / 11 months ago
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:. Source: 12 months ago
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. Source: about 1 year ago
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. Source: about 1 year ago
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... - Source: Hacker News / about 1 year ago
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. Source: about 1 year ago
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/tomorrow_corporations_time_travelling_debugger/. - Source: Hacker News / about 1 year ago
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. Source: about 1 year ago
New post, this time for my company Replay! Source: over 1 year ago
I can assure that's not Brian Vaughn. (context: Brian and I work together at Replay.io). Source: over 1 year ago
I'll also make a plug for the debugging tool that I build for my day job, which could be helpful here. I 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. Source: over 1 year ago
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_!... - Source: Hacker News / over 1 year ago
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 :). Source: over 1 year ago
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... Source: over 1 year ago
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... - Source: Hacker News / over 1 year ago
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... - Source: Hacker News / almost 2 years ago
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. Source: almost 2 years ago
Also, Redux itself is a Swiss army knife. You can put any state in there. That means it can be used for state that only lives in the client, and you can also use it as a place to cache "server state" as well. While it's certainly common to use Redux as a server state cache, there's also lots of reasons to use Redux for state that only ever lives on the client. (We do a lot of that in my day job at Replay.io -... Source: almost 2 years ago
Do you know an article comparing Replay.io to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Replay.io. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.