bun-types 1.2.19-canary.20250708T140633 → 1.2.19-canary.20250710T140803

package/docs/guides/util/which-path-to-executable-bin.md

@@ -12,4 +12,4 @@ Bun.which("bun"); // => "/home/user/.bun/bin/bun"
 
 ---
 
-See [Docs > API > Utils](https://bun.sh/docs/api/utils#bun-which) for complete documentation.
+See [Docs > API > Utils](https://bun.com/docs/api/utils#bun-which) for complete documentation.

package/docs/guides/websocket/context.md

@@ -4,7 +4,7 @@ name: Set per-socket contextual data on a WebSocket
 
 When building a WebSocket server, it's typically necessary to store some identifying information or context associated with each connected client.
 
-With [Bun.serve()](https://bun.sh/docs/api/websockets#contextual-data), this "contextual data" is set when the connection is initially upgraded by passing a `data` parameter in the `server.upgrade()` call.
+With [Bun.serve()](https://bun.com/docs/api/websockets#contextual-data), this "contextual data" is set when the connection is initially upgraded by passing a `data` parameter in the `server.upgrade()` call.
 
 ```ts
 Bun.serve<{ socketId: number }>({

package/docs/guides/websocket/simple.md

@@ -2,7 +2,7 @@
 name: Build a simple WebSocket server
 ---
 
-Start a simple WebSocket server using [`Bun.serve`](https://bun.sh/docs/api/http).
+Start a simple WebSocket server using [`Bun.serve`](https://bun.com/docs/api/http).
 
 Inside `fetch`, we attempt to upgrade incoming `ws:` or `wss:` requests to WebSocket connections.
 

package/docs/guides/write-file/basic.md

@@ -4,7 +4,7 @@ name: Write a string to a file
 
 This code snippet writes a string to disk at a particular _absolute path_.
 
-It uses the fast [`Bun.write()`](https://bun.sh/docs/api/file-io#writing-files-bun-write) API to efficiently write data to disk. The first argument is a _destination_; the second is the _data_ to write.
+It uses the fast [`Bun.write()`](https://bun.com/docs/api/file-io#writing-files-bun-write) API to efficiently write data to disk. The first argument is a _destination_; the second is the _data_ to write.
 
 ```ts
 const path = "/path/to/file.txt";
@@ -41,4 +41,4 @@ const bytes = await Bun.write(path, "Lorem ipsum");
 
 ---
 
-See [Docs > API > File I/O](https://bun.sh/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.
+See [Docs > API > File I/O](https://bun.com/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.

package/docs/guides/write-file/blob.md

@@ -4,7 +4,7 @@ name: Write a Blob to a file
 
 This code snippet writes a `Blob` to disk at a particular path.
 
-It uses the fast [`Bun.write()`](https://bun.sh/docs/api/file-io#writing-files-bun-write) API to efficiently write data to disk. The first argument is a _destination_, like an absolute path or `BunFile` instance. The second argument is the _data_ to write.
+It uses the fast [`Bun.write()`](https://bun.com/docs/api/file-io#writing-files-bun-write) API to efficiently write data to disk. The first argument is a _destination_, like an absolute path or `BunFile` instance. The second argument is the _data_ to write.
 
 ```ts
 const path = "/path/to/file.txt";
@@ -25,4 +25,4 @@ await Bun.write(path, data);
 
 ---
 
-See [Docs > API > File I/O](https://bun.sh/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.
+See [Docs > API > File I/O](https://bun.com/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.

package/docs/guides/write-file/cat.md

@@ -2,7 +2,7 @@
 name: Write a file to stdout
 ---
 
-Bun exposes `stdout` as a `BunFile` with the `Bun.stdout` property. This can be used as a destination for [`Bun.write()`](https://bun.sh/docs/api/file-io#writing-files-bun-write).
+Bun exposes `stdout` as a `BunFile` with the `Bun.stdout` property. This can be used as a destination for [`Bun.write()`](https://bun.com/docs/api/file-io#writing-files-bun-write).
 
 This code writes a file to `stdout` similar to the `cat` command in Unix.
 
@@ -14,4 +14,4 @@ await Bun.write(Bun.stdout, file);
 
 ---
 
-See [Docs > API > File I/O](https://bun.sh/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.
+See [Docs > API > File I/O](https://bun.com/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.

package/docs/guides/write-file/file-cp.md

@@ -4,7 +4,7 @@ name: Copy a file to another location
 
 This code snippet copies a file to another location on disk.
 
-It uses the fast [`Bun.write()`](https://bun.sh/docs/api/file-io#writing-files-bun-write) API to efficiently write data to disk. The first argument is a _destination_, like an absolute path or `BunFile` instance. The second argument is the _data_ to write.
+It uses the fast [`Bun.write()`](https://bun.com/docs/api/file-io#writing-files-bun-write) API to efficiently write data to disk. The first argument is a _destination_, like an absolute path or `BunFile` instance. The second argument is the _data_ to write.
 
 ```ts
 const file = Bun.file("/path/to/original.txt");
@@ -13,4 +13,4 @@ await Bun.write("/path/to/copy.txt", file);
 
 ---
 
-See [Docs > API > File I/O](https://bun.sh/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.
+See [Docs > API > File I/O](https://bun.com/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.

package/docs/guides/write-file/filesink.md

@@ -49,4 +49,4 @@ writer.end();
 
 ---
 
-Full documentation: [FileSink](https://bun.sh/docs/api/file-io#incremental-writing-with-filesink).
+Full documentation: [FileSink](https://bun.com/docs/api/file-io#incremental-writing-with-filesink).

package/docs/guides/write-file/response.md

@@ -4,14 +4,14 @@ name: Write a Response to a file
 
 This code snippet writes a `Response` to disk at a particular path. Bun will consume the `Response` body according to its `Content-Type` header.
 
-It uses the fast [`Bun.write()`](https://bun.sh/docs/api/file-io#writing-files-bun-write) API to efficiently write data to disk. The first argument is a _destination_, like an absolute path or `BunFile` instance. The second argument is the _data_ to write.
+It uses the fast [`Bun.write()`](https://bun.com/docs/api/file-io#writing-files-bun-write) API to efficiently write data to disk. The first argument is a _destination_, like an absolute path or `BunFile` instance. The second argument is the _data_ to write.
 
 ```ts
-const result = await fetch("https://bun.sh");
+const result = await fetch("https://bun.com");
 const path = "./file.txt";
 await Bun.write(path, result);
 ```
 
 ---
 
-See [Docs > API > File I/O](https://bun.sh/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.
+See [Docs > API > File I/O](https://bun.com/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.

package/docs/guides/write-file/stdout.md

@@ -10,7 +10,7 @@ console.log("Lorem ipsum");
 
 ---
 
-For more advanced use cases, Bun exposes `stdout` as a `BunFile` via the `Bun.stdout` property. This can be used as a destination for [`Bun.write()`](https://bun.sh/docs/api/file-io#writing-files-bun-write).
+For more advanced use cases, Bun exposes `stdout` as a `BunFile` via the `Bun.stdout` property. This can be used as a destination for [`Bun.write()`](https://bun.com/docs/api/file-io#writing-files-bun-write).
 
 ```ts
 await Bun.write(Bun.stdout, "Lorem ipsum");
@@ -18,4 +18,4 @@ await Bun.write(Bun.stdout, "Lorem ipsum");
 
 ---
 
-See [Docs > API > File I/O](https://bun.sh/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.
+See [Docs > API > File I/O](https://bun.com/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.

package/docs/guides/write-file/stream.md

@@ -2,7 +2,7 @@
 name: Write a ReadableStream to a file
 ---
 
-To write a `ReadableStream` to disk, first create a `Response` instance from the stream. This `Response` can then be written to disk using [`Bun.write()`](https://bun.sh/docs/api/file-io#writing-files-bun-write).
+To write a `ReadableStream` to disk, first create a `Response` instance from the stream. This `Response` can then be written to disk using [`Bun.write()`](https://bun.com/docs/api/file-io#writing-files-bun-write).
 
 ```ts
 const stream: ReadableStream = ...;
@@ -14,4 +14,4 @@ await Bun.write(path, response);
 
 ---
 
-See [Docs > API > File I/O](https://bun.sh/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.
+See [Docs > API > File I/O](https://bun.com/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.

package/docs/guides/write-file/unlink.md

@@ -13,4 +13,4 @@ await file.delete();
 
 ---
 
-See [Docs > API > File I/O](https://bun.sh/docs/api/file-io#reading-files-bun-file) for complete documentation of `Bun.file()`.
+See [Docs > API > File I/O](https://bun.com/docs/api/file-io#reading-files-bun-file) for complete documentation of `Bun.file()`.

package/docs/index.md

@@ -65,7 +65,7 @@ Bun is designed from the ground-up with today's JavaScript ecosystem in mind.
 - **TypeScript & JSX support**. You can directly execute `.jsx`, `.ts`, and `.tsx` files; Bun's transpiler converts these to vanilla JavaScript before execution.
 - **ESM & CommonJS compatibility**. The world is moving towards ES modules (ESM), but millions of packages on npm still require CommonJS. Bun recommends ES modules, but supports CommonJS.
 - **Web-standard APIs**. Bun implements standard Web APIs like `fetch`, `WebSocket`, and `ReadableStream`. Bun is powered by the JavaScriptCore engine, which is developed by Apple for Safari, so some APIs like [`Headers`](https://developer.mozilla.org/en-US/docs/Web/API/Headers) and [`URL`](https://developer.mozilla.org/en-US/docs/Web/API/URL) directly use [Safari's implementation](https://github.com/oven-sh/bun/blob/HEAD/src/bun.js/bindings/webcore/JSFetchHeaders.cpp).
-- **Node.js compatibility**. In addition to supporting Node-style module resolution, Bun aims for full compatibility with built-in Node.js globals (`process`, `Buffer`) and modules (`path`, `fs`, `http`, etc.) _This is an ongoing effort that is not complete._ Refer to the [compatibility page](https://bun.sh/docs/runtime/nodejs-apis) for the current status.
+- **Node.js compatibility**. In addition to supporting Node-style module resolution, Bun aims for full compatibility with built-in Node.js globals (`process`, `Buffer`) and modules (`path`, `fs`, `http`, etc.) _This is an ongoing effort that is not complete._ Refer to the [compatibility page](https://bun.com/docs/runtime/nodejs-apis) for the current status.
 
 Bun is more than a runtime. The long-term goal is to be a cohesive, infrastructural toolkit for building apps with JavaScript/TypeScript, including a package manager, transpiler, bundler, script runner, test runner, and more.
 

package/docs/install/lockfile.md

@@ -45,4 +45,4 @@ print = "yarn"
 
 Bun v1.2 changed the default lockfile format to the text-based `bun.lock`. Existing binary `bun.lockb` lockfiles can be migrated to the new format by running `bun install --save-text-lockfile --frozen-lockfile --lockfile-only` and deleting `bun.lockb`.
 
-More information about the new lockfile format can be found on [our blogpost](https://bun.sh/blog/bun-lock-text-lockfile).
+More information about the new lockfile format can be found on [our blogpost](https://bun.com/blog/bun-lock-text-lockfile).

package/docs/install/npmrc.md

@@ -2,7 +2,7 @@ Bun supports loading configuration options from [`.npmrc`](https://docs.npmjs.co
 
 {% callout %}
 
-**NOTE**: We recommend migrating your `.npmrc` file to Bun's [`bunfig.toml`](https://bun.sh/docs/runtime/bunfig) format, as it provides more flexible options and can let you configure Bun-specific options.
+**NOTE**: We recommend migrating your `.npmrc` file to Bun's [`bunfig.toml`](https://bun.com/docs/runtime/bunfig) format, as it provides more flexible options and can let you configure Bun-specific options.
 
 {% /callout %}
 
@@ -18,7 +18,7 @@ To change it, you can set the `registry` option in `.npmrc`:
 registry=http://localhost:4873/
 ```
 
-The equivalent `bunfig.toml` option is [`install.registry`](https://bun.sh/docs/runtime/bunfig#install-registry):
+The equivalent `bunfig.toml` option is [`install.registry`](https://bun.com/docs/runtime/bunfig#install-registry):
 
 ```toml
 install.registry = "http://localhost:4873/"
@@ -32,7 +32,7 @@ Allows you to set the registry for a specific scope:
 @myorg:registry=http://localhost:4873/
 ```
 
-The equivalent `bunfig.toml` option is to add a key in [`install.scopes`](https://bun.sh/docs/runtime/bunfig#install-registry):
+The equivalent `bunfig.toml` option is to add a key in [`install.scopes`](https://bun.com/docs/runtime/bunfig#install-registry):
 
 ```toml
 [install.scopes]
@@ -67,7 +67,7 @@ The following options are supported:
 - `_password` (base64 encoded password)
 - `_auth` (base64 encoded username:password, e.g. `btoa(username + ":" + password)`)
 
-The equivalent `bunfig.toml` option is to add a key in [`install.scopes`](https://bun.sh/docs/runtime/bunfig#install-registry):
+The equivalent `bunfig.toml` option is to add a key in [`install.scopes`](https://bun.com/docs/runtime/bunfig#install-registry):
 
 ```toml
 [install.scopes]

package/docs/install/patch.md

@@ -7,7 +7,7 @@ Features:
 - Generates `.patch` files applied to dependencies in `node_modules` on install
 - `.patch` files can be committed to your repository, reused across multiple installs, projects, and machines
 - `"patchedDependencies"` in `package.json` keeps track of patched packages
-- `bun patch` lets you patch packages in `node_modules/` while preserving the integrity of Bun's [Global Cache](https://bun.sh/docs/install/cache)
+- `bun patch` lets you patch packages in `node_modules/` while preserving the integrity of Bun's [Global Cache](https://bun.com/docs/install/cache)
 - Test your changes locally before committing them with `bun patch --commit <pkg>`
 - To preserve disk space and keep `bun install` fast, patched packages are committed to the Global Cache and shared across projects where possible
 
@@ -34,7 +34,7 @@ If you forget to do this, you might end up editing the package globally in the c
 
 #### Step 2. Test your changes locally
 
-`bun patch <pkg>` makes it safe to edit the `<pkg>` in `node_modules/` directly, while preserving the integrity of Bun's [Global Cache](https://bun.sh/docs/install/cache). This works by re-creating an unlinked clone of the package in `node_modules/` and diffing it against the original package in the Global Cache.
+`bun patch <pkg>` makes it safe to edit the `<pkg>` in `node_modules/` directly, while preserving the integrity of Bun's [Global Cache](https://bun.com/docs/install/cache). This works by re-creating an unlinked clone of the package in `node_modules/` and diffing it against the original package in the Global Cache.
 
 #### Step 3. Commit your changes
 

package/docs/install/registries.md

@@ -27,4 +27,4 @@ To configure a private registry scoped to a particular organization:
 
 ### `.npmrc`
 
-Bun also reads `.npmrc` files, [learn more](https://bun.sh/docs/install/npmrc).
+Bun also reads `.npmrc` files, [learn more](https://bun.com/docs/install/npmrc).

package/docs/install/workspaces.md

@@ -38,7 +38,7 @@ In the root `package.json`, the `"workspaces"` key is used to indicate which sub
 ```
 
 {% callout %}
-**Glob support** — Bun supports full glob syntax in `"workspaces"` (see [here](https://bun.sh/docs/api/glob#supported-glob-patterns) for a comprehensive list of supported syntax), _except_ for exclusions (e.g. `!**/excluded/**`), which are not implemented yet.
+**Glob support** — Bun supports full glob syntax in `"workspaces"` (see [here](https://bun.com/docs/api/glob#supported-glob-patterns) for a comprehensive list of supported syntax), _except_ for exclusions (e.g. `!**/excluded/**`), which are not implemented yet.
 {% /callout %}
 
 Each workspace has it's own `package.json`. When referencing other packages in the monorepo, semver or workspace protocols (e.g. `workspace:*`) can be used as the version field in your `package.json`.
@@ -81,7 +81,7 @@ 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.
 - **Dependencies can be de-duplicated.** If `a` and `b` share a common dependency, it will be _hoisted_ to the root `node_modules` directory. This reduces redundant disk usage and minimizes "dependency hell" issues associated with having multiple versions of a package installed simultaneously.
-- **Run scripts in multiple packages.** You can use the [`--filter` flag](https://bun.sh/docs/cli/filter) to easily run `package.json` scripts in multiple packages in your workspace.
+- **Run scripts in multiple packages.** You can use the [`--filter` flag](https://bun.com/docs/cli/filter) to easily run `package.json` scripts in multiple packages in your workspace.
 
 ## Share versions with Catalogs
 
@@ -89,7 +89,7 @@ When many packages need the same dependency versions, catalogs let you define
 those versions once in the root `package.json` and reference them from your
 workspaces using the `catalog:` protocol. Updating the catalog automatically
 updates every package that references it. See
-[Catalogs](https://bun.sh/docs/install/catalogs) for details.
+[Catalogs](https://bun.com/docs/install/catalogs) for details.
 
 {% callout %}
 ⚡️ **Speed** — Installs are fast, even for big monorepos. Bun installs the [Remix](https://github.com/remix-run/remix) monorepo in about `500ms` on Linux.

package/docs/installation.md

@@ -12,9 +12,9 @@ Kernel version 5.6 or higher is strongly recommended, but the minimum is 5.1. Us
 {% codetabs %}
 
 ```bash#macOS/Linux_(curl)
-$ curl -fsSL https://bun.sh/install | bash # for macOS, Linux, and WSL
+$ curl -fsSL https://bun.com/install | bash # for macOS, Linux, and WSL
 # to install a specific version
-$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.19-canary.20250708T140633"
+$ curl -fsSL https://bun.com/install | bash -s "bun-v1.2.19-canary.20250710T140803"
 ```
 
 ```bash#npm
@@ -39,7 +39,7 @@ To install, paste this into a terminal:
 {% codetabs %}
 
 ```powershell#PowerShell/cmd.exe
-> powershell -c "irm bun.sh/install.ps1|iex"
+> powershell -c "irm bun.com/install.ps1|iex"
 ```
 
 ```powershell#npm
@@ -56,7 +56,7 @@ To install, paste this into a terminal:
 Bun requires a minimum of Windows 10 version 1809
 {% /callout %}
 
-For support and discussion, please join the [#windows channel on our Discord](http://bun.sh/discord).
+For support and discussion, please join the [#windows channel on our Discord](http://bun.com/discord).
 
 ## Docker
 
@@ -189,10 +189,10 @@ Since Bun is a single binary, you can install older versions of Bun by re-runnin
 
 ### Installing a specific version of Bun on Linux/Mac
 
-To install a specific version of Bun, you can pass the git tag of the version you want to install to the install script, such as `bun-v1.2.0` or `bun-v1.2.19-canary.20250708T140633`.
+To install a specific version of Bun, you can pass the git tag of the version you want to install to the install script, such as `bun-v1.2.0` or `bun-v1.2.19-canary.20250710T140803`.
 
 ```sh
-$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.19-canary.20250708T140633"
+$ curl -fsSL https://bun.com/install | bash -s "bun-v1.2.19-canary.20250710T140803"
 ```
 
 ### Installing a specific version of Bun on Windows
@@ -201,7 +201,7 @@ On Windows, you can install a specific version of Bun by passing the version num
 
 ```sh
 # PowerShell:
-$ iex "& {$(irm https://bun.sh/install.ps1)} -Version 1.2.19-canary.20250708T140633"
+$ iex "& {$(irm https://bun.com/install.ps1)} -Version 1.2.19-canary.20250710T140803"
 ```
 
 ## Downloading Bun binaries directly
@@ -242,7 +242,7 @@ Bun also publishes `darwin-x64-baseline` binaries, but these are just a copy of
 Works on macOS x64 & Silicon, Linux x64, Windows Subsystem for Linux.
 
 ```sh
-$ curl -fsSL https://bun.sh/install | bash
+$ curl -fsSL https://bun.com/install | bash
 ```
 
 Once installed, the binary can upgrade itself.

package/docs/project/benchmarking.md

@@ -171,7 +171,7 @@ Once imported, you should see something like this:
 
 {% image alt="Viewing heap snapshot in Safari" src="https://user-images.githubusercontent.com/709451/204429337-b0d8935f-3509-4071-b991-217794d1fb27.png" caption="Viewing heap snapshot in Safari Dev Tools" /%}
 
-> The [web debugger](https://bun.sh/docs/runtime/debugger#inspect) also offers the timeline feature which allows you to track and examine the memory usage of the running debug session.
+> The [web debugger](https://bun.com/docs/runtime/debugger#inspect) also offers the timeline feature which allows you to track and examine the memory usage of the running debug session.
 
 ### Native heap stats
 

package/docs/project/building-windows.md

@@ -1,4 +1,4 @@
-This document describes the build process for Windows. If you run into problems, please join the [#contributing channel on our Discord](http://bun.sh/discord) for help.
+This document describes the build process for Windows. If you run into problems, please join the [#contributing channel on our Discord](http://bun.com/discord) for help.
 
 It is strongly recommended to use [PowerShell 7 (`pwsh.exe`)](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows?view=powershell-7.4) instead of the default `powershell.exe`.
 
@@ -47,7 +47,7 @@ By default, running unverified scripts are blocked.
 Bun v1.1 or later. We use Bun to run it's own code generators.
 
 ```ps1
-> irm bun.sh/install.ps1 | iex
+> irm bun.com/install.ps1 | iex
 ```
 
 [Visual Studio](https://visualstudio.microsoft.com) with the "Desktop Development with C++" workload. While installing, make sure to install Git as well, if Git for Windows is not already installed.

package/docs/project/contributing.md

@@ -1,6 +1,6 @@
 Configuring a development environment for Bun can take 10-30 minutes depending on your internet connection and computer speed. You will need ~10GB of free disk space for the repository and build artifacts.
 
-If you are using Windows, please refer to [this guide](https://bun.sh/docs/project/building-windows)
+If you are using Windows, please refer to [this guide](https://bun.com/docs/project/building-windows)
 
 ## Install Dependencies
 
@@ -37,7 +37,7 @@ Before starting, you will need to already have a release build of Bun installed,
 {% codetabs %}
 
 ```bash#Native
-$ curl -fsSL https://bun.sh/install | bash
+$ curl -fsSL https://bun.com/install | bash
 ```
 
 ```bash#npm

package/docs/quickstart.md

@@ -29,7 +29,7 @@ Since our entry point is a `*.ts` file, Bun generates a `tsconfig.json` for you.
 
 ## Run a file
 
-Open `index.ts` and paste the following code snippet, which implements a simple HTTP server with [`Bun.serve`](https://bun.sh/docs/api/http).
+Open `index.ts` and paste the following code snippet, which implements a simple HTTP server with [`Bun.serve`](https://bun.com/docs/api/http).
 
 ```ts
 const server = Bun.serve({

package/docs/runtime/autoimport.md

@@ -1,6 +1,6 @@
 If no `node_modules` directory is found in the working directory or higher, Bun will abandon Node.js-style module resolution in favor of the **Bun module resolution algorithm**.
 
-Under Bun-style module resolution, all imported packages are auto-installed on the fly into a [global module cache](https://bun.sh/docs/install/cache) during execution (the same cache used by [`bun install`](https://bun.sh/docs/cli/install)).
+Under Bun-style module resolution, all imported packages are auto-installed on the fly into a [global module cache](https://bun.com/docs/install/cache) during execution (the same cache used by [`bun install`](https://bun.com/docs/cli/install)).
 
 ```ts
 import { foo } from "foo"; // install `latest` version

package/docs/runtime/bun-apis.md

@@ -20,167 +20,167 @@ Click the link in the right column to jump to the associated documentation.
 ---
 
 - HTTP Server
-- [`Bun.serve`](https://bun.sh/docs/api/http#bun-serve)
+- [`Bun.serve`](https://bun.com/docs/api/http#bun-serve)
 
 ---
 
 - Shell
-- [`$`](https://bun.sh/docs/runtime/shell)
+- [`$`](https://bun.com/docs/runtime/shell)
 
 ---
 
 - Bundler
-- [`Bun.build`](https://bun.sh/docs/bundler)
+- [`Bun.build`](https://bun.com/docs/bundler)
 
 ---
 
 - File I/O
-- [`Bun.file`](https://bun.sh/docs/api/file-io#reading-files-bun-file), [`Bun.write`](https://bun.sh/docs/api/file-io#writing-files-bun-write), `Bun.stdin`, `Bun.stdout`, `Bun.stderr`
+- [`Bun.file`](https://bun.com/docs/api/file-io#reading-files-bun-file), [`Bun.write`](https://bun.com/docs/api/file-io#writing-files-bun-write), `Bun.stdin`, `Bun.stdout`, `Bun.stderr`
 
 ---
 
 - Child Processes
-- [`Bun.spawn`](https://bun.sh/docs/api/spawn#spawn-a-process-bun-spawn), [`Bun.spawnSync`](https://bun.sh/docs/api/spawn#blocking-api-bun-spawnsync)
+- [`Bun.spawn`](https://bun.com/docs/api/spawn#spawn-a-process-bun-spawn), [`Bun.spawnSync`](https://bun.com/docs/api/spawn#blocking-api-bun-spawnsync)
 
 ---
 
 - TCP Sockets
-- [`Bun.listen`](https://bun.sh/docs/api/tcp#start-a-server-bun-listen), [`Bun.connect`](https://bun.sh/docs/api/tcp#start-a-server-bun-listen)
+- [`Bun.listen`](https://bun.com/docs/api/tcp#start-a-server-bun-listen), [`Bun.connect`](https://bun.com/docs/api/tcp#start-a-server-bun-listen)
 
 ---
 
 - UDP Sockets
-- [`Bun.udpSocket`](https://bun.sh/docs/api/udp)
+- [`Bun.udpSocket`](https://bun.com/docs/api/udp)
 
 ---
 
 - WebSockets
-- `new WebSocket()` (client), [`Bun.serve`](https://bun.sh/docs/api/websockets) (server)
+- `new WebSocket()` (client), [`Bun.serve`](https://bun.com/docs/api/websockets) (server)
 
 ---
 
 - Transpiler
-- [`Bun.Transpiler`](https://bun.sh/docs/api/transpiler)
+- [`Bun.Transpiler`](https://bun.com/docs/api/transpiler)
 
 ---
 
 - Routing
-- [`Bun.FileSystemRouter`](https://bun.sh/docs/api/file-system-router)
+- [`Bun.FileSystemRouter`](https://bun.com/docs/api/file-system-router)
 
 ---
 
 - Streaming HTML
-- [`HTMLRewriter`](https://bun.sh/docs/api/html-rewriter)
+- [`HTMLRewriter`](https://bun.com/docs/api/html-rewriter)
 
 ---
 
 - Hashing
-- [`Bun.password`](https://bun.sh/docs/api/hashing#bun-password), [`Bun.hash`](https://bun.sh/docs/api/hashing#bun-hash), [`Bun.CryptoHasher`](https://bun.sh/docs/api/hashing#bun-cryptohasher), `Bun.sha`
+- [`Bun.password`](https://bun.com/docs/api/hashing#bun-password), [`Bun.hash`](https://bun.com/docs/api/hashing#bun-hash), [`Bun.CryptoHasher`](https://bun.com/docs/api/hashing#bun-cryptohasher), `Bun.sha`
 
 ---
 
 - SQLite
-- [`bun:sqlite`](https://bun.sh/docs/api/sqlite)
+- [`bun:sqlite`](https://bun.com/docs/api/sqlite)
 
 ---
 
 - PostgreSQL Client
-- [`Bun.SQL`](https://bun.sh/docs/api/sql), `Bun.sql`
+- [`Bun.SQL`](https://bun.com/docs/api/sql), `Bun.sql`
 
 ---
 
 - Redis (Valkey) Client
-- [`Bun.RedisClient`](https://bun.sh/docs/api/redis), `Bun.redis`
+- [`Bun.RedisClient`](https://bun.com/docs/api/redis), `Bun.redis`
 
 ---
 
 - FFI (Foreign Function Interface)
-- [`bun:ffi`](https://bun.sh/docs/api/ffi)
+- [`bun:ffi`](https://bun.com/docs/api/ffi)
 
 ---
 
 - DNS
-- [`Bun.dns.lookup`](https://bun.sh/docs/api/dns), `Bun.dns.prefetch`, `Bun.dns.getCacheStats`
+- [`Bun.dns.lookup`](https://bun.com/docs/api/dns), `Bun.dns.prefetch`, `Bun.dns.getCacheStats`
 
 ---
 
 - Testing
-- [`bun:test`](https://bun.sh/docs/cli/test)
+- [`bun:test`](https://bun.com/docs/cli/test)
 
 ---
 
 - Workers
-- [`new Worker()`](https://bun.sh/docs/api/workers)
+- [`new Worker()`](https://bun.com/docs/api/workers)
 
 ---
 
 - Module Loaders
-- [`Bun.plugin`](https://bun.sh/docs/bundler/plugins)
+- [`Bun.plugin`](https://bun.com/docs/bundler/plugins)
 
 ---
 
 - Glob
-- [`Bun.Glob`](https://bun.sh/docs/api/glob)
+- [`Bun.Glob`](https://bun.com/docs/api/glob)
 
 ---
 
 - Cookies
-- [`Bun.Cookie`](https://bun.sh/docs/api/cookie), [`Bun.CookieMap`](https://bun.sh/docs/api/cookie)
+- [`Bun.Cookie`](https://bun.com/docs/api/cookie), [`Bun.CookieMap`](https://bun.com/docs/api/cookie)
 
 ---
 
 - Node-API
-- [`Node-API`](https://bun.sh/docs/api/node-api)
+- [`Node-API`](https://bun.com/docs/api/node-api)
 
 ---
 
 - `import.meta`
-- [`import.meta`](https://bun.sh/docs/api/import-meta)
+- [`import.meta`](https://bun.com/docs/api/import-meta)
 
 ---
 
 - Utilities
-- [`Bun.version`](https://bun.sh/docs/api/utils#bun-version), [`Bun.revision`](https://bun.sh/docs/api/utils#bun-revision), [`Bun.env`](https://bun.sh/docs/api/utils#bun-env), [`Bun.main`](https://bun.sh/docs/api/utils#bun-main)
+- [`Bun.version`](https://bun.com/docs/api/utils#bun-version), [`Bun.revision`](https://bun.com/docs/api/utils#bun-revision), [`Bun.env`](https://bun.com/docs/api/utils#bun-env), [`Bun.main`](https://bun.com/docs/api/utils#bun-main)
 
 ---
 
 - Sleep & Timing
-- [`Bun.sleep()`](https://bun.sh/docs/api/utils#bun-sleep), [`Bun.sleepSync()`](https://bun.sh/docs/api/utils#bun-sleepsync), [`Bun.nanoseconds()`](https://bun.sh/docs/api/utils#bun-nanoseconds)
+- [`Bun.sleep()`](https://bun.com/docs/api/utils#bun-sleep), [`Bun.sleepSync()`](https://bun.com/docs/api/utils#bun-sleepsync), [`Bun.nanoseconds()`](https://bun.com/docs/api/utils#bun-nanoseconds)
 
 ---
 
 - Random & UUID
-- [`Bun.randomUUIDv7()`](https://bun.sh/docs/api/utils#bun-randomuuidv7)
+- [`Bun.randomUUIDv7()`](https://bun.com/docs/api/utils#bun-randomuuidv7)
 
 ---
 
 - System & Environment
-- [`Bun.which()`](https://bun.sh/docs/api/utils#bun-which)
+- [`Bun.which()`](https://bun.com/docs/api/utils#bun-which)
 
 ---
 
 - Comparison & Inspection
-- [`Bun.peek()`](https://bun.sh/docs/api/utils#bun-peek), [`Bun.deepEquals()`](https://bun.sh/docs/api/utils#bun-deepequals), `Bun.deepMatch`, [`Bun.inspect()`](https://bun.sh/docs/api/utils#bun-inspect)
+- [`Bun.peek()`](https://bun.com/docs/api/utils#bun-peek), [`Bun.deepEquals()`](https://bun.com/docs/api/utils#bun-deepequals), `Bun.deepMatch`, [`Bun.inspect()`](https://bun.com/docs/api/utils#bun-inspect)
 
 ---
 
 - String & Text Processing
-- [`Bun.escapeHTML()`](https://bun.sh/docs/api/utils#bun-escapehtml), [`Bun.stringWidth()`](https://bun.sh/docs/api/utils#bun-stringwidth), `Bun.indexOfLine`
+- [`Bun.escapeHTML()`](https://bun.com/docs/api/utils#bun-escapehtml), [`Bun.stringWidth()`](https://bun.com/docs/api/utils#bun-stringwidth), `Bun.indexOfLine`
 
 ---
 
 - URL & Path Utilities
-- [`Bun.fileURLToPath()`](https://bun.sh/docs/api/utils#bun-fileurltopath), [`Bun.pathToFileURL()`](https://bun.sh/docs/api/utils#bun-pathtofileurl)
+- [`Bun.fileURLToPath()`](https://bun.com/docs/api/utils#bun-fileurltopath), [`Bun.pathToFileURL()`](https://bun.com/docs/api/utils#bun-pathtofileurl)
 
 ---
 
 - Compression
-- [`Bun.gzipSync()`](https://bun.sh/docs/api/utils#bun-gzipsync), [`Bun.gunzipSync()`](https://bun.sh/docs/api/utils#bun-gunzipsync), [`Bun.deflateSync()`](https://bun.sh/docs/api/utils#bun-deflatesync), [`Bun.inflateSync()`](https://bun.sh/docs/api/utils#bun-inflatesync), `Bun.zstdCompressSync()`, `Bun.zstdDecompressSync()`, `Bun.zstdCompress()`, `Bun.zstdDecompress()`
+- [`Bun.gzipSync()`](https://bun.com/docs/api/utils#bun-gzipsync), [`Bun.gunzipSync()`](https://bun.com/docs/api/utils#bun-gunzipsync), [`Bun.deflateSync()`](https://bun.com/docs/api/utils#bun-deflatesync), [`Bun.inflateSync()`](https://bun.com/docs/api/utils#bun-inflatesync), `Bun.zstdCompressSync()`, `Bun.zstdDecompressSync()`, `Bun.zstdCompress()`, `Bun.zstdDecompress()`
 
 ---
 
 - Stream Processing
-- [`Bun.readableStreamTo*()`](https://bun.sh/docs/api/utils#bun-readablestreamto), `Bun.readableStreamToBytes()`, `Bun.readableStreamToBlob()`, `Bun.readableStreamToFormData()`, `Bun.readableStreamToJSON()`, `Bun.readableStreamToArray()`
+- [`Bun.readableStreamTo*()`](https://bun.com/docs/api/utils#bun-readablestreamto), `Bun.readableStreamToBytes()`, `Bun.readableStreamToBlob()`, `Bun.readableStreamToFormData()`, `Bun.readableStreamToJSON()`, `Bun.readableStreamToArray()`
 
 ---
 
@@ -190,17 +190,17 @@ Click the link in the right column to jump to the associated documentation.
 ---
 
 - Module Resolution
-- [`Bun.resolveSync()`](https://bun.sh/docs/api/utils#bun-resolvesync)
+- [`Bun.resolveSync()`](https://bun.com/docs/api/utils#bun-resolvesync)
 
 ---
 
 - Parsing & Formatting
-- [`Bun.semver`](https://bun.sh/docs/api/semver), `Bun.TOML.parse`, [`Bun.color`](https://bun.sh/docs/api/color)
+- [`Bun.semver`](https://bun.com/docs/api/semver), `Bun.TOML.parse`, [`Bun.color`](https://bun.com/docs/api/color)
 
 ---
 
 - Low-level / Internals
-- `Bun.mmap`, `Bun.gc`, `Bun.generateHeapSnapshot`, [`bun:jsc`](https://bun.sh/docs/api/bun-jsc)
+- `Bun.mmap`, `Bun.gc`, `Bun.generateHeapSnapshot`, [`bun:jsc`](https://bun.com/docs/api/bun-jsc)
 
 ---