Repository navigation
worker.onmessage is not called #26856
Description
Activity
- addedworkerIssues and PRs related to the worker_threads module and Worker API.Issues and PRs related to the worker_threads module and Worker API.
on Mar 27, 2019 Thanks, we should also consider supporting
.addEventListenerand.removeEventListeneras well.
Web Worker in the browser support it.- addedfeature requestIssues requesting new Node.js features.Issues requesting new Node.js features.
on Jun 26, 2020 Refs: #34057
Reacted by Anna HenningsenTo be clear, #34057 does this for
MessagePort, notWorker. I’m not sure whether we really want this for theWorkerclass itself.Yep, not really seeing much value in having
WorkerextendEventTargetright now.There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be 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.
- addedstaleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Mar 8, 2022 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.
If you run the
main.mjsfile above, you’ll see only the EventEmitter handler is called, but not the one registered viaonmessage.I think for consistence (as well as the fake MessageEvent handling introduced in #26082), it is desirable to add support for
onmessageonWorker.cc @addaleax