Daniel

This is basically a duplicate of #281 / it works, please see #281 (you need to manually specify the patch version)

I just had this dumb error too: ``` TypeError [ERR_INVALID_ARG_TYPE]: The "event" argument must be an instance of Event. Received an instance of OpenEvent at new NodeError (node:internal/errors:363:5) at EventTarget.dispatchEvent...

Yeah I actually figured out that I can't redispatch events anyways, not even in the browser. So nvm for my part. But it would still be better if you used...

> The once option is already supported. See 2e5c01f. Ah ok, but if I use .onmessage at the same time it doesn't seem to work IIRC

> > Ah ok, but if I use .onmessage at the same time it doesn't seem to work IIRC > > It works if `websocket.addEventListener()` is used after `websocket.onmessage`. It...

> If I understood correctly the spec, using on... remove all the previous handlers, both on... and addEventListener ones. That's why on... ones are totally discouraged and unrecommended in W3C...

> I respect your opinion, but I didn't do it. I've just tried to improve it. From #1818 (comment) Ah shoot, np. Thanks. Then node is the weird thing and...

> The EventEmitter came first and is more efficient in terms of both performance and memory usage. Weird. Why would they do that? > Yes, I guess that is a...

Damn, that's awesome. Props to you! One frustration less for users.

Also experiencing this issue when trying to workaround https://github.com/parcel-bundler/parcel/issues/7609 by using `bundle-text:` instead :( ``` 🚨 Build failed. Error: Cannot read properties of undefined (reading 'hashReferences') TypeError: Cannot read properties...