bun-types 1.1.44-canary.20250114T140519 → 1.1.44-canary.20250115T140647

package/ambient.d.ts

@@ -17,3 +17,9 @@ declare module "*/bun.lock" {
 	var contents: import("bun").BunLockFile;
 	export = contents;
 }
+
+declare module "*.html" {
+	// In Bun v1.2, we might change this to Bun.HTMLBundle
+	var contents: any;
+	export = contents;
+}

package/bun.d.ts

@@ -2081,6 +2081,18 @@ declare module "bun" {
 			data: string | ArrayBufferView | ArrayBuffer | SharedArrayBuffer,
 			seed?: bigint,
 		) => bigint;
+		xxHash32: (
+			data: string | ArrayBufferView | ArrayBuffer | SharedArrayBuffer,
+			seed?: number,
+		) => number;
+		xxHash64: (
+			data: string | ArrayBufferView | ArrayBuffer | SharedArrayBuffer,
+			seed?: bigint,
+		) => bigint;
+		xxHash3: (
+			data: string | ArrayBufferView | ArrayBuffer | SharedArrayBuffer,
+			seed?: bigint,
+		) => bigint;
 		murmur32v3: (
 			data: string | ArrayBufferView | ArrayBuffer | SharedArrayBuffer,
 			seed?: number,
@@ -5387,6 +5399,21 @@ declare module "bun" {
 	 */
 	const isMainThread: boolean;
 
+	/**
+	 * Used when importing an HTML file at runtime.
+	 *
+	 * @example
+	 *
+	 * ```ts
+	 * import app from "./index.html";
+	 * ```
+	 *
+	 * Bun.build support for this isn't imlpemented yet.
+	 */
+	interface HTMLBundle {
+		index: string;
+	}
+
 	interface Socket<Data = undefined> extends Disposable {
 		/**
 		 * Write `data` to the socket

package/docs/api/fetch.md

@@ -195,7 +195,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.1.44-canary.20250114T140519
+[fetch] > User-Agent: Bun/1.1.44-canary.20250115T140647
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br

package/docs/api/hashing.md

@@ -169,6 +169,9 @@ Bun.hash.crc32("data", 1234);
 Bun.hash.adler32("data", 1234);
 Bun.hash.cityHash32("data", 1234);
 Bun.hash.cityHash64("data", 1234);
+Bun.hash.xxHash32("data", 1234);
+Bun.hash.xxHash64("data", 1234);
+Bun.hash.xxHash3("data", 1234);
 Bun.hash.murmur32v3("data", 1234);
 Bun.hash.murmur32v2("data", 1234);
 Bun.hash.murmur64v2("data", 1234);

package/docs/api/spawn.md

@@ -110,7 +110,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.1.44-canary.20250114T140519"
+console.log(text); // => "1.1.44-canary.20250115T140647"
 ```
 
 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.1.44-canary.20250114T140519 (ca7428e9)
+bun publish v1.1.44-canary.20250115T140647 (ca7428e9)
 
 packed 203B package.json
 packed 224B README.md

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.1.44-canary.20250114T140519" -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.1.44-canary.20250115T140647" -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.1.44-canary.20250114T140519
+[fetch] > User-Agent: Bun/1.1.44-canary.20250115T140647
 [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.1.44-canary.20250114T140519
+[fetch] > User-Agent: Bun/1.1.44-canary.20250115T140647
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br
@@ -192,7 +192,7 @@ This prints the following to the console:
 
 Bun transpiles every file, which sounds like it would mean that the stack traces you see in the console would unhelpfully point to the transpiled output. To address this, Bun automatically generates and serves sourcemapped files for every file it transpiles. When you see a stack trace in the console, you can click on the file path and be taken to the original source code, even though it was written in TypeScript or JSX, or has some other transformation applied.
 
-<!-- TODO: uncomment once v1.1.13 regression is fixed (cc @paperdave) -->
+<!-- TODO: uncomment once v1.1.13 regression is fixed (cc @paperclover) -->
 <!-- In Bun, each `Error` object gets four additional properties:
 
 - `line` — the source-mapped line number. This number points to the input source code, not the transpiled output.

package/docs/test/dom.md

@@ -55,7 +55,7 @@ Let's run this test with `bun test`:
 
 ```bash
 $ bun test
-bun test v1.1.44-canary.20250114T140519
+bun test v1.1.44-canary.20250115T140647
 
 dom.test.ts:
 ✓ dom test [0.82ms]

package/package.json

@@ -1,5 +1,5 @@
 {
-	"version": "1.1.44-canary.20250114T140519",
+	"version": "1.1.44-canary.20250115T140647",
 	"name": "bun-types",
 	"license": "MIT",
 	"main": "",