bun-types 1.3.3 → 1.3.4-canary.20251123T140630

package/docs/guides/process/ctrl-c.mdx

@@ -15,4 +15,4 @@ process.on("SIGINT", () => {
 
 ---
 
-See [Docs > API > Utils](https://bun.com/docs/api/utils) for more useful utilities.
+See [Docs > API > Utils](/docs/runtime/utils) for more useful utilities.

package/docs/guides/process/ipc.mdx

@@ -4,7 +4,7 @@ sidebarTitle: Spawn a child process and communicate using IPC
 mode: center
 ---
 
-Use [`Bun.spawn()`](https://bun.com/docs/api/spawn) to spawn a child process. When spawning a second `bun` process, you can open a direct inter-process communication (IPC) channel between the two processes.
+Use [`Bun.spawn()`](/docs/runtime/child-process) to spawn a child process. When spawning a second `bun` process, you can open a direct inter-process communication (IPC) channel between the two processes.
 
 <Note>
   This API is only compatible with other `bun` processes. Use `process.execPath` to get a path to the currently running
@@ -66,4 +66,4 @@ process.send({ message: "Hello from child as object" });
 
 ---
 
-See [Docs > API > Child processes](https://bun.com/docs/api/spawn) for complete documentation.
+See [Docs > API > Child processes](/docs/runtime/child-process) for complete documentation.

package/docs/guides/process/nanoseconds.mdx

@@ -12,4 +12,4 @@ Bun.nanoseconds();
 
 ---
 
-See [Docs > API > Utils](https://bun.com/docs/api/utils) for more useful utilities.
+See [Docs > API > Utils](/docs/runtime/utils) for more useful utilities.

package/docs/guides/process/os-signals.mdx

@@ -38,4 +38,4 @@ process.on("exit", code => {
 
 ---
 
-See [Docs > API > Utils](https://bun.com/docs/api/utils) for more useful utilities.
+See [Docs > API > Utils](/docs/runtime/utils) for more useful utilities.

package/docs/guides/process/spawn-stderr.mdx

@@ -4,7 +4,7 @@ sidebarTitle: Read stderr
 mode: center
 ---
 
-When using [`Bun.spawn()`](https://bun.com/docs/api/spawn), the child process inherits the `stderr` of the spawning process. If instead you'd prefer to read and handle `stderr`, set the `stderr` option to `"pipe"`.
+When using [`Bun.spawn()`](/docs/runtime/child-process), the child process inherits the `stderr` of the spawning process. If instead you'd prefer to read and handle `stderr`, set the `stderr` option to `"pipe"`.
 
 ```ts
 const proc = Bun.spawn(["echo", "hello"], {
@@ -31,4 +31,4 @@ if (errors) {
 
 ---
 
-See [Docs > API > Child processes](https://bun.com/docs/api/spawn) for complete documentation.
+See [Docs > API > Child processes](/docs/runtime/child-process) for complete documentation.

package/docs/guides/process/spawn-stdout.mdx

@@ -4,7 +4,7 @@ sidebarTitle: Read stdout
 mode: center
 ---
 
-When using [`Bun.spawn()`](https://bun.com/docs/api/spawn), the `stdout` of the child process can be consumed as a `ReadableStream` via `proc.stdout`.
+When using [`Bun.spawn()`](/docs/runtime/child-process), the `stdout` of the child process can be consumed as a `ReadableStream` via `proc.stdout`.
 
 ```ts
 const proc = Bun.spawn(["echo", "hello"]);
@@ -25,4 +25,4 @@ const proc = Bun.spawn(["echo", "hello"], {
 
 ---
 
-See [Docs > API > Child processes](https://bun.com/docs/api/spawn) for complete documentation.
+See [Docs > API > Child processes](/docs/runtime/child-process) for complete documentation.

package/docs/guides/process/spawn.mdx

@@ -4,7 +4,7 @@ sidebarTitle: Spawn child process
 mode: center
 ---
 
-Use [`Bun.spawn()`](https://bun.com/docs/api/spawn) to spawn a child process.
+Use [`Bun.spawn()`](/docs/runtime/child-process) to spawn a child process.
 
 ```ts
 const proc = Bun.spawn(["echo", "hello"]);
@@ -40,4 +40,4 @@ output; // => "hello\n"
 
 ---
 
-See [Docs > API > Child processes](https://bun.com/docs/api/spawn) for complete documentation.
+See [Docs > API > Child processes](/docs/runtime/child-process) for complete documentation.

package/docs/guides/process/stdin.mdx

@@ -59,4 +59,4 @@ Chunk: hello
 
 ---
 
-See [Docs > API > Utils](https://bun.com/docs/api/utils) for more useful utilities.
+See [Docs > API > Utils](/docs/runtime/utils) for more useful utilities.

package/docs/guides/read-file/arraybuffer.mdx

@@ -15,7 +15,7 @@ const buffer = await file.arrayBuffer();
 
 ---
 
-The binary content in the `ArrayBuffer` can then be read as a typed array, such as `Int8Array`. For `Uint8Array`, use [`.bytes()`](./uint8array).
+The binary content in the `ArrayBuffer` can then be read as a typed array, such as `Int8Array`. For `Uint8Array`, use [`.bytes()`](/docs/guides/read-file/uint8array).
 
 ```ts index.ts icon="/icons/typescript.svg"
 const buffer = await file.arrayBuffer();
@@ -27,4 +27,4 @@ bytes.length;
 
 ---
 
-Refer to the [Typed arrays](https://bun.com/docs/api/binary-data#typedarray) docs for more information on working with typed arrays in Bun.
+Refer to the [Typed arrays](/docs/runtime/binary-data#typedarray) docs for more information on working with typed arrays in Bun.

package/docs/guides/read-file/buffer.mdx

@@ -18,4 +18,4 @@ const buffer = Buffer.from(arrbuf);
 
 ---
 
-Refer to [Binary data > Buffer](https://bun.com/docs/api/binary-data#buffer) for more information on working with `Buffer` and other binary data formats in Bun.
+Refer to [Binary data > Buffer](/docs/runtime/binary-data#buffer) for more information on working with `Buffer` and other binary data formats in Bun.

package/docs/guides/read-file/exists.mdx

@@ -15,4 +15,4 @@ await file.exists(); // boolean;
 
 ---
 
-Refer to [API > File I/O](https://bun.com/docs/api/file-io) for more information on working with `BunFile`.
+Refer to [API > File I/O](/docs/runtime/file-io) for more information on working with `BunFile`.

package/docs/guides/read-file/mime.mdx

@@ -19,4 +19,4 @@ file.type; // image/png
 
 ---
 
-Refer to [API > File I/O](https://bun.com/docs/api/file-io) for more information on working with `BunFile`.
+Refer to [API > File I/O](/docs/runtime/file-io) for more information on working with `BunFile`.

package/docs/guides/read-file/stream.mdx

@@ -25,4 +25,4 @@ for await (const chunk of stream) {
 
 ---
 
-Refer to the [Streams](https://bun.com/docs/api/streams) documentation for more information on working with streams in Bun.
+Refer to the [Streams](/docs/runtime/streams) documentation for more information on working with streams in Bun.

package/docs/guides/read-file/uint8array.mdx

@@ -20,4 +20,4 @@ byteArray.length; // length of byteArray
 
 ---
 
-Refer to [API > Binary data > Typed arrays](https://bun.com/docs/api/binary-data#typedarray) for more information on working with `Uint8Array` and other binary data formats in Bun.
+Refer to [API > Binary data > Typed arrays](/docs/runtime/binary-data#typedarray) for more information on working with `Uint8Array` and other binary data formats in Bun.

package/docs/guides/read-file/watch.mdx

@@ -63,4 +63,4 @@ process.on("SIGINT", () => {
 
 ---
 
-Refer to [API > Binary data > Typed arrays](https://bun.com/docs/api/binary-data#typedarray) for more information on working with `Uint8Array` and other binary data formats in Bun.
+Refer to [API > Binary data > Typed arrays](/docs/runtime/binary-data#typedarray) for more information on working with `Uint8Array` and other binary data formats in Bun.

package/docs/guides/runtime/build-time-constants.mdx

@@ -290,6 +290,6 @@ bun build --compile --target=bun-windows-x64 --define PLATFORM='"windows"' src/a
 
 ## Related
 
-- [Define constants at runtime](/guides/runtime/define-constant) - Using `--define` with `bun run`
-- [Building executables](/bundler/executables) - Complete guide to `bun build --compile`
-- [Bundler API](/bundler) - Full bundler documentation including `define` option
+- [Define constants at runtime](/docs/guides/runtime/define-constant) - Using `--define` with `bun run`
+- [Building executables](/docs/bundler/executables) - Complete guide to `bun build --compile`
+- [Bundler API](/docs/bundler) - Full bundler documentation including `define` option

package/docs/guides/runtime/cicd.mdx

@@ -37,7 +37,7 @@ jobs:
       # ...
       - uses: oven-sh/setup-bun@v2
         with: # [!code ++]
-          bun-version: 1.2.0 # or "latest", "canary", <sha> # [!code ++]
+          bun-version: 1.3.3 # or "latest", "canary", <sha> # [!code ++]
 ```
 
 ---

package/docs/guides/runtime/codesign-macos-executable.mdx

@@ -58,4 +58,4 @@ 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](/bundler/executables). This guide requires Bun v1.2.4 or newer.
+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.

package/docs/guides/runtime/delete-directory.mdx

@@ -36,4 +36,4 @@ try {
 
 ---
 
-See [Docs > API > FileSystem](https://bun.com/docs/api/file-io) for more filesystem operations.
+See [Docs > API > FileSystem](/docs/runtime/file-io) for more filesystem operations.

package/docs/guides/runtime/delete-file.mdx

@@ -18,4 +18,4 @@ const exists = await file.exists();
 
 ---
 
-See [Docs > API > FileSystem](https://bun.com/docs/api/file-io) for more filesystem operations.
+See [Docs > API > FileSystem](/docs/runtime/file-io) for more filesystem operations.

package/docs/guides/runtime/heap-snapshot.mdx

@@ -25,4 +25,4 @@ To view V8 heap snapshots in Chrome DevTools:
 3. Click the "Load" button (folder icon)
 4. Select your `.heapsnapshot` file
 
-<Frame>![Chrome DevTools Memory Tab](/images/chrome-devtools-memory.png)</Frame>
+<Frame>![Chrome DevTools Memory Tab](https://bun.com/images/chrome-devtools-memory.png)</Frame>

package/docs/guides/runtime/import-json.mdx

@@ -43,4 +43,4 @@ data.author.name; // => "John Dough"
 
 ---
 
-See [Docs > Runtime > TypeScript](https://bun.com/docs/runtime/typescript) for more information on using TypeScript with Bun.
+See [Docs > Runtime > TypeScript](/docs/runtime/typescript) for more information on using TypeScript with Bun.

package/docs/guides/runtime/import-toml.mdx

@@ -29,4 +29,4 @@ data.author.name; // => "John Dough"
 
 ---
 
-See [Docs > Runtime > TypeScript](https://bun.com/docs/runtime/typescript) for more information on using TypeScript with Bun.
+See [Docs > Runtime > TypeScript](/docs/runtime/typescript) for more information on using TypeScript with Bun.

package/docs/guides/runtime/import-yaml.mdx

@@ -101,4 +101,4 @@ export = contents;
 
 ---
 
-See [Docs > API > YAML](https://bun.com/docs/api/yaml) for complete documentation on YAML support in Bun.
+See [Docs > API > YAML](/docs/runtime/yaml) for complete documentation on YAML support in Bun.

package/docs/guides/runtime/read-env.mdx

@@ -34,4 +34,4 @@ FOOBAR=aaaaaa
 
 ---
 
-See [Docs > Runtime > Environment variables](https://bun.com/docs/runtime/env) for more information on using environment variables with Bun.
+See [Docs > Runtime > Environment variables](/docs/runtime/environment-variables) for more information on using environment variables with Bun.

package/docs/guides/runtime/set-env.mdx

@@ -21,7 +21,7 @@ Bun reads the following files automatically (listed in order of increasing prece
 - `.env.production`, `.env.development`, `.env.test` (depending on value of `NODE_ENV`)
 - `.env.local` (not loaded when `NODE_ENV=test`)
 
-```txt .env icon="settings"
+```ini .env icon="settings"
 FOO=hello
 BAR=world
 ```
@@ -48,4 +48,4 @@ $env:FOO="helloworld"; bun run dev
 
 ---
 
-See [Docs > Runtime > Environment variables](https://bun.com/docs/runtime/env) for more information on using environment variables with Bun.
+See [Docs > Runtime > Environment variables](/docs/runtime/environment-variables) for more information on using environment variables with Bun.

package/docs/guides/runtime/shell.mdx

@@ -39,4 +39,4 @@ for await (const line of $`ls -l`.lines()) {
 
 ---
 
-See [Docs > API > Shell](https://bun.com/docs/runtime/shell) for complete documentation.
+See [Docs > API > Shell](/docs/runtime/shell) for complete documentation.

package/docs/guides/runtime/tsconfig-paths.mdx

@@ -28,4 +28,4 @@ import { Button } from "@components/Button"; // imports from "./src/components/B
 
 ---
 
-See [Docs > Runtime > TypeScript](https://bun.com/docs/runtime/typescript) for more information on using TypeScript with Bun.
+See [Docs > Runtime > TypeScript](/docs/runtime/typescript) for more information on using TypeScript with Bun.

package/docs/guides/runtime/typescript.mdx

@@ -48,4 +48,4 @@ Below is the full set of recommended `compilerOptions` for a Bun project. With t
 
 ---
 
-Refer to [Ecosystem > TypeScript](https://bun.com/docs/runtime/typescript) for a complete guide to TypeScript support in Bun.
+Refer to [Ecosystem > TypeScript](/docs/runtime/typescript) for a complete guide to TypeScript support in Bun.

package/docs/guides/runtime/vscode-debugger.mdx

@@ -5,8 +5,7 @@ mode: center
 ---
 
 <Note>
-  VSCode extension support is currently buggy. We recommend the [Web
-  Debugger](https://bun.com/guides/runtime/web-debugger) for now.
+  VSCode extension support is currently buggy. We recommend the [Web Debugger](/docs/guides/runtime/web-debugger) for now.
 </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.

package/docs/guides/runtime/web-debugger.mdx

@@ -4,7 +4,7 @@ sidebarTitle: Web debugger
 mode: center
 ---
 
-Bun speaks the [WebKit Inspector Protocol](https://github.com/oven-sh/bun/blob/main/packages/bun-vscode/types/jsc.d.ts). To enable debugging when running code with Bun, use the `--inspect` flag. 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-inspector-protocol/src/protocol/jsc/index.d.ts). To enable debugging when running code with Bun, use the `--inspect` flag. For demonstration purposes, consider the following simple web server.
 
 ```ts server.ts icon="/icons/typescript.svg"
 Bun.serve({

package/docs/guides/streams/to-array.mdx

@@ -13,4 +13,4 @@ const str = await Bun.readableStreamToArray(stream);
 
 ---
 
-See [Docs > API > Utils](https://bun.com/docs/api/utils#bun-readablestreamto) for documentation on Bun's other `ReadableStream` conversion functions.
+See [Docs > API > Utils](/docs/runtime/utils#bun-readablestreamto) for documentation on Bun's other `ReadableStream` conversion functions.

package/docs/guides/streams/to-arraybuffer.mdx

@@ -13,4 +13,4 @@ const buf = await Bun.readableStreamToArrayBuffer(stream);
 
 ---
 
-See [Docs > API > Utils](https://bun.com/docs/api/utils#bun-readablestreamto) for documentation on Bun's other `ReadableStream` conversion functions.
+See [Docs > API > Utils](/docs/runtime/utils#bun-readablestreamto) for documentation on Bun's other `ReadableStream` conversion functions.

package/docs/guides/streams/to-blob.mdx

@@ -13,4 +13,4 @@ const blob = await Bun.readableStreamToBlob(stream);
 
 ---
 
-See [Docs > API > Utils](https://bun.com/docs/api/utils#bun-readablestreamto) for documentation on Bun's other `ReadableStream` conversion functions.
+See [Docs > API > Utils](/docs/runtime/utils#bun-readablestreamto) for documentation on Bun's other `ReadableStream` conversion functions.

package/docs/guides/streams/to-buffer.mdx

@@ -14,4 +14,4 @@ const nodeBuf = Buffer.from(arrBuf);
 
 ---
 
-See [Docs > API > Utils](https://bun.com/docs/api/utils#bun-readablestreamto) for documentation on Bun's other `ReadableStream` conversion functions.
+See [Docs > API > Utils](/docs/runtime/utils#bun-readablestreamto) for documentation on Bun's other `ReadableStream` conversion functions.

package/docs/guides/streams/to-json.mdx

@@ -13,4 +13,4 @@ const json = await stream.json();
 
 ---
 
-See [Docs > API > Utils](https://bun.com/docs/api/utils#bun-readablestreamto) for documentation on Bun's other `ReadableStream` conversion functions.
+See [Docs > API > Utils](/docs/runtime/utils#bun-readablestreamto) for documentation on Bun's other `ReadableStream` conversion functions.

package/docs/guides/streams/to-string.mdx

@@ -13,4 +13,4 @@ const str = await Bun.readableStreamToText(stream);
 
 ---
 
-See [Docs > API > Utils](https://bun.com/docs/api/utils#bun-readablestreamto) for documentation on Bun's other `ReadableStream` conversion functions.
+See [Docs > API > Utils](/docs/runtime/utils#bun-readablestreamto) for documentation on Bun's other `ReadableStream` conversion functions.

package/docs/guides/streams/to-typedarray.mdx

@@ -21,4 +21,4 @@ const uint8 = await Bun.readableStreamToBytes(stream);
 
 ---
 
-See [Docs > API > Utils](https://bun.com/docs/api/utils#bun-readablestreamto) for documentation on Bun's other `ReadableStream` conversion functions.
+See [Docs > API > Utils](/docs/runtime/utils#bun-readablestreamto) for documentation on Bun's other `ReadableStream` conversion functions.

package/docs/guides/test/bail.mdx

@@ -21,4 +21,4 @@ bun test --bail=10
 
 ---
 
-See [Docs > Test runner](https://bun.sh/docs/cli/test) for complete documentation of `bun test`.
+See [Docs > Test runner](/docs/test) for complete documentation of `bun test`.

package/docs/guides/test/concurrent-test-glob.mdx

@@ -2,6 +2,7 @@
 title: Selectively run tests concurrently with glob patterns
 sidebarTitle: Concurrent test glob
 mode: center
+description: Set a glob pattern to decide which tests from which files run in parallel
 ---
 
 This guide demonstrates how to use the `concurrentTestGlob` option to selectively run tests concurrently based on file naming patterns.
@@ -69,12 +70,14 @@ test("fetch user data", async () => {
   expect(response.ok).toBe(true);
 });
 
-test("fetch posts", async () => {
+// can also use test.concurrent() for explicitly marking it as concurrent
+test.concurrent("fetch posts", async () => {
   const response = await fetch("/api/posts");
   expect(response.ok).toBe(true);
 });
 
-test("fetch comments", async () => {
+// can also use test.serial() for explicitly marking it as sequential
+test.serial("fetch comments", async () => {
   const response = await fetch("/api/comments");
   expect(response.ok).toBe(true);
 });

package/docs/guides/test/coverage-threshold.mdx

@@ -64,4 +64,4 @@ coverageThreshold = { lines = 0.5, functions = 0.7 }
 
 ---
 
-See [Docs > Test runner > Coverage](https://bun.sh/docs/test/coverage) for complete documentation on code coverage reporting in Bun.
+See [Docs > Test runner > Coverage](/docs/test/code-coverage) for complete documentation on code coverage reporting in Bun.

package/docs/guides/test/coverage.mdx

@@ -46,4 +46,4 @@ coverage = true # always enable coverage
 
 ---
 
-Refer to [Docs > Test runner > Coverage](https://bun.sh/docs/test/coverage) for complete documentation on code coverage reporting in Bun.
+Refer to [Docs > Test runner > Coverage](/docs/test/code-coverage) for complete documentation on code coverage reporting in Bun.

package/docs/guides/test/happy-dom.mdx

@@ -70,4 +70,4 @@ Ran 1 tests across 1 files. 1 total [125.00ms]
 
 ---
 
-Refer to the [Happy DOM repo](https://github.com/capricorn86/happy-dom) and [Docs > Test runner > DOM](https://bun.sh/docs/test/dom) for complete documentation on writing browser tests with Bun.
+Refer to the [Happy DOM repo](https://github.com/capricorn86/happy-dom) and [Docs > Test runner > DOM](/docs/test/dom) for complete documentation on writing browser tests with Bun.

package/docs/guides/test/migrate-from-jest.mdx

@@ -62,7 +62,7 @@ describe("my test suite", () => {
 
 ---
 
-Bun implements the vast majority of Jest's matchers, but compatibility isn't 100% yet. Refer to the full compatibility table at [Docs > Test runner > Writing tests](https://bun.sh/docs/test/writing#matchers).
+Bun implements the vast majority of Jest's matchers, but compatibility isn't 100% yet. Refer to the full compatibility table at [Docs > Test runner > Writing tests](/docs/test/writing-tests#matchers).
 
 Some notable missing features:
 
@@ -70,11 +70,11 @@ Some notable missing features:
 
 ---
 
-If you're using `testEnvironment: "jsdom"` to run your tests in a browser-like environment, you should follow the [DOM testing with Bun and happy-dom](/guides/test/happy-dom) guide to inject browser APIs into the global scope. This guide relies on [`happy-dom`](https://github.com/capricorn86/happy-dom), which is a leaner and faster alternative to [`jsdom`](https://github.com/jsdom/jsdom).
+If you're using `testEnvironment: "jsdom"` to run your tests in a browser-like environment, you should follow the [DOM testing with Bun and happy-dom](/docs/guides/test/happy-dom) guide to inject browser APIs into the global scope. This guide relies on [`happy-dom`](https://github.com/capricorn86/happy-dom), which is a leaner and faster alternative to [`jsdom`](https://github.com/jsdom/jsdom).
 
 At the moment jsdom does not work in Bun due to its internal use of V8 APIs. Track support for it [here](https://github.com/oven-sh/bun/issues/3554).
 
-```toml bunfig.toml
+```toml bunfig.toml icon="settings"
 [test]
 preload = ["./happy-dom.ts"]
 ```
@@ -107,11 +107,11 @@ bun test --timeout 10000
 
 Many other flags become irrelevant or obsolete when using `bun test`.
 
-- `transform` — Bun supports TypeScript & JSX. Other file types can be configured with [Plugins](https://bun.sh/docs/runtime/plugins).
+- `transform` — Bun supports TypeScript & JSX. Other file types can be configured with [Plugins](/docs/runtime/plugins).
 - `extensionsToTreatAsEsm`
 - `haste` — Bun uses it's own internal source maps
 - `watchman`, `watchPlugins`, `watchPathIgnorePatterns` — use `--watch` to run tests in watch mode
-- `verbose` — set `logLevel: "debug"` in [`bunfig.toml`](https://bun.sh/docs/runtime/bunfig#loglevel)
+- `verbose` — set `logLevel: "debug"` in [`bunfig.toml`](/docs/runtime/bunfig#loglevel)
 
 ---
 
@@ -121,5 +121,5 @@ Settings that aren't mentioned here are not supported or have no equivalent. Ple
 
 See also:
 
-- [Mark a test as a todo](/guides/test/todo-tests)
-- [Docs > Test runner > Writing tests](https://bun.sh/docs/test/writing)
+- [Mark a test as a todo](/docs/guides/test/todo-tests)
+- [Docs > Test runner > Writing tests](/docs/test/writing-tests)

package/docs/guides/test/mock-clock.mdx

@@ -22,7 +22,7 @@ test("party like it's 1999", () => {
 
 ---
 
-The `setSystemTime` function is commonly used on conjunction with [Lifecycle Hooks](https://bun.sh/docs/test/lifecycle) to configure a testing environment with a deterministic "fake clock".
+The `setSystemTime` function is commonly used on conjunction with [Lifecycle Hooks](/docs/test/lifecycle) to configure a testing environment with a deterministic "fake clock".
 
 ```ts
 import { test, expect, beforeAll, setSystemTime } from "bun:test";
@@ -47,4 +47,4 @@ setSystemTime(); // reset to actual time
 
 ---
 
-See [Docs > Test Runner > Date and time](https://bun.sh/docs/test/time) for complete documentation on mocking with the Bun test runner.
+See [Docs > Test Runner > Date and time](/docs/test/dates-times) for complete documentation on mocking with the Bun test runner.

package/docs/guides/test/mock-functions.mdx

@@ -67,4 +67,4 @@ test("random", async () => {
 
 ---
 
-See [Docs > Test Runner > Mocks](https://bun.sh/docs/test/mocks) for complete documentation on mocking with the Bun test runner.
+See [Docs > Test Runner > Mocks](/docs/test/mocks) for complete documentation on mocking with the Bun test runner.

package/docs/guides/test/rerun-each.mdx

@@ -13,4 +13,4 @@ bun test --rerun-each 10
 
 ---
 
-See [Docs > Test runner](https://bun.sh/docs/cli/test) for complete documentation of `bun test`.
+See [Docs > Test runner](/docs/test) for complete documentation of `bun test`.

package/docs/guides/test/run-tests.mdx

@@ -4,7 +4,7 @@ sidebarTitle: Run tests
 mode: center
 ---
 
-Bun has a built-in [test runner](https://bun.sh/docs/cli/test) with a Jest-like `expect` API.
+Bun has a built-in [test runner](/docs/test) with a Jest-like `expect` API.
 
 ---
 
@@ -113,4 +113,4 @@ Ran 6 tests across 3 files. [59.00ms]
 
 ---
 
-See [Docs > Test Runner](https://bun.sh/docs/cli/test) for complete documentation on the test runner.
+See [Docs > Test Runner](/docs/test) for complete documentation on the test runner.

package/docs/guides/test/skip-tests.mdx

@@ -39,5 +39,5 @@ Ran 3 tests across 1 files. [74.00ms]
 
 See also:
 
-- [Mark a test as a todo](/guides/test/todo-tests)
-- [Docs > Test runner > Writing tests](https://bun.sh/docs/test/writing)
+- [Mark a test as a todo](/docs/guides/test/todo-tests)
+- [Docs > Test runner > Writing tests](/docs/test/writing-tests)

package/docs/guides/test/snapshot.mdx

@@ -49,7 +49,7 @@ test
 The `snap.test.ts.snap` file is a JavaScript file that exports a serialized version of the value passed into `expect()`. The `{foo: "bar"}` object has been serialized to JSON.
 
 ```js snap.test.ts.snap icon="file-code"
-// Bun Snapshot v1, https://bun.sh/docs/test/snapshots
+// Bun Snapshot v1, https://bun.com/docs/test/snapshots
 
 exports[`snapshot 1`] = `
 {
@@ -67,7 +67,7 @@ bun test
 ```
 
 ```txt
-bun test v1.3.2 (9c68abdb)
+bun test v1.3.3 (9c68abdb)
 test/snap.test.ts:
 ✓ snapshot [1.05ms]
 
@@ -86,7 +86,7 @@ bun test --update-snapshots
 ```
 
 ```txt
-bun test v1.3.2 (9c68abdb)
+bun test v1.3.3 (9c68abdb)
 test/snap.test.ts:
 ✓ snapshot [0.86ms]
 
@@ -99,4 +99,4 @@ Ran 1 tests across 1 files. [102.00ms]
 
 ---
 
-See [Docs > Test Runner > Snapshots](https://bun.sh/docs/test/snapshots) for complete documentation on snapshots with the Bun test runner.
+See [Docs > Test Runner > Snapshots](/docs/test/snapshots) for complete documentation on snapshots with the Bun test runner.

package/docs/guides/test/spy-on.mdx

@@ -46,4 +46,4 @@ test("turtles", () => { // [!code ++]
 
 ---
 
-See [Docs > Test Runner > Mocks](https://bun.sh/docs/test/mocks) for complete documentation on mocking with the Bun test runner.
+See [Docs > Test Runner > Mocks](/docs/test/mocks) for complete documentation on mocking with the Bun test runner.

package/docs/guides/test/svelte-test.mdx

@@ -4,7 +4,7 @@ sidebarTitle: Test Svelte
 mode: center
 ---
 
-Bun's [Plugin API](/runtime/plugins) lets you add custom loaders to your project. The `test.preload` option in `bunfig.toml` lets you configure your loader to start before your tests run.
+Bun's [Plugin API](/docs/runtime/plugins) lets you add custom loaders to your project. The `test.preload` option in `bunfig.toml` lets you configure your loader to start before your tests run.
 
 Firstly, install `@testing-library/svelte`, `svelte`, and `@happy-dom/global-registrator`.
 
@@ -14,7 +14,7 @@ bun add @testing-library/svelte svelte@4 @happy-dom/global-registrator
 
 Then, save this plugin in your project.
 
-```ts svelte-loader.js icon="/icons/typescript.svg"
+```ts svelte-loader.ts icon="/icons/typescript.svg"
 import { plugin } from "bun";
 import { compile } from "svelte/compiler";
 import { readFileSync } from "fs";
@@ -61,10 +61,10 @@ Add this to `bunfig.toml` to tell Bun to preload the plugin, so it loads before
 ```toml bunfig.toml icon="settings"
 [test]
 # Tell Bun to load this plugin before your tests run
-preload = ["./svelte-loader.js"]
+preload = ["./svelte-loader.ts"]
 
 # This also works:
-# test.preload = ["./svelte-loader.js"]
+# test.preload = ["./svelte-loader.ts"]
 ```
 
 ---

package/docs/guides/test/testing-library.mdx

@@ -8,7 +8,7 @@ You can use [Testing Library](https://testing-library.com/) with Bun's test runn
 
 ---
 
-As a prerequisite to using Testing Library you will need to install [Happy Dom](https://github.com/capricorn86/happy-dom). ([see Bun's Happy DOM guide for more information](https://bun.sh/guides/test/happy-dom)).
+As a prerequisite to using Testing Library you will need to install [Happy Dom](https://github.com/capricorn86/happy-dom). ([see Bun's Happy DOM guide for more information](/docs/guides/test/happy-dom)).
 
 ```sh terminal icon="terminal"
 bun add -D @happy-dom/global-registrator
@@ -24,7 +24,7 @@ bun add -D @testing-library/react @testing-library/dom @testing-library/jest-dom
 
 ---
 
-Next you will need to create a preload script for Happy DOM and for Testing Library. For more details about the Happy DOM setup script see [Bun's Happy DOM guide](https://bun.sh/guides/test/happy-dom).
+Next you will need to create a preload script for Happy DOM and for Testing Library. For more details about the Happy DOM setup script see [Bun's Happy DOM guide](/docs/guides/test/happy-dom).
 
 ```ts happydom.ts icon="/icons/typescript.svg"
 import { GlobalRegistrator } from "@happy-dom/global-registrator";
@@ -90,4 +90,4 @@ test("Can use Testing Library", () => {
 
 ---
 
-Refer to the [Testing Library docs](https://testing-library.com/), [Happy DOM repo](https://github.com/capricorn86/happy-dom) and [Docs > Test runner > DOM](https://bun.sh/docs/test/dom) for complete documentation on writing browser tests with Bun.
+Refer to the [Testing Library docs](https://testing-library.com/), [Happy DOM repo](https://github.com/capricorn86/happy-dom) and [Docs > Test runner > DOM](/docs/test/dom) for complete documentation on writing browser tests with Bun.

package/docs/guides/test/timeout.mdx

@@ -14,4 +14,4 @@ bun test --timeout 3000 # 3 seconds
 
 ---
 
-See [Docs > Test runner](https://bun.sh/docs/cli/test) for complete documentation of `bun test`.
+See [Docs > Test runner](/docs/test) for complete documentation of `bun test`.

package/docs/guides/test/todo-tests.mdx

@@ -70,5 +70,5 @@ $ echo $?
 
 See also:
 
-- [Skip a test](/guides/test/skip-tests)
-- [Docs > Test runner > Writing tests](https://bun.sh/docs/test/writing)
+- [Skip a test](/docs/guides/test/skip-tests)
+- [Docs > Test runner > Writing tests](/docs/test/writing-tests)