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

All time, since Sep 6.

Bundle asset paths use cwd

“should be directly usable as a filesystem path regardless of process.cwd().”

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

Built bundle fails to find asset files unless run from output directory. Asset paths in the generated bundle resolve against process.cwd() instead of the module's directory, so running from another directory fails.

Is this your bug?

File my report
Where
bun build output
Error text
TypeError: Bundled file "./index-8dsjzd60.js" not found. You may want to configure --asset-naming or `naming` when bundling.
Versions
1.4.2 to 1.4.4. Still reported on the newest version, 1.4.4.
Platforms
Linux, macOS
How bad
Breaks a normal workflow.

Not quite your bug?

  1. Import misses newly created files4 people
  2. Compiled binary keeps build __dirname2 people

Original reports2, newest first

  1. Full-stack build (--target=bun) only runs when launched from dist/: HTML import manifest paths resolve against cwd#48731
  2. type: "file" imports emit cwd-relative paths instead of module-relative paths#41780

Do you work on Bun?

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