Node.js v14.11.0 文档

目录

Error（错误）#

中英对照提交修改

Node.js 应用程序一般会遇到以下四类错误：

  • 标准的 JavaScript 错误，例如 <EvalError>、<SyntaxError>、<RangeError>、<ReferenceError>、<TypeError> 或 <URIError>。
  • 由底层操作系触发的系统错误，例如试图打开不存在的文件、或试图使用已关闭的 socket 发送数据。
  • 由应用程序代码触发的用户自定义的错误。
  • AssertionError 错误，当 Node.js 检测到不应该发生的异常逻辑时触发。这类错误通常来自 assert 模块。

所有由 Node.js 引起的 JavaScript 错误与系统错误都继承自或实例化自标准的 JavaScript <Error> 类，且保证至少提供类中的属性。

错误的冒泡和捕获#

中英对照提交修改

Node.js 支持几种当应用程序运行时发生的错误的冒泡和处理的机制。 如何报告和处理这些错误完全取决于 Error 的类型和被调用的 API 的风格。

所有 JavaScript 错误都会被作为异常处理，异常会立即产生并使用标准的 JavaScript throw 机制抛出一个错误。 这些都是使用 JavaScript 语言提供的 try…catch 语句处理的。

// 抛出一个 ReferenceError，因为 z 未定义。
try {
  const m = 1;
  const n = m + z;
} catch (err) {
  // 在这里处理错误。
}

JavaScript 的 throw 机制的任何使用都会引起异常，异常必须使用 try…catch 处理，否则 Node.js 进程会立即退出。

除了少数例外，同步的 API（任何不接受 callback 函数的阻塞方法，例如 fs.readFileSync）会使用 throw 报告错误。

异步的 API 中发生的错误可能会以多种方式进行报告：

  • 大多数的异步方法都接受一个 callback 函数，该函数会接受一个 Error 对象传入作为第一个参数。 如果第一个参数不是 null 而是一个 Error 实例，则说明发生了错误，应该进行处理。
const fs = require('fs');
fs.readFile('一个不存在的文件', (err, data) => {
  if (err) {
    console.error('读取文件出错！', err);
    return;
  }
  // 否则处理数据
});

  • 当一个异步方法被一个 EventEmitter 对象调用时，错误会被分发到对象的 'error' 事件上。

    const net = require('net');
const connection = net.connect('localhost');

// 添加一个 'error' 事件句柄到一个流：
connection.on('error', (err) => {
  // 如果连接被服务器重置，或无法连接，或发生任何错误，则错误会被发送到这里。 
  console.error(err);
});

connection.pipe(process.stdout);

  • Node.js API 中有一小部分普通的异步方法仍可能使用 throw 机制抛出异常，且必须使用 try…catch 处理。 这些方法并没有一个完整的列表；请参见各个方法的文档以确定所需的合适的错误处理机制。

'error' 事件机制的使用常见于基于流和基于事件触发器的 API，它们本身就代表了一系列的异步操作（相对于要么成功要么失败的单一操作）。

对于所有的 EventEmitter 对象，如果没有提供一个 'error' 事件句柄，则错误会被抛出，并造成 Node.js 进程报告一个未处理的异常且随即崩溃，除非： 适当地使用 domain 模块或已经注册了一个 'uncaughtException' 事件的句柄。

const EventEmitter = require('events');
const ee = new EventEmitter();

setImmediate(() => {
  // 这会使进程崩溃，因为还为添加 'error' 事件句柄。
  ee.emit('error', new Error('这会崩溃'));
});

这种方式产生的错误无法使用 try…catch 截获，因为它们是在调用的代码已经退出后抛出的。

开发者必须查阅各个方法的文档以明确在错误发生时这些方法是如何冒泡的。

回调中的 Error 参数#

中英对照提交修改

大多数 Node.js 核心 API 所提供的异步方法都遵从错误信息优先的回调模式惯例，这种模式有时也称为 Node.js 式回调。在这种模式中，一个回调函数首先被作为参数传给异步方法。当该方法完成操作或产生错误时，它会调用回调函数，并将可能存在的 Error 对象作为第一个参数传给回调函数。如果没有错误产生，那么第一个参数为 null 。

const fs = require('fs');

function errorFirstCallback(err, data) {
  if (err) {
    console.error('出错', err);
    return;
  }
  console.log(data);
}

fs.readFile('/some/file/that/does-not-exist', errorFirstCallback);
fs.readFile('/some/file/that/does-exist', errorFirstCallback);

JavaScript的 try…catch 机制不能用来截获异步方法产生的错误。新手的常见错误之一是试图在错误优先回调函数中使用 throw ：

// 这不可行：
const fs = require('fs');

try {
  fs.readFile('/some/file/that/does-not-exist', (err, data) => {
    // 错误的假设：在这里抛出错误。
    if (err) {
      throw err;
    }
  });
} catch (err) {
  // 这里不会截获回调函数中的 throw。
  console.error(err);
}

这样做不可行，因为传递给 fs.readFile() 的回调函数是异步调用的。 当回调函数被调用时，程序早已退出其周围的代码（包括 try…catch 部分）。 在回调函数内抛出异常在大多数时候会使 Node.js 进程崩溃。 但如果启用了 domains，或者有与 process.on('uncaughtException') 相关联的异常处理器，就可以截获这种错误。

Error 类#

中英对照提交修改

通用的 JavaScript <Error> 对象，不表明错误发生的具体情况。 Error 对象会捕获堆栈跟踪，详细说明实例化 Error 的代码点，并可能提供错误的文本描述。

Node.js 产生的所有错误（包括所有的系统错误和 JavaScript 错误），都实例化自或继承自 Error 类。

new Error(message)#

中英对照提交修改

新建一个 Error 实例，并设置 error.message 属性以提供文本信息。 如果 message 传的是一个对象，则会调用 message.toString() 生成文本信息。 error.stack 属性表示被调用的 new Error() 在代码中的位置。 堆栈跟踪是基于 V8 的堆栈跟踪 API 的。 堆栈跟踪只会取（a）异步代码执行的开头或（b）Error.stackTraceLimit 属性给出的栈帧中的最小项。

Error.captureStackTrace(targetObject[, constructorOpt])#

中英对照提交修改

在 targetObject 上创建一个 .stack 属性，当访问时返回一个表示代码中调用 Error.captureStackTrace() 的位置的字符串。

const myObject = {};
Error.captureStackTrace(myObject);
myObject.stack;  // 类似 `new Error().stack`

${myObject.name}: ${myObject.message} 会作为该堆栈跟踪的第一行。

可选的 constructorOpt 参数接受一个函数。 如果提供了，则 constructorOpt 之上包括自身在内的全部栈帧都会被生成的堆栈跟踪省略。

constructorOpt 参数用在向最终用户隐藏错误生成的具体细节时非常有用。例如：

function MyError() {
  Error.captureStackTrace(this, MyError);
}

// 没传入 MyError 到 captureStackTrace，MyError 帧会显示在 .stack 属性。
// 通过传入构造函数，可以省略该帧，且保留其下面的所有帧。
new MyError().stack;

Error.stackTraceLimit#

中英对照提交修改

Error.stackTraceLimit 属性指定了堆栈跟踪收集的栈帧数量（无论是 new Error().stack 或 Error.captureStackTrace(obj) 产生的）。

默认值为 10 ，但可设为任何有效的 JavaScript 数值。 值改变后的变化会影响所有捕获到的堆栈跟踪。

如果设为一个非数值或负数，则堆栈跟踪不会捕捉任何栈帧。

error.code#

中英对照提交修改

error.code 属性是标识错误类别的字符标签。 error.code 是识别错误的最稳定方法。 它只会在 Node.js 的主要版本之间更改。 相反， error.message 字符串可能会在 Node.js 的任何版本之间发生变化。 详见 Node.js 错误码关于特定的错误码。

error.message#

中英对照提交修改

error.message 属性是错误的字符串描述，通过调用 new Error(message) 设置。 传给构造函数的 message 也会出现在 Error 的堆栈跟踪的第一行。 但是， Error 对象创建后改变这个属性可能不会改变堆栈跟踪的第一行（比如当 error.stack 在该属性被改变之前被读取）。

const err = new Error('错误信息');
console.error(err.message);
// 打印: 错误信息

error.stack#

中英对照提交修改

error.stack 属性是一个字符串，描述代码中 Error 被实例化的位置。

