vercel[bot]
commented
1 year ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| socket-io-website | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jul 8, 2023 10:14am |
darrachequesne
I faced the problem with socket.io and it's documentation didn't helped. So I spent some time to find the answer that my problem was a conflict between express-status-monitor and socket.io because status monitor also runs socket.io instance:
From their github:
If you're using socket.io in your project, this module could break your project because this module by default will spawn its own socket.io instance. To mitigate that, fill websocket parameter with your main socket.io instance as well as port parameter.So I think it will be helpful to add this case in the troubleshooting section. I put a link on their GitHub repo where people can find a solution instead of writing the solution in docs just in case they will change something.