bun-types 1.2.13-canary.20250508T140628 → 1.2.13-canary.20250509T140559

package/docs/api/binary-data.md

@@ -557,6 +557,7 @@ Buffer.from(buf, 0, 10);
 #### To `string`
 
 As UTF-8:
+
 ```ts
 new TextDecoder().decode(buf);
 ```
@@ -638,6 +639,7 @@ Buffer.from(arr);
 #### To `string`
 
 As UTF-8:
+
 ```ts
 new TextDecoder().decode(arr);
 ```
@@ -716,6 +718,7 @@ Buffer.from(view.buffer, view.byteOffset, view.byteLength);
 #### To `string`
 
 As UTF-8:
+
 ```ts
 new TextDecoder().decode(view);
 ```
@@ -788,16 +791,21 @@ new DataView(buf.buffer, buf.byteOffset, buf.byteLength);
 #### To `string`
 
 As UTF-8:
+
 ```ts
 buf.toString();
 ```
+
 As base64:
+
 ```ts
-buf.toString('base64');
+buf.toString("base64");
 ```
+
 As hex:
+
 ```ts
-buf.toString('hex');
+buf.toString("hex");
 ```
 
 #### To `number[]`
@@ -876,6 +884,7 @@ Buffer.from(await blob.arrayBuffer());
 #### To `string`
 
 As UTF-8:
+
 ```ts
 await blob.text();
 ```
@@ -962,6 +971,7 @@ Buffer.from(Bun.readableStreamToArrayBuffer(stream));
 #### To `string`
 
 As UTF-8:
+
 ```ts
 // with Response
 await new Response(stream).text();

package/docs/api/dns.md

@@ -10,7 +10,7 @@ console.log(addrs);
 
 ## DNS caching in Bun
 
-In Bun v1.1.9, we added support for DNS caching. This cache makes repeated connections to the same hosts faster. 
+In Bun v1.1.9, we added support for DNS caching. This cache makes repeated connections to the same hosts faster.
 
 At the time of writing, we cache up to 255 entries for a maximum of 30 seconds (each). If any connections to a host fail, we remove the entry from the cache. When multiple connections are made to the same host simultaneously, DNS lookups are deduplicated to avoid making multiple requests for the same host.
 
@@ -27,10 +27,10 @@ This cache is automatically used by:
 
 Web browsers expose [`<link rel="dns-prefetch">`](https://developer.mozilla.org/en-US/docs/Web/Performance/dns-prefetch) to allow developers to prefetch DNS entries. This is useful when you know you'll need to connect to a host in the near future and want to avoid the initial DNS lookup.
 
-In Bun, you can use the `dns.prefetch` API to achieve the same effect. 
+In Bun, you can use the `dns.prefetch` API to achieve the same effect.
 
 ```ts
-import {dns} from "bun";
+import { dns } from "bun";
 
 dns.prefetch("my.database-host.com", 5432);
 ```
@@ -52,7 +52,7 @@ dns.prefetch(hostname: string, port: number): void;
 Here's an example:
 
 ```ts
-import {dns} from "bun";
+import { dns } from "bun";
 
 dns.prefetch("bun.sh", 443);
 //
@@ -66,13 +66,13 @@ await fetch("https://bun.sh");
 **🚧** — This API is experimental and may change in the future.
 {% /callout %}
 
-To get the current cache stats, you can use the `dns.getCacheStats` API. 
+To get the current cache stats, you can use the `dns.getCacheStats` API.
 
 This API returns an object with the following properties:
 
 ```ts
 {
-  // Cache hits 
+  // Cache hits
   cacheHitsCompleted: number;
   cacheHitsInflight: number;
   cacheMisses: number;
@@ -90,7 +90,7 @@ This API returns an object with the following properties:
 Example:
 
 ```ts
-import {dns} from "bun";
+import { dns } from "bun";
 
 const stats = dns.getCacheStats();
 console.log(stats);
@@ -107,7 +107,4 @@ BUN_CONFIG_DNS_TIME_TO_LIVE_SECONDS=5 bun run my-script.ts
 
 #### Why is 30 seconds the default?
 
