bun build --compile leads to .bun-build workspace clutter

[jeremybanka]

What version of Bun is running?

1.1.28+cf4e9cb69

What platform is your computer?

Darwin 24.0.0 arm64 arm

What steps can reproduce the bug?

It seems calling bun bulld --compile on any valid file will do, but for example:

echo 'console.log("Hi!")' >> main.js
bun build main.js --compile

Now, you will see the following files in your directory:

.17f66bb7eff7fbbd-00000000.bun-build # for example
main
main.js

.17f66bb7eff7fbbd-00000000.bun-build seems to be a temp file or build artifact of some kind. I don't know what it is. Deleting it has no bearing on soundness of the final binary, main.

What is the expected behavior?

No .bun-build files left behind in my workspace that I need to deal with.

What do you see instead?

A burgeoning pile of .bun-build files in my workspace.

I have to remove them constantly

So I'll keep a post-build script that deletes these as they pile up.

find . -maxdepth 1 -type f -name '*.bun-build' -exec rm -v {} \;

I kept accidentally checking them in

So I need to keep a pattern for them in my .gitignore

*.bun-build

Additional information

No response

[Jarred-Sumner]

Hm it's supposed to delete this

[jeremybanka]

Hm it's supposed to delete this

I would have thought so, is there any debug output I can find and share?

[paperdave]

this function is not well written.

it defines a cleanup function which is supposed to cleanup temporary information, but does not properly place it at all exit points.

the zig language has a feature to prevent these mistakes: defer. this code shouldnt just exit the process on failure and instead return an error so that proper cleanup happens. this is also why #6249 isnt implemented; any errors would interrupt the entire program instead of a JS exception