Version
v18.17.1
Platform
No response
Subsystem
fs
What steps will reproduce the bug?
mkdir -p test/include
touch test/libvips-cpp.so.42
constfs=require('fs');fs.readdirSync('test',{recursive: true,withFileTypes: true});How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
awaitfs.promises.readdir('test',{recursive: true,withFileTypes: true})[
Dirent { name: 'include', path: 'folder', [Symbol(type)]: 2 },
Dirent {
name: 'libvips-cpp.so.42',
path: 'folder',
[Symbol(type)]: 1
}
]What do you see instead?
[
Dirent { name: 'include', path: 'folder', [Symbol(type)]: 2 },
Dirent {
name: 'libvips-cpp.so.42',
path: 'folder',
[Symbol(type)]: 1
},
Dirent {
name: undefined,
path: 'folder/include',
[Symbol(type)]: undefined
},
Dirent {
name: undefined,
path: 'folder/include',
[Symbol(type)]: undefined
}
]Additional information
No response
Version
v18.17.1
Platform
No response
Subsystem
fs
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
[ Dirent { name: 'include', path: 'folder', [Symbol(type)]: 2 }, Dirent { name: 'libvips-cpp.so.42', path: 'folder', [Symbol(type)]: 1 } ]What do you see instead?
[ Dirent { name: 'include', path: 'folder', [Symbol(type)]: 2 }, Dirent { name: 'libvips-cpp.so.42', path: 'folder', [Symbol(type)]: 1 }, Dirent { name: undefined, path: 'folder/include', [Symbol(type)]: undefined }, Dirent { name: undefined, path: 'folder/include', [Symbol(type)]: undefined } ]Additional information
No response