-Unfortunately, the system API underneath (`getaddrinfo`) does not provide a way to get the TTL of a DNS entry. This means we have to pick a number arbitrarily. We chose 30 seconds because it's long enough to see the benefits of caching, and short enough to be unlikely to cause issues if a DNS entry changes. [Amazon Web Services recommends 5 seconds](https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/jvm-ttl-dns.html) for the Java Virtual Machine, however the JVM defaults to cache indefinitely. 
-
-
-
+Unfortunately, the system API underneath (`getaddrinfo`) does not provide a way to get the TTL of a DNS entry. This means we have to pick a number arbitrarily. We chose 30 seconds because it's long enough to see the benefits of caching, and short enough to be unlikely to cause issues if a DNS entry changes. [Amazon Web Services recommends 5 seconds](https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/jvm-ttl-dns.html) for the Java Virtual Machine, however the JVM defaults to cache indefinitely.

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.13-canary.20250508T140628
+[fetch] > User-Agent: Bun/1.2.13-canary.20250509T140559
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br

package/docs/api/file-io.md

@@ -67,7 +67,7 @@ Bun.stderr;
 You can delete a file by calling the `.delete()` function.
 
 ```ts
-await Bun.file("logs.json").delete()
+await Bun.file("logs.json").delete();
 ```
 
 ## Writing files (`Bun.write()`)

package/docs/api/s3.md

@@ -638,14 +638,10 @@ const credentials = {
 await S3Client.write("my-file.txt", "Hello World");
 
 // Write JSON with type
-await S3Client.write(
-  "data.json",
-  JSON.stringify({hello: "world"}),
-  {
-    ...credentials,
-    type: "application/json",
-  }
-);
+await S3Client.write("data.json", JSON.stringify({ hello: "world" }), {
+  ...credentials,
+  type: "application/json",
+});
 
 // Write from fetch
 const res = await fetch("https://example.com/data");
@@ -655,7 +651,7 @@ await S3Client.write("data.bin", res, credentials);
 await S3Client.write("public.html", html, {
   ...credentials,
   acl: "public-read",
-  type: "text/html"
+  type: "text/html",
 });
 ```
 

package/docs/api/spawn.md

@@ -120,7 +120,7 @@ You can read results from the subprocess via the `stdout` and `stderr` propertie
 ```ts
 const proc = Bun.spawn(["bun", "--version"]);
 const text = await new Response(proc.stdout).text();
-console.log(text); // => "1.2.13-canary.20250508T140628"
+console.log(text); // => "1.2.13-canary.20250509T140559"
 ```
 
 Configure the output stream by passing one of the following values to `stdout/stderr`:

package/docs/api/streams.md

@@ -61,10 +61,12 @@ When using a direct `ReadableStream`, all chunk queueing is handled by the desti
 Bun also supports async generator functions as a source for `Response` and `Request`. This is an easy way to create a `ReadableStream` that fetches data from an asynchronous source.
 
 ```ts
-const response = new Response(async function* () {
-  yield "hello";
-  yield "world";
-}());
+const response = new Response(
+  (async function* () {
+    yield "hello";
+    yield "world";
+  })(),
+);
 
 await response.text(); // "helloworld"
 ```

package/docs/api/udp.md

@@ -5,15 +5,16 @@ Use Bun's UDP API to implement services with advanced real-time requirements, su
 To create a new (bound) UDP socket:
 
 ```ts
-const socket = await Bun.udpSocket({})
+const socket = await Bun.udpSocket({});
 console.log(socket.port); // assigned by the operating system
 ```
 
 Specify a port:
+
 ```ts
 const socket = await Bun.udpSocket({
-  port: 41234
-})
+  port: 41234,
+});
 console.log(socket.port); // 41234
 ```
 
@@ -28,7 +29,6 @@ socket.send("Hello, world!", 41234, "127.0.0.1");
 Note that the address must be a valid IP address - `send` does not perform
 DNS resolution, as it is intended for low-latency operations.
 
-
 ### Receive datagrams
 
 When creating your socket, add a callback to specify what should be done when packets are received:
@@ -37,11 +37,11 @@ When creating your socket, add a callback to specify what should be done when pa
 const server = await Bun.udpSocket({
   socket: {
     data(socket, buf, port, addr) {
-      console.log(`message from ${addr}:${port}:`)
+      console.log(`message from ${addr}:${port}:`);
       console.log(buf.toString());
-    } 
-  }
-})
+    },
+  },
+});
 
 const client = await Bun.udpSocket({});
 client.send("Hello!", server.port, "127.0.0.1");
@@ -54,29 +54,26 @@ In such cases it can be beneficial to connect the socket to that peer, which spe
 and restricts incoming packets to that peer only.
 
 ```ts
