Update js_lexer.zig

.buildkite/ci.mjs

@@ -323,7 +323,6 @@ function getCppAgent(platform, options) {
  */
 function getZigAgent(platform, options) {
   const { arch } = platform;
-
   return {
     queue: "build-zig",
   };
@@ -384,22 +383,14 @@ function getBuildEnv(target, options) {
   const { canary } = options;
   const revision = typeof canary === "number" ? canary : 1;
 
-  const isMusl = abi === "musl";
-
-  let CMAKE_BUILD_TYPE = release ? "Release" : profile === "debug" ? "Debug" : "RelWithDebInfo";
-  if (isMusl && release) {
-    CMAKE_BUILD_TYPE = "MinSizeRel";
-  }
-
   return {
-    CMAKE_BUILD_TYPE,
+    CMAKE_BUILD_TYPE: release ? "Release" : profile === "debug" ? "Debug" : "RelWithDebInfo",
     ENABLE_BASELINE: baseline ? "ON" : "OFF",
     ENABLE_CANARY: revision > 0 ? "ON" : "OFF",
     CANARY_REVISION: revision,
     ENABLE_ASSERTIONS: release ? "OFF" : "ON",
     ENABLE_LOGS: release ? "OFF" : "ON",
-    ABI: isMusl ? "musl" : undefined,
-    CMAKE_TLS_VERIFY: "0",
+    ABI: abi === "musl" ? "musl" : undefined,
   };
 }
 
@@ -471,7 +462,7 @@ function getBuildZigStep(platform, options) {
     cancel_on_build_failing: isMergeQueue(),
     env: getBuildEnv(platform, options),
     command: `bun run build:ci --target bun-zig --toolchain ${toolchain}`,
-    timeout_in_minutes: 35,
+    timeout_in_minutes: 25,
   };
 }
 
@@ -628,21 +619,6 @@ function getReleaseStep(buildPlatforms, options) {
   };
 }
 
-/**
- * @returns {Step}
- */
-function getBenchmarkStep() {
-  return {
-    key: "benchmark",
-    label: "📊",
-    agents: {
-      queue: "build-zig",
-    },
-    command: "bun .buildkite/scripts/upload-benchmark.ts",
-    depends_on: [`linux-x64-build-bun`],
-  };
-}
-
 /**
  * @typedef {Object} Pipeline
  * @property {Step[]} [steps]
@@ -1121,8 +1097,6 @@ async function getPipeline(options = {}) {
     steps.push(getReleaseStep(buildPlatforms, options));
   }
 
-  steps.push(getBenchmarkStep());
-
   /** @type {Map<string, GroupStep>} */
   const stepsByGroup = new Map();
 

.buildkite/scripts/upload-benchmark.ts

@@ -1,7 +0,0 @@
-import { getCommit, getSecret } from "../../scripts/utils.mjs";
-
-console.log("Submitting...");
-const response = await fetch(getSecret("BENCHMARK_URL") + "?tag=_&commit=" + getCommit() + "&artifact_url=_", {
-  method: "POST",
-});
-console.log("Got status " + response.status);

.buildkite/scripts/upload-release.sh

@@ -158,36 +158,25 @@ function upload_s3_file() {
   run_command aws --endpoint-url="$AWS_ENDPOINT" s3 cp "$file" "s3://$AWS_BUCKET/$folder/$file"
 }
 
