Removes the need to manually manage 206 Partial Content headers. If you can tell me:

It would utilize a optimized stream pipeline to prevent memory leaks, resolving issues where large video fetches fail to release memory.

Instead of manually calculating CHUNK_SIZE and Content-Range headers with fs.statSync (as currently done in Express), Bun.serveVideo would automatically handle this based on the Range request header.

Bun does not support streaming videos with range requests #10440