-
 const server = await Bun.udpSocket({
   socket: {
     data(socket, buf, port, addr) {
-      console.log(`message from ${addr}:${port}:`)
+      console.log(`message from ${addr}:${port}:`);
       console.log(buf.toString());
-    } 
-  }
-})
+    },
+  },
+});
 const client = await Bun.udpSocket({
   connect: {
     port: server.port,
-    hostname: '127.0.0.1',
-  }
+    hostname: "127.0.0.1",
+  },
 });
 
 client.send("Hello");
-
 ```
 
 Because connections are implemented on the operating system level, you can potentially observe performance benefits, too.
 
-
 ### Send many packets at once using `sendMany()`
 
 If you want to send a large volume of packets at once, it can make sense to batch them all together to avoid the overhead
@@ -86,9 +83,9 @@ For an unconnected socket, `sendMany` takes an array as its only argument. Each
 The first item is the data to be sent, the second is the target port, and the last is the target address.
 
 ```ts
-const socket = await Bun.udpSocket({})
+const socket = await Bun.udpSocket({});
 // sends 'Hello' to 127.0.0.1:41234, and 'foo' to 1.1.1.1:53 in a single operation
-socket.sendMany(['Hello', 41234, '127.0.0.1', 'foo', 53, '1.1.1.1'])
+socket.sendMany(["Hello", 41234, "127.0.0.1", "foo", 53, "1.1.1.1"]);
 ```
 
 With a connected socket, `sendMany` simply takes an array, where each element represents the data to be sent to the peer.
@@ -97,10 +94,10 @@ With a connected socket, `sendMany` simply takes an array, where each element re
 const socket = await Bun.udpSocket({
   connect: {
     port: 41234,
-    hostname: 'localhost',
-  }
+    hostname: "localhost",
+  },
 });
-socket.sendMany(['foo', 'bar', 'baz']);
+socket.sendMany(["foo", "bar", "baz"]);
 ```
 
 `sendMany` returns the number of packets that were successfully sent. As with `send`, `sendMany` only takes valid IP addresses
@@ -110,16 +107,17 @@ as destinations, as it does not perform DNS resolution.
 
 It may happen that a packet that you're sending does not fit into the operating system's packet buffer. You can detect that this
 has happened when:
-- `send` returns `false` 
+
+- `send` returns `false`
 - `sendMany` returns a number smaller than the number of packets you specified
-In this case, the `drain` socket handler will be called once the socket becomes writable again:
+  In this case, the `drain` socket handler will be called once the socket becomes writable again:
 
 ```ts
 const socket = await Bun.udpSocket({
   socket: {
     drain(socket) {
       // continue sending data
-    }
-  }
+    },
+  },
 });
 ```

package/docs/bundler/index.md

@@ -1630,4 +1630,4 @@ declare class ResolveMessage {
 }
 ```
 
-{% bunCLIUsage command="build" /%}
+{% bunCLIUsage command="build" /%}

package/docs/bundler/macros.md

@@ -71,7 +71,7 @@ node_modules/evil/index.js:3:1 50
 Your application code can still import macros from `node_modules` and invoke them.
 
 ```ts
-import {macro} from "some-package" with { type: "macro" };
+import { macro } from "some-package" with { type: "macro" };
 
 macro();
 ```
@@ -95,8 +95,8 @@ When shipping a library containing a macro to `npm` or another package registry,
 With this configuration, users can consume your package at runtime or at bundle-time using the same import specifier:
 
 ```ts
