How Replay.io is Built and Maintaining Redux

How Replay.io is Built and Maintaining Redux

Tejas Kumar via YouTube Direct link

Running Code in the Browser

22 of 30

22 of 30

Running Code in the Browser

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

How Replay.io is Built and Maintaining Redux

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Introduction and Background
  2. 2 Replay.io and Time Travel Debugger
  3. 3 Modernizing the Codebase
  4. 4 The Challenges of Code Migration
  5. 5 Finding Joy in Legacy Code
  6. 6 Migrating to TypeScript
  7. 7 The Process of Modernization
  8. 8 The Pressure and Value of Modernization
  9. 9 The Trade-offs of Using the Latest Techniques
  10. 10 Capturing and Transmitting Data in Replay
  11. 11 Replay: Capturing and Replaying Browser Interactions
  12. 12 Why Replay Requires a Browser
  13. 13 Capturing Network Data and Security Concerns
  14. 14 Recording and Storing the Binary Archive
  15. 15 Downloading and Caching the Recording
  16. 16 Pre-Processing and Caching Basic Data
  17. 17 The Video Playback and Memory Snapshots
  18. 18 Inspecting Elements and the Bespoke Canvas
  19. 19 Building the Replay Debugger
  20. 20 Replay's Capabilities
  21. 21 Console Logging in Replays
  22. 22 Running Code in the Browser
  23. 23 Source Maps and Minified Code
  24. 24 Shipping Source Maps
  25. 25 Replay in Node.js
  26. 26 Using Replay in the Terminal
  27. 27 Manipulating Events in Replay
  28. 28 Replay's Backend API
  29. 29 Future Features: Root Cause Analysis and React Time Travel
  30. 30 Closing Remarks

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.