Unable to install @rtco/client
AnupamKris opened this issue · comments
I stumbled upon this project searching for peerjs which is not maintained anymore. But I cant seem to install this..
error Couldn't find package "@rtco/logger@*" required by "@rtco/client" on the "npm" registry.
I tried both yarn and npm, both gave me the same error.
Hey @AnupamKris! Thanks for trying out this project and reporting the issue.
Let me take a look and see if I can figure out how to fix it.
@AnupamKris Try the latest packages v0.1.22 and let me know if that worked for you. Feel free to open issues for any other things you may find.
I'm actively working on this now, so any help testing is much appreciated.
Yes, now it's installed! I'll try to test this very soon. Also, the call demo page is working now, it wasn't when I tried.
I am not able to initialize the Artico class
index.mjs:1 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'signaling')
I see that it's not connecting to the signalling server. Does this library provide a default server like peerjs or should I host one?
Also the server example is a 404 🙃
@AnupamKris I'm not seeing that specific error, but I do see it's failing to connect to the signaling server. That's because I had it setup to connect to localhost when NODE_ENV=development, which I realize is not good since most people will have that set during development. I do provide a public signaling server by default, just like PeerJS.
As for https://demo.artico.dev , I'm currently doing work there, so things are still pretty unstable as I'm actively working on this. I'm hoping to stabilize things in the next couple of weeks, as I get more time to work on the project.
Try v0.1.25 and let me know if it works now. Thank you for your patience!
On a different note, if you find this project useful, please consider giving it a star. That will help getting visibility and possibly growing the project faster. Thank you!!
It works! Everything works as expected.. I'll try to create something with this as soon as I get home, or probably put an article on building a VC app with artico..
@AnupamKris Awesome! Thanks again for the support.
The latest version should have the Room functionality as well. The demo seems to be working okay now, so give that a try as well if you're interested. Would love to get more feedback when you have some!
Yup.. I saw the demo.. Imma try it right now.. Just to be clear, the room works like a mesh network right? can you explain how to setup the server, I want to create a uid for each user and don't want clashing ids. I tried running the server/index.ts it said listening but idk what to do next.
@AnupamKris I intend to have a whole documentation website soon that should explain all the pieces and how it all works. Right now it's a little too soon for that, as I working at a fast pace to get the core implementation done.
But you are correct, right now a Room is a mesh between all its peers. As for peer IDs, when Artico connects to the signaling server, it generates a random ID (or you can pass one if you want) and tells the Server "this is the ID I'd like to use". If the ID is available, the server emits the open event with the assigned peer ID. If not, the server emits an error saying the ID is not available.
If you want to setup your own server, just take a look at Artico's server app
Hi, I don't know whether this is a temporary issue, so I am putting it here. The calls are not getting connected over the network, the on("call") is getting triggered but the on("open") is not working. I created a temporary application and still the same and condition is the same in the demo site too..
This should be fixed on v0.1.29. Please give that a try and let me know!
Also, whenever you find new issues, feel free to create new issues, so we can keep track of them in here. Thanks again for reporting this @AnupamKris !