1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: remove errors that were never released

Browse Source 
Refs: https://github.com/nodejs/node/pull/33764#issuecomment-653667275

PR-URL: https://github.com/nodejs/node/pull/34197
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
This commit is contained in:
Rich Trott 2020-07-04 06:26:30 -07:00 committed by James M Snell
parent 9f0671ebc9
commit bf772896fe
1 changed files with 0 additions and 72 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

72
doc/api/errors.md
View File

@ -2631,78 +2631,6 @@ removed: v10.0.0
Used when an attempt is made to use a `zlib` object after it has already been
closed.
### Other error codes
These errors have never been released, but had been present on master between
releases.
<a id="ERR_ENTRY_TYPE_MISMATCH"></a>
#### `ERR_ENTRY_TYPE_MISMATCH`
The `--entry-type=commonjs` flag was used to attempt to execute an `.mjs` file
or a `.js` file where the nearest parent `package.json` contains
`"type": "module"`; or
the `--entry-type=module` flag was used to attempt to execute a `.cjs` file or
a `.js` file where the nearest parent `package.json` either lacks a `"type"`
field or contains `"type": "commonjs"`.
<a id="ERR_FS_WATCHER_ALREADY_STARTED"></a>
#### `ERR_FS_WATCHER_ALREADY_STARTED`
An attempt was made to start a watcher returned by `fs.watch()` that has
already been started.
<a id="ERR_FS_WATCHER_NOT_STARTED"></a>
#### `ERR_FS_WATCHER_NOT_STARTED`
An attempt was made to initiate operations on a watcher returned by
`fs.watch()` that has not yet been started.
<a id="ERR_HTTP2_ALREADY_SHUTDOWN"></a>
#### `ERR_HTTP2_ALREADY_SHUTDOWN`
Occurs with multiple attempts to shutdown an HTTP/2 session.
<a id="ERR_HTTP2_ERROR"></a>
#### `ERR_HTTP2_ERROR`
A non-specific HTTP/2 error has occurred.
<a id="ERR_INVALID_REPL_HISTORY"></a>
#### `ERR_INVALID_REPL_HISTORY`
Used in the `repl` in case the old history file is used and an error occurred
while trying to read and parse it.
<a id="ERR_INVALID_REPL_TYPE"></a>
#### `ERR_INVALID_REPL_TYPE`
The `--entry-type=...` flag is not compatible with the Node.js REPL.
<a id="ERR_STREAM_HAS_STRINGDECODER"></a>
#### `ERR_STREAM_HAS_STRINGDECODER`
Used to prevent an abort if a string decoder was set on the Socket.
```js
const Socket = require('net').Socket;
const instance = new Socket();
instance.setEncoding('utf8');
```
<a id="ERR_STRING_TOO_LARGE"></a>
#### `ERR_STRING_TOO_LARGE`
An attempt has been made to create a string larger than the maximum allowed
size.
<a id="ERR_TTY_WRITABLE_NOT_READABLE"></a>
#### `ERR_TTY_WRITABLE_NOT_READABLE`
This `Error` is thrown when a read is attempted on a TTY `WriteStream`,
such as `process.stdout.on('data')`.
[`'uncaughtException'`]: process.html#process_event_uncaughtexception
[`--disable-proto=throw`]: cli.html#cli_disable_proto_mode
[`--force-fips`]: cli.html#cli_force_fips