`Symbol.toStringTag` on `MessageChannel` and `MessagePort`
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
Version
v26.7.0
Platform
Darwin MacBook-Air-3.local 25.5.0 Darwin Kernel Version 25.5.0: Tue Jun 9 22:26:46 PDT 2026; root:xnu-12377.121.10~1/RELEASE_ARM64_T8103 arm64
Subsystem
No response
What steps will reproduce the bug?
node -e "console.log(Object.prototype.toString.call(new MessageChannel()))"
node -e "console.log(Object.prototype.toString.call(new MessageChannel().port1))"
How often does it reproduce? Is there a required condition?
Always. No special required condition.
What is the expected behavior? Why is that the expected behavior?
Display [object MessageChannel] and [object MessagePort] respectively.
What do you see instead?
[object Object]
[object EventTarget]
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the two node -e reproduction commands from the issue and trace the MessageChannel and MessagePort runtime entry points that determine their object tags. Done means the calls produce [object MessageChannel] and [object MessagePort], with regression coverage added for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100