Protocol-Examples

Example apps demonstrating how to use the Replay Protocol API (by replayio)

Protocol-Examples Alternatives

Similar projects and alternatives to Protocol-Examples

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

Protocol-Examples reviews and mentions

Posts with mentions or reviews of Protocol-Examples. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-13.
  • Is Something Bugging You?
    10 projects | news.ycombinator.com | 13 Feb 2024
    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

  • Future-Proofing Web Scraping via JavaScript Runtime Heap Snapshots
    8 projects | news.ycombinator.com | 29 Apr 2022
    Not _quite_ what you're describing, but Replay [0], the company I work for, _is_ building a true "time-traveling debugger" for JS. It works by recording the OS-level interactions with the browser process, then re-running those in the cloud. From the user's perspective in our debugging client UI, they can jump to any point in a timeline and do typical step debugging. However, you can also see how many times any line of code ran, and also add print statements to any line that will print out the results from _every time that line got executed_.

    So, no heap analysis per se, but you can definitely inspect the variables and stack from anywhere in the recording.

    Right now our debugging client is just scratching the surface of the info we have available from our backend. We recently put together a couple small examples that use the Replay backend API to extract data from recordings and do other analysis, like generating code coverage reports and introspecting React's internals to determine whether a given component was mounting or re-rendering.

    Given that capability, we hope to add the ability to do "React component stack" debugging in the not-too-distant future, such as a button that would let you "Step Back to Parent Component". We're also working on adding Redux DevTools integration now (like, I filed an initial PR for this today! [2]), and hope to add integration with other frameworks down the road.

    [0] https://replay.io

    [1] https://github.com/RecordReplay/replay-protocol-examples

    [2] https://github.com/RecordReplay/devtools/pull/6601

Stats

Basic Protocol-Examples repo stats
2
8
4.6
7 months ago

replayio/Protocol-Examples is an open source project licensed under MIT License which is an OSI approved license.

The primary programming language of Protocol-Examples is TypeScript.


Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com