supabase-node-chat-backend VS Socket.io

Node - https://github.com/nsmet/supabase-node-chat-backend/blob/main/src/utils/socket.ts

You can see the full code for the react native app here and the full code for the backend here

{ "name": "supabase-node-chat-backend", "version": "1.0.0", "description": "Node backend for a chat application, using Supabase", "main": "index.ts", "scripts": { "start": "nodemon -r dotenv/config src/index.ts", "lint": "eslint . --fix", "test": "echo \"Error: no test specified\" && exit 1" }, "repository": { "type": "git", "url": "git+https://github.com/nsmet/supabase-node-chat-backend.git" }, "keywords": [ "supabase", "node", "chat" ], "author": "Nick Smet", "license": "ISC", "bugs": { "url": "https://github.com/nsmet/supabase-node-chat-backend/issues" }, "homepage": "https://github.com/nsmet/supabase-node-chat-backend#readme", "dependencies": { "@supabase/supabase-js": "^2.4.1", "body-parser": "^1.20.1", "dotenv": "^16.0.3", "express": "^4.18.2", "socket.io": "^4.5.4" }, "devDependencies": { "@types/express": "^4.17.15", "@types/node": "^18.11.18", "@typescript-eslint/eslint-plugin": "^5.48.2", "@typescript-eslint/parser": "^5.48.2", "eslint": "^8.32.0", "nodemon": "^2.0.20", "ts-node": "^10.9.1", "typescript": "^4.9.4" } }

The first is the script tag in the head of our HTML document that loads the Socket.IO client library. This script tag includes the Socket.IO client library that will communicate with our socket.io server from the code above.

Before diving into this tutorial, if you find microservices mysterious, check out my previous article for a detailed explanation. In this hands-on tutorial, we'll build a real-time chat server using Node.js, Socket.io, RabbitMQ, and Docker. Get ready for a practical journey into the world of microservices! Let's begin.

Socket.io Docs

Now we will be implementing socket logic using socket.io for building websockets. This library provides an abstraction layer on top of WebSockets, simplifying the process of creating real-time applications. For better maintainability, it is recommended to create a separate file for socket calls. To do this, navigate to the src folder, create a folder named services, and inside it, create a file named socket.ts under the services folder.

Hi I made a chat app using socket.io it worked fine locally but when i deployed the app on render.com socket is not working properly i have to refresh the page to see new messages please help...

Nextjs + socket.io.. Planning to use webrtc for video calls later

Implementação em Node usando Socket.io

I am using socket.io for real-time notification service. Previously my frontend part was deployed in Netlify and here the notification was not working properly as Netlify follows serverless architecture.

yes. Im running on DreamCompute currently. Discord.js and socket.io within same app. A dedicated server works too, but pricier.

No, not a library. More like, the frontend and backend just happen to need the same version to be compatible (socket.io is a good example, moment.js was the most basic I could think of).