setImmediate(callback[, ...args])

版本历史

版本	变更
v18.0.0	将无效回调传给 `callback` 参数现在会抛出 `ERR_INVALID_ARG_TYPE` 而不是 `ERR_INVALID_CALLBACK`。
v0.9.1	新增于: v0.9.1

callback <Function> 在本轮 Node.js 事件循环结束时调用的函数
...args <any> 调用 callback 时要传入的可选参数。
返回: <Immediate> 用于 clearImmediate()

在 I/O 事件的回调之后调度 callback 的“立即”执行。

当多次调用 setImmediate() 时，则 callback 函数会按照它们的创建顺序排队执行。每次事件循环迭代都会处理整个回调队列。如果立即定时器从正在执行的回调中排队，则直到下一次事件循环迭代才会触发该定时器。

如果 callback 不是函数，则将抛出 TypeError。

此方法具有可使用 timersPromises.setImmediate() 获得的 promise 的自定义变体。

History

Version	Changes
v18.0.0	Passing an invalid callback to the `callback` argument now throws `ERR_INVALID_ARG_TYPE` instead of `ERR_INVALID_CALLBACK`.
v0.9.1	Added in: v0.9.1

callback <Function> The function to call at the end of this turn of the Node.js Event Loop
...args <any> Optional arguments to pass when the callback is called.
Returns: <Immediate> for use with clearImmediate()

Schedules the "immediate" execution of the callback after I/O events' callbacks.

When multiple calls to setImmediate() are made, the callback functions are queued for execution in the order in which they are created. The entire callback queue is processed every event loop iteration. If an immediate timer is queued from inside an executing callback, that timer will not be triggered until the next event loop iteration.

If callback is not a function, a TypeError will be thrown.

This method has a custom variant for promises that is available using timersPromises.setImmediate().