-function send_discord_announcement() {
-  local value=$(buildkite-agent secret get "BUN_ANNOUNCE_CANARY_WEBHOOK_URL")
-  if [ -z "$value" ]; then
-    echo "warn: BUN_ANNOUNCE_CANARY_WEBHOOK_URL not set, skipping Discord announcement"
+function send_bench_webhook() {
+  if [ -z "$BENCHMARK_URL" ]; then
+    echo "error: \$BENCHMARK_URL is not set"
+    # exit 1 # TODO: this isn't live yet
     return
   fi
 
-  local version="$1"
+  local tag="$1"
   local commit="$BUILDKITE_COMMIT"
-  local short_sha="${commit:0:7}"
-  local commit_url="https://github.com/oven-sh/bun/commit/$commit"
+  local artifact_path="${commit}"
 
-  if [ "$version" == "canary" ]; then
-    local json_payload=$(cat <<EOF
-{
-  "embeds": [{
-    "title": "New Bun Canary now available",
-    "description": "A new canary build of Bun has been automatically uploaded ([${short_sha}](${commit_url})). To upgrade, run:\n\n\`\`\`shell\nbun upgrade --canary\n\`\`\`\nCommit: \`${commit}\`",
-    "color": 16023551,
-    "timestamp": "$(date -u +%Y-%m-%dT%H:%M:%SZ)"
-  }]
-}
-EOF
-)
-    
-    curl -H "Content-Type: application/json" \
-         -d "$json_payload" \
-         -sf \
-         "$value" >/dev/null
+  if [ "$tag" == "canary" ]; then
+    artifact_path="${commit}-canary"
   fi
+
+  local artifact_url="https://pub-5e11e972747a44bf9aaf9394f185a982.r2.dev/releases/$artifact_path/bun-linux-x64.zip"
+  local webhook_url="$BENCHMARK_URL?tag=$tag&commit=$commit&artifact_url=$artifact_url"
+  
+  curl -X POST "$webhook_url"
 }
 
 function create_release() {
@@ -238,7 +227,7 @@ function create_release() {
 
   update_github_release "$tag"
   create_sentry_release "$tag"
-  send_discord_announcement "$tag"
+  send_bench_webhook "$tag"
 }
 
 function assert_canary() {

.clangd

@@ -6,3 +6,6 @@ CompileFlags:
 
 Diagnostics:
   UnusedIncludes: None
+
+HeaderInsertion:
+  IncludeBlocks: Preserve # Do not auto-include headers.

.cursor/rules/building-bun.mdc

@@ -1,27 +0,0 @@
----
-description: How to build Bun
-globs: 
----
-# How to build Bun
-
-## CMake
-
-Bun is built using CMake, which you can find in `CMakeLists.txt` and in the `cmake/` directory.
-
-* `CMakeLists.txt`
-* `cmake/`
-  * `Globals.cmake` - macros and functions used by all the other files
-  * `Options.cmake` - build options for configuring the build (e.g. debug/release mode)
-  * `CompilerFlags.cmake` - compiler and linker flags used by all the targets
-  * `tools/` - setup scripts for various build tools (e.g. llvm, zig, webkit, rust, etc.)
-  * `targets/` - targets for bun and its dependencies (e.g. brotli, boringssl, libuv, etc.)
-
-## How to
-
-There are `package.json` scripts that make it easy to build Bun without calling CMake directly, for example:
-
-```sh
-bun run build # builds a debug build: `build/debug/bun-debug`
-bun run build:release # builds a release build: `build/release/bun`
-bun run build:assert # builds a release build with debug assertions: `build/assert/bun`
-```

.cursor/rules/dev-server-tests.mdc

@@ -1,139 +0,0 @@
----
-description: Writing HMR/Dev Server tests
-globs: test/bake/*
----
-
-# Writing HMR/Dev Server tests
-
-Dev server tests validate that hot-reloading is robust, correct, and reliable. Remember to write thorough, yet concise tests.
-
-## File Structure
-
-- `test/bake/bake-harness.ts` - shared utilities and test harness
-  - primary test functions `devTest` / `prodTest` / `devAndProductionTest`
-  - class `Dev` (controls subprocess for dev server)
-  - class `Client` (controls a happy-dom subprocess for having the page open)
-  - more helpers
-- `test/bake/client-fixture.mjs` - subprocess for what `Client` controls. it loads a page and uses IPC to query parts of the page, run javascript, and much more.
-- `test/bake/dev/*.test.ts` - these call `devTest` to test dev server and hot reloading
-- `test/bake/dev-and-prod.ts` - these use `devAndProductionTest` to run the same test on dev and production mode. these tests cannot really test hot reloading for obvious reasons.
-
-## Categories
-
-bundle.test.ts - Bundle tests are tests concerning bundling bugs that only occur in DevServer.
-css.test.ts - CSS tests concern bundling bugs with CSS files
-plugins.test.ts - Plugin tests concern plugins in development mode.
-ecosystem.test.ts - These tests involve ensuring certain libraries are correct. It is preferred to test more concrete bugs than testing entire packages.
-esm.test.ts - ESM tests are about various esm features in development mode.
-html.test.ts - HTML tests are tests relating to HTML files themselves.
-react-spa.test.ts - Tests relating to React, our react-refresh transform, and basic server component transforms.
-sourcemap.test.ts - Tests verifying source-maps are correct.
-
-## `devTest` Basics
-
-A test takes in two primary inputs: `files` and `async test(dev) {`
-
-```ts
-import { devTest, emptyHtmlFile } from "../bake-harness";
-
-devTest("html file is watched", {
-  files: {
-    "index.html": emptyHtmlFile({
-      scripts: ["/script.ts"],
-      body: "<h1>Hello</h1>",
-    }),
-    "script.ts": `
-      console.log("hello");
-    `,
-  },
-  async test(dev) {
-    await dev.fetch("/").expect.toInclude("<h1>Hello</h1>");
-    await dev.fetch("/").expect.toInclude("<h1>Hello</h1>");
-    await dev.patch("index.html", {
-      find: "Hello",
-      replace: "World",
-    });
-    await dev.fetch("/").expect.toInclude("<h1>World</h1>");
-
-    // Works
-    await using c = await dev.client("/");
-    await c.expectMessage("hello");
-
-    // Editing HTML reloads
-    await c.expectReload(async () => {
-      await dev.patch("index.html", {
-        find: "World",
-        replace: "Hello",
-      });
-      await dev.fetch("/").expect.toInclude("<h1>Hello</h1>");
-    });
-    await c.expectMessage("hello");
-
-    await c.expectReload(async () => {
-      await dev.patch("index.html", {
-        find: "Hello",
-        replace: "Bar",
-      });
-      await dev.fetch("/").expect.toInclude("<h1>Bar</h1>");
-    });
-    await c.expectMessage("hello");
-
-    await c.expectReload(async () => {
-      await dev.patch("script.ts", {
-        find: "hello",
-        replace: "world",
-      });
-    });
-    await c.expectMessage("world");
-  },
-});
-```
-
-`files` holds the initial state, and the callback runs with the server running. `dev.fetch()` runs HTTP requests, while `dev.client()` opens a browser instance to the code.
-
-Functions `dev.write` and `dev.patch` and `dev.delete` mutate the filesystem. Do not use `node:fs` APIs, as the dev server ones are hooked to wait for hot-reload, and all connected clients to recieve changes.
-
-When a change performs a hard-reload, that must be explicitly annotated with `expectReload`. This tells `client-fixture.mjs` that the test is meant to reload the page once; All other hard reloads automatically fail the test.
-
-Client's have `console.log` instrumented, so that any unasserted logs fail the test. This makes it more obvious when an extra reload or re-evaluation. Messages are awaited via `c.expectMessage("log")` or with multiple arguments if there are multiple logs.
-
-## Testing for bundling errors
-
-By default, a client opening a page to an error will fail the test. This makes testing errors explicit.
-
-```ts
-devTest("import then create", {
-  files: {
-    "index.html": `
-      <!DOCTYPE html>
-      <html>
-      <head></head>
-      <body>
-        <script type="module" src="/script.ts"></script>
-      </body>
-      </html>
-    `,
-    "script.ts": `
-      import data from "./data";
-      console.log(data);
-    `,
-  },
-  async test(dev) {
-    const c = await dev.client("/", {
-      errors: ['script.ts:1:18: error: Could not resolve: "./data"'],
-    });
-    await c.expectReload(async () => {
-      await dev.write("data.ts", "export default 'data';");
-    });
-    await c.expectMessage("data");
-  },
-});
-```
-
-Many functions take an options value to allow specifying it will produce errors. For example, this delete is going to cause a resolution failure.
-
-```ts
-await dev.delete("other.ts", {
-  errors: ['index.ts:1:16: error: Could not resolve: "./other"'],
-});
-```

.cursor/rules/javascriptcore-class.mdc

@@ -268,16 +268,16 @@ If there's a class, prototype, and constructor:
 2. Initialize the class structure in [ZigGlobalObject.cpp](mdc:src/bun.js/bindings/ZigGlobalObject.cpp) in `void GlobalObject::finishCreation(VM& vm)`
 3. Visit the class structure in visitChildren in [ZigGlobalObject.cpp](mdc:src/bun.js/bindings/ZigGlobalObject.cpp) in `void GlobalObject::visitChildrenImpl`
 
-```c++#ZigGlobalObject.cpp
-void GlobalObject::finishCreation(VM& vm) {
-// ...
+```c++
+
     m_JSStatsBigIntClassStructure.initLater(
         [](LazyClassStructure::Initializer& init) {
-            // Call the function to initialize our class structure.
             Bun::initJSBigIntStatsClassStructure(init);
         });
 ```
 
+If there's only a class, use `JSC::LazyProperty<JSGlobalObject, Structure>` instead of `JSC::LazyClassStructure`. 
+
 Then, implement the function that creates the structure:
 ```c++
 void setupX509CertificateClassStructure(LazyClassStructure::Initializer& init)
@@ -296,36 +296,6 @@ void setupX509CertificateClassStructure(LazyClassStructure::Initializer& init)
 }
 ```
 
-If there's only a class, use `JSC::LazyProperty<JSGlobalObject, Structure>` instead of `JSC::LazyClassStructure`:
-
-1. Add the `JSC::LazyProperty<JSGlobalObject, Structure>` to @ZigGlobalObject.h
-2. Initialize the class structure in @ZigGlobalObject.cpp in `void GlobalObject::finishCreation(VM& vm)`
-3. Visit the lazy property in visitChildren in @ZigGlobalObject.cpp in `void GlobalObject::visitChildrenImpl`
-void GlobalObject::finishCreation(VM& vm) {
-// ...
-   this.m_myLazyProperty.initLater([](const JSC::LazyProperty<JSC::JSGlobalObject, JSC::Structure>::Initializer& init) {
-        init.set(Bun::initMyStructure(init.vm, reinterpret_cast<Zig::GlobalObject*>(init.owner)));
-    });
-```
-
-Then, implement the function that creates the structure:
-```c++
-Structure* setupX509CertificateStructure(JSC::VM &vm, Zig::GlobalObject* globalObject)
-{
-    // If there is a prototype:
-    auto* prototypeStructure = JSX509CertificatePrototype::createStructure(init.vm, init.global, init.global->objectPrototype());
-    auto* prototype = JSX509CertificatePrototype::create(init.vm, init.global, prototypeStructure);
-
-    // If there is no prototype or it only has 
-
-    auto* structure = JSX509Certificate::createStructure(init.vm, init.global, prototype);
-    init.setPrototype(prototype);
-    init.setStructure(structure);
-    init.setConstructor(constructor);
-}
-```
-
-
 Then, use the structure by calling `globalObject.m_myStructureName.get(globalObject)`
 
 ```C++

.cursor/rules/writing-tests.mdc

@@ -1,91 +0,0 @@
----
-description: Writing tests for Bun
-globs: 
----
-# Writing tests for Bun
-
-## Where tests are found
-
-You'll find all of Bun's tests in the `test/` directory.
-
-* `test/`
-  * `cli/` - CLI command tests, like `bun install` or `bun init`
-  * `js/` - JavaScript & TypeScript tests
-    * `bun/` - `Bun` APIs tests, seperated by category, for example: `glob/` for `Bun.Glob` tests
-    * `node/` - Node.js module tests, seperated by module, for example: `assert/` for `node:assert` tests
-      * `test/` - Vendored Node.js tests, taken from the Node.js repository (does not conform to Bun's test style)
-    * `web/` - Web API tests, seperated by category, for example: `fetch/` for `Request` and `Response` tests
-    * `third_party/` - npm package tests, to validate that basic usage works in Bun
-  * `napi/` - N-API tests
-  * `v8/` - V8 C++ API tests
-  * `bundler/` - Bundler, transpiler, CSS, and `bun build` tests
-  * `regression/issue/[number]` - Regression tests, always make one when fixing a particular issue
-
-## How tests are written
-
-Bun's tests are written as JavaScript and TypeScript files with the Jest-style APIs, like `test`, `describe`, and `expect`. They are tested using Bun's own test runner, `bun test`. 
-
-```js
-import { describe, test, expect } from "bun:test";
-import assert, { AssertionError } from "assert";
-
-describe("assert(expr)", () => {
-  test.each([true, 1, "foo"])(`assert(%p) does not throw`, expr => {
-    expect(() => assert(expr)).not.toThrow();
-  });
-
-  test.each([false, 0, "", null, undefined])(`assert(%p) throws`, expr => {
-    expect(() => assert(expr)).toThrow(AssertionError);
-  });
-});
-```
-
-## Testing conventions
-
-* See `test/harness.ts` for common test utilities and helpers
-* Be rigorous and test for edge-cases and unexpected inputs
-* Use data-driven tests, e.g. `test.each`, to reduce boilerplate when possible
-* When you need to test Bun as a CLI, use the following pattern:
-
-```js
-import { test, expect } from "bun:test";
-import { spawn } from "bun";
-import { bunExe, bunEnv } from "harness";
-
-test("bun --version", async () => {
-  const { exited, stdout: stdoutStream, stderr: stderrStream } = spawn({
-    cmd: [bunExe(), "--version"],
-    env: bunEnv,
-    stdout: "pipe",
-    stderr: "pipe",
-  });
-  const [ exitCode, stdout, stderr ] = await Promise.all([
-    exited,
-    new Response(stdoutStream).text(),
-    new Response(stderrStream).text(),
-  ]);
-  expect({ exitCode, stdout, stderr }).toMatchObject({
-    exitCode: 0,
-    stdout: expect.stringContaining(Bun.version),
-    stderr: "",
-  });
-});
-```
-
-## Before writing a test
-
-* If you are fixing a bug, write the test first and make sure it fails (as expected) with the canary version of Bun
-* If you are fixing a Node.js compatibility bug, create a throw-away snippet of code and test that it works as you expect in Node.js, then that it fails (as expected) with the canary version of Bun
-* When the expected behaviour is ambigious, defer to matching what happens in Node.js
-* Always attempt to find related tests in an existing test file before creating a new test file
-
-
-
-
-
-
-
-
-
-
-

.github/workflows/packages-ci.yml

@@ -1,55 +0,0 @@
-name: Packages CI
-
-on:
-  push:
-    branches:
-      - main
-    paths:
-      - "packages/**"
-      - .prettierrc
-      - .prettierignore
-      - tsconfig.json
-      - oxlint.json
-      - "!**/*.md"
-  pull_request:
-    branches:
-      - main
-    paths:
-      - "packages/**"
-      - .prettierrc
-      - .prettierignore
-      - tsconfig.json
-      - oxlint.json
-      - "!**/*.md"
-
-env:
-  BUN_VERSION: "canary"
-
-jobs:
-  bun-plugin-svelte:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - name: Setup Bun
-        uses: ./.github/actions/setup-bun
-        with:
-          bun-version: ${{ env.BUN_VERSION }}
-
-      - name: Install dependencies
-        run: |
-          bun install
-          pushd ./packages/bun-plugin-svelte && bun install
-
-      - name: Lint
-        run: |
-          bunx oxlint@0.15 --format github --deny-warnings
-          bunx prettier --config ../../.prettierrc --check .
-        working-directory: ./packages/bun-plugin-svelte
-
-      - name: Check types
-        run: bun check:types
-        working-directory: ./packages/bun-plugin-svelte
-
-      - name: Test
-        run: bun test
-        working-directory: ./packages/bun-plugin-svelte

.github/workflows/release.yml

@@ -70,7 +70,7 @@ jobs:
       - name: Setup Bun
         uses: ./.github/actions/setup-bun
         with:
-          bun-version: "1.2.3"
+          bun-version: "1.2.0"
       - name: Install Dependencies
         run: bun install
       - name: Sign Release
@@ -98,7 +98,7 @@ jobs:
       - name: Setup Bun
         uses: ./.github/actions/setup-bun
         with:
-          bun-version: "1.2.3"
+          bun-version: "1.2.0"
       - name: Install Dependencies
         run: bun install
       - name: Release
@@ -127,7 +127,7 @@ jobs:
         if: ${{ env.BUN_VERSION != 'canary' }}
         uses: ./.github/actions/setup-bun
         with:
-          bun-version: "1.2.3"
+          bun-version: "1.2.0"
       - name: Setup Bun
         if: ${{ env.BUN_VERSION == 'canary' }}
         uses: ./.github/actions/setup-bun
@@ -167,16 +167,12 @@ jobs:
     permissions:
       contents: read
     steps:
-      - name: Checkout (DefinitelyTyped)
+      - name: Checkout
         uses: actions/checkout@v4
         with:
           repository: DefinitelyTyped/DefinitelyTyped
-      - name: Checkout (bun)
-        uses: actions/checkout@v4
-        with:
-          path: bun
       - name: Setup Bun
-        uses: ./bun/.github/actions/setup-bun
+        uses: ./.github/actions/setup-bun
         with:
           bun-version: "1.2.0"
       - id: bun-version
@@ -231,7 +227,7 @@ jobs:
       - name: Checkout
         uses: actions/checkout@v4
       - name: Setup Docker emulator
-        uses: docker/setup-qemu-action@v3
+        uses: docker/setup-qemu-action@v2
       - id: buildx
         name: Setup Docker buildx
         uses: docker/setup-buildx-action@v3
@@ -239,7 +235,7 @@ jobs:
           platforms: linux/amd64,linux/arm64
       - id: metadata
         name: Setup Docker metadata
-        uses: docker/metadata-action@v5
+        uses: docker/metadata-action@v4
         with:
           images: oven/bun
           flavor: |
@@ -256,7 +252,7 @@ jobs:
           username: ${{ secrets.DOCKER_USERNAME }}
           password: ${{ secrets.DOCKER_PASSWORD }}
       - name: Push to Docker
-        uses: docker/build-push-action@v6
+        uses: docker/build-push-action@v5
         with:
           context: ./dockerhub/${{ matrix.dir || matrix.variant }}
           platforms: linux/amd64,linux/arm64

.github/workflows/update-root-certs.yml

@@ -1,82 +0,0 @@
-name: Daily Root Certs Update Check
-
-on:
-  schedule:
-    - cron: "0 0 * * *" # Runs at 00:00 UTC every day
-  workflow_dispatch: # Allows manual trigger
-
-jobs:
-  check-and-update:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      pull-requests: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Setup Bun
-        uses: oven-sh/setup-bun@v1
-        with:
-          bun-version: latest
-
-      - name: Generate root certs and capture output
-        id: generate-certs
-        run: |
-          cd packages/bun-usockets/
-          OUTPUT=$(bun generate-root-certs.mjs -v)
-          echo "cert_output<<EOF" >> $GITHUB_ENV
-          echo "$OUTPUT" >> $GITHUB_ENV
-          echo "EOF" >> $GITHUB_ENV
-
-      - name: Check for changes and stage files
-        id: check-changes
-        run: |
-          if [[ -n "$(git status --porcelain)" ]]; then
-            echo "Found changes, staging modified files..."
-            git config --global user.name "github-actions[bot]"
-            git config --global user.email "github-actions[bot]@users.noreply.github.com"
-            
-            # Get list of modified files and add them
-            git status --porcelain | while read -r status file; do
-              # Remove leading status and whitespace
-              file=$(echo "$file" | sed 's/^.* //')
-              echo "Adding changed file: $file"
-              git add "$file"
-            done
-            
-            echo "changes=true" >> $GITHUB_OUTPUT
-            
-            # Store the list of changed files
-            CHANGED_FILES=$(git status --porcelain)
-            echo "changed_files<<EOF" >> $GITHUB_ENV
-            echo "$CHANGED_FILES" >> $GITHUB_ENV
-            echo "EOF" >> $GITHUB_ENV
-          else
-            echo "No changes detected"
-            echo "changes=false" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Create Pull Request
-        if: steps.check-changes.outputs.changes == 'true'
-        uses: peter-evans/create-pull-request@v5
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          commit-message: "update(root_certs): Update root certificates $(date +'%Y-%m-%d')"
-          title: "update(root_certs) $(date +'%Y-%m-%d')"
-          body: |
-            Automated root certificates update
-
-            ${{ env.cert_output }}
-
-            ## Changed Files:
-            ```
-            ${{ env.changed_files }}
-            ```
-          branch: certs/update-root-certs-${{ github.run_number }}
-          base: main
-          delete-branch: true
-          labels:
-            - "automation"
-            - "root-certs"

.github/workflows/update-sqlite3.yml

@@ -55,7 +55,7 @@ jobs:
 
           # Convert numeric version to semantic version for display
           LATEST_MAJOR=$((10#$LATEST_VERSION_NUM / 1000000))
-          LATEST_MINOR=$((($LATEST_VERSION_NUM / 10000) % 100))
+          LATEST_MINOR=$((($LATEST_VERSION_NUM / 1000) % 1000))
           LATEST_PATCH=$((10#$LATEST_VERSION_NUM % 1000))
           LATEST_VERSION="$LATEST_MAJOR.$LATEST_MINOR.$LATEST_PATCH"
 

.gitignore

@@ -16,7 +16,6 @@
 .vscode/clang*
 .vscode/cpp*
 .zig-cache
-.bake-debug
 *.a
 *.bc
 *.big
@@ -181,5 +180,3 @@ tmp
 .buildkite/ci.yml
 *.sock
 scratch*.{js,ts,tsx,cjs,mjs}
-
-*.bun-build

.vscode/launch.json

@@ -1131,13 +1131,6 @@
       // Don't pause when the GC runs while the debugger is open.
       "postRunCommands": ["command source '${workspaceFolder}/misctools/lldb/lldb_commands'"],
     },
-    {
-      "type": "midas-rr",
-      "request": "attach",
-      "name": "rr",
-      "trace": "Off",
-      "setupCommands": ["handle SIGPWR nostop noprint pass"],
-    },
   ],
   "inputs": [
     {

.vscode/settings.json

@@ -36,7 +36,6 @@
   // "zig.buildOnSave": true,
   "zig.buildFilePath": "${workspaceFolder}/build.zig",
   "zig.path": "${workspaceFolder}/vendor/zig/zig.exe",
-  "zig.zls.path": "${workspaceFolder}/vendor/zig/zls.exe",
   "zig.formattingProvider": "zls",
   "zig.zls.enableInlayHints": false,
   "[zig]": {
@@ -64,7 +63,6 @@
     "editor.tabSize": 4,
     "editor.defaultFormatter": "xaver.clang-format",
   },
-  "clangd.arguments": ["--header-insertion=never"],
 
   // JavaScript
   "prettier.enable": true,
@@ -141,11 +139,9 @@
     "packages/bun-uws/fuzzing": true,
   },
   "files.associations": {
-    "*.css": "tailwindcss",
     "*.idl": "cpp",
     "*.mdc": "markdown",
     "array": "cpp",
-    "ios": "cpp",
   },
   "C_Cpp.files.exclude": {
     "**/.vscode": true,

CMakeLists.txt

@@ -12,12 +12,6 @@ list(APPEND CMAKE_MODULE_PATH
 include(Policies)
 include(Globals)
 
-if (CMAKE_HOST_WIN32)
-  # Workaround for TLS certificate verification issue on Windows when downloading from GitHub
-  # Remove this once we've bumped the CI machines build image
-  set(CMAKE_TLS_VERIFY 0)
-endif()
-
 # --- Compilers ---
 
 if(CMAKE_HOST_APPLE)

CONTRIBUTING.md

@@ -67,7 +67,7 @@ $ wget https://apt.llvm.org/llvm.sh -O - | sudo bash -s -- 18 all
 ```
 
 ```bash#Arch
-$ sudo pacman -S llvm clang18 lld
+$ sudo pacman -S llvm clang lld
 ```
 
 ```bash#Fedora

LATEST

@@ -1 +1 @@
-1.2.4
+1.2.2

Makefile

@@ -1154,7 +1154,7 @@ jsc-copy-headers:
 	cp $(WEBKIT_DIR)/Source/JavaScriptCore/bytecode/StubInfoSummary.h $(WEBKIT_RELEASE_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/StubInfoSummary.h
 	cp $(WEBKIT_DIR)/Source/JavaScriptCore/runtime/CommonSlowPaths.h $(WEBKIT_RELEASE_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/CommonSlowPaths.h
 	cp $(WEBKIT_DIR)/Source/JavaScriptCore/runtime/DirectArguments.h $(WEBKIT_RELEASE_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/DirectArguments.h
-	cp $(WEBKIT_DIR)/Source/JavaScriptCore/runtime/GenericArgumentsImpl.h $(WEBKIT_RELEASE_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/GenericArgumentsImpl.h
+	cp $(WEBKIT_DIR)/Source/JavaScriptCore/runtime/GenericArguments.h $(WEBKIT_RELEASE_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/GenericArguments.h
 	cp $(WEBKIT_DIR)/Source/JavaScriptCore/runtime/SamplingProfiler.h $(WEBKIT_RELEASE_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/SamplingProfiler.h
 	cp $(WEBKIT_DIR)/Source/JavaScriptCore/runtime/ScopedArguments.h $(WEBKIT_RELEASE_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/ScopedArguments.h
 	cp $(WEBKIT_DIR)/Source/JavaScriptCore/runtime/JSLexicalEnvironment.h $(WEBKIT_RELEASE_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/JSLexicalEnvironment.h
@@ -1205,7 +1205,7 @@ jsc-copy-headers-debug:
 	cp $(WEBKIT_DIR)/Source/JavaScriptCore/bytecode/StubInfoSummary.h $(WEBKIT_DEBUG_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/StubInfoSummary.h
 	cp $(WEBKIT_DIR)/Source/JavaScriptCore/runtime/CommonSlowPaths.h $(WEBKIT_DEBUG_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/CommonSlowPaths.h
 	cp $(WEBKIT_DIR)/Source/JavaScriptCore/runtime/DirectArguments.h $(WEBKIT_DEBUG_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/DirectArguments.h
-	cp $(WEBKIT_DIR)/Source/JavaScriptCore/runtime/GenericArgumentsImpl.h $(WEBKIT_DEBUG_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/GenericArgumentsImpl.h
+	cp $(WEBKIT_DIR)/Source/JavaScriptCore/runtime/GenericArguments.h $(WEBKIT_DEBUG_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/GenericArguments.h
 	cp $(WEBKIT_DIR)/Source/JavaScriptCore/runtime/SamplingProfiler.h $(WEBKIT_DEBUG_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/SamplingProfiler.h
 	cp $(WEBKIT_DIR)/Source/JavaScriptCore/runtime/ScopedArguments.h $(WEBKIT_DEBUG_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/ScopedArguments.h
 	cp $(WEBKIT_DIR)/Source/JavaScriptCore/runtime/JSLexicalEnvironment.h $(WEBKIT_DEBUG_DIR)/JavaScriptCore/PrivateHeaders/JavaScriptCore/JSLexicalEnvironment.h

bench/glob/match.mjs

@@ -1,27 +1,19 @@
-import { Glob } from "bun";
+import micromatch from "micromatch";
 import { bench, run } from "../runner.mjs";
 
+const Glob = typeof Bun !== "undefined" ? Bun.Glob : undefined;
+const doMatch = typeof Bun === "undefined" ? micromatch.isMatch : (a, b) => new Glob(b).match(a);
 
-function benchPattern(name, glob, pattern) {
-    bench(name, () => {
-        new Glob(glob).match(pattern);
-    })
-}
-
-benchPattern("max-depth" , "1{2,3{4,5{6,7{8,9{a,b{c,d{e,f{g,h{i,j{k,l}}}}}}}}}}m", "13579bdfhjlm");
-benchPattern("non-ascii", "😎/¢£.{ts,tsx,js,jsx}", "😎/¢£.jsx");
-benchPattern("utf8", "フォルダ/**/*", "フォルダ/aaa.js");
-benchPattern("non-ascii+max-depth" , "1{2,3{4,5{6,7{8,😎{a,b{c,d{e,f{g,h{i,j{k,l}}}}}}}}}}m", "1357😎bdfhjlm");
-benchPattern("pretty-average", "test/{foo/**,bar}/baz", "test/bar/baz");
-benchPattern("pretty-average-2", "a/**/c/*.md", "a/bb.bb/aa/b.b/aa/c/xyz.md");
-benchPattern("pretty-average-3", "a/b/**/c{d,e}/**/xyz.md", "a/b/cd/xyz.md");
-benchPattern("pretty-average-4", "foo/bar/**/one/**/*.*", "foo/bar/baz/one/two/three/image.png");
-benchPattern("long-pretty-average", "some/**/needle.{js,tsx,mdx,ts,jsx,txt}", "some/a/bigger/path/to/the/crazy/needle.txt");
-benchPattern("brackets-lots", "f[^eiu][^eiu][^eiu][^eiu][^eiu]r", "foo-bar");
+bench((Glob ? "Bun.Glob - " : "micromatch - ") + "**/*.js", () => {
+  doMatch("foo/bar.js", "**/*.js");
+});
 
+bench((Glob ? "Bun.Glob - " : "micromatch - ") + "*.js", () => {
+  doMatch("bar.js", "*.js");
+});
 
 await run({
-    min_max: true,
-    percentiles: true,
-    avg: true,
-})
+  avg: true,
+  min_max: true,
+  percentiles: true,
+});

bench/glob/micromatch.mjs

@@ -1,19 +0,0 @@
-import micromatch from "micromatch";
-import { bench, run } from "../runner.mjs";
-
-const Glob = typeof Bun !== "undefined" ? Bun.Glob : undefined;
-const doMatch = typeof Bun === "undefined" ? micromatch.isMatch : (a, b) => new Glob(b).match(a);
-
-bench((Glob ? "Bun.Glob - " : "micromatch - ") + "**/*.js", () => {
-  doMatch("foo/bar.js", "**/*.js");
-});
-
-bench((Glob ? "Bun.Glob - " : "micromatch - ") + "*.js", () => {
-  doMatch("bar.js", "*.js");
-});
-
-await run({
-  avg: true,
-  min_max: true,
-  percentiles: true,
-});

bench/snippets/buffer-create.mjs

@@ -39,24 +39,24 @@ bench("Buffer.from(ArrayBuffer(100))", () => {
   return Buffer.from(hundred);
 });
 
+bench("new Buffer(ArrayBuffer(100))", () => {
+  return new Buffer(hundred);
+});
+
 var hundredArray = new Uint8Array(100);
 bench("Buffer.from(Uint8Array(100))", () => {
   return Buffer.from(hundredArray);
 });
 
+bench("new Buffer(Uint8Array(100))", () => {
+  return new Buffer(hundredArray);
+});
+
 var empty = new Uint8Array(0);
 bench("Buffer.from(Uint8Array(0))", () => {
   return Buffer.from(empty);
 });
 
-bench("new Buffer(ArrayBuffer(100))", () => {
-  return new Buffer(hundred);
-});
-
-bench("new Buffer(Uint8Array(100))", () => {
-  return new Buffer(hundredArray);
-});
-
 bench("new Buffer(Uint8Array(0))", () => {
   return new Buffer(empty);
 });

bench/snippets/buffer-includes.js

@@ -1,17 +0,0 @@
-const buf = Buffer.from(
-  "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.",
-);
-const INTERVAL = 9_999_999;
-
-const time = (name, fn) => {
-  for (let i = 0; i < INTERVAL; i++) fn();
-
-  console.time(name.padEnd(30));
-  for (let i = 0; i < INTERVAL; i++) fn();
-  console.timeEnd(name.padEnd(30));
-};
-
-console.log(`Run ${new Intl.NumberFormat().format(INTERVAL)} times with a warmup:`, "\n");
-
-time("includes true", () => buf.includes("nisi"));
-time("includes false", () => buf.includes("oopwo"));

bench/snippets/buffer.js

@@ -1,7 +1,7 @@
 // import { Buffer } from "buffer";
 var buf = new Buffer(1024);
 var view = new DataView(buf.buffer);
-var INTERVAL = 9_999_999;
+var INTERVAL = 9999999;
 var time = (name, fn) => {
   for (let i = 0; i < INTERVAL; i++) fn();
 

bench/snippets/decode.js

@@ -1,71 +0,0 @@
-import { bench, run } from "../runner.mjs";
-
-let decodeURIComponentSIMD;
-if (typeof Bun !== "undefined") {
-  ({ decodeURIComponentSIMD } = await import("bun:internal-for-testing"));
-}
-
-const hugeText = Buffer.alloc(1000000, "Hello, world!").toString();
-const hugeTextWithPercentAtEnd = Buffer.alloc(1000000, "Hello, world!%40").toString();
-
-const tinyText = Buffer.alloc(100, "Hello, world!").toString();
-const tinyTextWithPercentAtEnd = Buffer.alloc(100, "Hello, world!%40").toString();
-
-const veryTinyText = Buffer.alloc(8, "a").toString();
-const veryTinyTextWithPercentAtEnd = Buffer.alloc(8, "a%40").toString();
-
-decodeURIComponentSIMD &&
-  bench("decodeURIComponentSIMD -  no % x 8 bytes", () => {
-    decodeURIComponentSIMD(veryTinyText);
-  });
-
-bench("    decodeURIComponent -  no % x 8 bytes", () => {
-  decodeURIComponent(veryTinyText);
-});
-
-decodeURIComponentSIMD &&
-  bench("decodeURIComponentSIMD - yes % x 8 bytes", () => {
-    decodeURIComponentSIMD(veryTinyTextWithPercentAtEnd);
-  });
-
-bench("    decodeURIComponent - yes % x 8 bytes", () => {
-  decodeURIComponent(veryTinyTextWithPercentAtEnd);
-});
-
-decodeURIComponentSIMD &&
-  bench("decodeURIComponentSIMD -  no % x 100 bytes", () => {
-    decodeURIComponentSIMD(tinyText);
-  });
-
-bench("    decodeURIComponent -  no % x 100 bytes", () => {
-  decodeURIComponent(tinyText);
-});
-
-decodeURIComponentSIMD &&
-  bench("decodeURIComponentSIMD - yes % x 100 bytes", () => {
-    decodeURIComponentSIMD(tinyTextWithPercentAtEnd);
-  });
-
-bench("    decodeURIComponent - yes % x 100 bytes", () => {
-  decodeURIComponent(tinyTextWithPercentAtEnd);
-});
-
-decodeURIComponentSIMD &&
-  bench("decodeURIComponentSIMD -  no % x 1 MB", () => {
-    decodeURIComponentSIMD(hugeText);
-  });
-
-bench("    decodeURIComponent -  no % x 1 MB", () => {
-  decodeURIComponent(hugeText);
-});
-
-decodeURIComponentSIMD &&
-  bench("decodeURIComponentSIMD - yes % x 1 MB", () => {
-    decodeURIComponentSIMD(hugeTextWithPercentAtEnd);
-  });
-
-bench("    decodeURIComponent - yes % x 1 MB", () => {
-  decodeURIComponent(hugeTextWithPercentAtEnd);
-});
-
-await run();

bench/snippets/path-relative.mjs

@@ -1,25 +0,0 @@
-import { posix } from "path";
-import { bench, run } from "../runner.mjs";
-
-const pathConfigurations = [
-  ["", ""],
-  [".", "."],
-  ["/foo/bar", "/foo/bar"],
-  ["/foo/bar/baz", "/foo/bar"],
-  ["/foo/bar", "/foo/bar/baz"],
-  ["/foo/bar/baz", "/foo/bar/qux"],
-  ["/foo/bar/baz", "/foo/bar/baz/qux"],
-  ["/foo/bar/baz", "/foo/bar/baz/qux/quux"],
-  ["/", "/foo"],
-  ["/foo", "/"],
-  ["foo/bar/baz", "foo/bar/qux"],
-  ["../foo/bar", "../foo/baz"],
-];
-
-pathConfigurations.forEach(([from, to]) => {
-  bench(`relative(${JSON.stringify(from)}, ${JSON.stringify(to)})`, () => {
-    globalThis.abc = posix.relative(from, to);
-  });
-});
-
-await run();

build.zig

@@ -25,10 +25,9 @@ comptime {
     if (!std.mem.eql(u8, builtin.zig_version_string, recommended_zig_version)) {
         @compileError(
             "" ++
-                "Bun requires Zig version " ++ recommended_zig_version ++ " (found " ++
-                builtin.zig_version_string ++ "). This is " ++
-                "automatically configured via Bun's CMake setup. You likely meant to run " ++
-                "`bun setup`. If you are trying to upgrade the Zig compiler, " ++
+                "Bun requires Zig version " ++ recommended_zig_version ++ ". This is" ++
+                "automatically configured via Bun's CMake setup. You likely meant to run" ++
+                "`bun setup`. If you are trying to upgrade the Zig compiler," ++
                 "run `./scripts/download-zig.sh master` or comment this message out.",
         );
     }
@@ -83,7 +82,10 @@ const BunBuildOptions = struct {
 
         var opts = b.addOptions();
         opts.addOption([]const u8, "base_path", b.pathFromRoot("."));
-        opts.addOption([]const u8, "codegen_path", std.fs.path.resolve(b.graph.arena, &.{ b.build_root.path.?, this.codegen_path }) catch @panic("OOM"));
+        opts.addOption([]const u8, "codegen_path", std.fs.path.resolve(b.graph.arena, &.{
+            b.build_root.path.?,
+            this.codegen_path,
+        }) catch @panic("OOM"));
 
         opts.addOption(bool, "codegen_embed", this.shouldEmbedCode());
         opts.addOption(u32, "canary_revision", this.canary_revision orelse 0);
@@ -427,7 +429,7 @@ pub fn addBunObject(b: *Build, opts: *BunBuildOptions) *Compile {
         .name = if (opts.optimize == .Debug) "bun-debug" else "bun",
         .root_source_file = switch (opts.os) {
             .wasm => b.path("root_wasm.zig"),
-            else => b.path("src/main.zig"),
+            else => b.path("root.zig"),
             // else => b.path("root_css.zig"),
         },
         .target = opts.target,
@@ -517,6 +519,16 @@ fn exists(path: []const u8) bool {
 fn addInternalPackages(b: *Build, obj: *Compile, opts: *BunBuildOptions) void {
     const os = opts.os;
 
+    const io_path = switch (os) {
+        .mac => "src/io/io_darwin.zig",
+        .linux => "src/io/io_linux.zig",
+        .windows => "src/io/io_windows.zig",
+        else => "src/io/io_stub.zig",
+    };
+    obj.root_module.addAnonymousImport("async_io", .{
+        .root_source_file = b.path(io_path),
+    });
+
     const zlib_internal_path = switch (os) {
         .windows => "src/deps/zlib.win32.zig",
         .linux, .mac => "src/deps/zlib.posix.zig",
@@ -549,7 +561,6 @@ fn addInternalPackages(b: *Build, obj: *Compile, opts: *BunBuildOptions) void {
         .{ .file = "bun-error/index.js", .enable = opts.shouldEmbedCode() },
         .{ .file = "bun-error/bun-error.css", .enable = opts.shouldEmbedCode() },
         .{ .file = "fallback-decoder.js", .enable = opts.shouldEmbedCode() },
-        .{ .file = "node-fallbacks/react-refresh.js", .enable = opts.shouldEmbedCode() },
         .{ .file = "node-fallbacks/assert.js", .enable = opts.shouldEmbedCode() },
         .{ .file = "node-fallbacks/buffer.js", .enable = opts.shouldEmbedCode() },
         .{ .file = "node-fallbacks/console.js", .enable = opts.shouldEmbedCode() },
@@ -586,15 +597,6 @@ fn addInternalPackages(b: *Build, obj: *Compile, opts: *BunBuildOptions) void {
             });
         }
     }
-    inline for (.{
-        .{ .import = "completions-bash", .file = b.path("completions/bun.bash") },
-        .{ .import = "completions-zsh", .file = b.path("completions/bun.zsh") },
-        .{ .import = "completions-fish", .file = b.path("completions/bun.fish") },
-    }) |entry| {
-        obj.root_module.addAnonymousImport(entry.import, .{
-            .root_source_file = entry.file,
-        });
-    }
 
     if (os == .windows) {
         obj.root_module.addAnonymousImport("bun_shim_impl.exe", .{

bun.lock

@@ -10,8 +10,8 @@
         "@typescript-eslint/eslint-plugin": "^7.11.0",
         "@typescript-eslint/parser": "^7.11.0",
         "@vscode/debugadapter": "^1.65.0",
-        "autoprefixer": "^10.4.19",
-        "caniuse-lite": "^1.0.30001620",
+        "autoprefixer": "^10.4.20",
+        "caniuse-lite": "^1.0.30001660",
         "esbuild": "^0.21.4",
         "eslint": "^9.4.0",
         "eslint-config-prettier": "^9.1.0",
@@ -151,13 +151,13 @@
 
     "@qiwi/npm-registry-client": ["@qiwi/npm-registry-client@8.9.1", "", { "dependencies": { "concat-stream": "^2.0.0", "graceful-fs": "^4.2.4", "normalize-package-data": "~1.0.1 || ^2.0.0 || ^3.0.0", "npm-package-arg": "^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^8.0.0", "once": "^1.4.0", "request": "^2.88.2", "retry": "^0.12.0", "safe-buffer": "^5.2.1", "semver": "2 >=2.2.1 || 3.x || 4 || 5 || 7", "slide": "^1.1.6", "ssri": "^8.0.0" }, "optionalDependencies": { "npmlog": "2 || ^3.1.0 || ^4.0.0" } }, "sha512-rZF+mG+NfijR0SHphhTLHRr4aM4gtfdwoAMY6we2VGQam8vkN1cxGG1Lg/Llrj8Dd0Mu6VjdFQRyMMRZxtZR2A=="],
 
-    "@types/bun": ["@types/bun@1.2.2", "", { "dependencies": { "bun-types": "1.2.2" } }, "sha512-tr74gdku+AEDN5ergNiBnplr7hpDp3V1h7fqI2GcR/rsUaM39jpSeKH0TFibRvU0KwniRx5POgaYnaXbk0hU+w=="],
+    "@types/bun": ["@types/bun@1.1.17", "", { "dependencies": { "bun-types": "1.1.44" } }, "sha512-zZt0Kao/8hAwNOXh4bmt8nKbMEd4QD8n7PeTGF+NZTVY5ouXhU/TX7jUj4He1p7mgY+WdplnU1B6MB1j17vdzg=="],
 
     "@types/json-schema": ["@types/json-schema@7.0.15", "", {}, "sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA=="],
 
     "@types/json5": ["@types/json5@0.0.29", "", {}, "sha512-dRLjCWHYg4oaA77cxO64oO+7JwCwnIzkZPdrrC71jQmQtlhM556pwKo5bUzqvZndkVbeFLIIi+9TC40JNF5hNQ=="],
 
-    "@types/node": ["@types/node@22.13.5", "", { "dependencies": { "undici-types": "~6.20.0" } }, "sha512-+lTU0PxZXn0Dr1NBtC7Y8cR21AJr87dLLU953CWA6pMxxv/UDc7jYAY90upcrie1nRcD6XNG5HOYEDtgW5TxAg=="],
+    "@types/node": ["@types/node@22.10.7", "", { "dependencies": { "undici-types": "~6.20.0" } }, "sha512-V09KvXxFiutGp6B7XkpaDXlNadZxrzajcY50EuoLIpQ6WWYCSvf19lVIazzfIzQvhUN2HjX12spLojTnhuKlGg=="],
 
     "@types/prop-types": ["@types/prop-types@15.7.12", "", {}, "sha512-5zvhXYtRNRluoE/jAp4GVsSduVUzNWKkOZrCDBWYtE7biZywwdC2AcEzg+cSMLFRfVgeAFqpfNabiPjxFddV1Q=="],
 

ci/README.md

@@ -0,0 +1,84 @@
+# CI
+
+This directory contains scripts for building CI images for Bun.
+
+## Building
+
+### `macOS`
+
+On macOS, images are built using [`tart`](https://tart.run/), a tool that abstracts over the [`Virtualization.Framework`](https://developer.apple.com/documentation/virtualization) APIs, to run macOS VMs.
+
+To install the dependencies required, run:
+
+```sh
+$ cd ci
+$ bun run bootstrap
+```
+
+To build a vanilla macOS VM, run:
+
+```sh
+$ bun run build:darwin-aarch64-vanilla
+```
+
+This builds a vanilla macOS VM with the current macOS release on your machine. It runs scripts to disable things like spotlight and siri, but it does not install any software.
+
+> Note: The image size is 50GB, so make sure you have enough disk space.
+
+If you want to build a specific macOS release, you can run:
+
+```sh
+$ bun run build:darwin-aarch64-vanilla-15
+```
+
+> Note: You cannot build a newer release of macOS on an older macOS machine.
+
+To build a macOS VM with software installed to build and test Bun, run:
+
+```sh
+$ bun run build:darwin-aarch64
+```
+
+## Running
+
+### `macOS`
+
+## How To
+
+### Support a new macOS release
+
+1. Visit [`ipsw.me`](https://ipsw.me/VirtualMac2,1) and find the IPSW of the macOS release you want to build.
+
+2. Add an entry to [`ci/darwin/variables.pkr.hcl`](/ci/darwin/variables.pkr.hcl) with the following format:
+
+```hcl
+sonoma = {
+  distro  = "sonoma"
+  release = "15"
+  ipsw    = "https://updates.cdn-apple.com/..."
+}
+```
+
+3. Add matching scripts to [`ci/package.json`](/ci/package.json) to build the image, then test it:
+
+```sh
+$ bun run build:darwin-aarch64-vanilla-15
+```
+
+> Note: If you need to troubleshoot the build, you can remove the `headless = true` property from [`ci/darwin/image-vanilla.pkr.hcl`](/ci/darwin/image-vanilla.pkr.hcl) and the VM's screen will be displayed.
+
+4. Test and build the non-vanilla image:
+
+```sh
+$ bun run build:darwin-aarch64-15
+```
+
+This will use the vanilla image and run the [`scripts/bootstrap.sh`](/scripts/bootstrap.sh) script to install the required software to build and test Bun.
+
+5. Publish the images:
+
+```sh
+$ bun run login
+$ bun run publish:darwin-aarch64-vanilla-15
+$ bun run publish:darwin-aarch64-15
+```

ci/alpine/build.Dockerfile

@@ -0,0 +1,22 @@
+FROM alpine:edge AS build
+ARG GIT_SHA
+ENV GIT_SHA=${GIT_SHA}
+WORKDIR /app/bun
+ENV HOME=/root
+
+COPY . .
+RUN touch $HOME/.bashrc
+RUN ./scripts/bootstrap.sh
+RUN . $HOME/.bashrc && bun run build:release
+
+RUN apk add file
+RUN file ./build/release/bun
+RUN ldd ./build/release/bun
+RUN ./build/release/bun
+
+RUN cp -R /app/bun/build/* /output
+
+FROM scratch AS artifact
+COPY --from=build /output /
+
+# docker build -f ./ci/alpine/build.Dockerfile --progress=plain --build-arg GIT_SHA="$(git rev-parse HEAD)" --target=artifact --output type=local,dest=./build-alpine .

ci/alpine/test.Dockerfile

@@ -0,0 +1,20 @@
+FROM alpine:edge
+ENV HOME=/root
+WORKDIR /root
+COPY ./build-alpine/release/bun .
+COPY ./test ./test
+COPY ./scripts ./scripts
+COPY ./package.json ./package.json
+COPY ./packages ./packages
+
+RUN apk update
+RUN apk add nodejs lsb-release-minimal git python3 npm make g++
+RUN apk add file
+
+RUN file /root/bun
+RUN ldd /root/bun
+RUN /root/bun
+
+RUN ./scripts/runner.node.mjs --exec-path /root/bun
+
+# docker build -f ./ci/alpine/test.Dockerfile --progress=plain .

ci/darwin/image-vanilla.pkr.hcl

@@ -0,0 +1,46 @@
+# Generates a vanilla macOS VM with optimized settings for virtualized environments.
+# See login.sh and optimize.sh for details.
+
+data "external-raw" "boot-script" {
+  program = ["sh", "-c", templatefile("scripts/boot-image.sh", var)]
+}
+
+source "tart-cli" "bun-darwin-aarch64-vanilla" {
+  vm_name      = "bun-darwin-aarch64-vanilla-${local.release.distro}-${local.release.release}"
+  from_ipsw    = local.release.ipsw
+  cpu_count    = local.cpu_count
+  memory_gb    = local.memory_gb
+  disk_size_gb = local.disk_size_gb
+  ssh_username = local.username
+  ssh_password = local.password
+  ssh_timeout  = "120s"
+  create_grace_time = "30s"
+  boot_command = split("\n", data.external-raw.boot-script.result)
+  headless     = true # Disable if you need to debug why the boot_command is not working
+}
+
+build {
+  sources = ["source.tart-cli.bun-darwin-aarch64-vanilla"]
+
+  provisioner "file" {
+    content = file("scripts/setup-login.sh")
+    destination = "/tmp/setup-login.sh"
+  }
+
+  provisioner "shell" {
+    inline = ["echo \"${local.password}\" | sudo -S sh -c 'sh /tmp/setup-login.sh \"${local.username}\" \"${local.password}\"'"]
+  }
+
+  provisioner "file" {
+    content = file("scripts/optimize-machine.sh")
+    destination = "/tmp/optimize-machine.sh"
+  }
+
+  provisioner "shell" {
+    inline = ["sudo sh /tmp/optimize-machine.sh"]
+  }
+
+  provisioner "shell" {
+    inline = ["sudo rm -rf /tmp/*"]
+  }
+}

ci/darwin/image.pkr.hcl

@@ -0,0 +1,44 @@
+# Generates a macOS VM with software installed to build and test Bun.
+
+source "tart-cli" "bun-darwin-aarch64" {
+  vm_name      = "bun-darwin-aarch64-${local.release.distro}-${local.release.release}"
+  vm_base_name = "bun-darwin-aarch64-vanilla-${local.release.distro}-${local.release.release}"
+  cpu_count    = local.cpu_count
+  memory_gb    = local.memory_gb
+  disk_size_gb = local.disk_size_gb
+  ssh_username = local.username
+  ssh_password = local.password
+  ssh_timeout  = "120s"
+  headless     = true
+}
+
+build {
+  sources = ["source.tart-cli.bun-darwin-aarch64"]
+
+  provisioner "file" {
+    content = file("../../scripts/bootstrap.sh")
+    destination = "/tmp/bootstrap.sh"
+  }
+
+  provisioner "shell" {
+    inline = ["CI=true sh /tmp/bootstrap.sh"]
+  }
+
+  provisioner "file" {
+    source = "darwin/plists/"
+    destination = "/tmp/"
+  }
+
+  provisioner "shell" {
+    inline = [
+      "sudo ls /tmp/",
+      "sudo mv /tmp/*.plist /Library/LaunchDaemons/",
+      "sudo chown root:wheel /Library/LaunchDaemons/*.plist",
+      "sudo chmod 644 /Library/LaunchDaemons/*.plist",
+    ]
+  }
+
+  provisioner "shell" {
+    inline = ["sudo rm -rf /tmp/*"]
+  }
+}

ci/darwin/plists/buildkite-agent.plist

@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+  <dict>
+    <key>Label</key>
+    <string>com.buildkite.buildkite-agent</string>
+
+    <key>ProgramArguments</key>
+    <array>
+      <string>/usr/local/bin/buildkite-agent</string>
+      <string>start</string>
+    </array>
+
+    <key>KeepAlive</key>
+    <dict>
+      <key>SuccessfulExit</key>
+      <false />
+    </dict>
+
+    <key>RunAtLoad</key>
+    <true />
+
+    <key>StandardOutPath</key>
+    <string>/var/buildkite-agent/logs/buildkite-agent.log</string>
+
+    <key>StandardErrorPath</key>
+    <string>/var/buildkite-agent/logs/buildkite-agent.log</string>
+
+    <key>EnvironmentVariables</key>
+    <dict>
+      <key>BUILDKITE_AGENT_CONFIG</key>
+      <string>/etc/buildkite-agent/buildkite-agent.cfg</string>
+    </dict>
+
+    <key>LimitLoadToSessionType</key>
+    <array>
+      <string>Aqua</string>
+      <string>LoginWindow</string>
+      <string>Background</string>
+      <string>StandardIO</string>
+      <string>System</string>
+    </array>
+  </dict>
+</plist>

ci/darwin/plists/tailscale.plist

@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+  <dict>
+    <key>Label</key>
+    <string>com.tailscale.tailscaled</string>
+
+    <key>ProgramArguments</key>
+    <array>
+      <string>/usr/local/bin/tailscale</string>
+      <string>up</string>
+      <string>--ssh</string>
+      <string>--authkey</string>
+      <string>${TAILSCALE_AUTHKEY}</string>
+    </array>
+
+    <key>RunAtLoad</key>
+    <true />
+  </dict>
+</plist>

ci/darwin/plists/tailscaled.plist

@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+  <dict>
+    <key>Label</key>
+    <string>com.tailscale.tailscaled</string>
+
+    <key>ProgramArguments</key>
+    <array>
+      <string>/usr/local/bin/tailscaled</string>
+    </array>
+
+    <key>RunAtLoad</key>
+    <true />
+  </dict>
+</plist>

ci/darwin/scripts/boot-image.sh

@@ -0,0 +1,124 @@
+#!/bin/sh
+
+# This script generates the boot commands for the macOS installer GUI.
+# It is run on your local machine, not inside the VM.
+
+# Sources:
+# - https://github.com/cirruslabs/macos-image-templates/blob/master/templates/vanilla-sequoia.pkr.hcl
+
+if ! [ "${release}" ] || ! [ "${username}" ] || ! [ "${password}" ]; then
+  echo "Script must be run with variables: release, username, and password" >&2
+  exit 1
+fi
+
+# Hello, hola, bonjour, etc.
+echo "<wait120s><spacebar>"
+
+# Select Your Country and Region
+echo "<wait30s>italiano<esc>english<enter>"
+echo "<wait30s>united states<leftShiftOn><tab><leftShiftOff><spacebar>"
+
+# Written and Spoken Languages
+echo "<wait30s><leftShiftOn><tab><leftShiftOff><spacebar>"
+
+# Accessibility
+echo "<wait30s><leftShiftOn><tab><leftShiftOff><spacebar>"
+
+# Data & Privacy
+echo "<wait30s><leftShiftOn><tab><leftShiftOff><spacebar>"
+
+# Migration Assistant
+echo "<wait30s><tab><tab><tab><spacebar>"
+
+# Sign In with Your Apple ID
+echo "<wait30s><leftShiftOn><tab><leftShiftOff><leftShiftOn><tab><leftShiftOff><spacebar>"
+
+# Are you sure you want to skip signing in with an Apple ID?
+echo "<wait30s><tab><spacebar>"
+
+# Terms and Conditions
+echo "<wait30s><leftShiftOn><tab><leftShiftOff><spacebar>"
+
+# I have read and agree to the macOS Software License Agreement
+echo "<wait30s><tab><spacebar>"
+
+# Create a Computer Account
+echo "<wait30s>${username}<tab><tab>${password}<tab>${password}<tab><tab><tab><spacebar>"
+
+# Enable Location Services
+echo "<wait60s><leftShiftOn><tab><leftShiftOff><spacebar>"
+
+# Are you sure you don't want to use Location Services?
+echo "<wait30s><tab><spacebar>"
+
+# Select Your Time Zone
+echo "<wait30s><tab>UTC<enter><leftShiftOn><tab><leftShiftOff><spacebar>"
+
+# Analytics
+echo "<wait30s><leftShiftOn><tab><leftShiftOff><spacebar>"
+
+# Screen Time
+echo "<wait30s><tab><spacebar>"
+
+# Siri
+echo "<wait30s><tab><spacebar><leftShiftOn><tab><leftShiftOff><spacebar>"
+
+# Choose Your Look
+echo "<wait30s><leftShiftOn><tab><leftShiftOff><spacebar>"
+
+if [ "${release}" = "13" ] || [ "${release}" = "14" ]; then
+  # Enable Voice Over
+  echo "<wait30s><leftAltOn><f5><leftAltOff><wait5s>v"
+else
+  # Welcome to Mac
+  echo "<wait30s><spacebar>"
+
+  # Enable Keyboard navigation
+  echo "<wait30s><leftAltOn><spacebar><leftAltOff>Terminal<enter>"
+  echo "<wait30s>defaults write NSGlobalDomain AppleKeyboardUIMode -int 3<enter>"
+  echo "<wait30s><leftAltOn>q<leftAltOff>"
+fi
+
+# Now that the installation is done, open "System Settings"
+echo "<wait30s><leftAltOn><spacebar><leftAltOff>System Settings<enter>"
+
+# Navigate to "Sharing"
+echo "<wait30s><leftAltOn>f<leftAltOff>sharing<enter>"
+
+if [ "${release}" = "13" ]; then
+  # Navigate to "Screen Sharing" and enable it
+  echo "<wait30s><tab><down><spacebar>"
+
+  # Navigate to "Remote Login" and enable it
+  echo "<wait30s><tab><tab><tab><tab><tab><tab><spacebar>"
+
+  # Open "Remote Login" details
+  echo "<wait30s><tab><spacebar>"
+
+  # Enable "Full Disk Access"
+  echo "<wait30s><tab><spacebar>"
+
+  # Click "Done"
+  echo "<wait30s><leftShiftOn><tab><leftShiftOff><leftShiftOn><tab><leftShiftOff><spacebar>"
+
+  # Disable Voice Over
+  echo "<leftAltOn><f5><leftAltOff>"
+elif [ "${release}" = "14" ]; then
+  # Navigate to "Screen Sharing" and enable it
+  echo "<wait30s><tab><tab><tab><tab><tab><spacebar>"
+
+  # Navigate to "Remote Login" and enable it
+  echo "<wait30s><tab><tab><tab><tab><tab><tab><tab><tab><tab><tab><tab><tab><spacebar>"
+
+  # Disable Voice Over
+  echo "<wait30s><leftAltOn><f5><leftAltOff>"
+elif [ "${release}" = "15" ]; then  
+  # Navigate to "Screen Sharing" and enable it
+  echo "<wait30s><tab><tab><tab><tab><tab><spacebar>"
+
+  # Navigate to "Remote Login" and enable it
+  echo "<wait30s><tab><tab><tab><tab><tab><tab><tab><tab><tab><tab><tab><tab><spacebar>"
+fi
+
+# Quit System Settings
+echo "<wait30s><leftAltOn>q<leftAltOff>"

ci/darwin/scripts/optimize-machine.sh

@@ -0,0 +1,122 @@
+#!/bin/sh
+
+# This script optimizes macOS for virtualized environments.
+# It disables things like spotlight, screen saver, and sleep.
+
+# Sources:
+# - https://github.com/sickcodes/osx-optimizer
+# - https://github.com/koding88/MacBook-Optimization-Script
+# - https://www.macstadium.com/blog/simple-optimizations-for-macos-and-ios-build-agents
+
+if [ "$(id -u)" != "0" ]; then
+  echo "This script must be run using sudo." >&2
+  exit 1
+fi
+
+execute() {
+  echo "$ $@" >&2
+  if ! "$@"; then
+    echo "Command failed: $@" >&2
+    exit 1
+  fi
+}
+
+disable_software_update() {
+  execute softwareupdate --schedule off
+  execute defaults write com.apple.SoftwareUpdate AutomaticDownload -bool false
+  execute defaults write com.apple.SoftwareUpdate AutomaticCheckEnabled -bool false
+  execute defaults write com.apple.SoftwareUpdate ConfigDataInstall -int 0
+  execute defaults write com.apple.SoftwareUpdate CriticalUpdateInstall -int 0
+  execute defaults write com.apple.SoftwareUpdate ScheduleFrequency -int 0
+  execute defaults write com.apple.SoftwareUpdate AutomaticDownload -int 0
+  execute defaults write com.apple.commerce AutoUpdate -bool false
+  execute defaults write com.apple.commerce AutoUpdateRestartRequired -bool false
+}
+
+disable_spotlight() {
+  execute mdutil -i off -a
+  execute mdutil -E /
+}
+
+disable_siri() {
+  execute launchctl unload -w /System/Library/LaunchAgents/com.apple.Siri.agent.plist
+  execute defaults write com.apple.Siri StatusMenuVisible -bool false
+  execute defaults write com.apple.Siri UserHasDeclinedEnable -bool true
+  execute defaults write com.apple.assistant.support "Assistant Enabled" 0
+}
+
+disable_sleep() {
+  execute systemsetup -setsleep Never
+  execute systemsetup -setcomputersleep Never
+  execute systemsetup -setdisplaysleep Never
+  execute systemsetup -setharddisksleep Never
+}
+
+disable_screen_saver() {
+  execute defaults write com.apple.screensaver loginWindowIdleTime 0
+  execute defaults write com.apple.screensaver idleTime 0
+}
+
+disable_screen_lock() {
+  execute defaults write com.apple.loginwindow DisableScreenLock -bool true
+}
+
+disable_wallpaper() {
+  execute defaults write com.apple.loginwindow DesktopPicture ""
+}
+
+disable_application_state() {
+  execute defaults write com.apple.loginwindow TALLogoutSavesState -bool false
+}
+
+disable_accessibility() {
+  execute defaults write com.apple.Accessibility DifferentiateWithoutColor -int 1
+  execute defaults write com.apple.Accessibility ReduceMotionEnabled -int 1
+  execute defaults write com.apple.universalaccess reduceMotion -int 1
+  execute defaults write com.apple.universalaccess reduceTransparency -int 1
+}
+
+disable_dashboard() {
+  execute defaults write com.apple.dashboard mcx-disabled -boolean YES
+  execute killall Dock
+}
+
+disable_animations() {
+  execute defaults write NSGlobalDomain NSAutomaticWindowAnimationsEnabled -bool false
+  execute defaults write -g QLPanelAnimationDuration -float 0
+  execute defaults write com.apple.finder DisableAllAnimations -bool true
+}
+
+disable_time_machine() {
+  execute tmutil disable
+}
+
+enable_performance_mode() {
+  # https://support.apple.com/en-us/101992
+  if ! [ $(nvram boot-args 2>/dev/null | grep -q serverperfmode) ]; then
+    execute nvram boot-args="serverperfmode=1 $(nvram boot-args 2>/dev/null | cut -f 2-)"
+  fi
+}
+
+add_terminal_to_desktop() {
+  execute ln -sf /System/Applications/Utilities/Terminal.app ~/Desktop/Terminal
+}
+
+main() {
+  disable_software_update
+  disable_spotlight
+  disable_siri
+  disable_sleep
+  disable_screen_saver
+  disable_screen_lock
+  disable_wallpaper
+  disable_application_state
+  disable_accessibility
+  disable_dashboard
+  disable_animations
+  disable_time_machine
+  enable_performance_mode
+  add_terminal_to_desktop
+}
+
+main

ci/darwin/scripts/setup-login.sh

@@ -0,0 +1,78 @@
+#!/bin/sh
+
+# This script generates a /etc/kcpassword file to enable auto-login on macOS.
+# Yes, this stores your password in plain text. Do NOT do this on your local machine.
+
+# Sources:
+# - https://github.com/xfreebird/kcpassword/blob/master/kcpassword
+
+if [ "$(id -u)" != "0" ]; then
+  echo "This script must be run using sudo." >&2
+  exit 1
+fi
+
+execute() {
+  echo "$ $@" >&2
+  if ! "$@"; then
+    echo "Command failed: $@" >&2
+    exit 1
+  fi
+}
+
+kcpassword() {
+  passwd="$1"
+  key="7d 89 52 23 d2 bc dd ea a3 b9 1f"
+  passwd_hex=$(printf "%s" "$passwd" | xxd -p | tr -d '\n')
+  
+  key_len=33
+  passwd_len=${#passwd_hex}
+  remainder=$((passwd_len % key_len))
+  if [ $remainder -ne 0 ]; then
+    padding=$((key_len - remainder))
+    passwd_hex="${passwd_hex}$(printf '%0*x' $((padding / 2)) 0)"
+  fi
+
+  result=""
+  i=0
+  while [ $i -lt ${#passwd_hex} ]; do
+    for byte in $key; do
+      [ $i -ge ${#passwd_hex} ] && break
+      p="${passwd_hex:$i:2}"
+      r=$(printf '%02x' $((0x$p ^ 0x$byte)))
+      result="${result}${r}"
+      i=$((i + 2))
+    done
+  done
+
+  echo "$result"
+}
+
+login() {
+  username="$1"
+  password="$2"
+
+  enable_passwordless_sudo() {
+    execute mkdir -p /etc/sudoers.d/
+    echo "${username} ALL=(ALL) NOPASSWD: ALL" | EDITOR=tee execute visudo "/etc/sudoers.d/${username}-nopasswd"
+  }
+
+  enable_auto_login() {
+    echo "00000000: 1ced 3f4a bcbc ba2c caca 4e82" | execute xxd -r - /etc/kcpassword
+    execute defaults write /Library/Preferences/com.apple.loginwindow autoLoginUser "${username}"
+  }
+
+  disable_screen_lock() {
+    execute sysadminctl -screenLock off -password "${password}"
+  }
+
+  enable_passwordless_sudo
+  enable_auto_login
+  disable_screen_lock
+}
+
+if [ $# -ne 2 ]; then
+  echo "Usage: $0 <username> <password>" >&2
+  exit 1
+fi
+
+login "$@"

ci/darwin/variables.pkr.hcl

@@ -0,0 +1,78 @@
+packer {
+  required_plugins {
+    tart = {
+      version = ">= 1.12.0"
+      source  = "github.com/cirruslabs/tart"
+    }
+    external = {
+      version = ">= 0.0.2"
+      source  = "github.com/joomcode/external"
+    }
+  }
+}
+
+variable "release" {
+  type    = number
+  default = 13
+}
+
+variable "username" {
+  type    = string
+  default = "admin"
+}
+
+variable "password" {
+  type    = string
+  default = "admin"
+}
+
+variable "cpu_count" {
+  type    = number
+  default = 2
+}
+
+variable "memory_gb" {
+  type    = number
+  default = 4
+}
+
+variable "disk_size_gb" {
+  type    = number
+  default = 50
+}
+
+locals {
+  sequoia = {
+    tier    = 1
+    distro  = "sequoia"
+    release = "15"
+    ipsw    = "https://updates.cdn-apple.com/2024FallFCS/fullrestores/062-78489/BDA44327-C79E-4608-A7E0-455A7E91911F/UniversalMac_15.0_24A335_Restore.ipsw"
+  }
+
+  sonoma = {
+    tier    = 2
+    distro  = "sonoma"
+    release = "14"
+    ipsw    = "https://updates.cdn-apple.com/2023FallFCS/fullrestores/042-54934/0E101AD6-3117-4B63-9BF1-143B6DB9270A/UniversalMac_14.0_23A344_Restore.ipsw"
+  }
+
+  ventura = {
+    tier    = 2
+    distro  = "ventura"
+    release = "13"
+    ipsw    = "https://updates.cdn-apple.com/2022FallFCS/fullrestores/012-92188/2C38BCD1-2BFF-4A10-B358-94E8E28BE805/UniversalMac_13.0_22A380_Restore.ipsw"
+  }
+
+  releases = {
+    15 = local.sequoia
+    14 = local.sonoma
+    13 = local.ventura
+  }
+
+  release      = local.releases[var.release]
+  username     = var.username
+  password     = var.password
+  cpu_count    = var.cpu_count
+  memory_gb    = var.memory_gb
+  disk_size_gb = var.disk_size_gb
+}

ci/linux/Dockerfile

@@ -0,0 +1,18 @@
+ARG IMAGE=debian:11
+FROM $IMAGE
+COPY ./scripts/bootstrap.sh /tmp/bootstrap.sh
+ENV CI=true
+RUN sh /tmp/bootstrap.sh && rm -rf /tmp/*
+WORKDIR /workspace/bun
+COPY bunfig.toml bunfig.toml
+COPY package.json package.json
+COPY CMakeLists.txt CMakeLists.txt
+COPY cmake/ cmake/
+COPY scripts/ scripts/
+COPY patches/ patches/
+COPY *.zig ./
+COPY src/ src/
+COPY packages/ packages/
+COPY test/ test/
+RUN bun i
+RUN bun run build:ci

ci/linux/scripts/set-hostname.sh

@@ -0,0 +1,27 @@
+#!/bin/sh
+
+# This script sets the hostname of the current machine.
+
+execute() {
+  echo "$ $@" >&2
+  if ! "$@"; then
+    echo "Command failed: $@" >&2
+    exit 1
+  fi
+}
+
+main() {
+  if [ "$#" -ne 1 ]; then
+    echo "Usage: $0 <hostname>" >&2
+    exit 1
+  fi
+
+  if [ -f "$(which hostnamectl)" ]; then
+    execute hostnamectl set-hostname "$1"
+  else
+    echo "Error: hostnamectl is not installed." >&2
+    exit 1
+  fi
+}
+
+main "$@"

ci/linux/scripts/start-tailscale.sh

@@ -0,0 +1,22 @@
+#!/bin/sh
+
+# This script starts tailscale on the current machine.
+
+execute() {
+  echo "$ $@" >&2
+  if ! "$@"; then
+    echo "Command failed: $@" >&2
+    exit 1
+  fi
+}
+
+main() {
+  if [ "$#" -ne 1 ]; then
+    echo "Usage: $0 <auth-key>" >&2
+    exit 1
+  fi
+
+  execute tailscale up --reset --ssh --accept-risk=lose-ssh --auth-key="$1"
+}
+
+main "$@"

ci/package.json

@@ -0,0 +1,27 @@
+{
+  "private": true,
+  "scripts": {
+    "bootstrap": "brew install gh jq cirruslabs/cli/tart cirruslabs/cli/sshpass hashicorp/tap/packer && packer init darwin",
+    "login": "token=$(gh auth token); username=$(gh api user --jq .login); echo \"Login as $username...\"; echo \"$token\" | tart login ghcr.io --username \"$username\" --password-stdin; echo \"$token\" | docker login ghcr.io --username \"$username\" --password-stdin",
+    "fetch:image-name": "echo ghcr.io/oven-sh/bun-vm",
+    "fetch:darwin-version": "echo 1",
+    "fetch:macos-version": "sw_vers -productVersion | cut -d. -f1",
+    "fetch:script-version": "cat ../scripts/bootstrap.sh | grep 'v=' | sed 's/v=\"//;s/\"//' | head -n 1",
+    "build:darwin-aarch64-vanilla": "packer build '-only=*.bun-darwin-aarch64-vanilla' -var release=$(bun fetch:macos-version) darwin/",
+    "build:darwin-aarch64-vanilla-15": "packer build '-only=*.bun-darwin-aarch64-vanilla' -var release=15 darwin/",
+    "build:darwin-aarch64-vanilla-14": "packer build '-only=*.bun-darwin-aarch64-vanilla' -var release=14 darwin/",
+    "build:darwin-aarch64-vanilla-13": "packer build '-only=*.bun-darwin-aarch64-vanilla' -var release=13 darwin/",
+    "build:darwin-aarch64": "packer build '-only=*.bun-darwin-aarch64' -var release=$(bun fetch:macos-version) darwin/",
+    "build:darwin-aarch64-15": "packer build '-only=*.bun-darwin-aarch64' -var release=15 darwin/",
+    "build:darwin-aarch64-14": "packer build '-only=*.bun-darwin-aarch64' -var release=14 darwin/",
+    "build:darwin-aarch64-13": "packer build '-only=*.bun-darwin-aarch64' -var release=13 darwin/",
+    "publish:darwin-aarch64-vanilla": "image=$(tart list --format json | jq -r \".[] | select(.Name | test(\\\"^bun-darwin-aarch64-vanilla-.*-$(bun fetch:macos-version)$\\\")) | .Name\" | head -n 1 | sed 's/bun-//'); tart push \"bun-$image\" \"ghcr.io/oven-sh/bun-vm:$image-v$(bun fetch:darwin-version)\"",
+    "publish:darwin-aarch64-vanilla-15": "tart push bun-darwin-aarch64-vanilla-sequoia-15 \"$(bun fetch:image-name):darwin-aarch64-vanilla-sequoia-15-v$(bun fetch:darwin-version)\"",
+    "publish:darwin-aarch64-vanilla-14": "tart push bun-darwin-aarch64-vanilla-sonoma-14 \"$(bun fetch:image-name):darwin-aarch64-vanilla-sonoma-14-v$(bun fetch:darwin-version)\"",
+    "publish:darwin-aarch64-vanilla-13": "tart push bun-darwin-aarch64-vanilla-ventura-13 \"$(bun fetch:image-name):darwin-aarch64-vanilla-ventura-13-v$(bun fetch:darwin-version)\"",
+    "publish:darwin-aarch64": "image=$(tart list --format json | jq -r \".[] | select(.Name | test(\\\"^bun-darwin-aarch64-.*-$(bun fetch:macos-version)$\\\")) | .Name\" | head -n 1 | sed 's/bun-//'); tart push \"bun-$image\" \"ghcr.io/oven-sh/bun-vm:$image-v$(bun fetch:script-version)\"",
+    "publish:darwin-aarch64-15": "tart push bun-darwin-aarch64-sequoia-15 \"$(bun fetch:image-name):darwin-aarch64-sequoia-15-v$(bun fetch:script-version)\"",
+    "publish:darwin-aarch64-14": "tart push bun-darwin-aarch64-sonoma-14 \"$(bun fetch:image-name):darwin-aarch64-sonoma-14-v$(bun fetch:script-version)\"",
+    "publish:darwin-aarch64-13": "tart push bun-darwin-aarch64-ventura-13 \"$(bun fetch:image-name):darwin-aarch64-ventura-13-v$(bun fetch:script-version)\""
+  }
+}

cmake/scripts/DownloadZig.cmake

@@ -1,16 +1,16 @@
 get_filename_component(SCRIPT_NAME ${CMAKE_CURRENT_LIST_FILE} NAME)
 message(STATUS "Running script: ${SCRIPT_NAME}")
 
-if(NOT ZIG_PATH OR NOT ZIG_COMMIT)
-  message(FATAL_ERROR "ZIG_PATH and ZIG_COMMIT required")
+if(NOT ZIG_PATH OR NOT ZIG_COMMIT OR NOT ZIG_VERSION)
+  message(FATAL_ERROR "ZIG_PATH, ZIG_COMMIT, and ZIG_VERSION are required")
 endif()
 
 if(CMAKE_HOST_APPLE)
-  set(ZIG_OS_ABI "macos-none")
+  set(ZIG_OS "macos")
 elseif(CMAKE_HOST_WIN32)
-  set(ZIG_OS_ABI "windows-gnu")
+  set(ZIG_OS "windows")
 elseif(CMAKE_HOST_UNIX)
-  set(ZIG_OS_ABI "linux-musl")
+  set(ZIG_OS "linux")
 else()
   message(FATAL_ERROR "Unsupported operating system: ${CMAKE_HOST_SYSTEM_NAME}")
 endif()
@@ -28,16 +28,22 @@ else()
   message(FATAL_ERROR "Unsupported architecture: ${CMAKE_HOST_SYSTEM_PROCESSOR}")
 endif()
 
-set(ZIG_NAME bootstrap-${ZIG_ARCH}-${ZIG_OS_ABI})
-set(ZIG_FILENAME ${ZIG_NAME}.zip)
+set(ZIG_ASAN "")
+if(ENABLE_ASAN)
+  set(ZIG_ASAN "+asan")
+endif()
+
+set(ZIG_NAME zig-${ZIG_OS}-${ZIG_ARCH}-${ZIG_VERSION}${ZIG_ASAN})
 
 if(CMAKE_HOST_WIN32)
   set(ZIG_EXE "zig.exe")
+  set(ZIG_FILENAME ${ZIG_NAME}.zip)
 else()
   set(ZIG_EXE "zig")
+  set(ZIG_FILENAME ${ZIG_NAME}.tar.xz)
 endif()
 
-set(ZIG_DOWNLOAD_URL https://github.com/oven-sh/zig/releases/download/autobuild-${ZIG_COMMIT}/${ZIG_FILENAME})
+set(ZIG_DOWNLOAD_URL https://bun-ci-assets.bun.sh/${ZIG_FILENAME})
 
 execute_process(
   COMMAND
@@ -61,8 +67,35 @@ if(NOT EXISTS ${ZIG_PATH}/${ZIG_EXE})
 endif()
 
 # Tools like VSCode need a stable path to the zig executable, on both Unix and Windows
-# To workaround this, we create a `zig.exe` & `zls.exe` symlink on Unix.
+# To workaround this, we create a `bun.exe` symlink on Unix.
 if(NOT WIN32)
   file(CREATE_LINK ${ZIG_PATH}/${ZIG_EXE} ${ZIG_PATH}/zig.exe SYMBOLIC)
-  file(CREATE_LINK ${ZIG_PATH}/zls ${ZIG_PATH}/zls.exe SYMBOLIC)
 endif()
+
+set(ZIG_REPOSITORY_PATH ${ZIG_PATH}/repository)
+
+execute_process(
+  COMMAND
+    ${CMAKE_COMMAND}
+      -DGIT_PATH=${ZIG_REPOSITORY_PATH}
+      -DGIT_REPOSITORY=oven-sh/zig
+      -DGIT_COMMIT=${ZIG_COMMIT}
+      -P ${CMAKE_CURRENT_LIST_DIR}/GitClone.cmake
+  ERROR_STRIP_TRAILING_WHITESPACE
+  ERROR_VARIABLE
+    ZIG_REPOSITORY_ERROR
+  RESULT_VARIABLE
+    ZIG_REPOSITORY_RESULT
+)
+
+if(NOT ZIG_REPOSITORY_RESULT EQUAL 0)
+  message(FATAL_ERROR "Download failed: ${ZIG_REPOSITORY_ERROR}")
+endif()
+
+file(REMOVE_RECURSE ${ZIG_PATH}/lib)
+
+# Use copy_directory instead of file(RENAME) because there were
+# race conditions in CI where some files were not copied.
+execute_process(COMMAND ${CMAKE_COMMAND} -E copy_directory ${ZIG_REPOSITORY_PATH}/lib ${ZIG_PATH}/lib)
+
+file(REMOVE_RECURSE ${ZIG_REPOSITORY_PATH})

cmake/targets/BuildBun.cmake

@@ -1,8 +1,8 @@
 if(DEBUG)
   set(bun bun-debug)
-# elseif(ENABLE_SMOL)
-#   set(bun bun-smol-profile)
-#   set(bunStrip bun-smol)
+elseif(ENABLE_SMOL)
+  set(bun bun-smol-profile)
+  set(bunStrip bun-smol)
 elseif(ENABLE_VALGRIND)
   set(bun bun-valgrind)
 elseif(ENABLE_ASSERTIONS)
@@ -179,32 +179,6 @@ register_command(
     ${BUN_NODE_FALLBACKS_OUTPUTS}
 )
 
-# An embedded copy of react-refresh is used when the user forgets to install it.
-# The library is not versioned alongside React.
-set(BUN_REACT_REFRESH_OUTPUT ${BUN_NODE_FALLBACKS_OUTPUT}/react-refresh.js)
-register_command(
-  TARGET
-    bun-node-fallbacks-react-refresh
-  COMMENT
-    "Building node-fallbacks/react-refresh.js"
-  CWD
-    ${BUN_NODE_FALLBACKS_SOURCE}
-  COMMAND
-    ${BUN_EXECUTABLE} build
-      ${BUN_NODE_FALLBACKS_SOURCE}/node_modules/react-refresh/cjs/react-refresh-runtime.development.js
-      --outfile=${BUN_REACT_REFRESH_OUTPUT}
-      --target=browser
-      --format=cjs
-      --minify
-      --define:process.env.NODE_ENV=\"'development'\"
-  SOURCES
-    ${BUN_NODE_FALLBACKS_SOURCE}/package.json
-    ${BUN_NODE_FALLBACKS_SOURCE}/bun.lock
-    ${BUN_NODE_FALLBACKS_NODE_MODULES}
-  OUTPUTS
-    ${BUN_REACT_REFRESH_OUTPUT}
-)
-
 set(BUN_ERROR_CODE_SCRIPT ${CWD}/src/codegen/generate-node-errors.ts)
 
 set(BUN_ERROR_CODE_SOURCES
@@ -432,7 +406,6 @@ set(BUN_OBJECT_LUT_SOURCES
   ${CWD}/src/bun.js/bindings/BunProcess.cpp
   ${CWD}/src/bun.js/bindings/ProcessBindingBuffer.cpp
   ${CWD}/src/bun.js/bindings/ProcessBindingConstants.cpp
-  ${CWD}/src/bun.js/bindings/ProcessBindingFs.cpp
   ${CWD}/src/bun.js/bindings/ProcessBindingNatives.cpp
   ${CWD}/src/bun.js/modules/NodeModuleModule.cpp
   ${CODEGEN_PATH}/ZigGeneratedClasses.lut.txt
@@ -445,7 +418,6 @@ set(BUN_OBJECT_LUT_OUTPUTS
   ${CODEGEN_PATH}/BunProcess.lut.h
   ${CODEGEN_PATH}/ProcessBindingBuffer.lut.h
   ${CODEGEN_PATH}/ProcessBindingConstants.lut.h
-  ${CODEGEN_PATH}/ProcessBindingFs.lut.h
   ${CODEGEN_PATH}/ProcessBindingNatives.lut.h
   ${CODEGEN_PATH}/NodeModuleModule.lut.h
   ${CODEGEN_PATH}/ZigGeneratedClasses.lut.h
@@ -528,7 +500,8 @@ file(GLOB_RECURSE BUN_ZIG_SOURCES ${CONFIGURE_DEPENDS}
 
 list(APPEND BUN_ZIG_SOURCES
   ${CWD}/build.zig
-  ${CWD}/src/main.zig
+  ${CWD}/root.zig
+  ${CWD}/root_wasm.zig
   ${BUN_BINDGEN_ZIG_OUTPUTS}
 )
 
@@ -537,7 +510,6 @@ set(BUN_ZIG_GENERATED_SOURCES
   ${BUN_FALLBACK_DECODER_OUTPUT}
   ${BUN_RUNTIME_JS_OUTPUT}
   ${BUN_NODE_FALLBACKS_OUTPUTS}
-  ${BUN_REACT_REFRESH_OUTPUT}
   ${BUN_ERROR_CODE_OUTPUTS}
   ${BUN_ZIG_GENERATED_CLASSES_OUTPUTS}
   ${BUN_JAVASCRIPT_OUTPUTS}
@@ -595,6 +567,7 @@ register_command(
       -Dcanary=${CANARY_REVISION}
       -Dcodegen_path=${CODEGEN_PATH}
       -Dcodegen_embed=$<IF:$<BOOL:${CODEGEN_EMBED}>,true,false>
+      -Denable_asan=$<IF:$<BOOL:${ENABLE_ASAN}>,true,false>
       --prominent-compile-errors
       ${ZIG_FLAGS_BUN}
   ARTIFACTS
@@ -622,7 +595,6 @@ file(GLOB BUN_CXX_SOURCES ${CONFIGURE_DEPENDS}
   ${CWD}/src/bun.js/bindings/sqlite/*.cpp
   ${CWD}/src/bun.js/bindings/webcrypto/*.cpp
   ${CWD}/src/bun.js/bindings/webcrypto/*/*.cpp
-  ${CWD}/src/bun.js/bindings/node/crypto/*.cpp
   ${CWD}/src/bun.js/bindings/v8/*.cpp
   ${CWD}/src/bun.js/bindings/v8/shim/*.cpp
   ${CWD}/src/bake/*.cpp
@@ -760,7 +732,6 @@ target_include_directories(${bun} PRIVATE
   ${CWD}/src/bun.js/bindings
   ${CWD}/src/bun.js/bindings/webcore
   ${CWD}/src/bun.js/bindings/webcrypto
-  ${CWD}/src/bun.js/bindings/node/crypto
   ${CWD}/src/bun.js/bindings/sqlite
   ${CWD}/src/bun.js/bindings/v8
   ${CWD}/src/bun.js/modules
@@ -1093,7 +1064,6 @@ add_custom_target(dependencies DEPENDS ${BUN_TARGETS})
 
 if(APPLE)
   target_link_libraries(${bun} PRIVATE icucore resolv)
-  target_compile_definitions(${bun} PRIVATE U_DISABLE_RENAMING=1)
 endif()
 
 if(USE_STATIC_SQLITE)

cmake/targets/BuildLshpack.cmake

@@ -4,7 +4,7 @@ register_repository(
   REPOSITORY
     litespeedtech/ls-hpack
   COMMIT
-    8905c024b6d052f083a3d11d0a169b3c2735c8a1
+    32e96f10593c7cb8553cd8c9c12721100ae9e924
 )
 
 if(WIN32)

cmake/tools/SetupBun.cmake

@@ -9,14 +9,6 @@ find_command(
     >=1.1.26
 )
 
-if (NOT CI)
-  # If node.js is not installed, it is extremely easy to make this path point to
-  # a tempdir such as /private/tmp/bun-node-ce532901c/bun, which may cause this
-  # CMake configuration break after tempdir is cleaned up (ex. after reboot).
-  get_filename_component(BUN_EXECUTABLE ${BUN_EXECUTABLE} REALPATH)
-  set(BUN_EXECUTABLE ${BUN_EXECUTABLE} CACHE FILEPATH "Bun executable" FORCE)
-endif()
-
 # If this is not set, some advanced features are not checked.
 # https://github.com/oven-sh/bun/blob/cd7f6a1589db7f1e39dc4e3f4a17234afbe7826c/src/bun.js/javascript.zig#L1069-L1072
 setenv(BUN_GARBAGE_COLLECTOR_LEVEL 1)

cmake/tools/SetupWebKit.cmake

@@ -2,7 +2,7 @@ option(WEBKIT_VERSION "The version of WebKit to use")
 option(WEBKIT_LOCAL "If a local version of WebKit should be used instead of downloading")
 
 if(NOT WEBKIT_VERSION)
-  set(WEBKIT_VERSION abe5e808a649db1182333f65bef55e65bb374616)
+  set(WEBKIT_VERSION 851aabf42b06ba583cc0485ff9088e3f84c22f3d)
 endif()
 
 string(SUBSTRING ${WEBKIT_VERSION} 0 16 WEBKIT_VERSION_PREFIX)

cmake/tools/SetupZig.cmake

@@ -20,7 +20,8 @@ else()
   unsupported(CMAKE_SYSTEM_NAME)
 endif()
 
-set(ZIG_COMMIT "bb9d6ab2c0bbbf20cc24dad03e88f3b3ffdb7de7")
+optionx(ZIG_VERSION STRING "The zig version of the compiler to download" DEFAULT "0.14.0-dev.2987+183bb8b08")
+optionx(ZIG_COMMIT STRING "The zig commit to use in oven-sh/zig" DEFAULT "63f8ed52c011beafde83216efba766492491ef4b")
 optionx(ZIG_TARGET STRING "The zig target to use" DEFAULT ${DEFAULT_ZIG_TARGET})
 
 if(CMAKE_BUILD_TYPE STREQUAL "Release")
@@ -76,6 +77,7 @@ register_command(
   COMMAND
     ${CMAKE_COMMAND}
       -DZIG_PATH=${ZIG_PATH}
+      -DZIG_VERSION=${ZIG_VERSION}
       -DZIG_COMMIT=${ZIG_COMMIT}
       -DENABLE_ASAN=${ENABLE_ASAN}
       -P ${CWD}/cmake/scripts/DownloadZig.cmake

dockerhub/debian-slim/Dockerfile

@@ -1,4 +1,4 @@
-FROM debian:bookworm-slim AS build
+FROM debian:bullseye-slim AS build
 
 # https://github.com/oven-sh/bun/releases
 ARG BUN_VERSION=latest

dockerhub/debian/Dockerfile

@@ -1,4 +1,4 @@
-FROM debian:bookworm-slim AS build
+FROM debian:bullseye-slim AS build
 
 # https://github.com/oven-sh/bun/releases
 ARG BUN_VERSION=latest

dockerhub/distroless/Dockerfile

@@ -1,4 +1,4 @@
-FROM debian:bookworm-slim AS build
+FROM debian:bullseye-slim AS build
 
 # https://github.com/oven-sh/bun/releases
 ARG BUN_VERSION=latest

docs/api/fetch.md

@@ -204,7 +204,7 @@ To customize the TLS validation, use the `checkServerIdentity` option in `tls`
 await fetch("https://example.com", {
   tls: {
     checkServerIdentity: (hostname, peerCertificate) => {
-      // Return an Error if the certificate is invalid
+      // Return an error if the certificate is invalid
     },
   },
 });

docs/api/ffi.md

@@ -1,7 +1,3 @@
-{% callout %}
-**⚠️ Warning** — `bun:ffi` is **experimental**, with known bugs and limitations, and should not be relied on in production. The most stable way to interact with native code from Bun is to write a [Node-API module](/docs/api/node-api).
-{% /callout %}
-
 Use the built-in `bun:ffi` module to efficiently call native libraries from JavaScript. It works with languages that support the C ABI (Zig, Rust, C/C++, C#, Nim, Kotlin, etc).
 
 ## dlopen usage (`bun:ffi`)
@@ -302,11 +298,7 @@ setTimeout(() => {
 When you're done with a JSCallback, you should call `close()` to free the memory.
 
 ### Experimental thread-safe callbacks
-
-`JSCallback` has experimental support for thread-safe callbacks. This will be needed if you pass a callback function into a different thread from its instantiation context. You can enable it with the optional `threadsafe` parameter.
-
-Currently, thread-safe callbacks work best when run from another thread that is running JavaScript code, i.e. a [`Worker`](/docs/api/workers). A future version of Bun will enable them to be called from any thread (such as new threads spawned by your native library that Bun is not aware of).
-
+`JSCallback` has experimental support for thread-safe callbacks. This will be needed if you pass a callback function into a different thread from it's instantiation context. You can enable it with the optional `threadsafe` option flag.
 ```ts
 const searchIterator = new JSCallback(
   (ptr, length) => /hello/.test(new CString(ptr, length)),
@@ -317,6 +309,7 @@ const searchIterator = new JSCallback(
   },
 );
 ```
+Be aware that there are still cases where this does not 100% work.
 
 {% callout %}
 

docs/api/http.md

@@ -8,421 +8,19 @@ To start a high-performance HTTP server with a clean API, the recommended approa
 
 ## `Bun.serve()`
 
-Use `Bun.serve` to start an HTTP server in Bun.
+Start an HTTP server in Bun with `Bun.serve`.
 
 ```ts
 Bun.serve({
-  // `routes` requires Bun v1.2.3+
-  routes: {
-    // Static routes
-    "/api/status": new Response("OK"),
-
-    // Dynamic routes
-    "/users/:id": req => {
-      return new Response(`Hello User ${req.params.id}!`);
-    },
-
-    // Per-HTTP method handlers
-    "/api/posts": {
-      GET: () => new Response("List posts"),
-      POST: async req => {
-        const body = await req.json();
-        return Response.json({ created: true, ...body });
-      },
-    },
-
-    // Wildcard route for all routes that start with "/api/" and aren't otherwise matched
-    "/api/*": Response.json({ message: "Not found" }, { status: 404 }),
-
-    // Redirect from /blog/hello to /blog/hello/world
-    "/blog/hello": Response.redirect("/blog/hello/world"),
-
-    // Serve a file by buffering it in memory
-    "/favicon.ico": new Response(await Bun.file("./favicon.ico").bytes(), {
-      headers: {
-        "Content-Type": "image/x-icon",
-      },
-    }),
-  },
-
-  // (optional) fallback for unmatched routes:
-  // Required if Bun's version < 1.2.3
   fetch(req) {
-    return new Response("Not Found", { status: 404 });
+    return new Response("Bun!");
   },
 });
 ```
 
-### Routing
-
-Routes in `Bun.serve()` receive a `BunRequest` (which extends [`Request`](https://developer.mozilla.org/en-US/docs/Web/API/Request)) and return a [`Response`](https://developer.mozilla.org/en-US/docs/Web/API/Response) or `Promise<Response>`. This makes it easier to use the same code for both sending & receiving HTTP requests.
-
-```ts
-// Simplified for brevity
-interface BunRequest<T extends string> extends Request {
-  params: Record<T, string>;
-}
-```
-
-#### Async/await in routes
-
-You can use async/await in route handlers to return a `Promise<Response>`.
-
-```ts
-import { sql, serve } from "bun";
-
-serve({
-  port: 3001,
-  routes: {
-    "/api/version": async () => {
-      const [version] = await sql`SELECT version()`;
-      return Response.json(version);
-    },
-  },
-});
-```
-
-#### Promise in routes
-
-You can also return a `Promise<Response>` from a route handler.
-
-```ts
-import { sql, serve } from "bun";
-
-serve({
-  routes: {
-    "/api/version": () => {
-      return new Promise(resolve => {
-        setTimeout(async () => {
-          const [version] = await sql`SELECT version()`;
-          resolve(Response.json(version));
-        }, 100);
-      });
-    },
-  },
-});
-```
-
-#### Type-safe route parameters
-
-TypeScript parses route parameters when passed as a string literal, so that your editor will show autocomplete when accessing `request.params`.
-
-```ts
-import type { BunRequest } from "bun";
-
-Bun.serve({
-  routes: {
-    // TypeScript knows the shape of params when passed as a string literal
-    "/orgs/:orgId/repos/:repoId": req => {
-      const { orgId, repoId } = req.params;
-      return Response.json({ orgId, repoId });
-    },
-
-    "/orgs/:orgId/repos/:repoId/settings": (
-      // optional: you can explicitly pass a type to BunRequest:
-      req: BunRequest<"/orgs/:orgId/repos/:repoId/settings">,
-    ) => {
-      const { orgId, repoId } = req.params;
-      return Response.json({ orgId, repoId });
-    },
-  },
-});
-```
-
-Percent-encoded route parameter values are automatically decoded. Unicode characters are supported. Invalid unicode is replaced with the unicode replacement character `&0xFFFD;`.
-
-### Static responses
-
-Routes can also be `Response` objects (without the handler function). Bun.serve() optimizes it for zero-allocation dispatch - perfect for health checks, redirects, and fixed content:
-
-```ts
-Bun.serve({
-  routes: {
-    // Health checks
-    "/health": new Response("OK"),
-    "/ready": new Response("Ready", {
-      headers: {
-        // Pass custom headers
-        "X-Ready": "1",
-      },
-    }),
-
-    // Redirects
-    "/blog": Response.redirect("https://bun.sh/blog"),
-
-    // API responses
-    "/api/config": Response.json({
-      version: "1.0.0",
-      env: "production",
-    }),
-  },
-});
-```
-
-Static responses do not allocate additional memory after initialization. You can generally expect at least a 15% performance improvement over manually returning a `Response` object.
-
-Static route responses are cached for the lifetime of the server object. To reload static routes, call `server.reload(options)`.
-
-```ts
-const server = Bun.serve({
-  static: {
-    "/api/time": new Response(new Date().toISOString()),
-  },
-
-  fetch(req) {
-    return new Response("404!");
-  },
-});
-
-// Update the time every second.
-setInterval(() => {
-  server.reload({
-    static: {
-      "/api/time": new Response(new Date().toISOString()),
-    },
-
-    fetch(req) {
-      return new Response("404!");
-    },
-  });
-}, 1000);
-```
-
-Reloading routes only impact the next request. In-flight requests continue to use the old routes. After in-flight requests to old routes are finished, the old routes are freed from memory.
-
-To simplify error handling, static routes do not support streaming response bodies from `ReadableStream` or an `AsyncIterator`. Fortunately, you can still buffer the response in memory first:
-
-```ts
-const time = await fetch("https://api.example.com/v1/data");
-// Buffer the response in memory first.
-const blob = await time.blob();
-
-const server = Bun.serve({
-  static: {
-    "/api/data": new Response(blob),
-  },
-
-  fetch(req) {
-    return new Response("404!");
-  },
-});
-```
-
-### Route precedence
-
-Routes are matched in order of specificity:
-
-1. Exact routes (`/users/all`)
-2. Parameter routes (`/users/:id`)
-3. Wildcard routes (`/users/*`)
-4. Global catch-all (`/*`)
-
-```ts
-Bun.serve({
-  routes: {
-    // Most specific first
-    "/api/users/me": () => new Response("Current user"),
-    "/api/users/:id": req => new Response(`User ${req.params.id}`),
-    "/api/*": () => new Response("API catch-all"),
-    "/*": () => new Response("Global catch-all"),
-  },
-});
-```
-
-### Per-HTTP Method Routes
-
-Route handlers can be specialized by HTTP method:
-
-```ts
-Bun.serve({
-  routes: {
-    "/api/posts": {
-      // Different handlers per method
-      GET: () => new Response("List posts"),
-      POST: async req => {
-        const post = await req.json();
-        return Response.json({ id: crypto.randomUUID(), ...post });
-      },
-      PUT: async req => {
-        const updates = await req.json();
-        return Response.json({ updated: true, ...updates });
-      },
-      DELETE: () => new Response(null, { status: 204 }),
-    },
-  },
-});
-```
-
-You can pass any of the following methods:
-
-| Method    | Usecase example                 |
-| --------- | ------------------------------- |
-| `GET`     | Fetch a resource                |
-| `HEAD`    | Check if a resource exists      |
-| `OPTIONS` | Get allowed HTTP methods (CORS) |
-| `DELETE`  | Delete a resource               |
-| `PATCH`   | Update a resource               |
-| `POST`    | Create a resource               |
-| `PUT`     | Update a resource               |
-
-When passing a function instead of an object, all methods will be handled by that function:
-
-```ts
-const server = Bun.serve({
-  routes: {
-    "/api/version": () => Response.json({ version: "1.0.0" }),
-  },
-});
-
-await fetch(new URL("/api/version", server.url));
-await fetch(new URL("/api/version", server.url), { method: "PUT" });
-// ... etc
-```
-
-### Hot Route Reloading
-
-Update routes without server restarts using `server.reload()`:
-
-```ts
-const server = Bun.serve({
-  routes: {
-    "/api/version": () => Response.json({ version: "1.0.0" }),
-  },
-});
-
-// Deploy new routes without downtime
-server.reload({
-  routes: {
-    "/api/version": () => Response.json({ version: "2.0.0" }),
-  },
-});
-```
-
-### Error Handling
-
-Bun provides structured error handling for routes:
-
-```ts
-Bun.serve({
-  routes: {
-    // Errors are caught automatically
-    "/api/risky": () => {
-      throw new Error("Something went wrong");
-    },
-  },
-  // Global error handler
-  error(error) {
-    console.error(error);
-    return new Response(`Internal Error: ${error.message}`, {
-      status: 500,
-      headers: {
-        "Content-Type": "text/plain",
-      },
-    });
-  },
-});
-```
-
-### HTML imports
-
-To add a client-side single-page app, you can use an HTML import:
-
-```ts
-import myReactSinglePageApp from "./index.html";
-
-Bun.serve({
-  routes: {
-    "/": myReactSinglePageApp,
-  },
-});
-```
-
-HTML imports don't just serve HTML. It's a full-featured frontend bundler, transpiler, and toolkit built using Bun's [bundler](https://bun.sh/docs/bundler), JavaScript transpiler and CSS parser.
-
-You can use this to build a full-featured frontend with React, TypeScript, Tailwind CSS, and more. Check out [/docs/bundler/fullstack](https://bun.sh/docs/bundler/fullstack) to learn more.
-
-### Practical example: REST API
-
-Here's a basic database-backed REST API using Bun's router with zero dependencies:
-
-{% codetabs %}
-
-```ts#server.ts
-import type { Post } from "./types.ts";
-import { Database } from "bun:sqlite";
-
-const db = new Database("posts.db");
-db.exec(`
-  CREATE TABLE IF NOT EXISTS posts (
-    id TEXT PRIMARY KEY,
-    title TEXT NOT NULL,
-    content TEXT NOT NULL,
-    created_at TEXT NOT NULL
-  )
-`);
-
-Bun.serve({
-  routes: {
-    // List posts
-    "/api/posts": {
-      GET: () => {
-        const posts = db.query("SELECT * FROM posts").all();
-        return Response.json(posts);
-      },
-
-      // Create post
-      POST: async req => {
-        const post: Omit<Post, "id" | "created_at"> = await req.json();
-        const id = crypto.randomUUID();
-
-        db.query(
-          `INSERT INTO posts (id, title, content, created_at)
-           VALUES (?, ?, ?, ?)`,
-        ).run(id, post.title, post.content, new Date().toISOString());
-
-        return Response.json({ id, ...post }, { status: 201 });
-      },
-    },
-
-    // Get post by ID
-    "/api/posts/:id": req => {
-      const post = db
-        .query("SELECT * FROM posts WHERE id = ?")
-        .get(req.params.id);
-
-      if (!post) {
-        return new Response("Not Found", { status: 404 });
-      }
-
-      return Response.json(post);
-    },
-  },
-
-  error(error) {
-    console.error(error);
-    return new Response("Internal Server Error", { status: 500 });
-  },
-});
-```
-
-```ts#types.ts
-export interface Post {
-  id: string;
-  title: string;
-  content: string;
-  created_at: string;
-}
-```
-
-{% /codetabs %}
-
-### Routing performance
-
-`Bun.serve()`'s router builds on top uWebSocket's [tree-based approach](https://github.com/oven-sh/bun/blob/0d1a00fa0f7830f8ecd99c027fce8096c9d459b6/packages/bun-uws/src/HttpRouter.h#L57-L64) to add [SIMD-accelerated route parameter decoding](https://github.com/oven-sh/bun/blob/main/src/bun.js/bindings/decodeURIComponentSIMD.cpp#L21-L271) and [JavaScriptCore structure caching](https://github.com/oven-sh/bun/blob/main/src/bun.js/bindings/ServerRouteList.cpp#L100-L101) to push the performance limits of what modern hardware allows.
-
 ### `fetch` request handler
 
-The `fetch` handler handles incoming requests that weren't matched by any route. It receives a [`Request`](https://developer.mozilla.org/en-US/docs/Web/API/Request) object and returns a [`Response`](https://developer.mozilla.org/en-US/docs/Web/API/Response) or [`Promise<Response>`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise).
+The `fetch` handler handles incoming requests. It receives a [`Request`](https://developer.mozilla.org/en-US/docs/Web/API/Request) object and returns a [`Response`](https://developer.mozilla.org/en-US/docs/Web/API/Response) or `Promise<Response>`.
 
 ```ts
 Bun.serve({
@@ -472,6 +70,116 @@ const server = Bun.serve({
 });
 ```
 
+### Static routes
+
+Use the `static` option to serve static `Response` objects by route.
+
+```ts
+// Bun v1.1.27+ required
+Bun.serve({
+  static: {
+    // health-check endpoint
+    "/api/health-check": new Response("All good!"),
+
+    // redirect from /old-link to /new-link
+    "/old-link": Response.redirect("/new-link", 301),
+
+    // serve static text
+    "/": new Response("Hello World"),
+
+    // serve a file by buffering it in memory
+    "/index.html": new Response(await Bun.file("./index.html").bytes(), {
+      headers: {
+        "Content-Type": "text/html",
+      },
+    }),
+    "/favicon.ico": new Response(await Bun.file("./favicon.ico").bytes(), {
+      headers: {
+        "Content-Type": "image/x-icon",
+      },
+    }),
+
+    // serve JSON
+    "/api/version.json": Response.json({ version: "1.0.0" }),
+  },
+
+  fetch(req) {
+    return new Response("404!");
+  },
+});
+```
+
+Static routes support headers, status code, and other `Response` options.
+
+```ts
+Bun.serve({
+  static: {
+    "/api/time": new Response(new Date().toISOString(), {
+      headers: {
+        "X-Custom-Header": "Bun!",
+      },
+    }),
+  },
+
+  fetch(req) {
+    return new Response("404!");
+  },
+});
+```
+
+Static routes can serve Response bodies faster than `fetch` handlers because they don't create `Request` objects, they don't create `AbortSignal`, they don't create additional `Response` objects. The only per-request memory allocation is the TCP/TLS socket data needed for each request.
+
+{% note %}
+`static` is experimental
+{% /note %}
+
+Static route responses are cached for the lifetime of the server object. To reload static routes, call `server.reload(options)`.
+
+```ts
+const server = Bun.serve({
+  static: {
+    "/api/time": new Response(new Date().toISOString()),
+  },
+
+  fetch(req) {
+    return new Response("404!");
+  },
+});
+
+// Update the time every second.
+setInterval(() => {
+  server.reload({
+    static: {
+      "/api/time": new Response(new Date().toISOString()),
+    },
+
+    fetch(req) {
+      return new Response("404!");
+    },
+  });
+}, 1000);
+```
+
+Reloading static routes only impact the next request. In-flight requests continue to use the old static routes. After in-flight requests to old static routes are finished, the old static routes are freed from memory.
+
+To simplify error handling, static routes do not support streaming response bodies from `ReadableStream` or an `AsyncIterator`. Fortunately, you can still buffer the response in memory first:
+
+```ts
+const time = await fetch("https://api.example.com/v1/data");
+// Buffer the response in memory first.
+const blob = await time.blob();
+
+const server = Bun.serve({
+  static: {
+    "/api/data": new Response(blob),
+  },
+
+  fetch(req) {
+    return new Response("404!");
+  },
+});
+```
+
 ### Changing the `port` and `hostname`
 
 To configure which port and hostname the server will listen on, set `port` and `hostname` in the options object.
@@ -845,7 +553,7 @@ Update the server's handlers without restarting:
 
 ```ts
 const server = Bun.serve({
-  routes: {
+  static: {
     "/api/version": Response.json({ version: "v1" }),
   },
   fetch(req) {
@@ -855,7 +563,7 @@ const server = Bun.serve({
 
 // Update to new handler
 server.reload({
-  routes: {
+  static: {
     "/api/version": Response.json({ version: "v2" }),
   },
   fetch(req) {
@@ -864,7 +572,7 @@ server.reload({
 });
 ```
 
-This is useful for development and hot reloading. Only `fetch`, `error`, and `routes` can be updated.
+This is useful for development and hot reloading. Only `fetch`, `error`, and `static` handlers can be updated.
 
 ## Per-Request Controls
 

docs/api/s3.md

@@ -181,8 +181,8 @@ const download = s3.presign("my-file.txt"); // GET, text/plain, expires in 24 ho
 
 const upload = s3.presign("my-file", {
   expiresIn: 3600, // 1 hour
-  method: "PUT",
-  type: "application/json", // No extension for inferring, so we can specify the content type to be JSON
+  method: 'PUT',
+  type: 'application/json', // No extension for inferring, so we can specify the content type to be JSON
 });
 
 // You can call .presign() if on a file reference, but avoid doing so
@@ -361,56 +361,6 @@ const minio = new S3Client({
 });
 ```
 
-### Using Bun's S3Client with supabase
-
-To use Bun's S3 client with [supabase](https://supabase.com/), set `endpoint` to the supabase endpoint in the `S3Client` constructor. The supabase endpoint includes your account ID and /storage/v1/s3 path. Make sure to set Enable connection via S3 protocol on in the supabase dashboard in https://supabase.com/dashboard/project/<account-id>/settings/storage and to set the region informed in the same section.
-
-```ts
-import { S3Client } from "bun";
-
-const supabase = new S3Client({
-  accessKeyId: "access-key",
-  secretAccessKey: "secret-key",
-  bucket: "my-bucket",
-  region: "us-west-1",
-  endpoint: "https://<account-id>.supabase.co/storage/v1/s3/storage",
-});
-```
-
-### Using Bun's S3Client with S3 Virtual Hosted-Style endpoints
-
-When using a S3 Virtual Hosted-Style endpoint, you need to set the `virtualHostedStyle` option to `true` and if no endpoint is provided, Bun will use region and bucket to infer the endpoint to AWS S3, if no region is provided it will use `us-east-1`. If you provide a the endpoint, there are no need to provide the bucket name.
-
-```ts
-import { S3Client } from "bun";
-
-// AWS S3 endpoint inferred from region and bucket
-const s3 = new S3Client({
-  accessKeyId: "access-key",
-  secretAccessKey: "secret-key",
-  bucket: "my-bucket",
-  virtualHostedStyle: true,
-  // endpoint: "https://my-bucket.s3.us-east-1.amazonaws.com",
-  // region: "us-east-1",
-});
-
-// AWS S3
-const s3WithEndpoint = new S3Client({
-  accessKeyId: "access-key",
-  secretAccessKey: "secret-key",
-  endpoint: "https://<bucket-name>.s3.<region>.amazonaws.com",
-  virtualHostedStyle: true,
-});
-
-// Cloudflare R2
-const r2WithEndpoint = new S3Client({
-  accessKeyId: "access-key",
-  secretAccessKey: "secret-key",
-  endpoint: "https://<bucket-name>.<account-id>.r2.cloudflarestorage.com",
-  virtualHostedStyle: true,
-});
-```
-
 ## Credentials
 
 Credentials are one of the hardest parts of using S3, and we've tried to make it as easy as possible. By default, Bun reads the following environment variables for credentials.

docs/api/sql.md

@@ -87,7 +87,7 @@ await sql`INSERT INTO users ${sql(users)}`;
 
 ### Picking columns to insert
 
-You can use `sql(object, ...string)` to pick which columns to insert. Each of the columns must be defined on the object.
+You can use `sql(object, Array<string>)` to pick which columns to insert. Each of the columns must be defined on the object.
 
 ```ts
 const user = {
@@ -96,7 +96,7 @@ const user = {
   age: 25,
 };
 
-await sql`INSERT INTO users ${sql(user, "name", "email")}`;
+await sql`INSERT INTO users ${sql(user, ["name", "email"])}`;
 // Only inserts name and email columns, ignoring other fields
 ```
 
@@ -165,72 +165,13 @@ await sql`
 `;
 ```
 
-### Dynamic columns in updates
-
-You can use `sql(object, ...string)` to pick which columns to update. Each of the columns must be defined on the object. If the columns are not informed all keys will be used to update the row.
-
-```ts
-await sql`UPDATE users SET ${sql(user, "name", "email")} WHERE id = ${user.id}`;
-// uses all keys from the object to update the row
-await sql`UPDATE users SET ${sql(user)} WHERE id = ${user.id}`;
-```
-
-### Dynamic values and `where in`
-
-Value lists can also be created dynamically, making where in queries simple too. Optionally you can pass a array of objects and inform what key to use to create the list.
-
-```ts
-await sql`SELECT * FROM users WHERE id IN ${sql([1, 2, 3])}`;
-
-const users = [
-  { id: 1, name: "Alice" },
-  { id: 2, name: "Bob" },
-  { id: 3, name: "Charlie" },
-];
-await sql`SELECT * FROM users WHERE id IN ${sql(users, "id")}`;
-```
-
-## `sql``.simple()`
-
-The PostgreSQL wire protocol supports two types of queries: "simple" and "extended". Simple queries can contain multiple statements but don't support parameters, while extended queries (the default) support parameters but only allow one statement.
-
-To run multiple statements in a single query, use `sql``.simple()`:
-
-```ts
-// Multiple statements in one query
-await sql`
-  SELECT 1;
-  SELECT 2;
-`.simple();
-```
-
-Simple queries are often useful for database migrations and setup scripts.
-
-Note that simple queries cannot use parameters (`${value}`). If you need parameters, you must split your query into separate statements.
-
-### Queries in files
-
-You can use the `sql.file` method to read a query from a file and execute it, if the file includes $1, $2, etc you can pass parameters to the query. If no parameters are used it can execute multiple commands per file.
-
-```ts
-const result = await sql.file("query.sql", [1, 2, 3]);
-```
-
 ### Unsafe Queries
 
-You can use the `sql.unsafe` function to execute raw SQL strings. Use this with caution, as it will not escape user input. Executing more than one command per query is allowed if no parameters are used.
+You can use the `sql.unsafe` function to execute raw SQL strings. Use this with caution, as it will not escape user input.
 
 ```ts
-// Multiple commands without parameters
-const result = await sql.unsafe(`
-  SELECT ${userColumns} FROM users;
-  SELECT ${accountColumns} FROM accounts;
-`);
-
-// Using parameters (only one command is allowed)
 const result = await sql.unsafe(
-  "SELECT " + dangerous + " FROM users WHERE id = $1",
-  [id],
+  "SELECT " + columns + " FROM users WHERE id = " + id,
 );
 ```
 
@@ -321,21 +262,6 @@ const db = new SQL({
 });
 ```
 
-## Dynamic passwords
-
-When clients need to use alternative authentication schemes such as access tokens or connections to databases with rotating passwords, provide either a synchronous or asynchronous function that will resolve the dynamic password value at connection time.
-
-```ts
-import { SQL } from "bun";
-
-const sql = new SQL(url, {
-  // Other connection config
-  ...
-  // Password function for the database user
-  password: async () => await signer.getAuthToken(),
-});
-```
-
 ## Transactions
 
 To start a new transaction, use `sql.begin`. This method reserves a dedicated connection for the duration of the transaction and provides a scoped `sql` instance to use within the callback function. Once the callback completes, `sql.begin` resolves with the return value of the callback.
@@ -505,34 +431,6 @@ try {
 } // Automatically released
 ```
 
-## Prepared Statements
-
-By default, Bun's SQL client automatically creates named prepared statements for queries where it can be inferred that the query is static. This provides better performance. However, you can change this behavior by setting `prepare: false` in the connection options:
-
-```ts
-const sql = new SQL({
-  // ... other options ...
-  prepare: false, // Disable persisting named prepared statements on the server
-});
-```
-
-When `prepare: false` is set:
-
-Queries are still executed using the "extended" protocol, but they are executed using [unnamed prepared statements](https://www.postgresql.org/docs/current/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY), an unnamed prepared statement lasts only until the next Parse statement specifying the unnamed statement as destination is issued.
-
-- Parameter binding is still safe against SQL injection
-- Each query is parsed and planned from scratch by the server
-- Queries will not be [pipelined](https://www.postgresql.org/docs/current/protocol-flow.html#PROTOCOL-FLOW-PIPELINING)
-
-You might want to use `prepare: false` when:
-
-- Using PGBouncer in transaction mode (though since PGBouncer 1.21.0, protocol-level named prepared statements are supported when configured properly)
-- Debugging query execution plans
-- Working with dynamic SQL where query plans need to be regenerated frequently
-- More than one command per query will not be supported (unless you use `sql``.simple()`)
-
-Note that disabling prepared statements may impact performance for queries that are executed frequently with different parameters, as the server needs to parse and plan each query from scratch.
-
 ## Error Handling
 
 The client provides typed errors for different failure scenarios:
@@ -568,7 +466,6 @@ The client provides typed errors for different failure scenarios:
 | `ERR_POSTGRES_SERVER_ERROR`          | General error from PostgreSQL server       |
 | `ERR_POSTGRES_INVALID_QUERY_BINDING` | Invalid parameter binding                  |
 | `ERR_POSTGRES_QUERY_CANCELLED`       | Query was cancelled                        |
-| `ERR_POSTGRES_NOT_TAGGED_CALL`       | Query was called without a tagged call     |
 
 ### Data Type Errors
 
@@ -604,7 +501,7 @@ The client provides typed errors for different failure scenarios:
 
 ## Numbers and BigInt
 
-Bun's SQL client includes special handling for large numbers that exceed the range of a 53-bit integer. Here's how it works:
+Bun's SQL client includes special handling for large numbers that exceed the range of a 53-bit integer. Here’s how it works:
 
 ```ts
 import { sql } from "bun";

docs/api/workers.md

@@ -228,17 +228,3 @@ const worker = new Worker("./i-am-smol.ts", {
 {% details summary="What does `smol` mode actually do?" %}
 Setting `smol: true` sets `JSC::HeapSize` to be `Small` instead of the default `Large`.
 {% /details %}
-
-## `Bun.isMainThread`
-
-You can check if you're in the main thread by checking `Bun.isMainThread`.
-
-```ts
-if (Bun.isMainThread) {
-  console.log("I'm the main thread");
-} else {
-  console.log("I'm in a worker");
-}
-```
-
-This is useful for conditionally running code based on whether you're in the main thread or not.

docs/bundler/css_modules.md

@@ -1,145 +0,0 @@
-# CSS Modules
-
-Bun's bundler also supports bundling [CSS modules](https://css-tricks.com/css-modules-part-1-need/) in addition to [regular CSS](/docs/bundler/css) with support for the following features:
-
-- Automatically detecting CSS module files (`.module.css`) with zero configuration
-- Composition (`composes` property)
-- Importing CSS modules into JSX/TSX
-- Warnings/errors for invalid usages of CSS modules
-
-A CSS module is a CSS file (with the `.module.css` extension) where are all class names and animations are scoped to the file. This helps you avoid class name collisions as CSS declarations are globally scoped by default.
-
-Under the hood, Bun's bundler transforms locally scoped class names into unique identifiers.
-
-## Getting started
-
-Create a CSS file with the `.module.css` extension:
-
-```css
-/* styles.module.css */
-.button {
-  color: red;
-}
-
-/* other-styles.module.css */
-.button {
-  color: blue;
-}
-```
-
-You can then import this file, for example into a TSX file:
-
-```tsx
-import styles from "./styles.module.css";
-import otherStyles from "./other-styles.module.css";
-
-export default function App() {
-  return (
-    <>
-      <button className={styles.button}>Red button!</button>
-      <button className={otherStyles.button}>Blue button!</button>
-    </>
-  );
-}
-```
-
-The `styles` object from importing the CSS module file will be an object with all class names as keys and
-their unique identifiers as values:
-
-```tsx
-import styles from "./styles.module.css";
-import otherStyles from "./other-styles.module.css";
-
-console.log(styles);
-console.log(otherStyles);
-```
-
-This will output:
-
-```ts
-{
-  button: "button_123";
-}
-
-{
-  button: "button_456";
-}
-```
-
-As you can see, the class names are unique to each file, avoiding any collisions!
-
-### Composition
-
-CSS modules allow you to _compose_ class selectors together. This lets you reuse style rules across multiple classes.
-
-For example:
-
-```css
-/* styles.module.css */
-.button {
-  composes: background;
-  color: red;
-}
-
-.background {
-  background-color: blue;
-}
-```
-
-Would be the same as writing:
-
-```css
-.button {
-  background-color: blue;
-  color: red;
-}
-
-.background {
-  background-color: blue;
-}
-```
-
-{% callout %}
-There are a couple rules to keep in mind when using `composes`:
-
-- A `composes` property must come before any regular CSS properties or declarations
-- You can only use `composes` on a **simple selector with a single class name**:
-
-```css
-#button {
-  /* Invalid! `#button` is not a class selector */
-  composes: background;
-}
-
-.button,
-.button-secondary {
-  /* Invalid! `.button, .button-secondary` is not a simple selector */
-  composes: background;
-}
-```
-
-{% /callout %}
-
-### Composing from a separate CSS module file
-
-You can also compose from a separate CSS module file:
-
-```css
-/* background.module.css */
-.background {
-  background-color: blue;
-}
-
-/* styles.module.css */
-.button {
-  composes: background from "./background.module.css";
-  color: red;
-}
-```
-
-{% callout %}
-When composing classes from separate files, be sure that they do not contain the same properties.
-
-The CSS module spec says that composing classes from separate files with conflicting properties is
-undefined behavior, meaning that the output may differ and be unreliable.
-{% /callout %}

docs/bundler/executables.md

@@ -75,16 +75,14 @@ bun build --compile --target=bun-darwin-x64 ./path/to/my/app.ts --outfile myapp
 
 The order of the `--target` flag does not matter, as long as they're delimited by a `-`.
 
-| --target              | Operating System | Architecture | Modern | Baseline | Libc  |
-| --------------------- | ---------------- | ------------ | ------ | -------- | ----- |
-| bun-linux-x64         | Linux            | x64          | ✅     | ✅       | glibc |
-| bun-linux-arm64       | Linux            | arm64        | ✅     | N/A      | glibc |
-| bun-windows-x64       | Windows          | x64          | ✅     | ✅       | -     |
-| ~~bun-windows-arm64~~ | Windows          | arm64        | ❌     | ❌       | -     |
-| bun-darwin-x64        | macOS            | x64          | ✅     | ✅       | -     |
-| bun-darwin-arm64      | macOS            | arm64        | ✅     | N/A      | -     |
-| bun-linux-x64-musl    | Linux            | x64          | ✅     | ✅       | musl  |
-| bun-linux-arm64-musl  | Linux            | arm64        | ✅     | N/A      | musl  |
+| --target              | Operating System | Architecture | Modern | Baseline |
+| --------------------- | ---------------- | ------------ | ------ | -------- |
+| bun-linux-x64         | Linux            | x64          | ✅     | ✅       |
+| bun-linux-arm64       | Linux            | arm64        | ✅     | N/A      |
+| bun-windows-x64       | Windows          | x64          | ✅     | ✅       |
+| ~~bun-windows-arm64~~ | Windows          | arm64        | ❌     | ❌       |
+| bun-darwin-x64        | macOS            | x64          | ✅     | ✅       |
+| bun-darwin-arm64      | macOS            | arm64        | ✅     | N/A      |
 
 On x64 platforms, Bun uses SIMD optimizations which require a modern CPU supporting AVX2 instructions. The `-baseline` build of Bun is for older CPUs that don't support these optimizations. Normally, when you install Bun we automatically detect which version to use but this can be harder to do when cross-compiling since you might not know the target CPU. You usually don't need to worry about it on Darwin x64, but it is relevant for Windows x64 and Linux x64. If you or your users see `"Illegal instruction"` errors, you might need to use the baseline version.
 
@@ -198,8 +196,6 @@ import icon from "./icon.png" with { type: "file" };
 import { file } from "bun";
 
 const bytes = await file(icon).arrayBuffer();
-// await fs.promises.readFile(icon)
-// fs.readFileSync(icon)
 ```
 
 ### Embed SQLite databases
@@ -296,55 +292,6 @@ These flags currently cannot be used when cross-compiling because they depend on
 
 {% /callout %}
 
-## Code signing on macOS
-
-To codesign a standalone executable on macOS (which fixes Gatekeeper warnings), use the `codesign` command.
-
-```sh
-$ codesign --deep --force -vvvv --sign "XXXXXXXXXX" ./myapp
-```
-
-We recommend including an `entitlements.plist` file with JIT permissions.
-
-```xml#entitlements.plist
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
-<plist version="1.0">
-<dict>
-    <key>com.apple.security.cs.allow-jit</key>
-    <true/>
-    <key>com.apple.security.cs.allow-unsigned-executable-memory</key>
-    <true/>
-    <key>com.apple.security.cs.disable-executable-page-protection</key>
-    <true/>
-    <key>com.apple.security.cs.allow-dyld-environment-variables</key>
-    <true/>
-    <key>com.apple.security.cs.disable-library-validation</key>
-    <true/>
-</dict>
-</plist>
-```
-
-To codesign with JIT support, pass the `--entitlements` flag to `codesign`.
-
-```sh
-$ codesign --deep --force -vvvv --sign "XXXXXXXXXX" --entitlements entitlements.plist ./myapp
-```
-
-After codesigning, verify the executable:
-
-```sh
-$ codesign -vvv --verify ./myapp
-./myapp: valid on disk
-./myapp: satisfies its Designated Requirement
-```
-
-{% callout %}
-
-Codesign support requires Bun v1.2.4 or newer.
-
-{% /callout %}
-
 ## Unsupported CLI arguments
 
 Currently, the `--compile` flag can only accept a single entrypoint at a time and does not support the following flags:

docs/bundler/fullstack.md

@@ -1,50 +1,36 @@
-Using `Bun.serve()`'s `routes` option, you can run your frontend and backend in the same app with no extra steps.
+Using `Bun.serve()`'s `static` option, you can run your frontend and backend in the same app with no extra steps.
 
-To get started, import HTML files and pass them to the `routes` option in `Bun.serve()`.
+To get started, import HTML files and pass them to the `static` option in `Bun.serve()`.
 
 ```ts
-import { sql, serve } from "bun";
 import dashboard from "./dashboard.html";
 import homepage from "./index.html";
 
-const server = serve({
-  routes: {
-    // ** HTML imports **
-    // Bundle & route index.html to "/". This uses HTMLRewriter to scan the HTML for `<script>` and `<link>` tags, run's Bun's JavaScript & CSS bundler on them, transpiles any TypeScript, JSX, and TSX, downlevels CSS with Bun's CSS parser and serves the result.
+const server = Bun.serve({
+  // Add HTML imports to `static`
+  static: {
+    // Bundle & route index.html to "/"
     "/": homepage,
     // Bundle & route dashboard.html to "/dashboard"
     "/dashboard": dashboard,
-
-    // ** API endpoints ** (Bun v1.2.3+ required)
-    "/api/users": {
-      async GET(req) {
-        const users = await sql`SELECT * FROM users`;
-        return Response.json(users);
-      },
-      async POST(req) {
-        const { name, email } = await req.json();
-        const [user] =
-          await sql`INSERT INTO users (name, email) VALUES (${name}, ${email})`;
-        return Response.json(user);
-      },
-    },
-    "/api/users/:id": async req => {
-      const { id } = req.params;
-      const [user] = await sql`SELECT * FROM users WHERE id = ${id}`;
-      return Response.json(user);
-    },
   },
 
   // Enable development mode for:
   // - Detailed error messages
-  // - Hot reloading (Bun v1.2.3+ required)
+  // - Rebuild on request
   development: true,
 
-  // Prior to v1.2.3, the `fetch` option was used to handle all API requests. It is now optional.
-  // async fetch(req) {
-  //   // Return 404 for unmatched routes
-  //   return new Response("Not Found", { status: 404 });
-  // },
+  // Handle API requests
+  async fetch(req) {
+    // ...your API code
+    if (req.url.endsWith("/api/users")) {
+      const users = await Bun.sql`SELECT * FROM users`;
+      return Response.json(users);
+    }
+
+    // Return 404 for unmatched routes
+    return new Response("Not Found", { status: 404 });
+  },
 });
 
 console.log(`Listening on ${server.url}`);
@@ -69,7 +55,7 @@ These HTML files are used as routes in Bun's dev server you can pass to `Bun.ser
 
 ```ts
 Bun.serve({
-  routes: {
+  static: {
     "/": homepage,
     "/dashboard": dashboard,
   }
@@ -127,7 +113,7 @@ import dashboard from "../public/dashboard.html";
 import { serve } from "bun";
 
 serve({
-  routes: {
+  static: {
     "/": dashboard,
   },
 
@@ -185,7 +171,7 @@ import homepage from "./index.html";
 import dashboard from "./dashboard.html";
 
 Bun.serve({
-  routes: {
+  static: {
     "/": homepage,
     "/dashboard": dashboard,
   }
@@ -263,8 +249,6 @@ plugins = ["./my-plugin-implementation.ts"]
 
 Bun will lazily resolve and load each plugin and use them to bundle your routes.
 
-Note: this is currently in `bunfig.toml` to make it possible to know statically which plugins are in use when we eventually integrate this with the `bun build` CLI. These plugins work in `Bun.build()`'s JS API, but are not yet supported in the CLI.
-
 ## How this works
 
 Bun uses [`HTMLRewriter`](/docs/api/html-rewriter) to scan for `<script>` and `<link>` tags in HTML files, uses them as entrypoints for [Bun's bundler](/docs/bundler), generates an optimized bundle for the JavaScript/TypeScript/TSX/JSX and CSS files, and serves the result.
@@ -309,4 +293,5 @@ This works similarly to how [`Bun.build` processes HTML files](/docs/bundler/htm
 
 ## This is a work in progress
 
+- Client-side hot reloading isn't wired up yet. It will be in the future.
 - This doesn't support `bun build` yet. It also will in the future.

docs/bundler/hmr.md

@@ -1,234 +0,0 @@
-Hot Module Replacement (HMR) allows you to update modules in a running
-application without needing a full page reload. This preserves the application
-state and improves the development experience.
-
-HMR is enabled by default when using Bun's full-stack development server.
-
-## `import.meta.hot` API Reference
-
-Bun implements a client-side HMR API modeled after [Vite's `import.meta.hot` API](https://vitejs.dev/guide/api-hmr.html). It can be checked for with `if (import.meta.hot)`, tree-shaking it in production
-
-```ts
-if (import.meta.hot) {
-  // HMR APIs are available.
-}
-```
-
-However, **this check is often not needed** as Bun will dead-code-eliminate
-calls to all of the HMR APIs in production builds.
-
-```ts
-// This entire function call will be removed in production!
-import.meta.hot.dispose(() => {
-  console.log("dispose");
-});
-```
-
-For this to work, Bun forces these APIs to be called without indirection. That means the following do not work:
-
-```ts#invalid-hmr-usage.ts
-// INVALID: Assigning `hot` to a variable
-const hot = import.meta.hot;
-hot.accept();
-
-// INVALID: Assigning `import.meta` to a variable
-const meta = import.meta;
-meta.hot.accept();
-console.log(meta.hot.data);
-
-// INVALID: Passing to a function
-doSomething(import.meta.hot.dispose);
-
-// OK: The full phrase "import.meta.hot.<API>" must be called directly:
-import.meta.hot.accept();
-
-// OK: `data` can be passed to functions:
-doSomething(import.meta.hot.data);
-```
-
-{% callout %}
-
-**Note** — The HMR API is still a work in progress. Some features are missing. HMR can be disabled in `Bun.serve` by setting the `development` option to `{ hmr: false }`.
-
-{% endcallout %}
-
-|     | Method             | Notes                                                                 |
-| --- | ------------------ | --------------------------------------------------------------------- |
-| ✅  | `hot.accept()`     | Indicate that a hot update can be replaced gracefully.                |
-| ✅  | `hot.data`         | Persist data between module evaluations.                              |
-| ✅  | `hot.dispose()`    | Add a callback function to run when a module is about to be replaced. |
-| ❌  | `hot.invalidate()` |                                                                       |
-| ✅  | `hot.on()`         | Attach an event listener                                              |
-| ✅  | `hot.off()`        | Remove an event listener from `on`.                                   |
-| ❌  | `hot.send()`       |                                                                       |
-| 🚧  | `hot.prune()`      | **NOTE**: Callback is currently never called.                         |
-| ✅  | `hot.decline()`    | No-op to match Vite's `import.meta.hot`                               |
-
-### `import.meta.hot.accept()`
-
-The `accept()` method indicates that a module can be hot-replaced. When called
-without arguments, it indicates that this module can be replaced simply by
-re-evaluating the file. After a hot update, importers of this module will be
-automatically patched.
-
-```ts#index.ts
-import { getCount } from "./foo.ts";
-
-console.log("count is ", getCount());
-
-import.meta.hot.accept();
-
-export function getNegativeCount() {
-  return -getCount();
-}
-```
-
-This creates a hot-reloading boundary for all of the files that `index.ts`
-imports. That means whenever `foo.ts` or any of its dependencies are saved, the
-update will bubble up to `index.ts` will re-evaluate. Files that import
-`index.ts` will then be patched to import the new version of
-`getNegativeCount()`. If only `index.ts` is updated, only the one file will be
-re-evaluated, and the counter in `foo.ts` is reused.
-
-This may be used in combination with `import.meta.hot.data` to transfer state
-from the previous module to the new one.
-
-When no modules call `import.meta.hot.accept()` (and there isn't React Fast
-Refresh or a plugin calling it for you), the page will reload when the file
-updates, and a console warning shows which files were invalidated. This warning
-is safe to ignore if it makes more sense to rely on full page reloads.
-
-#### With callback
-
-When provided one callback, `import.meta.hot.accept` will function how it does
-in Vite. Instead of patching the importers of this module, it will call the
-callback with the new module.
-
-```ts
-export const count = 0;
-
-import.meta.hot.accept(newModule => {
-  if (newModule) {
-    // newModule is undefined when SyntaxError happened
-    console.log("updated: count is now ", newModule.count);
-  }
-});
-```
-
-Prefer using `import.meta.hot.accept()` without an argument as it usually makes your code easier to understand.
-
-#### Accepting other modules
-
-```ts
-import { count } from "./foo";
-
-import.meta.hot.accept("./foo", () => {
-  if (!newModule) return;
-
-  console.log("updated: count is now ", count);
-});
-```
-
-Indicates that a dependency's module can be accepted. When the dependency is updated, the callback will be called with the new module.
-
-#### With multiple dependencies
-
-```ts
-import.meta.hot.accept(["./foo", "./bar"], newModules => {
-  // newModules is an array where each item corresponds to the updated module
-  // or undefined if that module had a syntax error
-});
-```
-
-Indicates that multiple dependencies' modules can be accepted. This variant accepts an array of dependencies, where the callback will receive the updated modules, and `undefined` for any that had errors.
-
-### `import.meta.hot.data`
-
-`import.meta.hot.data` maintains state between module instances during hot
-replacement, enabling data transfer from previous to new versions. When
-`import.meta.hot.data` is written into, Bun will also mark this module as
-capable of self-accepting (equivalent of calling `import.meta.hot.accept()`).
-
-```ts
-import { createRoot } from "react-dom/client";
-import { App } from "./app";
-
-const root = import.meta.hot.data.root ??= createRoot(elem);
-root.render(<App />); // re-use an existing root
-```
-
-In production, `data` is inlined to be `{}`, meaning it cannot be used as a state holder.
-
-The above pattern is recommended for stateful modules because Bun knows it can minify `{}.prop ??= value` into `value` in production.
-
-### `import.meta.hot.dispose()`
-
-Attaches an on-dispose callback. This is called:
-
-- Just before the module is replaced with another copy (before the next is loaded)
-- After the module is detached (removing all imports to this module, see `import.meta.hot.prune()`)
-
-```ts
-const sideEffect = setupSideEffect();
-
-import.meta.hot.dispose(() => {
-  sideEffect.cleanup();
-});
-```
-
-This callback is not called on route navigation or when the browser tab closes.
-
-Returning a promise will delay module replacement until the module is disposed.
-All dispose callbacks are called in parallel.
-
-### `import.meta.hot.prune()`
-
-Attaches an on-prune callback. This is called when all imports to this module
-are removed, but the module was previously loaded.
-
-This can be used to clean up resources that were created when the module was
-loaded. Unlike `import.meta.hot.dispose()`, this pairs much better with `accept`
-and `data` to manage stateful resources. A full example managing a `WebSocket`:
-
-```ts
-import { something } from "./something";
-
-// Initialize or re-use a WebSocket connection
-export const ws = (import.meta.hot.data.ws ??= new WebSocket(location.origin));
-
-// If the module's import is removed, clean up the WebSocket connection.
-import.meta.hot.prune(() => {
-  ws.close();
-});
-```
-
-If `dispose` was used instead, the WebSocket would close and re-open on every
-hot update. Both versions of the code will prevent page reloads when imported
-files are updated.
-
-### `import.meta.hot.on()` and `off()`
-
-`on()` and `off()` are used to listen for events from the HMR runtime. Event names are prefixed with a prefix so that plugins do not conflict with each other.
-
-```ts
-import.meta.hot.on("bun:beforeUpdate", () => {
-  console.log("before a hot update");
-});
-```
-
-When a file is replaced, all of its event listeners are automatically removed.
-
-A list of all built-in events:
-
-| Event                  | Emitted when                                                                                    |
-| ---------------------- | ----------------------------------------------------------------------------------------------- |
-| `bun:beforeUpdate`     | before a hot update is applied.                                                                 |
-| `bun:afterUpdate`      | after a hot update is applied.                                                                  |
-| `bun:beforeFullReload` | before a full page reload happens.                                                              |
-| `bun:beforePrune`      | before prune callbacks are called.                                                              |
-| `bun:invalidate`       | when a module is invalidated with `import.meta.hot.invalidate()`                                |
-| `bun:error`            | when a build or runtime error occurs                                                            |
-| `bun:ws:disconnect`    | when the HMR WebSocket connection is lost. This can indicate the development server is offline. |
-| `bun:ws:connect`       | when the HMR WebSocket connects or re-connects.                                                 |
-
-For compatibility with Vite, the above events are also available via `vite:*` prefix instead of `bun:*`.

docs/bundler/html.md

@@ -301,6 +301,6 @@ This is a small wrapper around Bun's support for HTML imports in JavaScript.
 
 ### Adding a backend to your frontend
 
-To add a backend to your frontend, you can use the `"routes"` option in `Bun.serve`.
+To add a backend to your frontend, you can use the `"static"` option in `Bun.serve`.
 
 Learn more in [the full-stack docs](/docs/bundler/fullstack).

docs/bundler/index.md

@@ -1629,5 +1629,3 @@ declare class ResolveMessage {
   toString(): string;
 }
 ```
-
-{% bunCLIUsage command="build" /%}

docs/bundler/loaders.md

@@ -4,12 +4,6 @@ The Bun bundler implements a set of default loaders out of the box. As a rule of
 
 Bun uses the file extension to determine which built-in _loader_ should be used to parse the file. Every loader has a name, such as `js`, `tsx`, or `json`. These names are used when building [plugins](https://bun.sh/docs/bundler/plugins) that extend Bun with custom loaders.
 
-You can explicitly specify which loader to use using the 'loader' import attribute.
-
-```ts
-import my_toml from "./my_file" with { loader: "toml" };
-```
-
 ## Built-in loaders
 
 ### `js`
@@ -198,6 +192,8 @@ Otherwise, the database to embed is copied into the `outdir` with a hashed filen
 
 ### `html`
 
+**HTML loader**. Default for `.html` after Bun v1.2.0.
+
 The html loader processes HTML files and bundles any referenced assets. It will:
 
 - Bundle and hash referenced JavaScript files (`<script src="...">`)

docs/cli/add.md

@@ -169,5 +169,3 @@ This will add the following line to your `package.json`:
   }
 }
 ```
-
-{% bunCLIUsage command="add" /%}

docs/cli/bun-create.md

@@ -2,97 +2,10 @@
 **Note** — You don’t need `bun create` to use Bun. You don’t need any configuration at all. This command exists to make getting started a bit quicker and easier.
 {% /callout %}
 
-Template a new Bun project with `bun create`. This is a flexible command that can be used to create a new project from a React component, a `create-<template>` npm package, a GitHub repo, or a local template.
+Template a new Bun project with `bun create`. This is a flexible command that can be used to create a new project with a `create-<template>` npm package, a GitHub repo, or a local template.
 
 If you're looking to create a brand new empty project, use [`bun init`](https://bun.sh/docs/cli/init).
 
-## From a React component
-
-`bun create ./MyComponent.tsx` turns an existing React component into a complete dev environment with hot reload and production builds in one command.
-
-```bash
-$ bun create ./MyComponent.jsx # .tsx also supported
-```
-
-{% raw %}
-
-<video style="aspect-ratio: 2062 / 1344; width: 100%; height: 100%; object-fit: contain;"  loop autoplay muted playsinline>
-  <source src="/bun-create-shadcn.mp4" style="width: 100%; height: 100%; object-fit: contain;" type="video/mp4">
-</video>
-
-{% /raw %}
-
-{% callout %}
-🚀 **Create React App Successor** — `bun create <component>` provides everything developers loved about Create React App, but with modern tooling, faster builds, and backend support.
-{% /callout %}
-
-#### How this works
-
-When you run `bun create <component>`, Bun:
-
-1. Uses [Bun's JavaScript bundler](https://bun.sh/docs/bundler) to analyze your module graph.
-2. Collects all the dependencies needed to run the component.
-3. Scans the exports of the entry point for a React component.
-4. Generates a `package.json` file with the dependencies and scripts needed to run the component.
-5. Installs any missing dependencies using [`bun install --only-missing`](https://bun.sh/docs/cli/install).
-6. Generates the following files:
-   - `${component}.html`
-   - `${component}.client.tsx` (entry point for the frontend)
-   - `${component}.css` (css file)
-7. Starts a frontend dev server automatically.
-
-### Using TailwindCSS with Bun
-
-[TailwindCSS](https://tailwindcss.com/) is an extremely popular utility-first CSS framework used to style web applications.
-
-When you run `bun create <component>`, Bun scans your JSX/TSX file for TailwindCSS class names (and any files it imports). If it detects TailwindCSS class names, it will add the following dependencies to your `package.json`:
-
-```json#package.json
-{
-  "dependencies": {
-    "tailwindcss": "^4",
-    "bun-plugin-tailwind": "latest"
-  }
-}
-```
-
-We also configure `bunfig.toml` to use Bun's TailwindCSS plugin with `Bun.serve()`
-
-```toml#bunfig.toml
-[serve.static]
-plugins = ["bun-plugin-tailwind"]
-```
-
-And a `${component}.css` file with `@import "tailwindcss";` at the top:
-
-```css#MyComponent.css
-@import "tailwindcss";
-```
-
-### Using `shadcn/ui` with Bun
-
-[`shadcn/ui`](https://ui.shadcn.com/) is an extremely popular component library tool for building web applications.
-
-`bun create <component>` scans for any shadcn/ui components imported from `@/components/ui`.
-
-If it finds any, it runs:
-
-```bash
-# Assuming bun detected imports to @/components/ui/accordion and @/components/ui/button
-$ bunx shadcn@canary add accordion button # and any other components
-```
-
-Since `shadcn/ui` itself uses TailwindCSS, `bun create` also adds the necessary TailwindCSS dependencies to your `package.json` and configures `bunfig.toml` to use Bun's TailwindCSS plugin with `Bun.serve()` as described above.
-
-Additionally, we setup the following:
-
-- `tsconfig.json` to alias `"@/*"` to `"src/*"` or `.` (depending on if there is a `src/` directory)
-- `components.json` so that shadcn/ui knows its a shadcn/ui project
-- `styles/globals.css` file that configures Tailwind v4 in the way that shadcn/ui expects
-- `${component}.build.ts` file that builds the component for production with `bun-plugin-tailwind` configured
-
-`bun create ./MyComponent.jsx` is one of the easiest ways to run code generated from LLMs like [Claude](https://claude.ai) or ChatGPT locally.
-
 ## From `npm`
 
 ```sh

docs/cli/bun-dev.md

@@ -0,0 +1,21 @@
+In your project folder root (where `package.json` is):
+
+```bash
+$ bun bun ./entry-point-1.js ./entry-point-2.jsx
+$ bun dev
+```
+
+By default, `bun dev` will look for any HTML files in the `public` directory and serve that. For browsers navigating to the page, the `.html` file extension is optional in the URL, and `index.html` will automatically rewrite for the directory.
+
+Here are examples of routing from `public/` and how they’re matched:
+| Dev Server URL | File Path |
+|----------------|-----------|
+| /dir | public/dir/index.html |
+| / | public/index.html |
+| /index | public/index.html |
+| /hi | public/hi.html |
+| /file | public/file.html |
+| /font/Inter.woff2 | public/font/Inter.woff2 |
+| /hello | public/index.html |
+
+If `public/index.html` exists, it becomes the default page instead of a 404 page, unless that pathname has a file extension.

docs/cli/init.md

@@ -38,5 +38,3 @@ If you pass `-y` or `--yes`, it will assume you want to continue without asking
 At the end, it runs `bun install` to install `@types/bun`.
 
 {% /details %}
-
-{% bunCLIUsage command="init" /%}

docs/cli/install.md

@@ -235,5 +235,3 @@ jobs:
       - name: Build app
         run: bun run build
 ```
-
-{% bunCLIUsage command="install" /%}

docs/cli/link.md

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

docs/cli/outdated.md

@@ -1,47 +1,63 @@
-Use `bun outdated` to check for outdated dependencies in your project. This command displays a table of dependencies that have newer versions available.
+Use `bun outdated` to display a table of outdated dependencies with their latest versions for the current workspace:
 
-{% bunOutdatedTerminal displayGlob="" filter="" glob="" /%}
+```sh
+$ bun outdated
 
-## Version Information
+|--------------------------------------------------------------------|
+| Package                                | Current | Update | Latest |
+|----------------------------------------|---------|--------|--------|
+| @types/bun (dev)                       | 1.1.6   | 1.1.7  | 1.1.7  |
+|----------------------------------------|---------|--------|--------|
+| @types/react (dev)                     | 18.3.3  | 18.3.4 | 18.3.4 |
+|----------------------------------------|---------|--------|--------|
+| @typescript-eslint/eslint-plugin (dev) | 7.16.1  | 7.18.0 | 8.2.0  |
+|----------------------------------------|---------|--------|--------|
+| @typescript-eslint/parser (dev)        | 7.16.1  | 7.18.0 | 8.2.0  |
+|----------------------------------------|---------|--------|--------|
+| esbuild (dev)                          | 0.21.5  | 0.21.5 | 0.23.1 |
+|----------------------------------------|---------|--------|--------|
+| eslint (dev)                           | 9.7.0   | 9.9.1  | 9.9.1  |
+|----------------------------------------|---------|--------|--------|
+| typescript (dev)                       | 5.5.3   | 5.5.4  | 5.5.4  |
+|--------------------------------------------------------------------|
+```
 
-The output table shows three version columns:
+The `Update` column shows the version that would be installed if you ran `bun update [package]`. This version is the latest version that satisfies the version range specified in your `package.json`.
 
-- **Current**: The version currently installed
-- **Update**: The latest version that satisfies your package.json version range
-- **Latest**: The latest version published to the registry
+The `Latest` column shows the latest version available from the registry. `bun update --latest [package]` will update to this version.
 
-### Dependency Filters
+Dependency names can be provided to filter the output (pattern matching is supported):
 
-`bun outdated` supports searching for outdated dependencies by package names and glob patterns.
+```sh
+$ bun outdated "@types/*"
 
-To check if specific dependencies are outdated, pass the package names as positional arguments:
+|------------------------------------------------|
+| Package            | Current | Update | Latest |
+|--------------------|---------|--------|--------|
+| @types/bun (dev)   | 1.1.6   | 1.1.8  | 1.1.8  |
+|--------------------|---------|--------|--------|
+| @types/react (dev) | 18.3.3  | 18.3.4 | 18.3.4 |
+|------------------------------------------------|
+```
 
-{% bunOutdatedTerminal displayGlob="eslint-plugin-security eslint-plugin-sonarjs" glob="eslint-plugin-*"  /%}
+## `--filter`
 
-You can also pass glob patterns to check for outdated packages:
+The `--filter` flag can be used to select workspaces to include in the output. Workspace names or paths can be used as patterns.
 
-{% bunOutdatedTerminal displayGlob="'eslint*'" glob="eslint*"  /%}
+```sh
+$ bun outdated --filter <pattern>
+```
 
-For example, to check for outdated `@types/*` packages:
+For example, to only show outdated dependencies for workspaces in the `./apps` directory:
 
-{% bunOutdatedTerminal displayGlob="'@types/*'" glob="@types/*"  /%}
+```sh
+$ bun outdated --filter './apps/*'
+```
 
-Or to exclude all `@types/*` packages:
+If you want to do the same, but exclude the `./apps/api` workspace:
 
-{% bunOutdatedTerminal displayGlob="'!@types/*'" glob="!@types/*"  /%}
+```sh
+$ bun outdated --filter './apps/*' --filter '!./apps/api'
+```
 
-### Workspace Filters
-
-Use the `--filter` flag to check for outdated dependencies in a different workspace package:
-
-{% bunOutdatedTerminal  glob="t*" filter="@monorepo/types"  /%}
-
-You can pass multiple `--filter` flags to check multiple workspaces:
-
-{% bunOutdatedTerminal  glob="{e,t}*" displayGlob="--filter @monorepo/types --filter @monorepo/cli" /%}
-
-You can also pass glob patterns to filter by workspace names:
-
-{% bunOutdatedTerminal  glob="{e,t}*" displayGlob="--filter='@monorepo/{types,cli}'" /%}
-
-{% bunCLIUsage command="outdated" /%}
+Refer to [Package Manager > Filtering](https://bun.sh/docs/cli/filter#bun-install-and-bun-outdated) for more information on `--filter`.

docs/cli/patch-commit.md

@@ -7,5 +7,3 @@ To get started with patch, first prepare the package for patching with [`bun pat
 By default, `bun patch-commit` will use the `patches` directory in the temporary directory.
 
 You can specify a different directory with the `--patches-dir` flag.
-
-{% bunCLIUsage command="patch-commit" /%}

docs/cli/pm.md

@@ -12,12 +12,9 @@ Options for the `pack` command:
 
 - `--dry-run`: Perform all tasks except writing the tarball to disk.
 - `--destination`: Specify the directory where the tarball will be saved.
-- `--filename`: Specify an exact file name for the tarball to be saved at.
 - `--ignore-scripts`: Skip running pre/postpack and prepare scripts.
 - `--gzip-level`: Set a custom compression level for gzip, ranging from 0 to 9 (default is 9).
 
-> Note `--filename` and `--destination` cannot be used at the same time
-
 ## bin
 
 To print the path to the `bin` directory for the local project:

docs/cli/publish.md

@@ -82,11 +82,6 @@ The `--dry-run` flag can be used to simulate the publish process without actuall
 $ bun publish --dry-run
 ```
 
-### `--gzip-level`
-
-Specify the level of gzip compression to use when packing the package. Only applies to `bun publish` without a tarball path argument. Values range from `0` to `9` (default is `9`).
-{% bunCLIUsage command="publish" /%}
-
 ### `--auth-type`
 
 If you have 2FA enabled for your npm account, `bun publish` will prompt you for a one-time password. This can be done through a browser or the CLI. The `--auth-type` flag can be used to tell the npm registry which method you prefer. The possible values are `web` and `legacy`, with `web` being the default.
@@ -107,6 +102,6 @@ Provide a one-time password directly to the CLI. If the password is valid, this
 $ bun publish --otp 123456
 ```
 
-{% callout %}
-**Note** - `bun publish` respects the `NPM_CONFIG_TOKEN` environment variable which can be used when publishing in github actions or automated workflows.
-{% /callout %}
+### `--gzip-level`
+
+Specify the level of gzip compression to use when packing the package. Only applies to `bun publish` without a tarball path argument. Values range from `0` to `9` (default is `9`).

docs/cli/remove.md

@@ -3,5 +3,3 @@ To remove a dependency:
 ```bash
 $ bun remove ts-node
 ```
-
-{% bunCLIUsage command="remove" /%}

docs/cli/run.md

@@ -205,5 +205,3 @@ When there is a package.json script and a file with the same name, `bun run` pri
 2. Source files, eg `bun run src/main.js`
 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" /%}

docs/cli/test.md

@@ -247,5 +247,3 @@ $ bun test foo
 ```
 
 Any test file in the directory with an _absolute path_ that contains one of the targets will run. Glob patterns are not yet supported. -->
-
-{% bunCLIUsage command="test" /%}

docs/cli/unlink.md

@@ -5,5 +5,3 @@ $ cd /path/to/cool-pkg
 $ bun unlink
 bun unlink v1.x (7416672e)
 ```
-
-{% bunCLIUsage command="unlink" /%}

docs/cli/update.md

@@ -32,5 +32,3 @@ 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" /%}

docs/guides/ecosystem/render.md

@@ -70,7 +70,7 @@ In the Render UI, provide the following values during web service creation:
 | ----------------- | ------------- |
 | **Runtime**       | `Node`        |
 | **Build Command** | `bun install` |
-| **Start Command** | `bun app.ts`  |
+| **Start Command** | `bun app.js`  |
 
 ---
 

docs/guides/html-rewriter/extract-links.md

@@ -1,68 +0,0 @@
----
-name: Extract links from a webpage using HTMLRewriter
----
-
-## Extract links from a webpage
-
-Bun's [HTMLRewriter](https://bun.sh/docs/api/html-rewriter) API can be used to efficiently extract links from HTML content. It works by chaining together CSS selectors to match the elements, text, and attributes you want to process. This is a simple example of how to extract links from a webpage. You can pass `.transform` a `Response`, `Blob`, or `string`.
-
-```ts
-async function extractLinks(url: string) {
-  const links = new Set<string>();
-  const response = await fetch(url);
-
-  const rewriter = new HTMLRewriter().on("a[href]", {
-    element(el) {
-      const href = el.getAttribute("href");
-      if (href) {
-        links.add(href);
-      }
-    },
-  });
-
-  // Wait for the response to be processed
-  await rewriter.transform(response).blob();
-  console.log([...links]); // ["https://bun.sh", "/docs", ...]
-}
-
-// Extract all links from the Bun website
-await extractLinks("https://bun.sh");
-```
-
----
-
-## Convert relative URLs to absolute
-
-When scraping websites, you often want to convert relative URLs (like `/docs`) to absolute URLs. Here's how to handle URL resolution:
-
-```ts
-async function extractLinksFromURL(url: string) {
-  const response = await fetch(url);
-  const links = new Set<string>();
-
-  const rewriter = new HTMLRewriter().on("a[href]", {
-    element(el) {
-      const href = el.getAttribute("href");
-      if (href) {
-        // Convert relative URLs to absolute
-        try {
-          const absoluteURL = new URL(href, url).href;
-          links.add(absoluteURL);
-        } catch {
-          links.add(href);
-        }
-      }
-    },
-  });
-
-  // Wait for the response to be processed
-  await rewriter.transform(response).blob();
-  return [...links];
-}
-
-const websiteLinks = await extractLinksFromURL("https://example.com");
-```
-
----
-
-See [Docs > API > HTMLRewriter](https://bun.sh/docs/api/html-rewriter) for complete documentation on HTML transformation with Bun.

docs/guides/html-rewriter/extract-social-meta.md

@@ -1,93 +0,0 @@
----
-name: Extract social share images and Open Graph tags
----
-
-## Extract social share images and Open Graph tags
-
-Bun's [HTMLRewriter](https://bun.sh/docs/api/html-rewriter) API can be used to efficiently extract social share images and Open Graph metadata from HTML content. This is particularly useful for building link preview features, social media cards, or web scrapers. We can use HTMLRewriter to match CSS selectors to HTML elements, text, and attributes we want to process.
-
-```ts
-interface SocialMetadata {
-  title?: string;
-  description?: string;
-  image?: string;
-  url?: string;
-  siteName?: string;
-  type?: string;
-}
-
-async function extractSocialMetadata(url: string): Promise<SocialMetadata> {
-  const metadata: SocialMetadata = {};
-  const response = await fetch(url);
-
-  const rewriter = new HTMLRewriter()
-    // Extract Open Graph meta tags
-    .on('meta[property^="og:"]', {
-      element(el) {
-        const property = el.getAttribute("property");
-        const content = el.getAttribute("content");
-        if (property && content) {
-          // Convert "og:image" to "image" etc.
-          const key = property.replace("og:", "") as keyof SocialMetadata;
-          metadata[key] = content;
-        }
-      },
-    })
-    // Extract Twitter Card meta tags as fallback
-    .on('meta[name^="twitter:"]', {
-      element(el) {
-        const name = el.getAttribute("name");
-        const content = el.getAttribute("content");
-        if (name && content) {
-          const key = name.replace("twitter:", "") as keyof SocialMetadata;
-          // Only use Twitter Card data if we don't have OG data
-          if (!metadata[key]) {
-            metadata[key] = content;
-          }
-        }
-      },
-    })
-    // Fallback to regular meta tags
-    .on('meta[name="description"]', {
-      element(el) {
-        const content = el.getAttribute("content");
-        if (content && !metadata.description) {
-          metadata.description = content;
-        }
-      },
-    })
-    // Fallback to title tag
-    .on("title", {
-      text(text) {
-        if (!metadata.title) {
-          metadata.title = text.text;
-        }
-      },
-    });
-
-  // Process the response
-  await rewriter.transform(response).blob();
-
-  // Convert relative image URLs to absolute
-  if (metadata.image && !metadata.image.startsWith("http")) {
-    try {
-      metadata.image = new URL(metadata.image, url).href;
-    } catch {
-      // Keep the original URL if parsing fails
-    }
-  }
-
-  return metadata;
-}
-
-// Example usage
-const metadata = await extractSocialMetadata("https://bun.sh");
-console.log(metadata);
-// {
-//   title: "Bun — A fast all-in-one JavaScript runtime",
-//   description: "Bundle, transpile, install and run JavaScript & TypeScript projects — all in Bun. Bun is a fast all-in-one JavaScript runtime & toolkit designed for speed, complete with a bundler, test runner, and Node.js-compatible package manager.",
-//   image: "https://bun.sh/share.jpg",
-//   type: "website",
-//   ...
-// }
-```

docs/guides/html-rewriter/index.json

@@ -1,4 +0,0 @@
-{
-  "name": "HTMLRewriter",
-  "description": "A collection of guides for using the HTMLRewriter streaming HTML parser with Bun"
-}

docs/guides/runtime/codesign-macos-executable.md

@@ -1,56 +0,0 @@
----
-name: Codesign a single-file JavaScript executable on macOS
-description: Fix the "can't be opened because it is from an unidentified developer" Gatekeeper warning when running your JavaScript executable.
----
-
-Compile your executable using the `--compile` flag.
-
-```sh
-$ bun build --compile ./path/to/entry.ts --outfile myapp
-```
-
----
-
-List your available signing identities. One of these will be your signing identity that you pass to the `codesign` command. This command requires macOS.
-
-```sh
-$ security find-identity -v -p codesigning
-1. XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX "Developer ID Application: Your Name (ZZZZZZZZZZ)"
-   1 valid identities found
-```
-
----
-
-Optional, but recommended: create an `entitlements.plist` file with the necessary permissions for the JavaScript engine to work correctly.
-
-```xml#entitlements.plist
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
-<plist version="1.0">
-<dict>
-    <key>com.apple.security.cs.allow-jit</key>
-    <true/>
-    <key>com.apple.security.cs.allow-unsigned-executable-memory</key>
-    <true/>
-    <key>com.apple.security.cs.disable-executable-page-protection</key>
-    <true/>
-    <key>com.apple.security.cs.allow-dyld-environment-variables</key>
-    <true/>
-    <key>com.apple.security.cs.disable-library-validation</key>
-    <true/>
-</dict>
-</plist>
-```
-
----
-
-Sign your executable using the `codesign` command and verify it works.
-
-```bash
-$ codesign --entitlements entitlements.plist -vvvv --deep --sign "XXXXXXXXXX" ./myapp --force
-$ codesign -vvv --verify ./myapp
-```
-
----
-
-For more information on macOS codesigning, refer to [Apple's Code Signing documentation](https://developer.apple.com/documentation/security/code_signing_services). For details about creating single-file executables with Bun, see [Standalone Executables](/docs/bundler/executables). This guide requires Bun v1.2.4 or newer.

docs/guides/runtime/delete-directory.md

@@ -1,37 +0,0 @@
----
-name: Delete directories
----
-
-To recursively delete a directory and all its contents, use `rm` from `node:fs/promises`. This is like running `rm -rf` in JavaScript.
-
-```ts
-import { rm } from "node:fs/promises";
-
-// Delete a directory and all its contents
-await rm("path/to/directory", { recursive: true, force: true });
-```
-
----
-
-These options configure the deletion behavior:
-
-- `recursive: true` - Delete subdirectories and their contents
-- `force: true` - Don't throw errors if the directory doesn't exist
-
-You can also use it without `force` to ensure the directory exists:
-
-```ts
-try {
-  await rm("path/to/directory", { recursive: true });
-} catch (error) {
-  if (error.code === "ENOENT") {
-    console.log("Directory doesn't exist");
-  } else {
-    throw error;
-  }
-}
-```
-
----
-
-See [Docs > API > FileSystem](https://bun.sh/docs/api/file-io) for more filesystem operations.

docs/guides/runtime/delete-file.md

@@ -1,19 +0,0 @@
----
-name: Delete files
----
-
-To delete a file, use `Bun.file(path).delete()`.
-
-```ts
-// Delete a file
-const file = Bun.file("path/to/file.txt");
-await file.delete();
-
-// Now the file doesn't exist
-const exists = await file.exists();
-// => false
-```
-
----
-
-See [Docs > API > FileSystem](https://bun.sh/docs/api/file-io) for more filesystem operations.

docs/guides/runtime/heap-snapshot.md

@@ -1,26 +0,0 @@
----
-name: Inspect memory usage using V8 heap snapshots
----
-
-Bun implements V8's heap snapshot API, which allows you to create snapshots of the heap at runtime. This helps debug memory leaks in your JavaScript/TypeScript application.
-
-```ts#snapshot.ts
-import v8 from "node:v8";
-
-// Creates a heap snapshot file with an auto-generated name
-const snapshotPath = v8.writeHeapSnapshot();
-console.log(`Heap snapshot written to: ${snapshotPath}`);
-```
-
----
-
-## Inspect memory in Chrome DevTools
-
-To view V8 heap snapshots in Chrome DevTools:
-
-1. Open Chrome DevTools (F12 or right-click and select "Inspect")
-2. Go to the "Memory" tab
-3. Click the "Load" button (folder icon)
-4. Select your `.heapsnapshot` file
-
-{% image src="/images/chrome-devtools-memory.png" alt="Chrome DevTools Memory Tab" width="100%" /%}

docs/guides/runtime/set-env.md

@@ -28,21 +28,10 @@ BAR=world
 
 Variables can also be set via the command line.
 
-{% codetabs %}
-
-```sh#Linux/macOS
+```sh
 $ FOO=helloworld bun run dev
 ```
 
-```sh#Windows
-# Using CMD
-$ set FOO=helloworld && bun run dev
-
-# Using PowerShell
-$ $env:FOO="helloworld"; bun run dev
-```
-
-{% /codetabs %}
 ---
 
 See [Docs > Runtime > Environment variables](https://bun.sh/docs/runtime/env) for more information on using environment variables with Bun.

docs/guides/runtime/vscode-debugger.md

@@ -8,7 +8,7 @@ VSCode extension support is currently buggy. We recommend the [Web Debugger](htt
 
 {% /note %}
 
-Bun speaks the [WebKit Inspector Protocol](https://github.com/oven-sh/bun/blob/main/packages/bun-inspector-protocol/src/protocol/jsc/index.d.ts) so you can debug your code with an interactive debugger.
+Bun speaks the [WebKit Inspector Protocol](https://github.com/oven-sh/bun/blob/main/packages/bun-vscode/types/jsc.d.ts) so you can debug your code with an interactive debugger.
 
 ---
 

docs/install/lockfile.md

@@ -1,5 +1,7 @@
 Running `bun install` will create a lockfile called `bun.lock`.
 
+https://bun.sh/blog/bun-lock-text-lockfile
+
 #### Should it be committed to git?
 
 Yes

docs/install/patch.md

@@ -55,5 +55,3 @@ $ bun patch --commit react --patches-dir=mypatches
 # `patch-commit` is available for compatibility with pnpm
 $ bun patch-commit react
 ```
-
-{% bunCLIUsage command="patch" /%}

docs/install/workspaces.md

@@ -63,20 +63,6 @@ $ bun install --filter "pkg-*" --filter "!pkg-c"
 $ bun install --filter "./packages/pkg-*" --filter "!pkg-c" # or --filter "!./packages/pkg-c"
 ```
 
-When publishing, `workspace:` versions are replaced by the package's `package.json` version,
-
-```
-"workspace:*" -> "1.0.1"
-"workspace:^" -> "^1.0.1"
-"workspace:~" -> "~1.0.1"
-```
-
-Setting a specific version takes precedence over the package's `package.json` version,
-
-```
-"workspace:1.0.2" -> "1.0.2" // Even if current version is 1.0.1
-```
-
 Workspaces have a couple major benefits.
 
 - **Code can be split into logical parts.** If one package relies on another, you can simply add it as a dependency in `package.json`. If package `b` depends on `a`, `bun install` will install your local `packages/a` directory into `node_modules` instead of downloading it from the npm registry.

docs/installation.md

@@ -94,9 +94,7 @@ $ bun --revision
 
 If you've installed Bun but are seeing a `command not found` error, you may have to manually add the installation directory (`~/.bun/bin`) to your `PATH`.
 
-### How to add your `PATH`
-
-{% details summary="Linux / Mac" %}
+{% details summary="How to add to your `PATH`" %}
 First, determine what shell you're using:
 
 ```sh
@@ -131,27 +129,6 @@ Save the file. You'll need to open a new shell/terminal window for the changes t
 
 {% /details %}
 
-{% details summary="Windows" %}
-First, determine if the bun binary is properly installed on your system:
-
-```pwsh
-& "$env:USERPROFILE\.bun\bin\bun" --version
-```
-
-If the command runs successfully but `bun --version` is not recognized, it means that bun is not in your system's `PATH`. To fix this, open a Powershell terminal and run the following command:
-
-```pwsh
-[System.Environment]::SetEnvironmentVariable(
-    "Path",
-    [System.Environment]::GetEnvironmentVariable("Path", "User") + ";$env:USERPROFILE\.bun\bin",
-    [System.EnvironmentVariableTarget]::User
-)
-```
-
-After running the command, restart your terminal and test with `bun --version`
-
-{% /details %}
-
 ## Upgrading
 
 Once installed, the binary can upgrade itself.
@@ -220,12 +197,11 @@ For convenience, here are download links for the latest version:
 - [`bun-linux-aarch64.zip`](https://github.com/oven-sh/bun/releases/latest/download/bun-linux-aarch64.zip)
 - [`bun-linux-aarch64-musl.zip`](https://github.com/oven-sh/bun/releases/latest/download/bun-linux-aarch64-musl.zip)
 - [`bun-darwin-x64.zip`](https://github.com/oven-sh/bun/releases/latest/download/bun-darwin-x64.zip)
+- [`bun-darwin-x64-baseline.zip`](https://github.com/oven-sh/bun/releases/latest/download/bun-darwin-x64-baseline.zip)
 
 The `musl` binaries are built for distributions that do not ship with the glibc libraries by default, instead relying on musl. The two most popular distros are Void Linux and Alpine Linux, with the latter is used heavily in Docker containers. If you encounter an error like the following: `bun: /lib/x86_64-linux-gnu/libm.so.6: version GLIBC_2.29' not found (required by bun)`, try using the musl binary. Bun's install script automatically chooses the correct binary for your system.
 
-Bun's `x64` binaries target the Haswell CPU architecture, which means they require AVX and AVX2 instructions. For Linux and Windows, the `x64-baseline` binaries are also available which target the Nehalem architecture. If you run into an "Illegal Instruction" error when running Bun, try using the `baseline` binaries instead. Bun's install scripts automatically chooses the correct binary for your system which helps avoid this issue. Baseline builds are slower than regular builds, so use them only if necessary.
-
-Bun also publishes `darwin-x64-baseline` binaries, but these are just a copy of the `darwin-x64` ones so they still have the same CPU requirement. We only maintain these since some tools expect them to exist. Bun requires macOS 13.0 or later, which does not support any CPUs that don't meet our requirement.
+The `baseline` binaries are built for older CPUs which may not support AVX2 instructions. If you run into an "Illegal Instruction" error when running Bun, try using the `baseline` binaries instead. Bun's install scripts automatically chooses the correct binary for your system which helps avoid this issue. Baseline builds are slower than regular builds, so use them only if necessary.
 
 <!--
 ## Native

docs/nav.ts

@@ -27,7 +27,7 @@ export default {
     divider("Intro"),
     page("index", "What is Bun?", {
       description:
-        "Bun is an all-in-one runtime for JavaScript and TypeScript apps. Build, run, and test apps with one fast tool.",
+        "Bun is an all-in-one runtime for JavaScript and TypeScript apps. Run, bundle, and test apps with one fast tool.",
     }),
     page("installation", "Installation", {
       description: "Install Bun with npm, Homebrew, Docker, or the official install script.",
@@ -181,7 +181,7 @@ export default {
         "Bun's package manager installs all packages into a shared global cache to avoid redundant re-downloads.",
     }),
     page("install/workspaces", "Workspaces", {
-      description: "Bun's package manager supports workspaces and monorepo development workflows.",
+      description: "Bun's package manager supports workspaces and mono-repo development workflows.",
     }),
     page("install/lifecycle", "Lifecycle scripts", {
       description: "How Bun handles package lifecycle scripts with trustedDependencies",
@@ -194,8 +194,7 @@ export default {
         "Bun's lockfile `bun.lock` tracks your resolved dependency tree, making future installs fast and repeatable.",
     }),
     page("install/registries", "Scopes and registries", {
-      description:
-        "How to configure private scopes, custom package registries, authenticating with npm token, and more.",
+      description: "How to configure private scopes and custom package registries.",
     }),
     page("install/overrides", "Overrides and resolutions", {
       description: "Specify version ranges for nested dependencies",
@@ -215,19 +214,12 @@ export default {
     page("bundler", "`Bun.build`", {
       description: "Bundle code for consumption in the browser with Bun's native bundler.",
     }),
-    page("bundler/html", "HTML & static sites", {
-      description: `Zero-config HTML bundler for single-page apps and multi-page apps. Automatic bundling, TailwindCSS plugins, TypeScript, JSX, React support, and incredibly fast builds`,
-    }),
-    page("bundler/css", "CSS", {
-      description: `Production ready CSS bundler with support for modern CSS features, CSS modules, and more.`,
+    page("bundler/html", "Frontend & static sites", {
+      description: `Bundle html files with Bun's native bundler.`,
     }),
     page("bundler/fullstack", "Fullstack Dev Server", {
       description: "Serve your frontend and backend from the same app with Bun's dev server.",
     }),
-    page("bundler/hmr", "Hot reloading", {
-      description: `Update modules in a running application without reloading the page using import.meta.hot`,
-    }),
-
     page("bundler/loaders", "Loaders", {
       description: "Bun's built-in loaders for the bundler and runtime",
     }),

docs/runtime/debugger.md

@@ -2,7 +2,7 @@
 name: Debugging
 ---
 
-Bun speaks the [WebKit Inspector Protocol](https://github.com/oven-sh/bun/blob/main/packages/bun-inspector-protocol/src/protocol/jsc/index.d.ts), so you can debug your code with an interactive debugger. For demonstration purposes, consider the following simple web server.
+Bun speaks the [WebKit Inspector Protocol](https://github.com/oven-sh/bun/blob/main/packages/bun-types/jsc.d.ts), so you can debug your code with an interactive debugger. For demonstration purposes, consider the following simple web server.
 
 ## Debugging JavaScript and TypeScript
 

docs/runtime/env.md

@@ -15,40 +15,10 @@ BAR=world
 
 Variables can also be set via the command line.
 
-{% codetabs %}
-
-```sh#Linux/macOS
+```sh
 $ FOO=helloworld bun run dev
 ```
 
-```sh#Windows
-# Using CMD
-$ set FOO=helloworld && bun run dev
-
-# Using PowerShell
-$ $env:FOO="helloworld"; bun run dev
-```
-
-{% /codetabs %}
-
-{% details summary="Cross-platform solution with Windows" %}
-
-For a cross-platform solution, you can use [bun shell](https://bun.sh/docs/runtime/shell). For example, the `bun exec` command.
-
-```sh
-$ bun exec 'FOO=helloworld bun run dev'
-```
-
-On Windows, `package.json` scripts called with `bun run` will automatically use the **bun shell**, making the following also cross-platform.
-
-```json#package.json
-"scripts": {
-  "dev": "NODE_ENV=development bun --watch app.ts",
-},
-```
-
-{% /details %}
-
 Or programmatically by assigning a property to `process.env`.
 
 ```ts

docs/runtime/nodejs-apis.md

@@ -142,7 +142,7 @@ Some methods are not optimized yet.
 
 ### [`node:util`](https://nodejs.org/api/util.html)
 
-🟡 Missing `getCallSite` `getCallSites` `getSystemErrorMap` `getSystemErrorMessage` `transferableAbortSignal` `transferableAbortController` `MIMEType` `MIMEParams`
+🟡 Missing `MIMEParams` `MIMEType` `debug` `getSystemErrorMap` `transferableAbortController` `transferableAbortSignal` `stripVTControlCharacters`
 
 ### [`node:v8`](https://nodejs.org/api/v8.html)