We apologize for the delayed response.
As for the 404 error, your license is valid, so you have access to the @email@example.com package. Perhaps it is installed on you with the wrong registry. A working method for different versions of node/npm is described here: Webix Installation Guide of Getting Started, Start Coding with Webix Webix Docs.
The warnings that appear do not need attention. Since some dependencies are outdated, they work stably and will be updated in future versions.
Speaking of localhost on port 3200, this is just an example. In all examples, we write some kind of URL that roughly corresponds to what needs to be used with our demo backends.
Here, for example, is a chat background that can be used as a basis/reference for your chat:
Depending on how the backend is running (docker/standalone), the URL for the chat configuration will be
As for the chat and web server connection, our component allows you to completely replace our backend layer with a custom one.
Our backend is quite secure.
It is assumed that the user first undergoes authorization (outside of our component), during which a temporary token is transferred to the client (this is a cryptographically signed consent by the server that the user can use the chat, his ID in the chat).
And then when the chat is connected, a token is transferred there
That is, authorization is carried out first, and the chat does not interact with the authorization topic.
It is impossible to fake the token; it is signed by the server.
To steal a token, you need to have access to the user’s session, which means you need to hack the site or his account, which is already a big problem.
Please, if you have any further questions, be sure to ask. We will be happy to answer!