Implementation of close event of MessagePort API

[nononokam]

There was no timely and reliable way to detect when a MessagePort becomes disentangled, which made it difficult to release resources associated with ports.
We proposed to add a close event to MessagePort API.
The close event has landed to the HTML spec. Chrome has already completed implementation and it’s close to ship.

Initial issue: whatwg/html#1766
Explainer: https://github.com/fergald/explainer-messageport-close
HTML spec: https://html.spec.whatwg.org/multipage/web-messaging.html#disentangle
Chrome status: https://chromestatus.com/feature/5086799659794432
Mozilla standards position: mozilla/standards-positions#914
WebKit standards position: WebKit/standards-positions#271
HTML spec PR: whatwg/html#9933

Primary contacts: @rakina, @mingyc, @nononokam

[benjamingr]

@nodejs/workers

[github-actions]

There has been no activity on this feature request for 5 months. To help maintain relevant open issues, please add the never-stale Mark issue so that it is never considered stale label or close this issue if it should be closed. If not, the issue will be automatically closed 6 months after the last non-automated comment.
For more information on how the project manages feature requests, please consult the feature request management document.

[github-actions]

There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment.

For more information on how the project manages feature requests, please consult the feature request management document.

[juanarbol]

Hey, sorry for the delay, I'm probably misreading this.

https://nodejs.org/docs/latest/api/worker_threads.html#event-close

MessagePort already emits the close event.

https://nodejs.org/docs/latest/api/worker_threads.html#portclose

The 'close' event is emitted on both MessagePort instances that are part of the channel.