Error: Things keep happening!
   at /home/gbusey/file.js:525:2
   at Frobnicator.refrobulate (/home/gbusey/business-logic.js:424:21)
   at Actor.<anonymous> (/home/gbusey/actors.js:400:8)
   at increaseSynergy (/home/gbusey/actors.js:701:6)

第一行会被格式化为 <error class name>: <error message>，且带上一系列栈帧（每一行都以 "at " 开头）。 每一帧描述了一个代码中导致错误生成的调用点。 V8 引擎会试图显示每个函数的名称（变量名、函数名、或对象的方法名），但偶尔也可能找不到一个合适的名称。 如果 V8 引擎没法确定一个函数的名称，则只显示帧的位置信息。 否则，在位置信息的旁边会显示明确的函数名。

帧只由 JavaScript 函数产生。 例如，同步地执行一个名为 cheetahify 的 C++ 插件，且插件自身调用一个 JavaScript 函数，代表 cheetahify 回调的栈帧不会出现在堆栈跟踪里：

const cheetahify = require('./native-binding.node');

function makeFaster() {
  // `cheetahify()` 同步地调用 speedy。
  cheetahify(function speedy() {
    throw new Error('oh no!');
  });
}

makeFaster();
// will throw:
//   /home/gbusey/file.js:6
//       throw new Error('oh no!');
//           ^
//   Error: oh no!
//       at speedy (/home/gbusey/file.js:6:11)
//       at makeFaster (/home/gbusey/file.js:5:3)
//       at Object.<anonymous> (/home/gbusey/file.js:10:1)
//       at Module._compile (module.js:456:26)
//       at Object.Module._extensions..js (module.js:474:10)
//       at Module.load (module.js:356:32)
//       at Function.Module._load (module.js:312:12)
//       at Function.Module.runMain (module.js:497:10)
//       at startup (node.js:119:16)
//       at node.js:906:3

位置信息会是其中之一：

  • native，帧表示一个 V8 引擎内部的调用（比如， [].forEach）。
  • plain-filename.js:line:column，帧表示一个 Node.js 内部的调用。
  • /absolute/path/to/file.js:line:column，帧表示一个用户程序或其依赖的调用。

代表堆栈跟踪的字符串是在 error.stack 属性被访问时才生成的。

堆栈跟踪捕获的帧的数量是由 Error.stackTraceLimit 或当前事件循环中可用的帧数量的最小值界定的。

AssertionError 类#

中英对照提交修改

表明断言的失败。 详见 assert.AssertionError 类。

RangeError 类#

中英对照提交修改

表明提供的参数不在函数的可接受值的集合或范围内；无论是一个数字范围，还是在给定的函数参数的选项的集合之外。

require('net').connect(-1);
// 抛出 "RangeError: "port" option should be >= 0 and < 65536: -1"

Node.js 将会以参数验证的形式立即地生成并抛出 RangeError 实例。

ReferenceError 类#

中英对照提交修改

表明试图访问一个未定义的变量。 此类错误通常表明代码有拼写错误或程序已损坏。

虽然客户端代码可能产生和传播这些错误，但在实践中，只有 V8 引擎会这么做。

doesNotExist;
// 抛出 ReferenceError，在这个程序中 doesNotExist 不是一个变量。

除非应用程序是动态地生成并运行代码，否则 ReferenceError 实例表示代码中或其依赖中的错误。

SyntaxError 类#

中英对照提交修改

表明程序不是有效的 JavaScript。 这些错误可能仅在代码评估的结果中产生和传播。 代码评估可能产生自 eval、 Function、 require 或 vm。 这些错误几乎总是表明程序已损坏。

try {
  require('vm').runInThisContext('nodejs.cn ! 中文网');
} catch (err) {
  // `err` 是一个 SyntaxError。
}

SyntaxError 实例在创建它们的上下文中是不可恢复的，它们只可能被其他上下文捕获。

SystemError 类#

中英对照提交修改

Node.js generates system errors when exceptions occur within its runtime environment. These usually occur when an application violates an operating system constraint. For example, a system error will occur if an application attempts to read a file that does not exist.

  • address <string> If present, the address to which a network connection failed
  • code <string> The string error code
  • dest <string> If present, the file path destination when reporting a file system error
  • errno <number> The system-provided error number
  • info <Object> If present, extra details about the error condition
  • message <string> A system-provided human-readable description of the error
  • path <string> If present, the file path when reporting a file system error
  • port <number> If present, the network connection port that is not available
  • syscall <string> The name of the system call that triggered the error

error.address#

中英对照提交修改

如果存在，则 error.address 是描述网络连接失败的地址的字符串。

error.code#

中英对照提交修改

error.code 属性是表示错误代码的字符串。

error.dest#

暂无中英对照提交修改

If present, error.dest is the file path destination when reporting a file system error.

error.errno#

中英对照提交修改

error.errno 属性是一个负数，对应 libuv 错误处理 中定义的错误码。

在 Windows 上，系统提供的错误码由 libuv 进行规范化。

要获取错误码的字符串表示形式，则使用 util.getSystemErrorName(error.errno)。

error.info#

中英对照提交修改

如果存在，则 error.info 是一个对象，其中包含有关错误情况的详细信息。

error.message#

中英对照提交修改

error.message 是系统提供的可读性错误描述。

error.path#

中英对照提交修改

如果存在，则 error.path 是包含相关无效路径名的字符串。

error.port#

中英对照提交修改

如果存在，则 error.port 是不可用的网络连接端口。

error.syscall#

中英对照提交修改

error.syscall 属性是一个字符串，描述失败的系统调用。

常见的系统错误#

中英对照提交修改

以下列表是不完整的，但列举了编写 Node.js 程序时会遇到的一些常见的系统错误。 详细的列表可从 errno(3) 参考手册找到。

  • EACCES (拒绝访问): 试图以被一个文件的访问权限禁止的方式访问一个文件。

  • EADDRINUSE (地址已被使用): 试图绑定一个服务器（net、http 或 https）到本地地址，但因另一个本地系统的服务器已占用了该地址而导致失败。

  • ECONNREFUSED (连接被拒绝): 无法连接，因为目标机器积极拒绝。 这通常是因为试图连接到外部主机上的弃用的服务。

  • ECONNRESET (连接被重置): 一个连接被强行关闭。 这通常是因为连接到远程 socket 超时或重启。 常发生于 http 和 net 模块。

  • EEXIST (文件已存在): 一个操作的目标文件已存在，而要求目标不存在。

  • EISDIR (是一个目录): 一个操作要求一个文件，但给定的路径是一个目录。

  • EMFILE (系统打开了太多文件): 已达到系统文件描述符允许的最大数量，且描述符的请求不能被满足直到至少关闭其中一个。 当一次并行打开多个文件时会发生这个错误，尤其是在进程的文件描述限制数量较低的操作系统（如 macOS）。 要解决这个限制，可在运行 Node.js 进程的同一 shell 中运行 ulimit -n 2048。

  • ENOENT (无此文件或目录): 通常是由 fs 操作引起的，表明指定的路径不存在。给定的路径找不到文件或目录。

  • ENOTDIR (不是一个目录): 给定的路径虽然存在，但不是一个目录。 通常是由 fs.readdir 引起的。

  • ENOTEMPTY (目录非空): 一个操作的目标是一个非空的目录，而要求的是一个空目录，通常是由 fs.unlink 引起的。

  • ENOTFOUND (DNS查找失败): 表示 EAI_NODATA 或 EAI_NONAME 的 DNS 失败。 这不是标准的 POSIX 错误。

  • EPERM (操作不被允许): 试图执行一个需要更高权限的操作。

  • EPIPE (管道损坏): 写入一个管道、socket 或 FIFO 时没有进程读取数据。 常见于 net 和 http 层，表明远端要写入的流已被关闭。

  • ETIMEDOUT (操作超时): 一个连接或发送的请求失败，因为连接方在一段时间后没有做出合适的响应。 常见于 http 或 net。 往往标志着 socket.end() 没有被正确地调用。

TypeError 类#

中英对照提交修改

表明提供的参数不是被允许的类型。 例如，将函数传给期望字符串的参数，则会抛出 TypeError。

require('url').parse(() => { });
// 抛出 TypeError，因为它期望的是字符串。

Node.js 将会以参数验证的形式立即地生成并抛出 TypeError 实例。

异常与错误#

中英对照提交修改

JavaScript 异常是一个作为一个无效操作的结果或作为一个 throw 声明的目标所抛出的值。 虽然它不要求这些值是 Error 的实例或继承自 Error 的类的实例，但所有通过 Node.js 或 JavaScript 运行时抛出的异常都是 Error 实例。

