peerjs VS peerjs-server

this app is using peerjs to connect peers over a webrtc connection. check out thier docs for more info. with webrtc, things like file-transfer, should be very performant compared to cloud storage providers... especially over LAN. network speed doesnt seems to be an issue i have experienced.

I'm using the client-side PeerJS https://peerjs.com/ library for networking. As the name may imply, a direct connection is established between two peers using WebRTC via "handshake" through an intermediary server they host - and, they provide source for the server as well. I have found it to be quite reliable, thus far.

You kind of sound like a beginner. The browser APIs are a bit painful to work with. It might be easier to use PeerJS: https://peerjs.com/

If you want you can use Preact. PreactJS is a lightweight alternative to ReactJS, designed for high performance and compatibility. is often used in applications where performance is critical and has a small footprint.

This opens up a lot of neat possibilities, and fortunately I found a very easy JavaScript library for handling multiplayer called PeerJS. The way you can send packets from player to player is very simple and something even a beginner to JavaScript could understand.

You might be able to eliminate the VPS by making it P2P using something like PeerJS [1]. PeerJS provides a free shared connection broker server.

[1]: https://peerjs.com/

Note: peerjs is a good starting point!

We use peer.js module to create a WebRTC connection between clients

Now that we have all the required boilerplate we can start building the actual game. For the communications between peers we are going to use PeerJS a peer-to-peer library built on top of WebRTC.

i would like to aim for this to not be nessesary. the peerjs-server is used only to establish a webrtc connection (note: there is an option during profile creating to set a custom host for selfhosters). the app doesnt use anything like a central database... details like encryption and authentication is handled by frontend javascript as described by this code.

my code results in the static files you can save from the link to the app (html, js, css, etc). you can ctrl/cmd+s to save the statics and host them on a static-server of your choice (easier than me providing a .zip?). you can also host your own peerjs-server.

Hi, Peer.JS internally uses a publicly hosted version of PeerServer (https://github.com/peers/peerjs-server) , if you don’t specify your own. This is basically the back end “server” I mentioned in your solution that will internally store a map of IDs to webrtc ICE candidates (use to connect between two peers)

I am using https://peerjs.com/. I am currently using their default brokering system (which is the default out-of-the-box). it seems (when necessary) i am able to run my own version as provided at: https://github.com/peers/peerjs-server