-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
events: remove NodeEventTarget #33665
Conversation
The extending of EventTarget with EventEmitter emulation is contentious and not something that is strictly necessary for minimal support. Signed-off-by: James M Snell <jasnell@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes LGTM though I do see value in exposing this like we expose Buffer on top of types arrays.
Where did this get pushback?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not think this is comparable to Buffer, because Buffer existed in Node.js before typed arrays. EventTarget
is a new API and nothing in the ecosystem can rely on NodeEventTarget
yet because it was never released.
8ae28ff
to
2935f72
Compare
Fwiw, I’m somewhat under the impression that this would make turning Or, put another way: It would require something like (There’s also the question of whether it’s possible to perform that change to |
We can hold off on this if there is other places we can use it. The pushback that I've seen in really in the places we'd use it... like |
I like the approach we took with NodeEventTarget and we can take a similar approach for |
The extending of EventTarget with EventEmitter emulation is contentious
and not something that is strictly necessary for minimal support.
/cc @benjamingr
Signed-off-by: James M Snell jasnell@gmail.com
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes