fs.rmSync('', { recursive: true }) deletes the contents of the current directory on Windows (Node throws ENOENT) #47420

What version of Bun is running?

1.4.4+38afee6c8 (also seen on 1.4.2)

What platform is your computer?

Windows 11 Pro 10.0.26200, x64

What steps can reproduce the bug?

Run this inside an empty scratch directory that holds one file. It deletes the contents of the current working directory, so do not run it anywhere else.

mkdir sandbox && cd sandbox && echo keep > sentinel.txt
bun -e "try { require('node:fs').rmSync('', { recursive: true }) } catch (e) { console.log(e.code) }"
ls -A

What is the expected behavior?

An empty path names no file, so nothing is removed and the call throws ENOENT. That is what Node v25.9.0 does for the same script: it throws ENOENT, and sentinel.txt is still there.

What do you see instead?

Bun removes everything inside the current working directory, then throws EBUSY: resource busy or locked, rm when it reaches the directory itself. sentinel.txt is gone.

The same happens for every recursive form we tried:

So the recursive path appears to resolve '' to the current directory, where the non-recursive path rejects it.

Additional information

We hit this in a real project. A test fixture's cleanup computed an empty path and called rmSync(path, { recursive: true }). The test was running with its cwd at the root of a git worktree, and it emptied the whole working tree, .git file included. Only Windows has been checked; we have not tried Linux or macOS.