bun-types 1.2.9-canary.20250401T140709 → 1.2.9-canary.20250403T140620

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.9-canary.20250401T140709
+[fetch] > User-Agent: Bun/1.2.9-canary.20250403T140620
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br

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.9-canary.20250401T140709"
+console.log(text); // => "1.2.9-canary.20250403T140620"
 ```
 
 Configure the output stream by passing one of the following values to `stdout/stderr`:

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.9-canary.20250401T140709 (ca7428e9)
+bun publish v1.2.9-canary.20250403T140620 (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.9-canary.20250401T140709 (16b4bf34)
+bun install v1.2.9-canary.20250403T140620 (16b4bf34)
  + @nuxt/devtools@0.8.2
  + nuxt@3.7.0
  785 packages installed [2.67s]

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

@@ -16,7 +16,7 @@ This will add the package to `peerDependencies` in `package.json`.
 ```json-diff
 {
   "peerDependencies": {
-+   "@types/bun": "^1.2.9-canary.20250401T140709"
++   "@types/bun": "^1.2.9-canary.20250403T140620"
   }
 }
 ```
@@ -28,7 +28,7 @@ Running `bun install` will install peer dependencies by default, unless marked o
 ```json-diff
 {
   "peerDependencies": {
-    "@types/bun": "^1.2.9-canary.20250401T140709"
+    "@types/bun": "^1.2.9-canary.20250403T140620"
   },
   "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.9-canary.20250401T140709
+$ bun update @types/bun@1.2.9-canary.20250403T140620
 
 # 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.9-canary.20250401T140709 (9c68abdb)
+bun test v1.2.9-canary.20250403T140620 (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.9-canary.20250401T140709 (9c68abdb)
+bun test v1.2.9-canary.20250403T140620 (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.9-canary.20250401T140709 (9c68abdb)
+bun test v1.2.9-canary.20250403T140620 (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.9-canary.20250401T140709 (9c68abdb)
+bun test v1.2.9-canary.20250403T140620 (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.9-canary.20250401T140709 (9c68abdb)
+bun test v1.2.9-canary.20250403T140620 (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.9-canary.20250401T140709 (9c68abdb)
+bun test v1.2.9-canary.20250403T140620 (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.9-canary.20250401T140709 (9c68abdb)
+bun test v1.2.9-canary.20250403T140620 (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.9-canary.20250401T140709"
+Bun.version; // => "1.2.9-canary.20250403T140620"
 ```
 
 ---

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.9-canary.20250401T140709"
+$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.9-canary.20250403T140620"
 ```
 
 ```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.9-canary.20250401T140709`.
+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.9-canary.20250403T140620`.
 
 ```sh
-$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.9-canary.20250401T140709"
+$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.9-canary.20250403T140620"
 ```
 
 ### 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.9-canary.20250401T140709"
+$ iex "& {$(irm https://bun.sh/install.ps1)} -Version 1.2.9-canary.20250403T140620"
 ```
 
 ## 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.9-canary.20250401T140709" -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.9-canary.20250403T140620" -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.9-canary.20250401T140709
+[fetch] > User-Agent: Bun/1.2.9-canary.20250403T140620
 [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.9-canary.20250401T140709
+[fetch] > User-Agent: Bun/1.2.9-canary.20250403T140620
 [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.9-canary.20250401T140709
+bun test v1.2.9-canary.20250403T140620
 
 dom.test.ts:
 ✓ dom test [0.82ms]

package/package.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.2.9-canary.20250401T140709",
+  "version": "1.2.9-canary.20250403T140620",
   "name": "bun-types",
   "license": "MIT",
   "types": "./index.d.ts",

package/s3.d.ts

@@ -617,6 +617,106 @@ declare module "bun" {
     stat(): Promise<S3Stats>;
   }
 
+  interface S3ListObjectsOptions {
+    /** Limits the response to keys that begin with the specified prefix. */
+    prefix?: string;
+    /** ContinuationToken indicates to S3 that the list is being continued on this bucket with a token. ContinuationToken is obfuscated and is not a real key. You can use this ContinuationToken for pagination of the list results. */
+    continuationToken?: string;
+    /** A delimiter is a character that you use to group keys. */
+    delimiter?: string;
+    /** Sets the maximum number of keys returned in the response. By default, the action returns up to 1,000 key names. The response might contain fewer keys but will never contain more. */
+    maxKeys?: number;
+    /** StartAfter is where you want S3 to start listing from. S3 starts listing after this specified key. StartAfter can be any key in the bucket. */
+    startAfter?: string;
+    /** Encoding type used by S3 to encode the object keys in the response. Responses are encoded only in UTF-8. An object key can contain any Unicode character. However, the XML 1.0 parser can't parse certain characters, such as characters with an ASCII value from 0 to 10. For characters that aren't supported in XML 1.0, you can add this parameter to request that S3 encode the keys in the response. */
+    encodingType?: "url";
+    /** If you want to return the owner field with each key in the result, then set the FetchOwner field to true. */
+    fetchOwner?: boolean;
+  }
+
+  interface S3ListObjectsResponse {
+    /** All of the keys (up to 1,000) that share the same prefix are grouped together. When counting the total numbers of returns by this API operation, this group of keys is considered as one item.
+     *
+     * A response can contain CommonPrefixes only if you specify a delimiter.
+     *
+     * CommonPrefixes contains all (if there are any) keys between Prefix and the next occurrence of the string specified by a delimiter.
+     *
+     * CommonPrefixes lists keys that act like subdirectories in the directory specified by Prefix.
+     *
+     * For example, if the prefix is notes/ and the delimiter is a slash (/) as in notes/summer/july, the common prefix is notes/summer/. All of the keys that roll up into a common prefix count as a single return when calculating the number of returns. */
+    commonPrefixes?: { prefix: string }[];
+    /** Metadata about each object returned. */
+    contents?: {
+      /** The algorithm that was used to create a checksum of the object. */
+      checksumAlgorithm?: "CRC32" | "CRC32C" | "SHA1" | "SHA256" | "CRC64NVME";
+      /** The checksum type that is used to calculate the object’s checksum value. */
+      checksumType?: "COMPOSITE" | "FULL_OBJECT";
+      /**
+       * The entity tag is a hash of the object. The ETag reflects changes only to the contents of an object, not its metadata. The ETag may or may not be an MD5 digest of the object data. Whether or not it is depends on how the object was created and how it is encrypted as described below:
+       *
+       * - Objects created by the PUT Object, POST Object, or Copy operation, or through the AWS Management Console, and are encrypted by SSE-S3 or plaintext, have ETags that are an MD5 digest of their object data.
+       * - Objects created by the PUT Object, POST Object, or Copy operation, or through the AWS Management Console, and are encrypted by SSE-C or SSE-KMS, have ETags that are not an MD5 digest of their object data.
+       * - If an object is created by either the Multipart Upload or Part Copy operation, the ETag is not an MD5 digest, regardless of the method of encryption. If an object is larger than 16 MB, the AWS Management Console will upload or copy that object as a Multipart Upload, and therefore the ETag will not be an MD5 digest.
+       *
+       * MD5 is not supported by directory buckets.
+       */
+      eTag?: string;
+      /** The name that you assign to an object. You use the object key to retrieve the object. */
+      key: string;
+      /** Creation date of the object. */
+      lastModified?: string;
+      /** The owner of the object */
+      owner?: {
+        /** The ID of the owner. */
+        id?: string;
+        /** The display name of the owner. */
+        displayName?: string;
+      };
+      /** Specifies the restoration status of an object. Objects in certain storage classes must be restored before they can be retrieved. */
+      restoreStatus?: {
+        /** Specifies whether the object is currently being restored. */
+        isRestoreInProgress?: boolean;
+        /** Indicates when the restored copy will expire. This value is populated only if the object has already been restored. */
+        restoreExpiryDate?: string;
+      };
+      /** Size in bytes of the object */
+      size?: number;
+      /** The class of storage used to store the object. */
+      storageClass?:
+        | "STANDARD"
+        | "REDUCED_REDUNDANCY"
+        | "GLACIER"
+        | "STANDARD_IA"
+        | "ONEZONE_IA"
+        | "INTELLIGENT_TIERING"
+        | "DEEP_ARCHIVE"
+        | "OUTPOSTS"
+        | "GLACIER_IR"
+        | "SNOW"
+        | "EXPRESS_ONEZONE";
+    }[];
+    /** If ContinuationToken was sent with the request, it is included in the response. You can use the returned ContinuationToken for pagination of the list response.  */
+    continuationToken?: string;
+    /** Causes keys that contain the same string between the prefix and the first occurrence of the delimiter to be rolled up into a single result element in the CommonPrefixes collection. These rolled-up keys are not returned elsewhere in the response. Each rolled-up result counts as only one return against the MaxKeys value. */
+    delimiter?: string;
+    /** Encoding type used by S3 to encode object key names in the XML response. */
+    encodingType?: "url";
+    /** Set to false if all of the results were returned. Set to true if more keys are available to return. If the number of results exceeds that specified by MaxKeys, all of the results might not be returned. */
+    isTruncated?: boolean;
+    /** KeyCount is the number of keys returned with this request. KeyCount will always be less than or equal to the MaxKeys field. For example, if you ask for 50 keys, your result will include 50 keys or fewer. */
+    keyCount?: number;
+    /** Sets the maximum number of keys returned in the response. By default, the action returns up to 1,000 key names. The response might contain fewer keys but will never contain more. */
+    maxKeys?: number;
+    /** The bucket name. */
+    name?: string;
+    /** NextContinuationToken is sent when isTruncated is true, which means there are more keys in the bucket that can be listed. The next list requests to S3 can be continued with this NextContinuationToken. NextContinuationToken is obfuscated and is not a real key. */
+    nextContinuationToken?: string;
+    /** Keys that begin with the indicated prefix. */
+    prefix?: string;
+    /** If StartAfter was sent with the request, it is included in the response. */
+    startAfter?: string;
+  }
+
   /**
    * A configured S3 bucket instance for managing files.
    * The instance is callable to create S3File instances and provides methods
@@ -818,6 +918,20 @@ declare module "bun" {
      * @param options The options to use for the S3 client.
      */
     stat(path: string, options?: S3Options): Promise<S3Stats>;
+
+    /** Returns some or all (up to 1,000) of the objects in a bucket with each request.
+     *
+     * You can  use the request parameters as selection criteria to return a subset of the objects in a bucket.
+     */
+    list(
+      input?: S3ListObjectsOptions | null,
+      options?: Pick<S3Options, "accessKeyId" | "secretAccessKey" | "sessionToken" | "region" | "bucket" | "endpoint">,
+    ): Promise<S3ListObjectsResponse>;
+
+    static list(
+      input?: S3ListObjectsOptions | null,
+      options?: Pick<S3Options, "accessKeyId" | "secretAccessKey" | "sessionToken" | "region" | "bucket" | "endpoint">,
+    ): Promise<S3ListObjectsResponse>;
   }
 
   /**