Tin mới
Single executable applications
Error propagation and interception#
Node.js supports several mechanisms for propagating and handling errors that occur while an application is running. How these errors are reported and handled depends entirely on the type of Error and the style of the API
Error propagation and interception#
Node.js supports several mechanisms for propagating and handling errors that occur while an application is running. How these errors are reported and handled depends entirely on the type of Error and the style of the API
Node.js supports several mechanisms for propagating and handling errors that occur while an application is running. How these errors are reported and handled depends entirely on the type of Error and the style of the API
Node.js supports several mechanisms for propagating and handling errors that occur while an application is running. How these errors are reported and handled depends entirely on the type of Error and the style of the API
Error propagation and interception#
Node.js supports several mechanisms for propagating and handling errors that occur while an application is running. How these errors are reported and handled depends entirely on the type of Error and the style of the API
Indicates the failure of an assertion. For details, see Class: assert.AssertionError.
Indicates that a program is not valid JavaScript. These errors may only be generated and propagated as a result of code evaluation. Code evaluation may happen as a result of eval, Function, require, or vm. These errors a
util.getSystemErrorName(error.errno)
The error.errno property is a negative number which corresponds to the error code defined in libuv Error handling.
A special type of error that is triggered whenever Node.js tries to get access to a resource restricted by the Permission Model.
require('node:crypto').setEngine()
An invalid crypto engine identifier was passed to require('node:crypto').setEngine().
v8.startupSnapshot.setDeserializeMainFunction()
v8.startupSnapshot.setDeserializeMainFunction() could not be called because it had already been called before.
The given ServerResponse was already assigned a socket.
An attempt was made to send an unsupported "handle" over an IPC communication channel to a child process. See subprocess.send() and process.send() for more information.
Both breakEvalOnSigint and eval options were set in the REPL config, which is not supported.
An element in the iterable provided to the WHATWG URLSearchParams constructor did not represent a [name, value] tuple – that is, if an element is not iterable, or does not consist of exactly two elements.
ERR_MESSAGE_TARGET_CONTEXT_UNAVAILABLE#
A message posted to a MessagePort could not be deserialized in the target vm Context. Not all Node.js objects can be successfully instantiated in any context at this time, and attempting to transfer them using postMessag
The Node.js error code for a QuicError thrown to abort a QUIC stream or session with an explicit application or transport error code.
The server.listen() method was called while a net.Server was already listening. This applies to all instances of net.Server, including HTTP, HTTPS, and HTTP/2 Server instances.
An invalid (negative) size was passed for either the recvBufferSize or sendBufferSize options in dgram.createSocket().
A named entry was requested from a ZipFile or ZipBuffer that does not contain an entry with that name.