node VS rrweb

Replay deterministically replays the recording, so if the state of the application when you recorded it caused a network call, then when replaying it we will also "make" a network call _but_, instead of actually going out to the network we will instead return the exact data that was returned when you recorded it.

You can learn more about how Replay works here https://medium.com/replay-io/how-replay-works-5c9c29580c58

Can you expand more on what you mean by a race condition in network calls? If it's a series of network calls that the browser could make in any order than we will make them in the order that they occurred when you recorded it. If it's a race condition that occurs in your backend, then the Replay browser won't really help there (though it will show you the responses you got from your backend when you recorded it).

For help with that, you might want to use Replay on the backend. Right now we have Node support (https://github.com/RecordReplay/node), but other runtimes are on the roadmap.

Interesting project!

How does this compare to rrweb[0], the library that Sentry and many other commercial offerings for frontend monitoring use?

[0]: https://www.rrweb.io/

Congrats on being the only commercial company to actually sponsor rrweb[0] rather than just fork it and contribute absolutely nothing back (or in the case of Sentry - remove their copyright and violate their license).

Seeing as you're "open-source", why chose to fork and detach the project rather than contribute directly to it? With a detached fork, other users can't even compare your changes to the original and pull in fixes. If you truly believed in the spirit of open source, you'd believe in working together and giving back, not just taking advantage of a free lunch.

It feels like all these "open-source" companies are just closed source but with open-source as a marketing gimmick.

[0] https://github.com/rrweb-io/rrweb

if you want I can help to install www.rrweb.io free, DM me

In the end, I had to experiment quite a few times. First, I tried using rrweb since it was something that was already on my radar. The idea is I would record using that and convert it into a video using rrvideo.

I didn't think postHog was a good comparison either,

I knew of rrweb https://www.rrweb.io/

Great to see more open source contendants in the space

(something like https://www.rrweb.io/)

I'm indie/solo making Linkkraft browser (to make a living from it). Browser to be effective researcher & collector. It visualizes your steps as tree and makes html snapshot for your each step (even steps in SPAs like twitter).