Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit b4091ea

Browse filesBrowse files
jasnelldanielleadams
jasnell
authored and
danielleadams
committed
doc: clarify when messageerror is emitted
Adapting addaleax's explanation from the issue. Fixes: #36333 Signed-off-by: James M Snell <jasnell@gmail.com> PR-URL: #36780 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
1 parent 61b0393 commit b4091ea
Copy full SHA for b4091ea

File tree

Expand file treeCollapse file tree

1 file changed

+6
-0
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+6
-0
lines changed
Open diff view settings
Collapse file

‎doc/api/worker_threads.md‎

Copy file name to clipboardExpand all lines: doc/api/worker_threads.md
+6Lines changed: 6 additions & 0 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -452,6 +452,12 @@ added:
452452

453453
The `'messageerror'` event is emitted when deserializing a message failed.
454454

455+
Currently, this event is emitted when there is an error occurring while
456+
instantiating the posted JS object on the receiving end. Such situations
457+
are rare, but can happen, for instance, when certain Node.js API objects
458+
are received in a `vm.Context` (where Node.js APIs are currently
459+
unavailable).
460+
455461
### `port.close()`
456462
<!-- YAML
457463
added: v10.5.0

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.