Description
Version
16.14.1
Platform
Linux
Subsystem
No response
What steps will reproduce the bug?
No response
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
Same as fs.mkdirSync without options:
> fs.mkdirSync('./a')
Uncaught Error: ENOSPC: no space left on device, mkdir './a'
at Object.mkdirSync (node:fs:1336:3) {
errno: -28,
syscall: 'mkdir',
code: 'ENOSPC',
path: './a'
}What do you see instead?
> fs.mkdirSync('./a', {recursive: true})
Uncaught Error: ENOENT: no such file or directory, mkdir './a'
at Object.mkdirSync (node:fs:1336:3) {
errno: -2,
syscall: 'mkdir',
code: 'ENOENT',Additional information
No response
Activity