有些异常在 JavaScript 层是无法恢复的。 这些异常总会引起 Node.js 进程的崩溃。 例如 assert() 检测或在 C++ 层调用的 abort()。

OpenSSL 错误#

暂无中英对照提交修改

Errors originating in crypto or tls are of class Error, and in addition to the standard .code and .message properties, may have some additional OpenSSL-specific properties.

error.opensslErrorStack#

暂无中英对照提交修改

An array of errors that can give context to where in the OpenSSL library an error originates from.

error.function#

暂无中英对照提交修改

The OpenSSL function the error originates in.

error.library#

暂无中英对照提交修改

The OpenSSL library the error originates in.

error.reason#

暂无中英对照提交修改

A human-readable string describing the reason for the error.

Node.js 错误码#

暂无中英对照提交修改

ERR_AMBIGUOUS_ARGUMENT#

暂无中英对照提交修改

A function argument is being used in a way that suggests that the function signature may be misunderstood. This is thrown by the assert module when the message parameter in assert.throws(block, message) matches the error message thrown by block because that usage suggests that the user believes message is the expected message rather than the message the AssertionError will display if block does not throw.

ERR_ARG_NOT_ITERABLE#

中英对照提交修改

需要可遍历的参数（也就是可使用 for...of 遍历的值），但没提供给 Node.js API。

ERR_ASSERTION#

暂无中英对照提交修改

A special type of error that can be triggered whenever Node.js detects an exceptional logic violation that should never occur. These are raised typically by the assert module.

ERR_ASYNC_CALLBACK#

中英对照提交修改

试图注册不是 AsyncHooks 回调的函数。

ERR_ASYNC_TYPE#

中英对照提交修改

异步资源的类型不合法。 如果使用公共嵌入的 API，则用户可以定义自己的类型。

ERR_BROTLI_COMPRESSION_FAILED#

暂无中英对照提交修改

Data passed to a Brotli stream was not successfully compressed.

ERR_BROTLI_INVALID_PARAM#

暂无中英对照提交修改

An invalid parameter key was passed during construction of a Brotli stream.

ERR_BUFFER_CONTEXT_NOT_AVAILABLE#

暂无中英对照提交修改

An attempt was made to create a Node.js Buffer instance from addon or embedder code, while in a JS engine Context that is not associated with a Node.js instance. The data passed to the Buffer method will have been released by the time the method returns.

When encountering this error, a possible alternative to creating a Buffer instance is to create a normal Uint8Array, which only differs in the prototype of the resulting object. Uint8Arrays are generally accepted in all Node.js core APIs where Buffers are; they are available in all Contexts.

ERR_BUFFER_OUT_OF_BOUNDS#

暂无中英对照提交修改

An operation outside the bounds of a Buffer was attempted.

ERR_BUFFER_TOO_LARGE#

暂无中英对照提交修改

An attempt has been made to create a Buffer larger than the maximum allowed size.

ERR_CANNOT_WATCH_SIGINT#

暂无中英对照提交修改

Node.js was unable to watch for the SIGINT signal.

ERR_CHILD_CLOSED_BEFORE_REPLY#

暂无中英对照提交修改

A child process was closed before the parent received a reply.

ERR_CHILD_PROCESS_IPC_REQUIRED#

暂无中英对照提交修改

Used when a child process is being forked without specifying an IPC channel.

ERR_CHILD_PROCESS_STDIO_MAXBUFFER#

暂无中英对照提交修改

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_CONSOLE_WRITABLE_STREAM#

暂无中英对照提交修改

Console was instantiated without stdout stream, or Console has a non-writable stdout or stderr stream.

ERR_CONTEXT_NOT_INITIALIZED#

暂无中英对照提交修改

The vm context passed into the API is not yet initialized. This could happen when an error occurs (and is caught) during the creation of the context, for example, when the allocation fails or the maximum call stack size is reached when the context is created.

ERR_CONSTRUCT_CALL_REQUIRED#

暂无中英对照提交修改

A constructor for a class was called without new.

ERR_CONSTRUCT_CALL_INVALID#

暂无中英对照提交修改

A class constructor was called that is not callable.

ERR_CPU_USAGE#

暂无中英对照提交修改

The native call from process.cpuUsage could not be processed.

ERR_CRYPTO_CUSTOM_ENGINE_NOT_SUPPORTED#

暂无中英对照提交修改

A client certificate engine was requested that is not supported by the version of OpenSSL being used.

ERR_CRYPTO_ECDH_INVALID_FORMAT#

暂无中英对照提交修改

An invalid value for the format argument was passed to the crypto.ECDH() class getPublicKey() method.

ERR_CRYPTO_ECDH_INVALID_PUBLIC_KEY#

暂无中英对照提交修改

An invalid value for the key argument has been passed to the crypto.ECDH() class computeSecret() method. It means that the public key lies outside of the elliptic curve.

ERR_CRYPTO_ENGINE_UNKNOWN#

暂无中英对照提交修改

An invalid crypto engine identifier was passed to require('crypto').setEngine().

ERR_CRYPTO_FIPS_FORCED#

暂无中英对照提交修改

The --force-fips command-line argument was used but there was an attempt to enable or disable FIPS mode in the crypto module.

ERR_CRYPTO_FIPS_UNAVAILABLE#

暂无中英对照提交修改

An attempt was made to enable or disable FIPS mode, but FIPS mode was not available.

ERR_CRYPTO_HASH_FINALIZED#

暂无中英对照提交修改

hash.digest() was called multiple times. The hash.digest() method must be called no more than one time per instance of a Hash object.

ERR_CRYPTO_HASH_UPDATE_FAILED#

暂无中英对照提交修改

hash.update() failed for any reason. This should rarely, if ever, happen.

ERR_CRYPTO_INCOMPATIBLE_KEY#

暂无中英对照提交修改

The given crypto keys are incompatible with the attempted operation.

ERR_CRYPTO_INCOMPATIBLE_KEY_OPTIONS#

暂无中英对照提交修改

The selected public or private key encoding is incompatible with other options.

ERR_CRYPTO_INVALID_DIGEST#

暂无中英对照提交修改

An invalid crypto digest algorithm was specified.

ERR_CRYPTO_INVALID_KEY_OBJECT_TYPE#

暂无中英对照提交修改

The given crypto key object's type is invalid for the attempted operation.

ERR_CRYPTO_INVALID_STATE#

暂无中英对照提交修改

A crypto method was used on an object that was in an invalid state. For instance, calling cipher.getAuthTag() before calling cipher.final().

ERR_CRYPTO_PBKDF2_ERROR#

暂无中英对照提交修改

The PBKDF2 algorithm failed for unspecified reasons. OpenSSL does not provide more details and therefore neither does Node.js.

ERR_CRYPTO_SCRYPT_INVALID_PARAMETER#

暂无中英对照提交修改

One or more crypto.scrypt() or crypto.scryptSync() parameters are outside their legal range.

ERR_CRYPTO_SCRYPT_NOT_SUPPORTED#

暂无中英对照提交修改

Node.js was compiled without scrypt support. Not possible with the official release binaries but can happen with custom builds, including distro builds.

ERR_CRYPTO_SIGN_KEY_REQUIRED#

暂无中英对照提交修改

A signing key was not provided to the sign.sign() method.

ERR_CRYPTO_TIMING_SAFE_EQUAL_LENGTH#

暂无中英对照提交修改

crypto.timingSafeEqual() was called with Buffer, TypedArray, or DataView arguments of different lengths.

ERR_CRYPTO_UNKNOWN_CIPHER#

暂无中英对照提交修改

An unknown cipher was specified.

ERR_CRYPTO_UNKNOWN_DH_GROUP#

暂无中英对照提交修改

An unknown Diffie-Hellman group name was given. See crypto.getDiffieHellman() for a list of valid group names.

ERR_DIR_CLOSED#

暂无中英对照提交修改

The fs.Dir was previously closed.

ERR_DIR_CONCURRENT_OPERATION#

暂无中英对照提交修改

新增于: v14.3.0

A synchronous read or close call was attempted on an fs.Dir which has ongoing asynchronous operations.

ERR_DNS_SET_SERVERS_FAILED#

暂无中英对照提交修改

c-ares failed to set the DNS server.

ERR_DOMAIN_CALLBACK_NOT_AVAILABLE#

暂无中英对照提交修改

The domain module was not usable since it could not establish the required error handling hooks, because process.setUncaughtExceptionCaptureCallback() had been called at an earlier point in time.

