Any way we can make socket.io easier to debug with a debugger
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 63.2k
- Forks
- 10.3k
- Avg merge
- 11d 20h
- Merged PRs (30d)
- 2
Description
I noticed that whenever I go in with an IDE debugger for socket.io I cannot debug because as I am working through the code the connection is closed and I cannot go to the next step and I am forced to use log statements and try my best to debug the problem. Is there a better solution that could allow me to use the debugger and go through the code slowly without the connection being closed?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file, test, or entry point. Start by reproducing the debugger pause behavior in a socket.io connection, then trace what closes the connection while stepping through the code. Done should mean a developer can pause and advance through the relevant code without the connection being closed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100