revert #5578 - #5793
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5793 +/- ##
=======================================
Coverage 93.51% 93.52%
=======================================
Files 110 110
Lines 39359 39337 -22
=======================================
- Hits 36808 36791 -17
+ Misses 2551 2546 -5 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
mcollina
left a comment
There was a problem hiding this comment.
Because this is how Node.js is supposed to interact with WHATWG spec objects that need this functionality and make the object ref'd / unref'd.
It has been there for quite some time:
https://nodejs.org/docs/latest/api/process.html#processrefmayberefable
cc @jasnell who added those in to Node.js in the first place.
jasnell
left a comment
There was a problem hiding this comment.
This isn't a browser implementation of WebSocket and the all caps in the PR description is really unnecessary.
|
Something that could be improved is making those property non-enumerable. |
|
tbh I wrote 2 posts arguing over it not being a "browser implementation", but I deleted them since I can't be bothered arguing. I will say that if WebSocket is not a browser implementation (since it certainly isn't compatible), then it should not exist. The implementation of WebSocket is embarrassingly bad and I regret ever adding it, since I could have saved myself so much time by doing |
reverts #5578 / 1089808
USE WS IF YOU NEED TO DO THIS
why does a browser implementation of WebSocket need all this bloat?