Repository navigation
path.relative behavior inconsistent on case insensitive file system. #18406
Description
- Version: v9.4.0
- Platform: Darwin matts-air.lan 17.2.0 Darwin Kernel Version 17.2.0: Fri Sep 29 18:27:05 PDT 2017; root:xnu-4570.20.62~3/RELEASE_X86_64 x86_64
- Subsystem: path
I have a small demo program to show this issue.
here is the environment:
$ pwd
/Users/matt/test
$ ls -d $(find .)
. ./dir ./dir/file.json ./index.jsHere is index.js:
const sourceFile = "/users/matt/test/dir/file.json";
const destDir = "/Users/matt/test/dest";
const relativePath = require("path").relative(process.cwd(), sourceFile);
const destPath = require("path").join(destDir, relativePath);
console.log(destPath);when I run I get:
$ node index.js
/Users/users/matt/test/dir/file.jsonNotice /Users/users in the path. If I make a change in index.js:
// ...
const sourceFile = "/Users/matt/test/dir/file.json";
// notice capital "Users"
// ...I get:
matts-air:test matt$ node index.js
/Users/matt/test/dest/dir/file.json /Users/matt/test/dest/dir/file.json is correct. So the case is effecting the result and I would expect the result to be the same on a case insensitive file system.
Activity
bnoordhuis commentedon Jan 27, 2018
This is a duplicate of several other reports. To summarize: it's working as expected, it's not a bug.
The
pathmodule doesn't perform I/O, it manipulates strings. It doesn't know about case (in)sensitivity because that is a property of the file system. It can't know about it either because that would rule out the possibility of constructing paths that don't already exist.mattrenaud commentedon Jan 27, 2018
Ok thanks