Node.js v18.12.1 documentation

Table of contents

Domain#

History
Version版本Changes变更
v8.8.0

Any Promise s created in VM contexts no longer have a .domain property. 在VM上下文中创建的任何Promise都不再具有.domain属性。Their handlers are still executed in the proper domain, however, and Promise s created in the main context still possess a .domain property.然而，它们的处理程序仍然在适当的域中执行，并且在主上下文中创建的Promise仍然具有.domain属性。

v8.0.0

Handlers for Promise s are now invoked in the domain in which the first promise of a chain was created.Promise的处理程序现在在创建链的第一个Promise的域中调用。

v1.4.2

Deprecated since: v1.4.2

Stability: 0 - Deprecated

Source Code: lib/domain.js

This module is pending deprecation.此模块正在等待弃用。 Once a replacement API has been finalized, this module will be fully deprecated. 一旦完成替换API，此模块将被完全弃用。Most developers should not have cause to use this module. 大多数开发人员应该没有理由使用此模块。Users who absolutely must have the functionality that domains provide may rely on it for the time being but should expect to have to migrate to a different solution in the future.绝对必须拥有域提供的功能的用户可能暂时依赖它，但将来应该需要迁移到不同的解决方案。

Domains provide a way to handle multiple different IO operations as a single group. 域提供了一种将多个不同IO操作作为单个组处理的方法。If any of the event emitters or callbacks registered to a domain emit an 'error' event, or throw an error, then the domain object will be notified, rather than losing the context of the error in the process.on('uncaughtException') handler, or causing the program to exit immediately with an error code.如果注册到域的任何事件发射器或回调发出'error'事件或抛出错误，则将通知域对象，而不是在process.on('uncaughtException')处理程序中丢失错误上下文，或导致程序立即退出并返回错误代码。