That's not quite correct. From https://github.com/feross/webtorrent-hybrid https://github.com/feross/webtorrent-hybrid: > In node.js, the webtorrent package on

That's not quite correct. From https://github.com/feross/webtorrent-hybrid https://github.com/feross/webtorrent-hybrid: > In node.js, the webtorrent package only connects to normal TCP/UDP peers, not WebRTC peers. That's why there's this webtorrent-hybrid client which runs a hidden electron process to communicate with WebRTC peers and normal TCP/UDP peers. According to the readme, there's (understandably; it's running chromium in the background) a lot of overhead with this method so they're working toward a non-electron version of WebRTC in Node.