{"version":"2.1.265","anchor":"image-handling-switched-to-buns-native-image-api","canonical_anchor":"image-handling-switched-to-buns-native-image-api","heading":"Image handling switched to Bun's native Image API","tier":"internal","area":"Images","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/image-handling-switched-to-buns-native-image-api","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Image handling switched to Bun's native Image API\n\nImage handling now uses Bun's built-in Image type instead of a custom wrapper object\n\n**What**\n\nA 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.\n\n**Why**\n\nThis 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.\n\n- Area: Images\n- Names: `Bun.Image`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}