ERR_DOMAIN_CANNOT_SET_UNCAUGHT_EXCEPTION_CAPTURE#

暂无中英对照提交修改

process.setUncaughtExceptionCaptureCallback() could not be called because the domain module has been loaded at an earlier point in time.

The stack trace is extended to include the point in time at which the domain module had been loaded.

ERR_ENCODING_INVALID_ENCODED_DATA#

中英对照提交修改

提供给 TextDecoder() API 的数据不符合指定的编码。

ERR_ENCODING_NOT_SUPPORTED#

中英对照提交修改

提供给 TextDecoder() API 的字符编码不是 WHATWG 支持的字符编码。

ERR_EVAL_ESM_CANNOT_PRINT#

暂无中英对照提交修改

--print cannot be used with ESM input.

ERR_EVENT_RECURSION#

暂无中英对照提交修改

Thrown when an attempt is made to recursively dispatch an event on EventTarget.

ERR_EXECUTION_ENVIRONMENT_NOT_AVAILABLE#

暂无中英对照提交修改

The JS execution context is not associated with a Node.js environment. This may occur when Node.js is used as an embedded library and some hooks for the JS engine are not set up properly.

ERR_FALSY_VALUE_REJECTION#

暂无中英对照提交修改

A Promise that was callbackified via util.callbackify() was rejected with a falsy value.

ERR_FEATURE_UNAVAILABLE_ON_PLATFORM#

暂无中英对照提交修改

新增于: v14.0.0

Used when a feature that is not available to the current platform which is running Node.js is used.

ERR_FS_FILE_TOO_LARGE#

暂无中英对照提交修改

An attempt has been made to read a file whose size is larger than the maximum allowed size for a Buffer.

ERR_FS_INVALID_SYMLINK_TYPE#

暂无中英对照提交修改

An invalid symlink type was passed to the fs.symlink() or fs.symlinkSync() methods.

ERR_HTTP_REQUEST_TIMEOUT#

暂无中英对照提交修改

The client has not sent the entire request within the allowed time.

ERR_HTTP_HEADERS_SENT#

中英对照提交修改

当消息头已发送后，还试图添加消息头。

ERR_HTTP_INVALID_HEADER_VALUE#

暂无中英对照提交修改

An invalid HTTP header value was specified.

ERR_HTTP_INVALID_STATUS_CODE#

中英对照提交修改

状态码超出正常范围（100-999）。

ERR_HTTP_TRAILER_INVALID#

暂无中英对照提交修改

The Trailer header was set even though the transfer encoding does not support that.

ERR_HTTP2_ALTSVC_INVALID_ORIGIN#

暂无中英对照提交修改

HTTP/2 ALTSVC frames require a valid origin.

ERR_HTTP2_ALTSVC_LENGTH#

暂无中英对照提交修改

HTTP/2 ALTSVC frames are limited to a maximum of 16,382 payload bytes.

ERR_HTTP2_CONNECT_AUTHORITY#

暂无中英对照提交修改

For HTTP/2 requests using the CONNECT method, the :authority pseudo-header is required.

ERR_HTTP2_CONNECT_PATH#

中英对照提交修改

通过 CONNECT 方法发送的 HTTP/2 请求时， :path 伪消息头被禁用。

ERR_HTTP2_CONNECT_SCHEME#

中英对照提交修改

通过 CONNECT 方法发送 HTTP/2 请求时， :scheme 伪消息头被禁用。

ERR_HTTP2_ERROR#

暂无中英对照提交修改

A non-specific HTTP/2 error has occurred.

ERR_HTTP2_GOAWAY_SESSION#

暂无中英对照提交修改

New HTTP/2 Streams may not be opened after the Http2Session has received a GOAWAY frame from the connected peer.

ERR_HTTP2_HEADERS_AFTER_RESPOND#

暂无中英对照提交修改

An additional headers was specified after an HTTP/2 response was initiated.

ERR_HTTP2_HEADERS_SENT#

暂无中英对照提交修改

An attempt was made to send multiple response headers.

ERR_HTTP2_HEADER_SINGLE_VALUE#

中英对照提交修改

为只需一个值的 HTTP/2 消息头提供了多个值。

ERR_HTTP2_INFO_STATUS_NOT_ALLOWED#

暂无中英对照提交修改

Informational HTTP status codes (1xx) may not be set as the response status code on HTTP/2 responses.

ERR_HTTP2_INVALID_CONNECTION_HEADERS#

暂无中英对照提交修改

HTTP/1 connection specific headers are forbidden to be used in HTTP/2 requests and responses.

ERR_HTTP2_INVALID_HEADER_VALUE#

暂无中英对照提交修改

An invalid HTTP/2 header value was specified.

ERR_HTTP2_INVALID_INFO_STATUS#

暂无中英对照提交修改

An invalid HTTP informational status code has been specified. Informational status codes must be an integer between 100 and 199 (inclusive).

ERR_HTTP2_INVALID_ORIGIN#

暂无中英对照提交修改

HTTP/2 ORIGIN frames require a valid origin.

ERR_HTTP2_INVALID_PACKED_SETTINGS_LENGTH#

暂无中英对照提交修改

Input Buffer and Uint8Array instances passed to the http2.getUnpackedSettings() API must have a length that is a multiple of six.

ERR_HTTP2_INVALID_PSEUDOHEADER#

暂无中英对照提交修改

Only valid HTTP/2 pseudoheaders (:status, :path, :authority, :scheme, and :method) may be used.

ERR_HTTP2_INVALID_SESSION#

暂无中英对照提交修改

An action was performed on an Http2Session object that had already been destroyed.

ERR_HTTP2_INVALID_SETTING_VALUE#

暂无中英对照提交修改

An invalid value has been specified for an HTTP/2 setting.

ERR_HTTP2_INVALID_STREAM#

暂无中英对照提交修改

An operation was performed on a stream that had already been destroyed.

ERR_HTTP2_MAX_PENDING_SETTINGS_ACK#

暂无中英对照提交修改

Whenever an HTTP/2 SETTINGS frame is sent to a connected peer, the peer is required to send an acknowledgment that it has received and applied the new SETTINGS. By default, a maximum number of unacknowledged SETTINGS frames may be sent at any given time. This error code is used when that limit has been reached.

ERR_HTTP2_NESTED_PUSH#

暂无中英对照提交修改

An attempt was made to initiate a new push stream from within a push stream. Nested push streams are not permitted.

ERR_HTTP2_NO_SOCKET_MANIPULATION#

暂无中英对照提交修改

An attempt was made to directly manipulate (read, write, pause, resume, etc.) a socket attached to an Http2Session.

ERR_HTTP2_ORIGIN_LENGTH#

暂无中英对照提交修改

HTTP/2 ORIGIN frames are limited to a length of 16382 bytes.

ERR_HTTP2_OUT_OF_STREAMS#

暂无中英对照提交修改

The number of streams created on a single HTTP/2 session reached the maximum limit.

ERR_HTTP2_PAYLOAD_FORBIDDEN#

暂无中英对照提交修改

A message payload was specified for an HTTP response code for which a payload is forbidden.

ERR_HTTP2_PING_CANCEL#

暂无中英对照提交修改

An HTTP/2 ping was canceled.

ERR_HTTP2_PING_LENGTH#

暂无中英对照提交修改

HTTP/2 ping payloads must be exactly 8 bytes in length.

ERR_HTTP2_PSEUDOHEADER_NOT_ALLOWED#

暂无中英对照提交修改

An HTTP/2 pseudo-header has been used inappropriately. Pseudo-headers are header key names that begin with the : prefix.

ERR_HTTP2_PUSH_DISABLED#

暂无中英对照提交修改

An attempt was made to create a push stream, which had been disabled by the client.

ERR_HTTP2_SEND_FILE#

暂无中英对照提交修改

An attempt was made to use the Http2Stream.prototype.responseWithFile() API to send a directory.

ERR_HTTP2_SEND_FILE_NOSEEK#

暂无中英对照提交修改

An attempt was made to use the Http2Stream.prototype.responseWithFile() API to send something other than a regular file, but offset or length options were provided.

ERR_HTTP2_SESSION_ERROR#

暂无中英对照提交修改

The Http2Session closed with a non-zero error code.

ERR_HTTP2_SETTINGS_CANCEL#

暂无中英对照提交修改

The Http2Session settings canceled.

ERR_HTTP2_SOCKET_BOUND#

暂无中英对照提交修改

