Node.js v10.3.0 文档


目录

Error (错误)#

查看英文版参与翻译

Node.js 中运行的应用程序一般会遇到以下四类错误:

  • 标准的 JavaScript 错误:
  • 由底层操作系触发的系统错误,例如试图打开一个不存在的文件、试图通过一个已关闭的 socket 发送数据等。
  • 由应用程序代码触发的用户自定义的错误。
  • 断言错误是错误的一个特殊类别,每当 Node.js 检测到一个不应该发生的异常逻辑时触发。 这类错误通常由 assert 模块引起。

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

错误的冒泡和捕获#

查看英文版参与翻译

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

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

// 抛出一个 ReferenceError,因为 z 为 undefined
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 模块或已经注册了一个 process.on('uncaughtException') 事件的句柄。

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

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

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

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

Error-first callbacks#

查看英文版参与翻译

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

const fs = require('fs');

function errorFirstCallback(err, data) {
  if (err) {
    console.error('There was an 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) => {
    // mistaken assumption: throwing here...
    if (err) {
      throw err;
    }
  });
} catch (err) {
  // 这里不会截获回调函数中的throw
  console.error(err);
}

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

Error 类#

查看英文版参与翻译

一个通用的 JavaScript Error 对象,它不表示错误发生的具体情况。 Error 对象会捕捉一个“堆栈跟踪”,详细说明被实例化的 Error 对象在代码中的位置,并可能提供错误的文字描述。

只对于加密,如果在抛出错误时可以使用 Error 对象,则会将OpenSSL错误堆栈放入到名为 opensslErrorStack 的单独属性中。

所有由 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().stackError.captureStackTrace(obj) 产生的)。

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

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

error.code#

查看英文版参与翻译

error.code 属性是标识错误类别的字符标签。详见 Node.js Error Codes 关于特定的错误码

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 或当前事件循环中可用的帧数量的最小值界定的。

系统级的错误是由扩展的 Error 实例产生的,详见系统错误

Class: AssertionError#

查看英文版参与翻译

Error 的子类,表示断言失败。 这种错误通常表示实际值和预期值不相等。

比如:

assert.strictEqual(1, 2);
// AssertionError [ERR_ASSERTION]: 1 === 2

RangeError 类#

查看英文版参与翻译

Error 的一个子类,表明一个函数的一个给定的参数的值不在可接受的集合或范围内; 无论是一个数字范围还是给定函数参数的选项的集合。

例子:

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

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

ReferenceError 类#

查看英文版参与翻译

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

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

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

除非应用程序是动态生成并运行的代码,否则 ReferenceError 实例应该始终被视为代码中或其依赖中的错误。

SyntaxError 类#

查看英文版参与翻译

Error 的一个子类,表明程序不是有效的 JavaScript 代码。 这些错误是代码执行的结果产生和传播的。 代码执行可能产生自 evalFunctionrequirevm。 这些错误几乎都表明程序已损坏。

try {
  require('vm').runInThisContext('binary ! isNotOk');
} catch (err) {
  // err 是一个 SyntaxError
}

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

TypeError 类#

查看英文版参与翻译

Error 的一个子类,表明提供的参数不是一个被允许的类型。 例如,将一个函数传给一个期望字符串的参数会被视为一个 TypeError

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

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

异常与错误#

查看英文版参与翻译

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

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

系统错误#

查看英文版参与翻译

系统错误是当程序运行环境中发生异常时产生的。 特别是,当应用程序违反了操作系统的限制时发生的操作错误,例如试图读取一个不存在的文件或用户没有足够的权限。

系统错误通常产生于系统调用层级。 在大多数 Unix 系统上,可通过运行 man 2 introman 3 errno、或在线文档获取错误代码的详细清单和含义。

系统错误是由扩展的 Error 对象加上附加属性表现的。

Class: SystemError#

error.info#

查看英文版参与翻译

SystemError 实例可能附有一个 info 属性,其值是一个对象,记录了关于错误情况的更多细节。

SystemError 实例提供以下属性:

  • code <string> 错误代码字符串
  • errno <number> 系统提供的错误代号
  • message <string> 系统提供的常人能理解的错误描述
  • syscall <string> 触发了错误的系统调用的名称
  • path <Buffer> 当汇报文件系统的错误时,path 包含与之有关的文件的路径
  • dest <Buffer> 当汇报文件系统的错误时,dest 包含与之有关的文件目的地的路径(如果存在)

error.code#

查看英文版参与翻译

error.code 属性是一个表示错误码的字符串,总是 E 带上一串大写字母。

error.errno#

查看英文版参与翻译

error.errno 属性是一个数值或字符串。 如果返回一个数值,则数值是一个负数,对应 libuv 错误处理 中定义的错误码。 详见 uv-errno.h 头文件(Node.js 源代码中的 deps/uv/include/uv-errno.h)。 如果返回一个字符串,则同 error.code

error.syscall#

查看英文版参与翻译

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

error.path#

查看英文版参与翻译

错误出现时 (比如 在 fschild_process), error.path属性是一个字符串,包含了相关不可用路径名。

error.address#

查看英文版参与翻译

错误出现时 (比如 在 netdgram), error.address 属性是对链接失败的地址的描述。

error.port#

查看英文版参与翻译

