Outputting in the same directory as the current is broken

[assyrus-favolo]

I'm in Windows 11, using PowerShell.
I run this command:

bunx swc file.js --out-file file.min.js

And I get this error:

EEXSIT: file already exists, mkdir '.'

If I do this instead:

bunx swc file.js --out-file build/file.min.js

The file is created without issue, is this intended or is it an oversight?

Originally posted by @assyrus-favolo in #11544

[kdy1]

@claude Please fix it

[claude]

Claude finished @kdy1's task in 10m 11s —— View job • claude/issue-11717-20260320-0904 • Create PR ➔

---

Fixing --out-file in same directory (EEXIST error)

• Find the relevant CLI code handling --out-file
• Identify the mkdir call causing the issue
• Fix the bug
• Add test for issue Outputting in the same directory as the current is broken #11717
• Run verification (fmt, clippy, tests)
• Commit and push

Root cause: When --out-file file.min.js is used without a directory component, Path::parent() returns an empty string "". Calling fs::create_dir_all("") fails on Windows with EEXIST.

Fix: Skip create_dir_all when the parent path is empty (i.e., the file is in the current directory). Applied to both --out-file and --out-dir code paths in crates/swc_cli_impl/src/commands/compile.rs.

Note: The original reporter used bunx swc which invokes @swc/cli (a separate repo). The same defensive fix has been applied here to the Rust CLI (swc_cli_impl). The @swc/cli JS package may need a similar fix in its repo.

|