Rank, 14 days: 6 on the Bun sheet
2 people reported

All time, since Oct 5.

fs.rm force throws ENOTDIR

“force: true means a missing path is not an error, so the call resolves.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/bun/issues/4448/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

fs.rm with force throws ENOTDIR on missing trailing-slash path. Under a gVisor (runsc) sandbox, unlink of a missing path with a trailing slash returns ENOTDIR, breaking Nitro-based builds.

Is this your bug?

File my report
Where
fs module
Versions
1.4.2 to 1.4.4. Still reported on the newest version, 1.4.4.
Platforms
Linux
How bad
Breaks a normal workflow.

Original reports2, newest first

  1. fs.rm / fs.rmSync with a trailing-slash path throws ENOTDIR under gVisor (force: true should ignore a missing path)#48559
  2. fs.rm with force fails with ENOTDIR on a missing path with a trailing slash (gVisor)#44587

Do you work on Bun?

Claim its RAP Sheet to see what your users report and answer them in one place.