Changing return value of Node.js recursive mkdir

[coreyfarrell]

Per nodejs/node#31530 node.js will soon return the first directory created rather than returning the requested directory. So if ./tmp/ does not exist the following script:

console.log(fs.mkdirSync('tmp/subdir', {recursive: true}));
console.log(fs.mkdirSync('tmp/subdir', {recursive: true}));

This will print tmp then undefined instead of printing tmp/subdir (also the result is never path.resolve'd). Knowing the first directory created can be useful when you need to set permissions or ownership of the created directories.

The node.js change itself will be masked by make-dir which returns path.resolve(input) but I think it would be useful for make-dir to emulate this new functionality. Maybe need to wait until it's known what versions of node.js will get this new functionality so useNativeRecursiveOption can be updated to ensure native is only used if it provides the result?

[sindresorhus]

Makes sense to align with Node.js behavior.

---

Maybe need to wait until it's known what versions of node.js will get this new functionality so useNativeRecursiveOption can be updated to ensure native is only used if it provides the result?

Yes, I think it would be good to know that beforehand.