-import pkg from "my-package";                            // runtime import
-import {macro} from "my-package" with { type: "macro" }; // macro import
+import pkg from "my-package"; // runtime import
+import { macro } from "my-package" with { type: "macro" }; // macro import
 ```
 
 The first import will resolve to `./node_modules/my-package/index.js`, while the second will be resolved by Bun's bundler to `./node_modules/my-package/index.macro.js`.
@@ -122,7 +122,7 @@ export function returnFalse() {
 ...then bundling the following file will produce an empty bundle, provided that the minify syntax option is enabled.
 
 ```ts
-import {returnFalse} from './returnFalse.ts' with { type: 'macro' };
+import { returnFalse } from "./returnFalse.ts" with { type: "macro" };
 
 if (returnFalse()) {
   console.log("This code is eliminated");
@@ -179,7 +179,7 @@ export function getText(url: string) {
 Macros can accept inputs, but only in limited cases. The value must be statically known. For example, the following is not allowed:
 
 ```ts
-import {getText} from './getText.ts' with { type: 'macro' };
+import { getText } from "./getText.ts" with { type: "macro" };
 
 export function howLong() {
   // the value of `foo` cannot be statically known
@@ -193,8 +193,8 @@ export function howLong() {
 However, if the value of `foo` is known at bundle-time (say, if it's a constant or the result of another macro) then it's allowed:
 
 ```ts
-import {getText} from './getText.ts' with { type: 'macro' };
-import {getFoo} from './getFoo.ts' with { type: 'macro' };
+import { getText } from "./getText.ts" with { type: "macro" };
+import { getFoo } from "./getFoo.ts" with { type: "macro" };
 
 export function howLong() {
   // this works because getFoo() is statically known
@@ -271,7 +271,9 @@ export async function extractMetaTags(url: string) {
     .on("meta", {
       element(element) {
         const name =
-          element.getAttribute("name") || element.getAttribute("property") || element.getAttribute("itemprop");
+          element.getAttribute("name") ||
+          element.getAttribute("property") ||
+          element.getAttribute("itemprop");
 
         if (name) meta[name] = element.getAttribute("content");
       },

package/docs/cli/add.md

@@ -63,8 +63,8 @@ This will add the following to your `package.json`:
     "react": "^18.2.0", // this matches >= 18.2.0 < 19.0.0
 
     // with --exact
-    "react": "18.2.0" // this matches only 18.2.0 exactly
-  }
+    "react": "18.2.0", // this matches only 18.2.0 exactly
+  },
 }
 ```
 
@@ -170,4 +170,4 @@ This will add the following line to your `package.json`:
 }
 ```
 
-{% bunCLIUsage command="add" /%}
+{% bunCLIUsage command="add" /%}

package/docs/cli/link.md

@@ -37,4 +37,4 @@ In addition, the `--save` flag can be used to add `cool-pkg` to the `dependencie
   }
 ```
 
-{% bunCLIUsage command="link" /%}
+{% bunCLIUsage command="link" /%}

package/docs/cli/patch-commit.md

@@ -8,4 +8,4 @@ By default, `bun patch-commit` will use the `patches` directory in the temporary
 
 You can specify a different directory with the `--patches-dir` flag.
 
-{% bunCLIUsage command="patch-commit" /%}
+{% bunCLIUsage command="patch-commit" /%}

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.13-canary.20250508T140628 (ca7428e9)
+bun publish v1.2.13-canary.20250509T140559 (ca7428e9)
 
 packed 203B package.json
 packed 224B README.md

package/docs/cli/run.md

@@ -206,4 +206,4 @@ When there is a package.json script and a file with the same name, `bun run` pri
 3. Binaries from project packages, eg `bun add eslint && bun run eslint`
 4. (`bun run` only) System commands, eg `bun run ls`
 
-{% bunCLIUsage command="run" /%}
+{% bunCLIUsage command="run" /%}

package/docs/cli/update.md

@@ -33,4 +33,4 @@ For example, with the following `package.json`:
 - `bun update` would update to a version that matches `17.x`.
 - `bun update --latest` would update to a version that matches `18.x` or later.
 
-{% bunCLIUsage command="update" /%}
+{% bunCLIUsage command="update" /%}

package/docs/ecosystem/stric.md

@@ -9,7 +9,7 @@ export default new Router()
   .get('/', () => new Response('Hi'));
 ```
 
-Stric provides support for [ArrowJS](https://www.arrow-js.com), a library for building reactive interfaces. 
+Stric provides support for [ArrowJS](https://www.arrow-js.com), a library for building reactive interfaces.
 
 {% codetabs %}
 
@@ -25,6 +25,7 @@ export function render() {
 // Set the path to handle
 export const path = '/';
 ```
+
 ```ts#index.ts
 import { PageRouter } from '@stricjs/arrow';
 

package/docs/guides/ecosystem/neon-drizzle.md

@@ -2,9 +2,9 @@
 name: Use Neon Postgres through Drizzle ORM
 ---
 
-[Neon](https://neon.tech/) is a fully managed serverless Postgres, separating compute and storage to offer features like autoscaling, branching and bottomless storage. Neon can be used from Bun directly using the `@neondatabase/serverless` driver or through an ORM like `Drizzle`. 
+[Neon](https://neon.tech/) is a fully managed serverless Postgres, separating compute and storage to offer features like autoscaling, branching and bottomless storage. Neon can be used from Bun directly using the `@neondatabase/serverless` driver or through an ORM like `Drizzle`.
 
-Drizzle ORM supports both a SQL-like "query builder" API and an ORM-like [Queries API](https://orm.drizzle.team/docs/rqb). Get started by creating a project directory, initializing the directory using `bun init`, and installing Drizzle and the [Neon serverless driver](https://github.com/neondatabase/serverless/). 
+Drizzle ORM supports both a SQL-like "query builder" API and an ORM-like [Queries API](https://orm.drizzle.team/docs/rqb). Get started by creating a project directory, initializing the directory using `bun init`, and installing Drizzle and the [Neon serverless driver](https://github.com/neondatabase/serverless/).
 
 ```sh
 $ mkdir bun-drizzle-neon
@@ -52,7 +52,7 @@ console.log(result.rows);
 
 ---
 
-Then run `index.ts` with Bun. 
+Then run `index.ts` with Bun.
 
 ```sh
 $ bun run index.ts
@@ -65,7 +65,7 @@ $ bun run index.ts
 
 ---
 
-We can define a schema for our database using Drizzle ORM primitives. Create a `schema.ts` file and add this code. 
+We can define a schema for our database using Drizzle ORM primitives. Create a `schema.ts` file and add this code.
 
 ```ts#schema.ts
 import { pgTable, integer, serial, text, timestamp } from "drizzle-orm/pg-core";
@@ -215,6 +215,6 @@ $ bun run index.ts
 
 ---
 
-This example used the Neon serverless driver's SQL-over-HTTP functionality. Neon's serverless driver also exposes `Client` and `Pool` constructors to enable sessions, interactive transactions, and node-postgres compatibility. Refer to [Neon's documentation](https://neon.tech/docs/serverless/serverless-driver) for a complete overview. 
+This example used the Neon serverless driver's SQL-over-HTTP functionality. Neon's serverless driver also exposes `Client` and `Pool` constructors to enable sessions, interactive transactions, and node-postgres compatibility. Refer to [Neon's documentation](https://neon.tech/docs/serverless/serverless-driver) for a complete overview.
 
 Refer to the [Drizzle website](https://orm.drizzle.team/docs/overview) for more documentation on using the Drizzle ORM.

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.13-canary.20250508T140628 (16b4bf34)
+bun install v1.2.13-canary.20250509T140559 (16b4bf34)
  + @nuxt/devtools@0.8.2
  + nuxt@3.7.0
  785 packages installed [2.67s]

package/docs/guides/ecosystem/pm2.md

@@ -40,7 +40,7 @@ module.exports = {
   interpreter: "bun", // Bun interpreter
   env: {
     PATH: `${process.env.HOME}/.bun/bin:${process.env.PATH}`, // Add "~/.bun/bin/bun" to PATH
-  }
+  },
 };
 ```
 

package/docs/guides/ecosystem/sveltekit.md

@@ -52,9 +52,9 @@ $ cd my-app
 $ bun --bun run dev
   $ vite dev
   Forced re-optimization of dependencies
-  
+
     VITE v5.4.10  ready in 424 ms
-  
+
     ➜  Local:   http://localhost:5173/
     ➜  Network: use --host to expose
     ➜  press h + enter to show help
@@ -88,7 +88,7 @@ Now, make the following changes to your `svelte.config.js`.
   	// Consult https://svelte.dev/docs/kit/integrations#preprocessors
   	// for more information about preprocessors
   	preprocess: vitePreprocess(),
-  
+
   	kit: {
   		// adapter-auto only supports some environments, see https://svelte.dev/docs/kit/adapter-auto for a list.
   		// If your environment is not supported, or you settled on a specific environment, switch out the adapter.
@@ -96,7 +96,7 @@ Now, make the following changes to your `svelte.config.js`.
   		adapter: adapter()
   	}
   };
-  
+
   export default config;
 ```
 
@@ -116,9 +116,9 @@ $ bun --bun run build
   ✓ built in 231ms
   ...
   ✓ built in 899ms
-  
+
   Run npm run preview to preview your production build locally.
-  
+
   > Using svelte-adapter-bun
     ✔ Start server with: bun ./build/index.js
     ✔ done

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

@@ -2,7 +2,6 @@
 name: Add a peer dependency
 ---
 
-
 To add an npm package as a peer dependency, use the `--peer` flag.
 
 ```sh
@@ -16,7 +15,7 @@ This will add the package to `peerDependencies` in `package.json`.
 ```json-diff
 {
   "peerDependencies": {
-+   "@types/bun": "^1.2.13-canary.20250508T140628"
++   "@types/bun": "^1.2.13-canary.20250509T140559"
   }
 }
 ```
@@ -28,7 +27,7 @@ Running `bun install` will install peer dependencies by default, unless marked o
 ```json-diff
 {
   "peerDependencies": {
-    "@types/bun": "^1.2.13-canary.20250508T140628"
+    "@types/bun": "^1.2.13-canary.20250509T140559"
   },
   "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.13-canary.20250508T140628
+$ bun update @types/bun@1.2.13-canary.20250509T140559
 
 # Update all dependencies to the latest versions
 $ bun update --latest

package/docs/guides/process/argv.md

@@ -56,4 +56,3 @@ $ bun run cli.ts --flag1 --flag2 value
 }
 [ "/path/to/bun", "/path/to/cli.ts" ]
 ```
-

package/docs/guides/runtime/set-env.md

@@ -42,7 +42,6 @@ $ set FOO=helloworld && bun run dev
 $ $env:FOO="helloworld"; bun run dev
 ```
 
-{% /codetabs %}
----
+## {% /codetabs %}
 
 See [Docs > Runtime > Environment variables](https://bun.sh/docs/runtime/env) for more information on using environment variables with Bun.

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.13-canary.20250508T140628 (9c68abdb)
+bun test v1.2.13-canary.20250509T140559 (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.13-canary.20250508T140628 (9c68abdb)
+bun test v1.2.13-canary.20250509T140559 (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.13-canary.20250508T140628 (9c68abdb)
+bun test v1.2.13-canary.20250509T140559 (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.13-canary.20250508T140628 (9c68abdb)
+bun test v1.2.13-canary.20250509T140559 (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.13-canary.20250508T140628 (9c68abdb)
+bun test v1.2.13-canary.20250509T140559 (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.13-canary.20250508T140628 (9c68abdb)
+bun test v1.2.13-canary.20250509T140559 (9c68abdb)
 
 test/snap.test.ts:
 ✓ snapshot [0.86ms]

package/docs/guides/test/testing-library.md

@@ -1,9 +1,11 @@
 ---
 name: Using Testing Library with Bun
 ---
+
 You can use [Testing Library](https://testing-library.com/) with Bun's test runner.
 
 ---
+
 As a prerequisite to using Testing Library you will need to install [Happy Dom](https://github.com/capricorn86/happy-dom). ([see Bun's Happy DOM guide for more information](https://bun.sh/guides/test/happy-dom)).
 
 ```sh
@@ -17,6 +19,7 @@ Next you should install the Testing Library packages you are planning on using.
 ```sh
 bun add -D @testing-library/react @testing-library/dom @testing-library/jest-dom
 ```
+
 ---
 
 Next you will need to create a preload script for Happy DOM and for Testing Library. For more details about the Happy DOM setup script see [Bun's Happy DOM guide](https://bun.sh/guides/test/happy-dom).
@@ -26,6 +29,7 @@ import { GlobalRegistrator } from '@happy-dom/global-registrator';
 
 GlobalRegistrator.register();
 ```
+
 ---
 
 For Testing Library, you will want to extend Bun's `expect` function with Testing Library's matchers. Optionally, to better match the behavior of test-runners like Jest, you may want to run cleanup after each test.
@@ -51,6 +55,7 @@ Next, add these preload scripts to your `bunfig.toml` (you can also have everyth
 [test]
 preload = ["./happydom.ts", "./testing-library.ts"]
 ```
+
 ---
 
 If you are using TypeScript you will also need to make use of declaration merging in order to get the new matcher types to show up in your editor. To do this, create a type declaration file that extends `Matchers` like this.
@@ -71,15 +76,15 @@ declare module 'bun:test' {
 You should now be able to use Testing Library in your tests
 
 ```ts
-import { test, expect } from 'bun:test';
-import { screen, render } from '@testing-library/react';
-import { MyComponent } from './myComponent';
+import { test, expect } from "bun:test";
+import { screen, render } from "@testing-library/react";
+import { MyComponent } from "./myComponent";
 
-test('Can use Testing Library', () => {
+test("Can use Testing Library", () => {
   render(MyComponent);
-  const myComponent = screen.getByTestId('my-component');
+  const myComponent = screen.getByTestId("my-component");
   expect(myComponent).toBeInTheDocument();
-})
+});
 ```
 
 ---

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.13-canary.20250508T140628 (9c68abdb)
+bun test v1.2.13-canary.20250509T140559 (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.13-canary.20250508T140628"
+Bun.version; // => "1.2.13-canary.20250509T140559"
 ```
 
 ---

package/docs/install/patch.md

@@ -56,4 +56,4 @@ $ bun patch --commit react --patches-dir=mypatches
 $ bun patch-commit react
 ```
 
-{% bunCLIUsage command="patch" /%}
+{% bunCLIUsage command="patch" /%}

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.sh/install | bash # for macOS, Linux, and WSL
 # to install a specific version
-$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.13-canary.20250508T140628"
+$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.13-canary.20250509T140559"
 ```
 
 ```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.13-canary.20250508T140628`.
+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.13-canary.20250509T140559`.
 
 ```sh
-$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.13-canary.20250508T140628"
+$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.13-canary.20250509T140559"
 ```
 
 ### 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.sh/install.ps1)} -Version 1.2.13-canary.20250508T140628"
+$ iex "& {$(irm https://bun.sh/install.ps1)} -Version 1.2.13-canary.20250509T140559"
 ```
 
 ## Downloading Bun binaries directly

package/docs/runtime/bunfig.md

@@ -198,7 +198,6 @@ Set path where coverage reports will be saved. Please notice, that it works only
 coverageDir = "path/to/somewhere"  # default "coverage"
 ```
 
-
 ## Package manager
 
 Package management is a complex issue; to support a range of use cases, the behavior of `bun install` can be configured under the `[install]` section.

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.13-canary.20250508T140628" -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.13-canary.20250509T140559" -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.13-canary.20250508T140628
+[fetch] > User-Agent: Bun/1.2.13-canary.20250509T140559
 [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.13-canary.20250508T140628
+[fetch] > User-Agent: Bun/1.2.13-canary.20250509T140559
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br

package/docs/runtime/hot.md

@@ -69,7 +69,6 @@ The **`--no-clear-screen`** flag is useful in scenarios where you don’t want t
 
 {% /callout %}
 
-
 ## `--hot` mode
 
 Use `bun --hot` to enable hot reloading when executing code with Bun. This is distinct from `--watch` mode in that Bun does not hard-restart the entire process. Instead, it detects code changes and updates its internal module cache with the new code.

package/docs/test/dom.md

@@ -55,7 +55,7 @@ Let's run this test with `bun test`:
 
 ```bash
 $ bun test
-bun test v1.2.13-canary.20250508T140628
+bun test v1.2.13-canary.20250509T140559
 
 dom.test.ts:
 ✓ dom test [0.82ms]

package/docs/test/mocks.md

@@ -206,11 +206,13 @@ Understanding how `mock.module()` works helps you use it more effectively:
 2. **Lazy Evaluation**: The mock factory callback is only evaluated when the module is actually imported or required.
 
 3. **Path Resolution**: Bun automatically resolves the module specifier as though you were doing an import, supporting:
+
    - Relative paths (`'./module'`)
    - Absolute paths (`'/path/to/module'`)
    - Package names (`'lodash'`)
 
-4. **Import Timing Effects**: 
+4. **Import Timing Effects**:
+
    - When mocking before first import: No side effects from the original module occur
    - When mocking after import: The original module's side effects have already happened
    - For this reason, using `--preload` is recommended for mocks that need to prevent side effects
@@ -232,15 +234,15 @@ const random2 = mock(() => Math.random());
 test("clearing all mocks", () => {
   random1();
   random2();
-  
+
   expect(random1).toHaveBeenCalledTimes(1);
   expect(random2).toHaveBeenCalledTimes(1);
-  
+
   mock.clearAllMocks();
-  
+
   expect(random1).toHaveBeenCalledTimes(0);
   expect(random2).toHaveBeenCalledTimes(0);
-  
+
   // Note: implementations are preserved
   expect(typeof random1()).toBe("number");
   expect(typeof random2()).toBe("number");
@@ -258,18 +260,18 @@ Using `mock.restore()` can reduce the amount of code in your tests by adding it
 ```ts
 import { expect, mock, spyOn, test } from "bun:test";
 
-import * as fooModule from './foo.ts';
-import * as barModule from './bar.ts';
-import * as bazModule from './baz.ts';
+import * as fooModule from "./foo.ts";
+import * as barModule from "./bar.ts";
+import * as bazModule from "./baz.ts";
 
-test('foo, bar, baz', () => {
-  const fooSpy = spyOn(fooModule, 'foo');
-  const barSpy = spyOn(barModule, 'bar');
-  const bazSpy = spyOn(bazModule, 'baz');
+test("foo, bar, baz", () => {
+  const fooSpy = spyOn(fooModule, "foo");
+  const barSpy = spyOn(barModule, "bar");
+  const bazSpy = spyOn(bazModule, "baz");
 
-  expect(fooSpy).toBe('foo');
-  expect(barSpy).toBe('bar');
-  expect(bazSpy).toBe('baz');
+  expect(fooSpy).toBe("foo");
+  expect(barSpy).toBe("bar");
+  expect(bazSpy).toBe("baz");
 
   fooSpy.mockImplementation(() => 42);
   barSpy.mockImplementation(() => 43);
@@ -281,9 +283,9 @@ test('foo, bar, baz', () => {
 
   mock.restore();
 
-  expect(fooSpy).toBe('foo');
-  expect(barSpy).toBe('bar');
-  expect(bazSpy).toBe('baz');
+  expect(fooSpy).toBe("foo");
+  expect(barSpy).toBe("bar");
+  expect(bazSpy).toBe("baz");
 });
 ```
 
@@ -297,10 +299,10 @@ import { test, expect } from "bun:test";
 // Using the 'vi' alias similar to Vitest
 test("vitest compatibility", () => {
   const mockFn = vi.fn(() => 42);
-  
+
   mockFn();
   expect(mockFn).toHaveBeenCalled();
-  
+
   // The following functions are available on the vi object:
   // vi.fn
   // vi.spyOn

package/docs/test/time.md

@@ -84,10 +84,10 @@ import { test, expect, jest } from "bun:test";
 test("get the current mocked time", () => {
   jest.useFakeTimers();
   jest.setSystemTime(new Date("2020-01-01T00:00:00.000Z"));
-  
+
   expect(Date.now()).toBe(1577836800000); // Jan 1, 2020 timestamp
   expect(jest.now()).toBe(1577836800000); // Same value
-  
+
   jest.useRealTimers();
 });
 ```

package/package.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.2.13-canary.20250508T140628",
+  "version": "1.2.13-canary.20250509T140559",
   "name": "bun-types",
   "license": "MIT",
   "types": "./index.d.ts",