> Maybe I'm missing something but how Node-WebRTC preferable?

Maybe another way of putting it is, Node-WebRTC actually works.

Hahaha! Thank you for saying this! Yes! Not to at all disparage the other suggested library, but I think its intended use case is more teaching and learning (at least in part). It says as much on its homepage: https://shinyoshiaki.github.io/werift-webrtc/website/build/

Ideal for learning: The code base is very small and all the protocol stacks of WebRTC are in one repository. It is also very easy to build, so you can easily add or modify features yourself.

It is undoubtedly a commendable and extraordinary achievement to create a largely compliant implementation of WebRTC in TypeScript tho.

You cannot use that library in the browser (as you cannot reimplement the primitives that use UDP as there are essentially no browser APIs for that (barring the Chrome-focused WebTransport I think)), but creating it in Node using udp libraries is possible. It's fantastic and dedicated stuff, but may not be the right fit if you want performance and reliability.

Yeah, that too. Basically incomplete. When you have something critical that you use and depend on, you can't have that kind of stuff.