bun-types 1.2.20-canary.20250731T140826 → 1.2.20-canary.20250801T140826

package/docs/api/fetch.md

@@ -337,7 +337,7 @@ This will print the request and response headers to your terminal:
 ```sh
 [fetch] > HTTP/1.1 GET http://example.com/
 [fetch] > Connection: keep-alive
-[fetch] > User-Agent: Bun/1.2.20-canary.20250731T140826
+[fetch] > User-Agent: Bun/1.2.20-canary.20250801T140826
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br

package/docs/api/http.md

@@ -164,6 +164,70 @@ Static responses do not allocate additional memory after initialization. You can
 
 Static route responses are cached for the lifetime of the server object. To reload static routes, call `server.reload(options)`.
 
+### File Responses vs Static Responses
+
+When serving files in routes, there are two distinct behaviors depending on whether you buffer the file content or serve it directly:
+
+```ts
+Bun.serve({
+  routes: {
+    // Static route - content is buffered in memory at startup
+    "/logo.png": new Response(await Bun.file("./logo.png").bytes()),
+
+    // File route - content is read from filesystem on each request
+    "/download.zip": new Response(Bun.file("./download.zip")),
+  },
+});
+```
+
+**Static routes** (`new Response(await file.bytes())`) buffer content in memory at startup:
+
+- **Zero filesystem I/O** during requests - content served entirely from memory
+- **ETag support** - Automatically generates and validates ETags for caching
+- **If-None-Match** - Returns `304 Not Modified` when client ETag matches
+- **No 404 handling** - Missing files cause startup errors, not runtime 404s
+- **Memory usage** - Full file content stored in RAM
+- **Best for**: Small static assets, API responses, frequently accessed files
+
+**File routes** (`new Response(Bun.file(path))`) read from filesystem per request:
+
+- **Filesystem reads** on each request - checks file existence and reads content
+- **Built-in 404 handling** - Returns `404 Not Found` if file doesn't exist or becomes inaccessible
+- **Last-Modified support** - Uses file modification time for `If-Modified-Since` headers
+- **If-Modified-Since** - Returns `304 Not Modified` when file hasn't changed since client's cached version
+- **Range request support** - Automatically handles partial content requests with `Content-Range` headers
+- **Streaming transfers** - Uses buffered reader with backpressure handling for efficient memory usage
+- **Memory efficient** - Only buffers small chunks during transfer, not entire file
+- **Best for**: Large files, dynamic content, user uploads, files that change frequently
+
+### HTTP Caching Behavior
+
+Both route types implement HTTP caching standards but with different strategies:
+
+#### Static Routes Caching
+
+- **ETag generation**: Automatically computes ETag hash from content at startup
+- **If-None-Match**: Validates client ETag against server ETag
+- **304 responses**: Returns `304 Not Modified` with empty body when ETags match
+- **Cache headers**: Inherits any `Cache-Control` headers you provide in the Response
+- **Consistency**: ETag remains constant until server restart or route reload
+
+#### File Routes Caching
+
+- **Last-Modified**: Uses file's `mtime` for `Last-Modified` header
+- **If-Modified-Since**: Compares client date with file modification time
+- **304 responses**: Returns `304 Not Modified` when file unchanged since client's cached version
+- **Content-Length**: Automatically set based on current file size
+- **Dynamic validation**: Checks file modification time on each request
+
+#### Status Code Handling
+
+Both route types automatically adjust status codes:
+
+- **200 → 204**: Empty files (0 bytes) return `204 No Content` instead of `200 OK`
+- **200 → 304**: Successful cache validation returns `304 Not Modified`
+- **File routes only**: Missing or inaccessible files return `404 Not Found`
+
 ```ts
 const server = Bun.serve({
   static: {

package/docs/api/spawn.md

@@ -140,7 +140,7 @@ You can read results from the subprocess via the `stdout` and `stderr` propertie
 ```ts
 const proc = Bun.spawn(["bun", "--version"]);
 const text = await proc.stdout.text();
-console.log(text); // => "1.2.20-canary.20250731T140826\n"
+console.log(text); // => "1.2.20-canary.20250801T140826\n"
 ```
 
 Configure the output stream by passing one of the following values to `stdout/stderr`:

package/docs/cli/pm.md

@@ -213,7 +213,7 @@ To display current package version and help:
 
 ```bash
 $ bun pm version
-bun pm version v1.2.20-canary.20250731T140826 (ca7428e9)
+bun pm version v1.2.20-canary.20250801T140826 (ca7428e9)
 Current package version: v1.0.0
 
 Increment:

package/docs/cli/publish.md

@@ -7,7 +7,7 @@ Use `bun publish` to publish a package to the npm registry.
 $ bun publish
 
 ## Output
-bun publish v1.2.20-canary.20250731T140826 (ca7428e9)
+bun publish v1.2.20-canary.20250801T140826 (ca7428e9)
 
 packed 203B package.json
 packed 224B README.md

package/docs/guides/ecosystem/nuxt.md

@@ -9,7 +9,7 @@ $ bunx nuxi init my-nuxt-app
 ✔ Which package manager would you like to use?
 bun
 ◐ Installing dependencies...
-bun install v1.2.20-canary.20250731T140826 (16b4bf34)
+bun install v1.2.20-canary.20250801T140826 (16b4bf34)
  + @nuxt/devtools@0.8.2
  + nuxt@3.7.0
  785 packages installed [2.67s]

package/docs/guides/install/add-peer.md

@@ -15,7 +15,7 @@ This will add the package to `peerDependencies` in `package.json`.
 ```json-diff
 {
   "peerDependencies": {
-+   "@types/bun": "^1.2.20-canary.20250731T140826"
++   "@types/bun": "^1.2.20-canary.20250801T140826"
   }
 }
 ```
@@ -27,7 +27,7 @@ Running `bun install` will install peer dependencies by default, unless marked o
 ```json-diff
 {
   "peerDependencies": {
-    "@types/bun": "^1.2.20-canary.20250731T140826"
+    "@types/bun": "^1.2.20-canary.20250801T140826"
   },
   "peerDependenciesMeta": {
 +   "@types/bun": {

package/docs/guides/install/from-npm-install-to-bun-install.md

@@ -97,7 +97,7 @@ $ bun update
 $ bun update @types/bun --latest
 
 # Update a dependency to a specific version
-$ bun update @types/bun@1.2.20-canary.20250731T140826
+$ bun update @types/bun@1.2.20-canary.20250801T140826
 
 # Update all dependencies to the latest versions
 $ bun update --latest

package/docs/guides/test/run-tests.md

@@ -21,7 +21,7 @@ Here's what the output of a typical test run looks like. In this case, there are
 
 ```sh
 $ bun test
-bun test v1.2.20-canary.20250731T140826 (9c68abdb)
+bun test v1.2.20-canary.20250801T140826 (9c68abdb)
 
 test.test.js:
 ✓ add [0.87ms]
@@ -47,7 +47,7 @@ To only run certain test files, pass a positional argument to `bun test`. The ru
 
 ```sh
 $ bun test test3
-bun test v1.2.20-canary.20250731T140826 (9c68abdb)
+bun test v1.2.20-canary.20250801T140826 (9c68abdb)
 
 test3.test.js:
 ✓ add [1.40ms]
@@ -85,7 +85,7 @@ Adding `-t add` will only run tests with "add" in the name. This works with test
 
 ```sh
 $ bun test -t add
-bun test v1.2.20-canary.20250731T140826 (9c68abdb)
+bun test v1.2.20-canary.20250801T140826 (9c68abdb)
 
 test.test.js:
 ✓ add [1.79ms]

package/docs/guides/test/snapshot.md

@@ -18,7 +18,7 @@ The first time this test is executed, Bun will evaluate the value passed into `e
 
 ```sh
 $ bun test test/snap
-bun test v1.2.20-canary.20250731T140826 (9c68abdb)
+bun test v1.2.20-canary.20250801T140826 (9c68abdb)
 
 test/snap.test.ts:
 ✓ snapshot [1.48ms]
@@ -61,7 +61,7 @@ Later, when this test file is executed again, Bun will read the snapshot file an
 
 ```sh
 $ bun test
-bun test v1.2.20-canary.20250731T140826 (9c68abdb)
+bun test v1.2.20-canary.20250801T140826 (9c68abdb)
 
 test/snap.test.ts:
 ✓ snapshot [1.05ms]
@@ -78,7 +78,7 @@ To update snapshots, use the `--update-snapshots` flag.
 
 ```sh
 $ bun test --update-snapshots
-bun test v1.2.20-canary.20250731T140826 (9c68abdb)
+bun test v1.2.20-canary.20250801T140826 (9c68abdb)
 
 test/snap.test.ts:
 ✓ snapshot [0.86ms]

package/docs/guides/test/update-snapshots.md

@@ -29,7 +29,7 @@ To regenerate snapshots, use the `--update-snapshots` flag.
 
 ```sh
 $ bun test --update-snapshots
-bun test v1.2.20-canary.20250731T140826 (9c68abdb)
+bun test v1.2.20-canary.20250801T140826 (9c68abdb)
 
 test/snap.test.ts:
 ✓ snapshot [0.86ms]

package/docs/guides/util/version.md

@@ -5,7 +5,7 @@ name: Get the current Bun version
 Get the current version of Bun in a semver format.
 
 ```ts#index.ts
-Bun.version; // => "1.2.20-canary.20250731T140826"
+Bun.version; // => "1.2.20-canary.20250801T140826"
 ```
 
 ---

package/docs/installation.md

@@ -14,7 +14,7 @@ Kernel version 5.6 or higher is strongly recommended, but the minimum is 5.1. Us
 ```bash#macOS/Linux_(curl)
 $ curl -fsSL https://bun.com/install | bash # for macOS, Linux, and WSL
 # to install a specific version
-$ curl -fsSL https://bun.com/install | bash -s "bun-v1.2.20-canary.20250731T140826"
+$ curl -fsSL https://bun.com/install | bash -s "bun-v1.2.20-canary.20250801T140826"
 ```
 
 ```bash#npm
@@ -189,10 +189,10 @@ Since Bun is a single binary, you can install older versions of Bun by re-runnin
 
 ### Installing a specific version of Bun on Linux/Mac
 
-To install a specific version of Bun, you can pass the git tag of the version you want to install to the install script, such as `bun-v1.2.0` or `bun-v1.2.20-canary.20250731T140826`.
+To install a specific version of Bun, you can pass the git tag of the version you want to install to the install script, such as `bun-v1.2.0` or `bun-v1.2.20-canary.20250801T140826`.
 
 ```sh
-$ curl -fsSL https://bun.com/install | bash -s "bun-v1.2.20-canary.20250731T140826"
+$ curl -fsSL https://bun.com/install | bash -s "bun-v1.2.20-canary.20250801T140826"
 ```
 
 ### Installing a specific version of Bun on Windows
@@ -201,7 +201,7 @@ On Windows, you can install a specific version of Bun by passing the version num
 
 ```sh
 # PowerShell:
-$ iex "& {$(irm https://bun.com/install.ps1)} -Version 1.2.20-canary.20250731T140826"
+$ iex "& {$(irm https://bun.com/install.ps1)} -Version 1.2.20-canary.20250801T140826"
 ```
 
 ## Downloading Bun binaries directly

package/docs/runtime/debugger.md

@@ -124,11 +124,11 @@ await fetch("https://example.com", {
 This prints the `fetch` request as a single-line `curl` command to let you copy-paste into your terminal to replicate the request.
 
 ```sh
-[fetch] $ curl --http1.1 "https://example.com/" -X POST -H "content-type: application/json" -H "Connection: keep-alive" -H "User-Agent: Bun/1.2.20-canary.20250731T140826" -H "Accept: */*" -H "Host: example.com" -H "Accept-Encoding: gzip, deflate, br" --compressed -H "Content-Length: 13" --data-raw "{\"foo\":\"bar\"}"
+[fetch] $ curl --http1.1 "https://example.com/" -X POST -H "content-type: application/json" -H "Connection: keep-alive" -H "User-Agent: Bun/1.2.20-canary.20250801T140826" -H "Accept: */*" -H "Host: example.com" -H "Accept-Encoding: gzip, deflate, br" --compressed -H "Content-Length: 13" --data-raw "{\"foo\":\"bar\"}"
 [fetch] > HTTP/1.1 POST https://example.com/
 [fetch] > content-type: application/json
 [fetch] > Connection: keep-alive
-[fetch] > User-Agent: Bun/1.2.20-canary.20250731T140826
+[fetch] > User-Agent: Bun/1.2.20-canary.20250801T140826
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br
@@ -170,7 +170,7 @@ This prints the following to the console:
 [fetch] > HTTP/1.1 POST https://example.com/
 [fetch] > content-type: application/json
 [fetch] > Connection: keep-alive
-[fetch] > User-Agent: Bun/1.2.20-canary.20250731T140826
+[fetch] > User-Agent: Bun/1.2.20-canary.20250801T140826
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br

package/docs/test/dom.md

@@ -55,7 +55,7 @@ Let's run this test with `bun test`:
 
 ```bash
 $ bun test
-bun test v1.2.20-canary.20250731T140826
+bun test v1.2.20-canary.20250801T140826
 
 dom.test.ts:
 ✓ dom test [0.82ms]

package/package.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.2.20-canary.20250731T140826",
+  "version": "1.2.20-canary.20250801T140826",
   "name": "bun-types",
   "license": "MIT",
   "types": "./index.d.ts",

package/sqlite.d.ts

@@ -383,19 +383,28 @@ declare module "bun:sqlite" {
      * ]);
      * ```
      */
-    transaction(insideTransaction: (...args: any) => void): CallableFunction & {
+    transaction<A extends any[], T>(
+      insideTransaction: (...args: A) => T,
+    ): {
       /**
-       * uses "BEGIN DEFERRED"
+       * Execute the transaction
        */
-      deferred: (...args: any) => void;
+      (...args: A): T;
+
       /**
-       * uses "BEGIN IMMEDIATE"
+       * Execute the transaction using "BEGIN DEFERRED"
        */
-      immediate: (...args: any) => void;
+      deferred: (...args: A) => T;
+
+      /**
+       * Execute the transaction using "BEGIN IMMEDIATE"
+       */
+      immediate: (...args: A) => T;
+
       /**
-       * uses "BEGIN EXCLUSIVE"
+       * Execute the transaction using "BEGIN EXCLUSIVE"
        */
-      exclusive: (...args: any) => void;
+      exclusive: (...args: A) => T;
     };
 
     /**