fs:mkdir should return path not undefined

[evenstensberg]

What is the problem this feature will solve?

When switching from mkdirp we should allow fs.mkdir return the path, not undefined.

What is the feature you are proposing to solve the problem?

Make fs.mkdir return the path

What alternatives have you considered?

N/A

[evenstensberg]

I'd like to fix this if you can point me to the correct code

[jakecastelli]

Hi @evenstensberg do you have a code snippet to demonstrate that it is returning undefined? cheers

[jakecastelli]

I can see from the doc, it explicitly mentioned that

path Present only if a directory is created with recursive set to true.

I think there might be a reason for this behaviour, I'd suggest you wait a little bit until we can hear from the node/fs team or other maintainers.

reference: lib/fs, c++ binding

[meixg]

Related to #43015

[meixg]

Seems that the path is added to solve a problem with recursive: true: #31530.
And since only one folder will be made without recursive: true, returning path does not provide more information.

I do agree we can return path to make it more consistent though.

[bnoordhuis]

No one has explicitly said it so far but the ask is to change the callback in fs.mkdir(loc, (err, path) => { /* ... */}) so that path is always a string, never undefined?

That's a backwards incompatible change from the documented behavior (i.e., likely to break existing code) and we don't usually make those unless the benefits clearly outweigh the drawbacks.

Being a little more compatible with a third-party module isn't a compelling enough reason.

[bnoordhuis]

Since no one chimed in after my last comment I'm going to close this but let me know if there is reason to reopen.