Replay.io Reviews and details

Social recommendations and mentions

• Show HN: Time travel debugging AI for more reliable vibe coding

  Hi HN, I'm the CEO at https://replay.io. We've been building a time travel debugger for web apps for several years now (previous HN post: https://news.ycombinator.com/item?id=28539247). We recently launched Nut (https://nut.new) as an open source project which uses this tech for building apps through prompting (vibe coding), similar to e.g. https://bolt.new and https://v0.dev. We want Nut to fix bugs effectively... - Source: Hacker News / about 2 months ago

• Time Travel Debugging: Beyond Console.log

  Tools like replay.io and Firefox's DevTools let you record your application's execution and play it back later. It's like TiVo for your code! - Source: dev.to / 3 months ago

• Don't Look Down on Print Debugging

  Have you ever been able to try https://replay.io time travel debugging as an alternative to conventional logging? Last time I tried it you were able to add logging statements "after the fact" (i.e. After reproducing the bug) and see what they would have printed. I believe they also have the ability to act like a conventional debugger. I think they're changing some aspects of their business model but the core... - Source: Hacker News / 5 months ago

• A (Mostly) Complete Guide to React Rendering Behavior

  Not at this time. I'm pretty full up at this point with day job ( https://replay.io ), conferences, and personal life stuff. My current ongoing Redux maintenance task is trying to revamp our "Redux Essentials" tutorial to be TS-first. Making slower progress on that than I'd wanted, but hopefully can get that wrapped up in the not _too_ distant future. Beyond that, we've got a ton of open RTK Query feature requests... - Source: Hacker News / 12 months ago

• 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-javascript Not only is the debugger itself time-traveling, but those time-travel capabilities are exposed by our backend API: -... - Source: Hacker News / about 1 year ago

• Why does the `useSyncExternalStore`docs example call `getSnapshot` 6 times on store update?

  I made a Replay recording of the sandbox:. Source: almost 2 years ago

• 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! Source: almost 2 years ago

• 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... - Source: Hacker News / almost 2 years ago

• 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:. Source: about 2 years ago

• 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. Source: about 2 years ago

• 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. Source: about 2 years ago

• 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... - Source: Hacker News / about 2 years ago

• 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. Source: about 2 years ago

• 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/tomorrow_corporations_time_travelling_debugger/. - Source: Hacker News / about 2 years ago

• 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. Source: about 2 years ago

• How We Rebuilt React DevTools with Replay Routines

  New post, this time for my company Replay! Source: over 2 years ago

• will firing of 11.000 devs on Meta hurt React in any way?

  I can assure that's not Brian Vaughn. (context: Brian and I work together at Replay.io). Source: over 2 years ago

• How to use stacktrace to pinpoint where in the code to look for errors

  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 2 years ago

• Reverse Debugging and Other Stories

  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 2 years ago

• Do I need old Redux.

  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 2 years ago

• what's the most complex issue you've had to use a state management library (redux) for

  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 2 years ago