From a52aedeae08b57daedae56fd818be09df5f32e86 Mon Sep 17 00:00:00 2001 From: Anna Henningsen Date: Thu, 7 Mar 2019 10:18:03 +0100 Subject: worker: remove `ERR_CLOSED_MESSAGE_PORT` This aligns `MessagePort`s more with the web API. Refs: https://github.com/nodejs/node/issues/26463 PR-URL: https://github.com/nodejs/node/pull/26487 Reviewed-By: Benjamin Gruenbaum Reviewed-By: Gireesh Punathil Reviewed-By: James M Snell Reviewed-By: Ruben Bridgewater --- doc/api/errors.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) (limited to 'doc/api/errors.md') diff --git a/doc/api/errors.md b/doc/api/errors.md index ebe7de64a2..f59a9ffcf5 100644 --- a/doc/api/errors.md +++ b/doc/api/errors.md @@ -688,12 +688,6 @@ Used when a child process is being forked without specifying an IPC channel. Used when the main process is trying to read data from the child process's STDERR/STDOUT, and the data's length is longer than the `maxBuffer` option. - -### ERR_CLOSED_MESSAGE_PORT - -There was an attempt to use a `MessagePort` instance in a closed -state, usually after `.close()` has been called. - ### ERR_CONSOLE_WRITABLE_STREAM @@ -1986,6 +1980,16 @@ A module file could not be resolved while attempting a [`require()`][] or > Stability: 0 - Deprecated. These error codes are either inconsistent, or have > been removed. + +### ERR_CLOSED_MESSAGE_PORT + + +There was an attempt to use a `MessagePort` instance in a closed +state, usually after `.close()` has been called. + ### ERR_HTTP2_FRAME_ERROR