Confused setTimout behaviour in NodeJS

Version

14, 18

Platform

22.2.0 Darwin Kernel arm64

Subsystem

No response

What steps will reproduce the bug?

setTimeout(() => {
  console.log('calling 1st timeout')
}, 1)

setTimeout(() => {
  console.log('calling 2rd timeout')
}, 0)

// in nodejs
// calling 1st timeout
// calling 2rd timeout

// however, in chrome browser
// calling 2rd timeout
// calling 1st timeout

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior?

Would expect the second time to be called first

What do you see instead?

The first time out is called then the second timeout in NodeJS

Additional information

No response

首先在 Node.js 14 和 18 上运行提供的 setTimeout 重现，然后将其与浏览器结果进行比较。阅读 Node.js 的 setTimeout 和事件循环文档，以确定该顺序是否有规范说明。完成的标准是确定预期顺序，以及 Node.js 的行为是否需要文档或实现方面的更改。