1 person reported

All time, since Aug 1.

--preserve-symlinks has no effect

“A module loaded through a symlink is still resolved from its real path, and __filename inside that module still reports the real path.”

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/5217/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

--preserve-symlinks has no effect on runtime module resolution. A module loaded through a symlink is still resolved from its real path, and __filename still reports the real path.

Is this your bug?

File my report
Where
module resolution
Versions
1.3.14 to 1.4.2
Platforms
Linux, Windows
How bad
Breaks a normal workflow.

Not quite your bug?

  1. Compiled binary keeps build __dirname2 people

Original reports2, newest first

  1. --preserve-symlinks is a no-op at runtime: module resolution and __filename still use the real path#43689
  2. --preserve-symlinks has no effect in the runtime — module paths are still canonicalized to the real path#36755

Do you work on Bun?

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