An attempt was made to connect a Http2Session object to a net.Socket or tls.TLSSocket that had already been bound to another Http2Session object.

ERR_HTTP2_SOCKET_UNBOUND#

暂无中英对照提交修改

An attempt was made to use the socket property of an Http2Session that has already been closed.

ERR_HTTP2_STATUS_101#

暂无中英对照提交修改

Use of the 101 Informational status code is forbidden in HTTP/2.

ERR_HTTP2_STATUS_INVALID#

暂无中英对照提交修改

An invalid HTTP status code has been specified. Status codes must be an integer between 100 and 599 (inclusive).

ERR_HTTP2_STREAM_CANCEL#

暂无中英对照提交修改

An Http2Stream was destroyed before any data was transmitted to the connected peer.

ERR_HTTP2_STREAM_ERROR#

暂无中英对照提交修改

A non-zero error code was been specified in an RST_STREAM frame.

ERR_HTTP2_STREAM_SELF_DEPENDENCY#

暂无中英对照提交修改

When setting the priority for an HTTP/2 stream, the stream may be marked as a dependency for a parent stream. This error code is used when an attempt is made to mark a stream and dependent of itself.

ERR_HTTP2_TRAILERS_ALREADY_SENT#

暂无中英对照提交修改

Trailing headers have already been sent on the Http2Stream.

ERR_HTTP2_TRAILERS_NOT_READY#

暂无中英对照提交修改

The http2stream.sendTrailers() method cannot be called until after the 'wantTrailers' event is emitted on an Http2Stream object. The 'wantTrailers' event will only be emitted if the waitForTrailers option is set for the Http2Stream.

ERR_HTTP2_UNSUPPORTED_PROTOCOL#

暂无中英对照提交修改

http2.connect() was passed a URL that uses any protocol other than http: or https:.

ERR_INTERNAL_ASSERTION#

暂无中英对照提交修改

There was a bug in Node.js or incorrect usage of Node.js internals. To fix the error, open an issue at https://github.com/nodejs/node/issues.

ERR_INCOMPATIBLE_OPTION_PAIR#

暂无中英对照提交修改

An option pair is incompatible with each other and cannot be used at the same time.

ERR_INPUT_TYPE_NOT_ALLOWED#

暂无中英对照

稳定性: 1 - 实验

The --input-type flag was used to attempt to execute a file. This flag can only be used with input via --eval, --print or STDIN.

ERR_INSPECTOR_ALREADY_ACTIVATED#

暂无中英对照提交修改

While using the inspector module, an attempt was made to activate the inspector when it already started to listen on a port. Use inspector.close() before activating it on a different address.

ERR_INSPECTOR_ALREADY_CONNECTED#

暂无中英对照提交修改

While using the inspector module, an attempt was made to connect when the inspector was already connected.

ERR_INSPECTOR_CLOSED#

暂无中英对照提交修改

While using the inspector module, an attempt was made to use the inspector after the session had already closed.

ERR_INSPECTOR_COMMAND#

暂无中英对照提交修改

An error occurred while issuing a command via the inspector module.

ERR_INSPECTOR_NOT_ACTIVE#

暂无中英对照提交修改

The inspector is not active when inspector.waitForDebugger() is called.

ERR_INSPECTOR_NOT_AVAILABLE#

暂无中英对照提交修改

The inspector module is not available for use.

ERR_INSPECTOR_NOT_CONNECTED#

暂无中英对照提交修改

While using the inspector module, an attempt was made to use the inspector before it was connected.

ERR_INSPECTOR_NOT_WORKER#

暂无中英对照提交修改

An API was called on the main thread that can only be used from the worker thread.

ERR_INVALID_ADDRESS_FAMILY#

暂无中英对照提交修改

The provided address family is not understood by the Node.js API.

ERR_INVALID_ARG_TYPE#

暂无中英对照提交修改

An argument of the wrong type was passed to a Node.js API.

ERR_INVALID_ARG_VALUE#

暂无中英对照提交修改

An invalid or unsupported value was passed for a given argument.

ERR_INVALID_ASYNC_ID#

暂无中英对照提交修改

An invalid asyncId or triggerAsyncId was passed using AsyncHooks. An id less than -1 should never happen.

ERR_INVALID_BUFFER_SIZE#

暂无中英对照提交修改

A swap was performed on a Buffer but its size was not compatible with the operation.

ERR_INVALID_CALLBACK#

暂无中英对照提交修改

A callback function was required but was not been provided to a Node.js API.

ERR_INVALID_CHAR#

暂无中英对照提交修改

Invalid characters were detected in headers.

ERR_INVALID_CURSOR_POS#

暂无中英对照提交修改

A cursor on a given stream cannot be moved to a specified row without a specified column.

ERR_INVALID_FD#

暂无中英对照提交修改

A file descriptor ('fd') was not valid (e.g. it was a negative value).

ERR_INVALID_FD_TYPE#

暂无中英对照提交修改

A file descriptor ('fd') type was not valid.

ERR_INVALID_FILE_URL_HOST#

暂无中英对照提交修改

A Node.js API that consumes file: URLs (such as certain functions in the fs module) encountered a file URL with an incompatible host. This situation can only occur on Unix-like systems where only localhost or an empty host is supported.

ERR_INVALID_FILE_URL_PATH#

暂无中英对照提交修改

A Node.js API that consumes file: URLs (such as certain functions in the fs module) encountered a file URL with an incompatible path. The exact semantics for determining whether a path can be used is platform-dependent.

ERR_INVALID_HANDLE_TYPE#

暂无中英对照提交修改

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.

ERR_INVALID_HTTP_TOKEN#

暂无中英对照提交修改

An invalid HTTP token was supplied.

ERR_INVALID_IP_ADDRESS#

暂无中英对照提交修改

An IP address is not valid.

ERR_INVALID_MODULE_SPECIFIER#

暂无中英对照提交修改

The imported module string is an invalid URL, package name, or package subpath specifier.

ERR_INVALID_OPT_VALUE#

暂无中英对照提交修改

An invalid or unexpected value was passed in an options object.

ERR_INVALID_OPT_VALUE_ENCODING#

暂无中英对照提交修改

An invalid or unknown file encoding was passed.

ERR_INVALID_PACKAGE_CONFIG#

暂无中英对照提交修改

An invalid package.json file was found which failed parsing.

ERR_INVALID_PACKAGE_TARGET#

暂无中英对照提交修改

The package.json exports field contains an invalid target mapping value for the attempted module resolution.

ERR_INVALID_PERFORMANCE_MARK#

暂无中英对照提交修改

While using the Performance Timing API (perf_hooks), a performance mark is invalid.

ERR_INVALID_PROTOCOL#

暂无中英对照提交修改

An invalid options.protocol was passed to http.request().

ERR_INVALID_REPL_EVAL_CONFIG#

暂无中英对照提交修改

Both breakEvalOnSigint and eval options were set in the REPL config, which is not supported.

ERR_INVALID_REPL_INPUT#

暂无中英对照提交修改

The input may not be used in the REPL. All prohibited inputs are documented in the REPL's documentation.

ERR_INVALID_RETURN_PROPERTY#

暂无中英对照提交修改

Thrown in case a function option does not provide a valid value for one of its returned object properties on execution.

ERR_INVALID_RETURN_PROPERTY_VALUE#

暂无中英对照提交修改

Thrown in case a function option does not provide an expected value type for one of its returned object properties on execution.

ERR_INVALID_RETURN_VALUE#

暂无中英对照提交修改

Thrown in case a function option does not return an expected value type on execution, such as when a function is expected to return a promise.

ERR_INVALID_SYNC_FORK_INPUT#

暂无中英对照提交修改

A Buffer, TypedArray, DataView or string was provided as stdio input to an asynchronous fork. See the documentation for the child_process module for more information.

ERR_INVALID_THIS#

暂无中英对照提交修改

A Node.js API function was called with an incompatible this value.

const urlSearchParams = new URLSearchParams('foo=bar&baz=new');

const buf = Buffer.alloc(1);
urlSearchParams.has.call(buf, 'foo');
// Throws a TypeError with code 'ERR_INVALID_THIS'

ERR_INVALID_TRANSFER_OBJECT#

暂无中英对照提交修改

An invalid transfer object was passed to postMessage().

ERR_INVALID_TUPLE#

暂无中英对照提交修改

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_INVALID_URI#

暂无中英对照提交修改

An invalid URI was passed.

ERR_INVALID_URL#

暂无中英对照提交修改