错误出现时 (比如 在 netdgram), error.port是一个链接端口不可用的端口值

常见的系统错误#

查看英文版参与翻译

以下列表是不完整的,但列举了编写 Node.js 程序时会遇到的一些常见的系统错误。 详细的列表可从 ERRNO 文档找到。

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

  • EADDRINUSE (地址已被使用): 试图绑定一个服务器(nethttphttps)到本地地址,但因另一个本地系统的服务器已占用了该地址而导致失败。

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

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

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

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

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

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

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

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

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

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

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

Node.js Error Codes#

查看英文版参与翻译

ERR_AMBIGUOUS_ARGUMENT##

查看英文版参与翻译

This is triggered by the assert module in case e.g., assert.throws(fn, message) is used in a way that the message is the thrown error message. This is ambiguous because the message is not verifying the error message and will only be thrown in case no error is thrown.

ERR_ARG_NOT_ITERABLE##

查看英文版参与翻译

需要可遍历的参数(也就是可使用 for...of 遍历的值)。

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_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_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_DIGEST_NO_UTF16##

查看英文版参与翻译

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_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_INVALID_DIGEST##

查看英文版参与翻译

An invalid crypto digest algorithm was specified.

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

查看英文版参与翻译

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

ERR_ENCODING_NOT_SUPPORTED##

查看英文版参与翻译

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

ERR_FALSY_VALUE_REJECTION##

查看英文版参与翻译

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

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_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 伪header 被禁用

ERR_HTTP2_CONNECT_SCHEME##

查看英文版参与翻译

通过CONNECT方法发送HTTP/2请求时,:scheme伪header 被禁用。

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

查看英文版参与翻译

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

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_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_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 acknowledgement 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_NO_SOCKET_MANIPULATION##

查看英文版参与翻译

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

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 cancelled.

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 something other than a regular file.

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_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_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_INDEX_OUT_OF_RANGE##

查看英文版参与翻译

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

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_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_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_ARRAY_LENGTH##

查看英文版参与翻译

An array was not of the expected length or in a valid range.

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

查看英文版参与翻译

hostname can not be parsed from a provided URL.

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_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_PERFORMANCE_MARK##

查看英文版参与翻译

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

ERR_INVALID_PROTOCOL##

查看英文版参与翻译

An invalid options.protocol was passed.

ERR_INVALID_REPL_EVAL_CONFIG##

查看英文版参与翻译

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

ERR_INVALID_RETURN_VALUE##

查看英文版参与翻译

Thrown in case a function option does not return an expected value on execution. For example when a function is expected to return a promise.

ERR_INVALID_SYNC_FORK_INPUT##

查看英文版参与翻译

A Buffer, Uint8Array or string was provided as stdio input to a synchronous 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.

Example:

const { URLSearchParams } = require('url');
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_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_MEMORY_ALLOCATION_FAILED##

查看英文版参与翻译

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

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

查看英文版参与翻译

Stability: 1 - Experimental

An ES6 module could not be resolved.

ERR_MODULE_RESOLUTION_LEGACY##

查看英文版参与翻译

Stability: 1 - Experimental

A failure occurred resolving imports in an ES6 module.

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_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_NO_LONGER_SUPPORTED##

查看英文版参与翻译

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

ERR_OUT_OF_RANGE##

查看英文版参与翻译

A given value is out of the accepted range.

ERR_REQUIRE_ESM##

查看英文版参与翻译

Stability: 1 - Experimental

An attempt was made to require() an ES6 module.

ERR_SCRIPT_EXECUTION_INTERRUPTED##

查看英文版参与翻译

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

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

查看英文版参与翻译

Data could be sent on a socket.

ERR_SOCKET_CLOSED##

查看英文版参与翻译

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

ERR_SOCKET_DGRAM_NOT_RUNNING##

查看英文版参与翻译

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

ERR_STDERR_CLOSE##

查看英文版参与翻译

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

查看英文版参与翻译

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

查看英文版参与翻译

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

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

查看英文版参与翻译

An attempt was made to use a readable stream that did not implement readable._read().

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.

Example

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_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_STREAM_DESTROYED##

查看英文版参与翻译

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

ERR_STRING_TOO_LONG##

查看英文版参与翻译

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

ERR_TLS_CERT_ALTNAME_INVALID##

查看英文版参与翻译

While using TLS, the hostname/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_REQUIRED_SERVER_NAME##

查看英文版参与翻译

While using TLS, the server.addContext() method was called without providing a hostname 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_RENEGOTIATION_DISABLED##

查看英文版参与翻译

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

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_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_ENCODING##

查看英文版参与翻译

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

ERR_UNKNOWN_FILE_EXTENSION##

查看英文版参与翻译

Stability: 1 - Experimental

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

ERR_UNKNOWN_MODULE_FORMAT##

查看英文版参与翻译

Stability: 1 - Experimental

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

查看英文版参与翻译

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

查看英文版参与翻译

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

查看英文版参与翻译

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

ERR_VALUE_OUT_OF_RANGE##

查看英文版参与翻译

A given value is out of the accepted range.

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_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_LINKED##

查看英文版参与翻译

The module must be successfully linked before instantiation.

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

查看英文版参与翻译

Creation of a zlib object failed due to incorrect configuration.