fs async functions (both callback and promises APIs) return Errors without stack trace

• Version: 13.3.0
• Platform: Windows 10 x64

const fs = require('fs')
fs.readFile('nonexistentfile', (err) => console.log(err.stack))

What is the expected output?
The err.stack should contain error text and stack
Same as readFileSync function:

Error: ENOENT: no such file or directory, open 'nonexistentfile'
at Object.openSync (fs.js:446:3)
at Object.readFileSync (fs.js:348:35)
...

What do you see instead?
err.stack only contains error text

Error: ENOENT: no such file or directory, open 'C:\dev\projects\ntest\nonexistentfile'

fs.writeFile have same trouble
Аnother strange thing is that the error text is also different (local/absolute path)

首先，在报告的 Node.js 版本上重现 fs.readFile 和 fs.writeFile 的 callback 情况，然后将它们的错误与 readFileSync 进行比较。也检查相应的 promise API；当异步错误包含 stack trace，并使用预期的路径和错误文本时，即表示完成。