fs.realpathSync('') returns CWD

[drsm]

$ node -v
v12.18.4

What steps will reproduce the bug?

$ cd /tmp
$ node -e "console.log(fs.realpathSync(''))"
/tmp

What is the expected behavior?

$ node -e "fs.realpath.native('', (e) => void console.log(e))"
[Error: ENOENT: no such file or directory, realpath ''] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'realpath',
  path: ''
}

[ChALkeR]

For more context:

• fs.promises.realpath('') returns a rejection with ENOENT.
• fs.realpath('', (...args) => console.log(args)) passes null, CWD to the callback.
• fs.realpathSync('') returns CWD.

[bnoordhuis]

That output kind of makes sense, knowing what I know about how fs.realpath() is implemented, but it behaves differently on Windows so we should make a judgment call on what we think is the appropriate behavior.

fs.promises.realpath('') returns a rejection with ENOENT.

That's because it's a wrapper around fs.realpath.native rather than fs.realpath. No idea why.

[drsm]

here is some more on this:

> fs.realpath(Buffer.from([]), (e, p) => console.log([e && e.path, p]))
undefined
> [ null, '/tmp' ]

> fs.realpath.native(Buffer.from([]), (e, p) => console.log([e && e.path, p]))
undefined
> [ '', undefined ]

> fs.realpath(Buffer.from([1]), (e, p) => console.log([e && e.path, p]))
undefined
> [ '/tmp/\u0001', undefined ]

> fs.realpath.native(Buffer.from([1]), (e, p) => console.log([e && e.path, p]))
undefined
> [ '\u0001', undefined ]

[github-actions]

This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

[github-actions]

This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.