bun-types 1.2.12-canary.20250502T140709 → 1.2.12-canary.20250503T140622

package/bun.d.ts

@@ -3258,6 +3258,12 @@ declare module "bun" {
            *
            */
           hmr?: boolean;
+
+          /**
+           * Enable console log streaming from browser to server
+           * @default false
+           */
+          console?: boolean;
         };
 
     error?: (this: Server, error: ErrorLike) => Response | Promise<Response> | void | Promise<void>;

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.12-canary.20250502T140709
+[fetch] > User-Agent: Bun/1.2.12-canary.20250503T140622
 [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.12-canary.20250502T140709"
+console.log(text); // => "1.2.12-canary.20250503T140622"
 ```
 
 Configure the output stream by passing one of the following values to `stdout/stderr`:

package/docs/bundler/fullstack.md

@@ -203,6 +203,34 @@ When `development` is `true`, Bun will:
 - Include the `SourceMap` header in the response so that devtools can show the original source code
 - Disable minification
 - Re-bundle assets on each request to a .html file
+- Enable hot module reloading (unless `hmr: false` is set)
+
+#### Echo console logs from browser to terminal
+
+Bun.serve() supports echoing console logs from the browser to the terminal.
+
+To enable this, pass `console: true` in the `development` object in `Bun.serve()`.
+
+```ts
+import homepage from "./index.html";
+
+Bun.serve({
+  // development can also be an object.
+  development: {
+    // Enable Hot Module Reloading
+    hmr: true,
+
+    // Echo console logs from the browser to the terminal
+    console: true,
+  },
+
+  routes: {
+    "/": homepage,
+  },
+});
+```
+
+When `console: true` is set, Bun will stream console logs from the browser to the terminal. This reuses the existing WebSocket connection from HMR to send the logs.
 
 #### Production mode
 

package/docs/bundler/html.md

@@ -194,6 +194,18 @@ import "tailwindcss";
 
 Only one of those are necessary, not all three.
 
+## `--console` streams console logs from the browser to the terminal
+
+Bun's dev server supports streaming console logs from the browser to the terminal.
+
+To enable, pass the `--console` CLI flag.
+
+{% bunDevServerTerminal alt="bun --console ./index.html" path="./index.html" routes="" /%}
+
+Each call to `console.log` or `console.error` will be broadcast to the terminal that started the server.
+
+Internally, this reuses the existing WebSocket connection from hot module reloading to send the logs.
+
 ## Keyboard Shortcuts
 
 While the server is running:
@@ -288,7 +300,6 @@ All paths are resolved relative to your HTML file, making it easy to organize yo
 
 ## This is a work in progress
 
-- No HMR support yet
 - Need more plugins
 - Need more configuration options for things like asset handling
 - Need a way to configure CORS, headers, etc.

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.12-canary.20250502T140709 (ca7428e9)
+bun publish v1.2.12-canary.20250503T140622 (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.12-canary.20250502T140709 (16b4bf34)
+bun install v1.2.12-canary.20250503T140622 (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.12-canary.20250502T140709"
++   "@types/bun": "^1.2.12-canary.20250503T140622"
   }
 }
 ```
@@ -28,7 +28,7 @@ Running `bun install` will install peer dependencies by default, unless marked o
 ```json-diff
 {
   "peerDependencies": {
-    "@types/bun": "^1.2.12-canary.20250502T140709"
+    "@types/bun": "^1.2.12-canary.20250503T140622"
   },
   "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.12-canary.20250502T140709
+$ bun update @types/bun@1.2.12-canary.20250503T140622
 
 # 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.12-canary.20250502T140709 (9c68abdb)
+bun test v1.2.12-canary.20250503T140622 (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.12-canary.20250502T140709 (9c68abdb)
+bun test v1.2.12-canary.20250503T140622 (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.12-canary.20250502T140709 (9c68abdb)
+bun test v1.2.12-canary.20250503T140622 (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.12-canary.20250502T140709 (9c68abdb)
+bun test v1.2.12-canary.20250503T140622 (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.12-canary.20250502T140709 (9c68abdb)
+bun test v1.2.12-canary.20250503T140622 (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.12-canary.20250502T140709 (9c68abdb)
+bun test v1.2.12-canary.20250503T140622 (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.12-canary.20250502T140709 (9c68abdb)
+bun test v1.2.12-canary.20250503T140622 (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.12-canary.20250502T140709"
+Bun.version; // => "1.2.12-canary.20250503T140622"
 ```
 
 ---

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.12-canary.20250502T140709"
+$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.12-canary.20250503T140622"
 ```
 
 ```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.12-canary.20250502T140709`.
+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.12-canary.20250503T140622`.
 
 ```sh
-$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.12-canary.20250502T140709"
+$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.12-canary.20250503T140622"
 ```
 
 ### 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.12-canary.20250502T140709"
+$ iex "& {$(irm https://bun.sh/install.ps1)} -Version 1.2.12-canary.20250503T140622"
 ```
 
 ## Downloading Bun binaries directly

package/docs/project/asan.md

@@ -0,0 +1,124 @@
+# ASAN Builds for Bun
+
+This document explains how to use and configure ASAN (Address Sanitizer) builds for Bun.
+
+> **Note**: ASAN builds are available in CI for Linux and are configured to help identify memory issues in release builds.
+
+## What is ASAN?
+
+ASAN (Address Sanitizer) is a memory error detector for C/C++ and Zig code. It can detect:
+
+- Use-after-free
+- Heap buffer overflow
+- Stack buffer overflow
+- Global buffer overflow
+- Use-after-return
+- Use-after-scope
+- Initialization order bugs
+- Memory leaks
+
+## ASAN Builds in CI
+
+Bun CI includes ASAN builds to catch memory errors. These builds are configured with:
+
+- Release optimizations for speed
+- ASAN instrumentation for memory error detection
+- Assertions enabled for both Bun and WebKit
+
+The CI pipeline automatically:
+
+- Builds a special ASAN-enabled release build for Linux
+- Runs all tests to thoroughly check for memory issues
+- Uses reduced parallelism to avoid memory pressure during testing
+- Applies suppressions for known false positives
+- Extends test timeouts to accommodate ASAN overhead
+- Includes ASAN builds in release artifacts for debugging purposes
+
+## Local ASAN Builds
+
+To build Bun with ASAN locally, you can use the npm script:
+
+```bash
+# Build a release build with ASAN and assertions (recommended)
+bun run build:asan
+```
+
+Or manually with CMake:
+
+```bash
+# Debug build with ASAN
+cmake -B build -DCMAKE_BUILD_TYPE=Debug -DENABLE_ASAN=ON
+
+# Release build with ASAN
+cmake -B build -DCMAKE_BUILD_TYPE=Release -DENABLE_ASAN=ON
+
+# Release build with ASAN and assertions
+cmake -B build -DCMAKE_BUILD_TYPE=Release -DENABLE_ASAN=ON -DENABLE_ASSERTIONS=ON
+```
+
+## Running with ASAN
+
+When running an ASAN build, you can configure behavior with environment variables:
+
+```bash
+# Basic ASAN options - leak detection disabled (recommended)
+ASAN_OPTIONS=detect_leaks=0:halt_on_error=0:detect_odr_violation=0 ./build/bun-asan
+
+# If you really need leak detection (will produce A LOT of noise)
+# ASAN_OPTIONS=detect_leaks=1:leak_check_at_exit=1:halt_on_error=0 ./build/bun-asan
+# LSAN_OPTIONS=suppressions=lsan.supp:print_suppressions=1 ./build/bun-asan
+```
+
+> **Warning**: Enabling leak detection will generate excessive noise due to deliberately uncollected memory in WebKit and other components. It's recommended to keep leak detection disabled and focus on other memory errors like use-after-free, buffer overflows, etc.
+
+## Other Memory Error Types
+
+ASAN can detect several types of memory errors:
+
+1. **Use-after-free**: When a program continues to use memory after it's been freed
+2. **Buffer overflow**: When a program writes beyond the bounds of allocated memory
+3. **Stack overflow**: When a function's stack usage exceeds available space
+4. **Memory corruption**: Often caused by writing to invalid memory locations
+5. **Use-after-return**: When a function returns a pointer to stack memory that's no longer valid
+
+When an error is detected, ASAN will print a helpful report showing:
+
+- The type of error
+- The memory address where the error occurred
+- A stack trace showing the code path that led to the error
+- Information about the memory allocation/deallocation (if relevant)
+
+Example error output:
+
+```
+==1234==ERROR: AddressSanitizer: heap-use-after-free on address 0x614000000044 at pc 0x55d8e2ac1f14...
+READ of size 4 at 0x614000000044 thread T0
+    #0 0x55d8e2ac1f14 in main example.c:10
+    #1 0x7f91e6f5e0b2 in __libc_start_main...
+```
+
+## Understanding ASAN Reports
+
+ASAN reports contain detailed information about memory errors:
+
+```
+==12345==ERROR: AddressSanitizer: heap-use-after-free on address 0x7f7ddab8c084
+READ of size 4 at 0x7f7ddab8c084 thread T0
+    #0 0x43b45a in Function source/file.cpp:123:45
+    #1 0x44af90 in AnotherFunction source/file.cpp:234:10
+    ...
+```
+
+Key components of the report:
+
+- Error type (heap-use-after-free, heap-buffer-overflow, etc.)
+- Operation (READ/WRITE) and size
+- Stack trace showing where the error occurred
+- Information about the allocated/freed memory
+
+## Best Practices
+
+1. Run tests with ASAN builds regularly
+2. Add suppressions only for well-understood false positives
+3. Fix real issues promptly - ASAN errors indicate real problems
+4. Consider using ASAN in debug builds during development

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.12-canary.20250502T140709" -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.12-canary.20250503T140622" -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.12-canary.20250502T140709
+[fetch] > User-Agent: Bun/1.2.12-canary.20250503T140622
 [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.12-canary.20250502T140709
+[fetch] > User-Agent: Bun/1.2.12-canary.20250503T140622
 [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.12-canary.20250502T140709
+bun test v1.2.12-canary.20250503T140622
 
 dom.test.ts:
 ✓ dom test [0.82ms]

package/package.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.2.12-canary.20250502T140709",
+  "version": "1.2.12-canary.20250503T140622",
   "name": "bun-types",
   "license": "MIT",
   "types": "./index.d.ts",