An invalid URL was passed to the WHATWG URL constructor to be parsed. The thrown error object typically has an additional property 'input' that contains the URL that failed to parse.

ERR_INVALID_URL_SCHEME#

暂无中英对照提交修改

An attempt was made to use a URL of an incompatible scheme (protocol) for a specific purpose. It is only used in the WHATWG URL API support in the fs module (which only accepts URLs with 'file' scheme), but may be used in other Node.js APIs as well in the future.

ERR_IPC_CHANNEL_CLOSED#

暂无中英对照提交修改

An attempt was made to use an IPC communication channel that was already closed.

ERR_IPC_DISCONNECTED#

暂无中英对照提交修改

An attempt was made to disconnect an IPC communication channel that was already disconnected. See the documentation for the child_process module for more information.

ERR_IPC_ONE_PIPE#

暂无中英对照提交修改

An attempt was made to create a child Node.js process using more than one IPC communication channel. See the documentation for the child_process module for more information.

ERR_IPC_SYNC_FORK#

暂无中英对照提交修改

An attempt was made to open an IPC communication channel with a synchronously forked Node.js process. See the documentation for the child_process module for more information.

ERR_MANIFEST_ASSERT_INTEGRITY#

暂无中英对照提交修改

An attempt was made to load a resource, but the resource did not match the integrity defined by the policy manifest. See the documentation for policy manifests for more information.

ERR_MANIFEST_DEPENDENCY_MISSING#

暂无中英对照提交修改

An attempt was made to load a resource, but the resource was not listed as a dependency from the location that attempted to load it. See the documentation for policy manifests for more information.

ERR_MANIFEST_INTEGRITY_MISMATCH#

暂无中英对照提交修改

An attempt was made to load a policy manifest, but the manifest had multiple entries for a resource which did not match each other. Update the manifest entries to match in order to resolve this error. See the documentation for policy manifests for more information.

ERR_MANIFEST_INVALID_RESOURCE_FIELD#

暂无中英对照提交修改

A policy manifest resource had an invalid value for one of its fields. Update the manifest entry to match in order to resolve this error. See the documentation for policy manifests for more information.

ERR_MANIFEST_PARSE_POLICY#

暂无中英对照提交修改

An attempt was made to load a policy manifest, but the manifest was unable to be parsed. See the documentation for policy manifests for more information.

ERR_MANIFEST_TDZ#

暂无中英对照提交修改

An attempt was made to read from a policy manifest, but the manifest initialization has not yet taken place. This is likely a bug in Node.js.

ERR_MANIFEST_UNKNOWN_ONERROR#

暂无中英对照提交修改

A policy manifest was loaded, but had an unknown value for its "onerror" behavior. See the documentation for policy manifests for more information.

ERR_MEMORY_ALLOCATION_FAILED#

暂无中英对照提交修改

An attempt was made to allocate memory (usually in the C++ layer) but it failed.

ERR_MESSAGE_TARGET_CONTEXT_UNAVAILABLE#

暂无中英对照提交修改

新增于: v14.5.0

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 postMessage() can fail on the receiving side in that case.

ERR_METHOD_NOT_IMPLEMENTED#

暂无中英对照提交修改

A method is required but not implemented.

ERR_MISSING_ARGS#

暂无中英对照提交修改

A required argument of a Node.js API was not passed. This is only used for strict compliance with the API specification (which in some cases may accept func(undefined) but not func()). In most native Node.js APIs, func(undefined) and func() are treated identically, and the ERR_INVALID_ARG_TYPE error code may be used instead.

ERR_MISSING_OPTION#

暂无中英对照提交修改

For APIs that accept options objects, some options might be mandatory. This code is thrown if a required option is missing.

ERR_MISSING_MESSAGE_PORT_IN_TRANSFER_LIST#

暂无中英对照提交修改

An object that needs to be explicitly listed in the transferList argument was found in the object passed to a postMessage() call, but not provided in the transferList for that call. Usually, this is a MessagePort.

ERR_MISSING_PASSPHRASE#

暂无中英对照提交修改

An attempt was made to read an encrypted key without specifying a passphrase.

ERR_MISSING_PLATFORM_FOR_WORKER#

暂无中英对照提交修改

The V8 platform used by this instance of Node.js does not support creating Workers. This is caused by lack of embedder support for Workers. In particular, this error will not occur with standard builds of Node.js.

ERR_MODULE_NOT_FOUND#

暂无中英对照

稳定性: 1 - 实验

An ES Module could not be resolved.

ERR_MULTIPLE_CALLBACK#

暂无中英对照提交修改

A callback was called more than once.

A callback is almost always meant to only be called once as the query can either be fulfilled or rejected but not both at the same time. The latter would be possible by calling a callback more than once.

ERR_NAPI_CONS_FUNCTION#

暂无中英对照提交修改

While using N-API, a constructor passed was not a function.

ERR_NAPI_INVALID_DATAVIEW_ARGS#

暂无中英对照提交修改

While calling napi_create_dataview(), a given offset was outside the bounds of the dataview or offset + length was larger than a length of given buffer.

ERR_NAPI_INVALID_TYPEDARRAY_ALIGNMENT#

暂无中英对照提交修改

While calling napi_create_typedarray(), the provided offset was not a multiple of the element size.

ERR_NAPI_INVALID_TYPEDARRAY_LENGTH#

暂无中英对照提交修改

While calling napi_create_typedarray(), (length * size_of_element) + byte_offset was larger than the length of given buffer.

ERR_NAPI_TSFN_CALL_JS#

暂无中英对照提交修改

An error occurred while invoking the JavaScript portion of the thread-safe function.

ERR_NAPI_TSFN_GET_UNDEFINED#

暂无中英对照提交修改

An error occurred while attempting to retrieve the JavaScript undefined value.

ERR_NAPI_TSFN_START_IDLE_LOOP#

暂无中英对照提交修改

On the main thread, values are removed from the queue associated with the thread-safe function in an idle loop. This error indicates that an error has occurred when attempting to start the loop.

ERR_NAPI_TSFN_STOP_IDLE_LOOP#

暂无中英对照提交修改

Once no more items are left in the queue, the idle loop must be suspended. This error indicates that the idle loop has failed to stop.

ERR_NO_CRYPTO#

暂无中英对照提交修改

An attempt was made to use crypto features while Node.js was not compiled with OpenSSL crypto support.

ERR_NO_ICU#

暂无中英对照提交修改

An attempt was made to use features that require ICU, but Node.js was not compiled with ICU support.

ERR_NON_CONTEXT_AWARE_DISABLED#

暂无中英对照提交修改

A non-context-aware native addon was loaded in a process that disallows them.

ERR_OUT_OF_RANGE#

暂无中英对照提交修改

A given value is out of the accepted range.

ERR_PACKAGE_IMPORT_NOT_DEFINED#

暂无中英对照提交修改

The package.json "imports" field does not define the given internal package specifier mapping.

ERR_PACKAGE_PATH_NOT_EXPORTED#

暂无中英对照提交修改

The package.json exports field does not export the requested subpath. Because exports are encapsulated, private internal modules that are not exported cannot be imported through the package resolution, unless using an absolute URL.

ERR_PROTO_ACCESS#

暂无中英对照提交修改

Accessing Object.prototype.__proto__ has been forbidden using --disable-proto=throw. Object.getPrototypeOf and Object.setPrototypeOf should be used to get and set the prototype of an object.

ERR_REQUIRE_ESM#

暂无中英对照

稳定性: 1 - 实验

An attempt was made to require() an ES Module.

ERR_SCRIPT_EXECUTION_INTERRUPTED#

暂无中英对照提交修改

Script execution was interrupted by SIGINT (For example, when Ctrl+C was pressed).

ERR_SCRIPT_EXECUTION_TIMEOUT#

暂无中英对照提交修改

Script execution timed out, possibly due to bugs in the script being executed.

ERR_SERVER_ALREADY_LISTEN#

暂无中英对照提交修改

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.

ERR_SERVER_NOT_RUNNING#

暂无中英对照提交修改

The server.close() method was called when a net.Server was not running. This applies to all instances of net.Server, including HTTP, HTTPS, and HTTP/2 Server instances.

ERR_SOCKET_ALREADY_BOUND#

暂无中英对照提交修改

An attempt was made to bind a socket that has already been bound.

ERR_SOCKET_BAD_BUFFER_SIZE#

暂无中英对照提交修改

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

ERR_SOCKET_BAD_PORT#

暂无中英对照提交修改

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

ERR_SOCKET_BAD_TYPE#

