// script.js
const wsUri = "ws://localhost:3000";
const outputDiv = doc.getElementById("output");
const messageInput = doc.getElementById("message");
const sendButton = doc.getElementById("send-btn");
let websocket;
perform join() {
websocket = new WebSocket(wsUri);
websocket.onopen = perform (occasion) {
outputDiv.innerHTML += "Related to server!
";
};
websocket.onmessage = perform (occasion) {
const receivedMessage = occasion.knowledge;
outputDiv.innerHTML += "Acquired: " + receivedMessage + "
";
};
websocket.onerror = perform (occasion) {
outputDiv.innerHTML += "Error: " + occasion.error + "
";
};
websocket.onclose = perform (occasion) {
outputDiv.innerHTML += "Connection closed.
";
};
}
sendButton.addEventListener("click on", perform () {
const message = messageInput.worth;
if (websocket && websocket.readyState === WebSocket.OPEN) {
websocket.ship(message);
messageInput.worth = "";
} else {
outputDiv.innerHTML += "Error: Connection not open.
";
}
});
join(); // Join instantly
This script units up a number of occasion handlers utilizing the browser-native API. We begin up the WebSocket as quickly because the script is loaded and look ahead to open, onclose, onmessage, and onerror occasions. Every one appends its updates to the DOM. Crucial one is onmessage, the place we settle for the message from the server and show it.
The Click on handler on the button itself takes the enter typed in by the person (messageInput.worth) and makes use of the WebSocket object to ship it to the server with the ship() perform. Then we reset the worth of the enter to a clean string.
Assuming the again finish remains to be operating and accessible at ws://localhost:3000, we will now run the entrance finish. We will use http-server as a easy strategy to run the entrance finish. It’s a easy strategy to host static information in an online server, akin to Python’s http module or Java’s Easy Internet Server, however for Node. It may be put in as a worldwide NPM bundle or just run with npx, from the consumer listing:
