Under the hood
No documentation found
Image handling now uses Bun's built-in Image type instead of a custom wrapper object
What
A function that previously constructed a custom, frozen wrapper object to represent an image (holding call, signal, event, and origin data) now simply returns new Bun.Image(...), using the image type built into the Bun JavaScript runtime instead.
Why
This simplifies image handling by relying on the runtime's native support rather than a hand-built substitute, though the finding doesn't describe any visible behavior change.
Names in the bundleBun.Image