MessagePort#onmessage type changed in @types/[email protected]

[yume-chan]

In @types/[email protected], both events are MessageEvents:

const port = new MessagePort();

port.onmessage = (event) => {
  console.log(event.data)
}

port.addEventListener('message', event => {
  console.log(event.data)
})

Playground: https://www.typescriptlang.org/play/?lib=lib.esnext.d.ts&ts=5.7.2#code/PTAEAEBsEsCMC5QFMDOA7JAPALgKF9ALYAOA9gE7agDk42AnsasAIYCuAJtKQO4UDWkJNmoBuUCFAMmKRAAYAdIoBsAFnwBjUmhRUylUAF5QGHqACyqFCwDmSAAoVsACgCUo-PuwLthK7aQjUGckADckNGxXIwA+UABvXFBQLR1SIQVIUhsQ8MiFDhZsFldcAF9PJwUWDg4AUTzsABloXQikcmdqPxRrO2oAGmRG2ISklO0UdKRM7NyI70Li0rLXIA

---

In @types/[email protected], the event in onmessage becomes Event:

const port = new MessagePort();

port.onmessage = (event) => {
  console.log(event.data) // Property 'data' does not exist on type 'Event'. (2339)
}

port.addEventListener('message', event => {
  console.log(event.data)
})

Playground: https://www.typescriptlang.org/play/?lib=lib.esnext.d.ts&ts=5.7.2#code/PTAEAEBsEsCMC5QFMDOA7JAPALgKF9ALYAOA9gE7agDk42AnsasAIYCuAJtKQO4UDWkJNmoBuUCFAMmKRAAYAdIoBsAVnwBjUmhRUylUAF5QGHqACyqFCwDmSAAoVsACgCUo-PuwLthK7aQjUGckADckNGxXIwA+UABvXFBQLR1SIQVIUhsQ8MiFDhZsFmjJe3JSJkp6GkLi6lAOUlQTUiosaF1QbSlGQOoAUTyRBWCAJgBmCYBOV1wAX08nBRYODiGI7AAZTuwIpHJnaj8UaztqABpkYdiEpJTtFHSkTOzczYKikoXXIA

---

Is it intended?

[Bashamega]

Hello @yume-chan 😃,

This looks like a bug. Feel free to open a PR if you'd like! If you don’t have time, just let me know, and I’ll take care of it.

[yume-chan]

Looks like it has already been fixed in version 0.0.66: playground

[Bashamega]

Your are right