Open sandy081 opened 1 year ago
Relevant upstream issue: https://github.com/nodejs/node/issues/27534 And suggested PR: https://github.com/nodejs/node/pull/27662
I am not entirely convinced we should take a change here that was not accepted in node.js. We try to stay identical to node.js behaviour with our path library for good reason so that there is identical interop.
I would close this "as designed".
It just got fixed in Node.js and should be released soon in newer versions