Node.js error codes

An invalid (negative) size was passed for either the recvBufferSize or sendBufferSize options in dgram.createSocket().

An API function expecting a port >= 0 and < 65536 received an invalid value.

An API function expecting a socket type (udp4 or udp6) received an invalid value.

While using dgram.createSocket(), the size of the receive or send Buffer could not be determined.

Data could not be sent on a socket.

An attempt was made to operate on an already closed socket.

When calling net.Socket.write() on a connecting socket and the socket was closed before the connection was established.

The socket was unable to connect to any address returned by the DNS within the allowed timeout when using the family autoselection algorithm.

A dgram.connect() call was made on an already connected socket.

A dgram.disconnect() or dgram.remoteAddress() call was made on a disconnected socket.

A call was made and the UDP subsystem was not running.

An operation was attempted on a BoundSocket that had already been adopted by a net.Server or net.Socket, or transferred to another thread. Once a bound socket is adopted or transferred, its address() and close() methods can no longer be used.

The source map could not be parsed because it does not exist, or is corrupt.

A file imported from a source map was not found.

The provided module import does not provide a source phase imports representation for source phase import syntax import source x from 'x' or import.source(x).

An error was returned from SQLite.

A string was provided for a Subresource Integrity check, but was unable to be parsed. Check the format of integrity attributes by looking at the Subresource Integrity specification.

An attempt was made to close the process.stderr stream. By design, Node.js does not allow stdout or stderr streams to be closed by user code.

An attempt was made to close the process.stdout stream. By design, Node.js does not allow stdout or stderr streams to be closed by user code.

A stream method was called that cannot complete because the stream was finished.

An attempt was made to call stream.pipe() on a Writable stream.

A stream method was called that cannot complete because the stream was destroyed using stream.destroy().

A stream/iter API was used without the --experimental-stream-iter CLI flag enabled.

An attempt was made to call stream.write() with a null chunk.

An error returned by stream.finished() and stream.pipeline(), when a stream or a pipeline ends non gracefully with no explicit error.

An attempt was made to call stream.push() after a null(EOF) had been pushed to the stream.

Used when an attempt is made to use a readable stream that has not implemented readable._read().

An attempt was made to pipe to a closed or destroyed stream in a pipeline.

An attempt was made to call stream.unshift() after the 'end' event was emitted.

Prevents an abort if a string decoder was set on the Socket or if the decoder is in objectMode.

An attempt was made to call stream.write() after stream.end() has been called.

An attempt has been made to create a string longer than the maximum allowed length.

An artificial error object used to capture the call stack for diagnostic reports.

An unspecified or non-specific system error has occurred within the Node.js process. The error object will have an err.info object property with additional details.

An error representing a failing lexer state.

An error representing a failing parser state. Additional information about the token causing the error is available via the cause property.

This error represents a failed TAP validation.

This error represents a failed test. Additional information about the failure is available via the cause property. The failureType property specifies what the test was doing when the failure occurred.

A call was dropped because a throttled function could not invoke it immediately or its pending queue was full.

This error is thrown when an ALPNCallback returns a value that is not in the list of ALPN protocols offered by the client.