---
title: "Bun v1.3.14: built-in image processing, global virtual store, HTTP/3, and more"
url: https://daily.dev/posts/bun-v1-3-14-built-in-image-processing-global-virtual-store-http-3-and-more-sntpql4my
source_url: https://daily.dev/posts/bun-v1-3-14-built-in-image-processing-global-virtual-store-http-3-and-more-sntpql4my
type: collection
source: "Collections"
published: 2026-05-13T04:09:37.000Z
updated: 2026-05-13T04:10:10.114Z
tags: ["javascript", "nodejs", "image-processing", "bun"]
reading_time: 2
upvotes: 68
comments: 3
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Bun v1.3.14: built-in image processing, global virtual store, HTTP/3, and more

**[Collections](https://daily.dev/sources/collections)** · 2 min read · 68 upvotes · 3 comments

## Summary

Bun v1.3.14 ships with a native image processing API (Bun.Image) that claims to outperform sharp, ~7x faster warm installs via a global virtual store, experimental HTTP/2 and HTTP/3 client support in fetch(), and HTTP/3 (QUIC) server support in Bun.serve(). The fs.watch() backend has been fully rewritten for Linux, macOS, and FreeBSD. Additional highlights include ~12% faster ESM module loading, a JavaScriptCore engine upgrade with 565 upstream commits, cross-language LTO reducing Windows binary size by up to 18 MB, Bun.Terminal on Windows via ConPTY, FreeBSD and Android builds, and 92 bug fixes including Node.js compatibility and memory leak improvements.

## Content

Bun v1.3.14 is out, fixing 92 issues and shipping a lot of new stuff. Here's what's worth knowing.

## Built-in image processing with `Bun.Image`

`Bun.Image` is a new native image processing API built directly into Bun. No native module installs, no `sharp` dependency, and according to the Bun team, faster than `sharp` in benchmarks.

## ~7x faster warm installs

The isolated linker now uses a global virtual store, which cuts warm install times dramatically - around 7x faster in testing.

## HTTP/2 and HTTP/3 client support

`fetch()` now has experimental HTTP/2 and HTTP/3 client support. On the server side, `Bun.serve()` gains HTTP/3 (QUIC) support as well.

## Rewritten `fs.watch()` backend

The `fs.watch()` implementation has been fully rewritten on Linux, macOS, and FreeBSD. If you've hit reliability issues with file watching, this is worth testing.

## Other additions

- `--no-orphans` CLI flag for process lifecycle management
- `process.execve()` support
- `Bun.Terminal` on Windows via ConPTY
- FreeBSD and Android builds
- Shared SSL_CTX cache that fixes memory leaks with MongoDB/Mongoose
- Cross-language LTO for Zig/C++ reducing binary size by up to 18 MB on Windows
- ~12% faster ESM module loading
- JavaScriptCore engine upgraded with 565 upstream commits
- Dozens of Node.js compatibility and memory leak fixes

## Community discussion

Top comments from developers on daily.dev.

**@claudson** · 5 upvotes

> I love Bun. I don't need to install 1000+ packages just to get the basics: HTTP, SQL, S3, WebView, TypeScript, and testing all come built in. To me, the Bun team delivered what Node failed to.

**@webkmsyed** · 2 upvotes

> The built-in Bun. Image API is especially exciting no more Sharp dependency and apparently faster too? Thats going to be a game changer for a lot of developers.
>
> Also, 7x faster warm installs and HTTP/3 support are huge quality of life improvements. Bun is moving insanely fast.
>
> The team is shipping at an incredible pace. Really impressive work.
>
> Anyone already tried the new Bun. Image? How does it compare to Sharp in real usage?

**@alexeyzerkalenkov** · 2 upvotes

> All great tools start small. Ban comes with a built-in set of essential and frequently used tools—and they are constantly expanding this collection. The danger lies in the fact that it can quickly become very bloated. Consequently, the need for configuration will inevitably arise—a process that, over time, will only grow more complex... The question is: when will they stop, maintaining that delicate balance between the feature set and overall complexity?

## Similar posts on daily.dev

- [Bun v1.3.12](https://daily.dev/posts/bun-v1-3-12-f5ph0rgqu) · Bun · 140 upvotes · 2 comments
- [Bun v1.3.5](https://daily.dev/posts/bun-v1-3-5-1kprmpe2g) · Bun · 101 upvotes · 0 comments

---

Tags: [#javascript](https://daily.dev/tags/javascript), [#nodejs](https://daily.dev/tags/nodejs), [#image-processing](https://daily.dev/tags/image-processing), [#bun](https://daily.dev/tags/bun)

[View this post on daily.dev](https://daily.dev/posts/bun-v1-3-14-built-in-image-processing-global-virtual-store-http-3-and-more-sntpql4my)