暂无中英对照提交修改

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

ERR_SOCKET_BUFFER_SIZE#

暂无中英对照提交修改

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

ERR_SOCKET_CLOSED#

暂无中英对照提交修改

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

ERR_SOCKET_DGRAM_IS_CONNECTED#

暂无中英对照提交修改

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

ERR_SOCKET_DGRAM_NOT_CONNECTED#

暂无中英对照提交修改

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

ERR_SOCKET_DGRAM_NOT_RUNNING#

暂无中英对照提交修改

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

ERR_SRI_PARSE#

暂无中英对照提交修改

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.

ERR_STREAM_CANNOT_PIPE#

暂无中英对照提交修改

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

ERR_STREAM_DESTROYED#

暂无中英对照提交修改

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

ERR_STREAM_ALREADY_FINISHED#

暂无中英对照提交修改

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

ERR_STREAM_NULL_VALUES#

暂无中英对照提交修改

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

ERR_STREAM_PREMATURE_CLOSE#

暂无中英对照提交修改

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

ERR_STREAM_PUSH_AFTER_EOF#

暂无中英对照提交修改

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

ERR_STREAM_UNSHIFT_AFTER_END_EVENT#

暂无中英对照提交修改

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

ERR_STREAM_WRAP#

暂无中英对照提交修改

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

const Socket = require('net').Socket;
const instance = new Socket();

instance.setEncoding('utf8');

ERR_STREAM_WRITE_AFTER_END#

暂无中英对照提交修改

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

ERR_STRING_TOO_LONG#

暂无中英对照提交修改

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

ERR_SYNTHETIC#

暂无中英对照提交修改

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

ERR_SYSTEM_ERROR#

暂无中英对照提交修改

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.

ERR_TLS_CERT_ALTNAME_INVALID#

暂无中英对照提交修改

While using TLS, the host name/IP of the peer did not match any of the subjectAltNames in its certificate.

ERR_TLS_DH_PARAM_SIZE#

暂无中英对照提交修改

While using TLS, the parameter offered for the Diffie-Hellman (DH) key-agreement protocol is too small. By default, the key length must be greater than or equal to 1024 bits to avoid vulnerabilities, even though it is strongly recommended to use 2048 bits or larger for stronger security.

ERR_TLS_HANDSHAKE_TIMEOUT#

暂无中英对照提交修改

A TLS/SSL handshake timed out. In this case, the server must also abort the connection.

ERR_TLS_INVALID_CONTEXT#

暂无中英对照提交修改

新增于: v13.3.0

The context must be a SecureContext.

ERR_TLS_INVALID_STATE#

暂无中英对照提交修改

新增于: v13.10.0

The TLS socket must be connected and securily established. Ensure the 'secure' event is emitted before continuing.

ERR_TLS_INVALID_PROTOCOL_METHOD#

暂无中英对照提交修改

The specified secureProtocol method is invalid. It is either unknown, or disabled because it is insecure.

ERR_TLS_INVALID_PROTOCOL_VERSION#

暂无中英对照提交修改

Valid TLS protocol versions are 'TLSv1', 'TLSv1.1', or 'TLSv1.2'.

ERR_TLS_PROTOCOL_VERSION_CONFLICT#

暂无中英对照提交修改

Attempting to set a TLS protocol minVersion or maxVersion conflicts with an attempt to set the secureProtocol explicitly. Use one mechanism or the other.

ERR_TLS_RENEGOTIATION_DISABLED#

暂无中英对照提交修改

An attempt was made to renegotiate TLS on a socket instance with TLS disabled.

ERR_TLS_REQUIRED_SERVER_NAME#

暂无中英对照提交修改

While using TLS, the server.addContext() method was called without providing a host name in the first parameter.

ERR_TLS_SESSION_ATTACK#

暂无中英对照提交修改

An excessive amount of TLS renegotiations is detected, which is a potential vector for denial-of-service attacks.

ERR_TLS_SNI_FROM_SERVER#

暂无中英对照提交修改

An attempt was made to issue Server Name Indication from a TLS server-side socket, which is only valid from a client.

ERR_TLS_PSK_SET_IDENTIY_HINT_FAILED#

暂无中英对照提交修改

Failed to set PSK identity hint. Hint may be too long.

ERR_TRACE_EVENTS_CATEGORY_REQUIRED#

暂无中英对照提交修改

The trace_events.createTracing() method requires at least one trace event category.

ERR_TRACE_EVENTS_UNAVAILABLE#

暂无中英对照提交修改

The trace_events module could not be loaded because Node.js was compiled with the --without-v8-platform flag.

ERR_TRANSFORM_ALREADY_TRANSFORMING#

暂无中英对照提交修改

A Transform stream finished while it was still transforming.

ERR_TRANSFORM_WITH_LENGTH_0#

暂无中英对照提交修改

A Transform stream finished with data still in the write buffer.

ERR_TTY_INIT_FAILED#

暂无中英对照提交修改

The initialization of a TTY failed due to a system error.

ERR_UNAVAILABLE_DURING_EXIT#

暂无中英对照提交修改

Function was called within a process.on('exit') handler that shouldn't be called within process.on('exit') handler.

ERR_UNCAUGHT_EXCEPTION_CAPTURE_ALREADY_SET#

暂无中英对照提交修改

process.setUncaughtExceptionCaptureCallback() was called twice, without first resetting the callback to null.

This error is designed to prevent accidentally overwriting a callback registered from another module.

ERR_UNESCAPED_CHARACTERS#

暂无中英对照提交修改

A string that contained unescaped characters was received.

ERR_UNHANDLED_ERROR#

暂无中英对照提交修改

An unhandled error occurred (for instance, when an 'error' event is emitted by an EventEmitter but an 'error' handler is not registered).

ERR_UNKNOWN_BUILTIN_MODULE#

暂无中英对照提交修改

Used to identify a specific kind of internal Node.js error that should not typically be triggered by user code. Instances of this error point to an internal bug within the Node.js binary itself.

ERR_UNKNOWN_CREDENTIAL#

暂无中英对照提交修改

A Unix group or user identifier that does not exist was passed.

ERR_UNKNOWN_ENCODING#

暂无中英对照提交修改

An invalid or unknown encoding option was passed to an API.

ERR_UNKNOWN_FILE_EXTENSION#

暂无中英对照

稳定性: 1 - 实验

An attempt was made to load a module with an unknown or unsupported file extension.

ERR_UNKNOWN_MODULE_FORMAT#

暂无中英对照

稳定性: 1 - 实验

An attempt was made to load a module with an unknown or unsupported format.

ERR_UNKNOWN_SIGNAL#

暂无中英对照提交修改

An invalid or unknown process signal was passed to an API expecting a valid signal (such as subprocess.kill()).

ERR_UNSUPPORTED_DIR_IMPORT#

暂无中英对照提交修改

import a directory URL is unsupported. Instead, self-reference a package using its name and define a custom subpath in the "exports" field of the package.json file.

import './'; // unsupported
import './index.js'; // supported
import 'package-name'; // supported

ERR_UNSUPPORTED_ESM_URL_SCHEME#

暂无中英对照提交修改

import with URL schemes other than file and data is unsupported.

ERR_VALID_PERFORMANCE_ENTRY_TYPE#

暂无中英对照提交修改

While using the Performance Timing API (perf_hooks), no valid performance entry types were found.

ERR_VM_DYNAMIC_IMPORT_CALLBACK_MISSING#

暂无中英对照提交修改

A dynamic import callback was not specified.

ERR_VM_MODULE_ALREADY_LINKED#

暂无中英对照提交修改

The module attempted to be linked is not eligible for linking, because of one of the following reasons:

  • It has already been linked (linkingStatus is 'linked')
  • It is being linked (linkingStatus is 'linking')
  • Linking has failed for this module (linkingStatus is 'errored')

ERR_VM_MODULE_CACHED_DATA_REJECTED#

暂无中英对照提交修改

The cachedData option passed to a module constructor is invalid.

ERR_VM_MODULE_CANNOT_CREATE_CACHED_DATA#

暂无中英对照提交修改

Cached data cannot be created for modules which have already been evaluated.

ERR_VM_MODULE_DIFFERENT_CONTEXT#

暂无中英对照提交修改

The module being returned from the linker function is from a different context than the parent module. Linked modules must share the same context.

ERR_VM_MODULE_LINKING_ERRORED#

暂无中英对照提交修改

The linker function returned a module for which linking has failed.

ERR_VM_MODULE_NOT_MODULE#

