This issue is still there in pkg 4.2.2 when making a build with node 12. In node 12 fspromises is no longer experimental, so I would expect it to work.
I made a small project to test the support:
`
const fs = require('fs');
const fsPromises = fs.promises;
const path = require('path');
const file = path.resolve(path.join(__dirname, 'testfile.json'));

console.log(exists sync: ${fs.existsSync(file)});

fs.readFile(file, (err, data) => {
if (err) {
console.error(Failed to read ${file} using fs.readFile: ${err});
} else {
console.info(read file ${file} successfully using fs.readFile);
}
});
fsPromises.readFile(file).then(() => {
console.info(read file ${file} successfully using fsPromises.readFile);
}).catch(err=> {
console.error(Failed to read ${file} using fsPromises.readFile: ${err});
}
);
Output:
exists sync: true
read file D:\snapshot\pkg fspromise bug\testfile.json successfully using fs.readFile
Failed to read D:\snapshot\pkg fspromise bug\testfile.json using fsPromises.readFile: Error: ENOENT: no such file or directory, open 'D:\snapshot\pkg fspromise bug\testfile.json'
`

fs.promises readdir, readFile, etc. fail with ENOENT #455

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions