Bun.Image adds native image pipeline

This looks like Bun pushing further from “runtime” into “platform,” and that matters because image work is one of the first places teams hit dependency sprawl and native-module pain.

• –The appeal is consolidation: fetch from S3, transform, and write back inside one Bun workflow instead of stitching together separate tooling
• –Clipboard import is a small feature on paper, but it signals Bun is targeting real app workflows, not just server-side scripts
• –If the implementation is fast and broadly compatible, Bun.Image could replace a chunk of Sharp/ImageMagick-style glue for straightforward pipelines
• –The downside is surface-area creep: every new builtin increases Bun’s maintenance burden and raises the bar for cross-platform consistency
• –This is most relevant for teams already using Bun in backend or automation code, where reducing process hops and native deps is a concrete win