暂无中英对照提交修改

The fulfilled value of a linking promise is not a vm.Module object.

ERR_VM_MODULE_STATUS#

暂无中英对照提交修改

The current module's status does not allow for this operation. The specific meaning of the error depends on the specific function.

ERR_WASI_ALREADY_STARTED#

暂无中英对照提交修改

The WASI instance has already started.

ERR_WASI_NOT_STARTED#

暂无中英对照提交修改

The WASI instance has not been started.

ERR_WORKER_INIT_FAILED#

暂无中英对照提交修改

The Worker initialization failed.

ERR_WORKER_INVALID_EXEC_ARGV#

暂无中英对照提交修改

The execArgv option passed to the Worker constructor contains invalid flags.

ERR_WORKER_NOT_RUNNING#

暂无中英对照提交修改

An operation failed because the Worker instance is not currently running.

ERR_WORKER_OUT_OF_MEMORY#

暂无中英对照提交修改

The Worker instance terminated because it reached its memory limit.

ERR_WORKER_PATH#

暂无中英对照提交修改

The path for the main script of a worker is neither an absolute path nor a relative path starting with ./ or ../.

ERR_WORKER_UNSERIALIZABLE_ERROR#

暂无中英对照提交修改

All attempts at serializing an uncaught exception from a worker thread failed.

ERR_WORKER_UNSUPPORTED_EXTENSION#

暂无中英对照提交修改

The pathname used for the main script of a worker has an unknown file extension.

ERR_WORKER_UNSUPPORTED_OPERATION#

暂无中英对照提交修改

The requested functionality is not supported in worker threads.

ERR_ZLIB_INITIALIZATION_FAILED#

暂无中英对照提交修改

Creation of a zlib object failed due to incorrect configuration.

HPE_HEADER_OVERFLOW#

暂无中英对照提交修改

版本历史
版本变更
v11.4.0, v10.15.0

Max header size in http_parser was set to 8KB.

Too much HTTP header data was received. In order to protect against malicious or malconfigured clients, if more than 8KB of HTTP header data is received then HTTP parsing will abort without a request or response object being created, and an Error with this code will be emitted.

HPE_UNEXPECTED_CONTENT_LENGTH#

暂无中英对照提交修改

Server is sending both a Content-Length header and Transfer-Encoding: chunked.

Transfer-Encoding: chunked allows the server to maintain an HTTP persistent connection for dynamically generated content. In this case, the Content-Length HTTP header cannot be used.

Use Content-Length or Transfer-Encoding: chunked.

MODULE_NOT_FOUND#

暂无中英对照提交修改

版本历史
版本变更
v12.0.0

Added requireStack property.

A module file could not be resolved while attempting a require() or import operation.

弃用的 Node.js 错误码#

暂无中英对照

稳定性: 0 - 弃用. These error codes are either inconsistent, 或 have been removed.

ERR_CANNOT_TRANSFER_OBJECT#

暂无中英对照提交修改

The value passed to postMessage() contained an object that is not supported for transferring.

ERR_CLOSED_MESSAGE_PORT#

暂无中英对照提交修改

新增于: v10.5.0移除于: v11.12.0

There was an attempt to use a MessagePort instance in a closed state, usually after .close() has been called.

ERR_CRYPTO_HASH_DIGEST_NO_UTF16#

暂无中英对照提交修改

新增于: v9.0.0移除于: v12.12.0

The UTF-16 encoding was used with hash.digest(). While the hash.digest() method does allow an encoding argument to be passed in, causing the method to return a string rather than a Buffer, the UTF-16 encoding (e.g. ucs or utf16le) is not supported.

ERR_HTTP2_FRAME_ERROR#

中英对照提交修改

新增于: v9.0.0移除于: v10.0.0

通过 HTTP/2 会话发送单个数据帧失败。

ERR_HTTP2_HEADERS_OBJECT#

暂无中英对照提交修改

新增于: v9.0.0移除于: v10.0.0

Used when an HTTP/2 Headers Object is expected.

ERR_HTTP2_HEADER_REQUIRED#

中英对照提交修改

新增于: v9.0.0移除于: v10.0.0

HTTP/2 消息缺少必需的消息头。

ERR_HTTP2_INFO_HEADERS_AFTER_RESPOND#

暂无中英对照提交修改

新增于: v9.0.0移除于: v10.0.0

HTTP/2 informational headers must only be sent prior to calling the Http2Stream.prototype.respond() method.

ERR_HTTP2_STREAM_CLOSED#

暂无中英对照提交修改

新增于: v9.0.0移除于: v10.0.0

Used when an action has been performed on an HTTP/2 Stream that has already been closed.

ERR_HTTP_INVALID_CHAR#

中英对照提交修改

新增于: v9.0.0移除于: v10.0.0

HTTP 响应的状态信息中存在非法字符（原因短语）。

ERR_INDEX_OUT_OF_RANGE#

暂无中英对照提交修改

新增于: v10.0.0移除于: v11.0.0

A given index was out of the accepted range (e.g. negative offsets).

ERR_NAPI_CONS_PROTOTYPE_OBJECT#

暂无中英对照提交修改

新增于: v9.0.0移除于: v10.0.0

Used by the N-API when Constructor.prototype is not an object.

ERR_NO_LONGER_SUPPORTED#

暂无中英对照提交修改

A Node.js API was called in an unsupported manner, such as Buffer.write(string, encoding, offset[, length]).

ERR_OUTOFMEMORY#

暂无中英对照提交修改

新增于: v9.0.0移除于: v10.0.0

Used generically to identify that an operation caused an out of memory condition.

ERR_PARSE_HISTORY_DATA#

暂无中英对照提交修改

新增于: v9.0.0移除于: v10.0.0

The repl module was unable to parse data from the REPL history file.

ERR_SOCKET_CANNOT_SEND#

暂无中英对照提交修改

新增于: v9.0.0移除于: v14.0.0

Data could not be sent on a socket.

ERR_STDERR_CLOSE#

暂无中英对照提交修改

版本历史
版本变更
v10.12.0

Rather than emitting an error, process.stderr.end() now only closes the stream side but not the underlying resource, making this error obsolete.

v10.12.0

移除于: v10.12.0

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.

ERR_STDOUT_CLOSE#

暂无中英对照提交修改

版本历史
版本变更
v10.12.0

Rather than emitting an error, process.stderr.end() now only closes the stream side but not the underlying resource, making this error obsolete.

v10.12.0

移除于: v10.12.0

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.

ERR_STREAM_READ_NOT_IMPLEMENTED#

暂无中英对照提交修改

新增于: v9.0.0移除于: v10.0.0

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

ERR_TLS_RENEGOTIATION_FAILED#

暂无中英对照提交修改

新增于: v9.0.0移除于: v10.0.0

Used when a TLS renegotiation request has failed in a non-specific way.

ERR_TRANSFERRING_EXTERNALIZED_SHAREDARRAYBUFFER#

暂无中英对照提交修改

新增于: v10.5.0移除于: v14.0.0

A SharedArrayBuffer whose memory is not managed by the JavaScript engine or by Node.js was encountered during serialization. Such a SharedArrayBuffer cannot be serialized.

This can only happen when native addons create SharedArrayBuffers in "externalized" mode, or put existing SharedArrayBuffer into externalized mode.

ERR_UNKNOWN_STDIN_TYPE#

暂无中英对照提交修改

新增于: v8.0.0移除于: v11.7.0

An attempt was made to launch a Node.js process with an unknown stdin file type. This error is usually an indication of a bug within Node.js itself, although it is possible for user code to trigger it.

ERR_UNKNOWN_STREAM_TYPE#

暂无中英对照提交修改

新增于: v8.0.0移除于: v11.7.0

An attempt was made to launch a Node.js process with an unknown stdout or stderr file type. This error is usually an indication of a bug within Node.js itself, although it is possible for user code to trigger it.

ERR_V8BREAKITERATOR#

暂无中英对照提交修改

The V8 BreakIterator API was used but the full ICU data set is not installed.

ERR_VALUE_OUT_OF_RANGE#

暂无中英对照提交修改

新增于: v9.0.0移除于: v10.0.0

Used when a given value is out of the accepted range.

ERR_VM_MODULE_NOT_LINKED#

暂无中英对照提交修改

The module must be successfully linked before instantiation.

ERR_ZLIB_BINDING_CLOSED#

暂无中英对照提交修改

新增于: v9.0.0移除于: v10.0.0

Used when an attempt is made to use a zlib object after it has already been closed.