bun-types 1.3.2-canary.20251105T140650 → 1.3.2-canary.20251106T140813

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

@@ -1,22 +0,0 @@
----
-name: Convert a ReadableStream to a Uint8Array
----
-
-Bun provides a number of convenience functions for reading the contents of a [`ReadableStream`](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream) into different formats. This snippet reads the contents of a `ReadableStream` to an [`ArrayBuffer`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer), then creates a [`Uint8Array`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Uint8Array) that points to the buffer.
-
-```ts
-const stream = new ReadableStream();
-const buf = await Bun.readableStreamToArrayBuffer(stream);
-const uint8 = new Uint8Array(buf);
-```
-
-Additionally, there is a convenience method to convert to `Uint8Array` directly.
-
-```ts
-const stream = new ReadableStream();
-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.

package/docs/guides/test/bail.md

@@ -1,22 +0,0 @@
----
-name: Bail early with the Bun test runner
----
-
-Use the `--bail` flag to bail on a test run after a single failure. This is useful for aborting as soon as possible in a continuous integration environment.
-
-```sh
-$ bun test --bail
-```
-
----
-
-To bail after a certain threshold of failures, optionally specify a number after the flag.
-
-```sh
-# bail after 10 failures
-$ bun test --bail=10
-```
-
----
-
-See [Docs > Test runner](https://bun.sh/docs/cli/test) for complete documentation of `bun test`.

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

@@ -1,60 +0,0 @@
----
-name: Set a code coverage threshold with the Bun test runner
----
-
-Bun's test runner supports built-in code coverage reporting via the `--coverage` flag.
-
-```sh
-$ bun test --coverage
-
-test.test.ts:
-✓ math > add [0.71ms]
-✓ math > multiply [0.03ms]
-✓ random [0.13ms]
--------------|---------|---------|-------------------
-File         | % Funcs | % Lines | Uncovered Line #s
--------------|---------|---------|-------------------
-All files    |   66.67 |   77.78 |
- math.ts     |   50.00 |   66.67 |
- random.ts   |   50.00 |   66.67 |
--------------|---------|---------|-------------------
-
- 3 pass
- 0 fail
- 3 expect() calls
-```
-
----
-
-To set a minimum coverage threshold, add the following line to your `bunfig.toml`. This requires that 90% of your codebase is covered by tests.
-
-```toml
-[test]
-# to require 90% line-level and function-level coverage
-coverageThreshold = 0.9
-```
-
----
-
-If your test suite does not meet this threshold, `bun test` will exit with a non-zero exit code to signal a failure.
-
-```sh
-$ bun test --coverage
-<test output>
-$ echo $?
-1 # this is the exit code of the previous command
-```
-
----
-
-Different thresholds can be set for line-level and function-level coverage.
-
-```toml
-[test]
-# to set different thresholds for lines and functions
-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.

package/docs/guides/test/coverage.md

@@ -1,44 +0,0 @@
----
-name: Generate code coverage reports with the Bun test runner
----
-
-Bun's test runner supports built-in _code coverage reporting_. This makes it easy to see how much of the codebase is covered by tests and find areas that are not currently well-tested.
-
----
-
-Pass the `--coverage` flag to `bun test` to enable this feature. This will print a coverage report after the test run.
-
-The coverage report lists the source files that were executed during the test run, the percentage of functions and lines that were executed, and the line ranges that were not executed during the run.
-
-```sh
-$ bun test --coverage
-
-test.test.ts:
-✓ math > add [0.71ms]
-✓ math > multiply [0.03ms]
-✓ random [0.13ms]
--------------|---------|---------|-------------------
-File         | % Funcs | % Lines | Uncovered Line #s
--------------|---------|---------|-------------------
-All files    |   66.67 |   77.78 |
- math.ts     |   50.00 |   66.67 |
- random.ts   |   50.00 |   66.67 |
--------------|---------|---------|-------------------
-
- 3 pass
- 0 fail
- 3 expect() calls
-```
-
----
-
-To always enable coverage reporting by default, add the following line to your `bunfig.toml`:
-
-```toml
-[test]
-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.

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

@@ -1,68 +0,0 @@
----
-name: Write browser DOM tests with Bun and happy-dom
----
-
-You can write and run browser tests with Bun's test runner in conjunction with [Happy DOM](https://github.com/capricorn86/happy-dom). Happy DOM implements mocked versions of browser APIs like `document` and `location`.
-
----
-
-To get started, install `happy-dom`.
-
-```sh
-$ bun add -d @happy-dom/global-registrator
-```
-
----
-
-This module exports a "registrator" that injects the mocked browser APIs to the global scope.
-
-```ts#happydom.ts
-import { GlobalRegistrator } from "@happy-dom/global-registrator";
-
-GlobalRegistrator.register();
-```
-
----
-
-We need to make sure this file is executed before any of our test files. That's a job for Bun's built-in [_preload_]() functionality. Create a `bunfig.toml` file in the root of your project (if it doesn't already exist) and add the following lines.
-
-The `./happydom.ts` file should contain the registration code above.
-
-```toml#bunfig.toml
-[test]
-preload = "./happydom.ts"
-```
-
----
-
-Now running `bun test` inside our project will automatically execute `happydom.ts` first. We can start writing tests that use browser APIs.
-
-```ts
-import { test, expect } from "bun:test";
-
-test("set button text", () => {
-  document.body.innerHTML = `<button>My button</button>`;
-  const button = document.querySelector("button");
-  expect(button?.innerText).toEqual("My button");
-});
-```
-
----
-
-With Happy DOM properly configured, this test runs as expected.
-
-```sh
-$ bun test
-
-dom.test.ts:
-✓ set button text [0.82ms]
-
- 1 pass
- 0 fail
- 1 expect() calls
-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.

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

@@ -1,143 +0,0 @@
----
-name: Migrate from Jest to Bun's test runner
----
-
-In many cases, Bun's test runner can run Jest test suites with no code changes. Just run `bun test` instead of `npx jest`, `yarn test`, etc.
-
-```sh
-- $ npx jest
-- $ yarn test
-+ $ bun test
-```
-
----
-
-There's often no need for code changes.
-
-- Bun internally re-writes imports from `@jest/globals` to use the `bun:test` equivalents.
-- If you're relying on Jest to inject `test`, `expect`, etc. as globals, Bun does that too.
-
-But if you'd rather switch to the `bun:test` imports, you can do that too.
-
-```ts-diff
-- import {test, expect} from "@jest/globals";
-+ import {test, expect} from "bun:test";
-```
-
----
-
-Since Bun v1.2.19, you can enable **TypeScript support** for global test functions with a single triple-slash directive. This makes migrating from Jest even easier since you only need to add the directive once in your entire project:
-
-Add this directive to _just one file_ in your project, such as:
-
-- A `global.d.ts` file in your project root
-- Your test `preload.ts` setup file (if using `preload` in bunfig.toml)
-- Any single `.ts` file that TypeScript includes in your compilation
-
-```ts
-/// <reference types="bun-types/test-globals" />
-```
-
----
-
-Once added, all test files in your project automatically get TypeScript support for Jest globals:
-
-```ts#math.test.ts
-describe("my test suite", () => {
-  test("should work", () => {
-    expect(1 + 1).toBe(2);
-  });
-
-  beforeAll(() => {
-    // setup code
-  });
-
-  afterEach(() => {
-    // cleanup code
-  });
-});
-```
-
----
-
-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).
-
-Some notable missing features:
-
-- `expect().toHaveReturned()`
-
----
-
-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).
-
-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
-[test]
-preload = ["./happy-dom.ts"]
-```
-
----
-
-Replace `bail` in your Jest config with the `--bail` CLI flag.
-
-<!-- ```ts-diff
-- import type {Config} from 'jest';
--
-- const config: Config = {
--   bail: 3
-- };
-``` -->
-
-```sh
-$ bun test --bail=3
-```
-
----
-
-Replace `collectCoverage` with the `--coverage` CLI flag.
-
-<!-- ```ts-diff
-- import type {Config} from 'jest';
--
-- const config: Config = {
--   collectCoverageFrom: [
--     '**/*.{js,jsx}',
--     '!**/node_modules/**',
--     '!**/vendor/**',
--   ],
-- };
-``` -->
-
-```sh
-$ bun test --coverage
-```
-
----
-
-Replace `testTimeout` with the `--test-timeout` CLI flag.
-
-```sh
-$ 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).
-- `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)
-
----
-
-Settings that aren't mentioned here are not supported or have no equivalent. Please [file a feature request](https://github.com/oven-sh/bun) if something important is missing.
-
----
-
-See also:
-
-- [Mark a test as a todo](/guides/test/todo-tests)
-- [Docs > Test runner > Writing tests](https://bun.sh/docs/test/writing)

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

@@ -1,48 +0,0 @@
----
-name: Set the system time in Bun's test runner
----
-
-Bun's test runner supports setting the system time programmatically with the `setSystemTime` function.
-
-```ts
-import { test, expect, setSystemTime } from "bun:test";
-
-test("party like it's 1999", () => {
-  const date = new Date("1999-01-01T00:00:00.000Z");
-  setSystemTime(date); // it's now January 1, 1999
-
-  const now = new Date();
-  expect(now.getFullYear()).toBe(1999);
-  expect(now.getMonth()).toBe(0);
-  expect(now.getDate()).toBe(1);
-});
-```
-
----
-
-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".
-
-```ts
-import { test, expect, beforeAll, setSystemTime } from "bun:test";
-
-beforeAll(() => {
-  const date = new Date("1999-01-01T00:00:00.000Z");
-  setSystemTime(date); // it's now January 1, 1999
-});
-
-// tests...
-```
-
----
-
-To reset the system clock to the actual time, call `setSystemTime` with no arguments.
-
-```ts
-import { test, expect, beforeAll, setSystemTime } from "bun:test";
-
-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.

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

@@ -1,68 +0,0 @@
----
-name: Mock functions in `bun test`
----
-
-Create mocks with the `mock` function from `bun:test`.
-
-```ts
-import { test, expect, mock } from "bun:test";
-
-const random = mock(() => Math.random());
-```
-
----
-
-The mock function can accept arguments.
-
-```ts
-import { test, expect, mock } from "bun:test";
-
-const random = mock((multiplier: number) => multiplier * Math.random());
-```
-
----
-
-The result of `mock()` is a new function that's been decorated with some additional properties.
-
-```ts
-import { mock } from "bun:test";
-
-const random = mock((multiplier: number) => multiplier * Math.random());
-
-random(2);
-random(10);
-
-random.mock.calls;
-// [[ 2 ], [ 10 ]]
-
-random.mock.results;
-//  [
-//    { type: "return", value: 0.6533907460954099 },
-//    { type: "return", value: 0.6452713933037312 }
-//  ]
-```
-
----
-
-These extra properties make it possible to write `expect` assertions about usage of the mock function, including how many times it was called, the arguments, and the return values.
-
-```ts
-import { test, expect, mock } from "bun:test";
-
-const random = mock((multiplier: number) => multiplier * Math.random());
-
-test("random", async () => {
-  const a = random(1);
-  const b = random(2);
-  const c = random(3);
-
-  expect(random).toHaveBeenCalled();
-  expect(random).toHaveBeenCalledTimes(3);
-  expect(random.mock.args).toEqual([[1], [2], [3]]);
-  expect(random.mock.results[0]).toEqual({ type: "return", value: a });
-});
-```
-
----
-
-See [Docs > Test Runner > Mocks](https://bun.sh/docs/test/mocks) for complete documentation on mocking with the Bun test runner.

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

@@ -1,14 +0,0 @@
----
-name: Re-run tests multiple times with the Bun test runner
----
-
-Use the `--rerun-each` flag to re-run every test multiple times with the Bun test runner. This is useful for finding flaky or non-deterministic tests.
-
-```sh
-# re-run each test 10 times
-$ bun test --rerun-each 10
-```
-
----
-
-See [Docs > Test runner](https://bun.sh/docs/cli/test) for complete documentation of `bun test`.

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

@@ -1,111 +0,0 @@
----
-name: Run your tests with the Bun test runner
----
-
-Bun has a built-in [test runner](https://bun.sh/docs/cli/test) with a Jest-like `expect` API.
-
----
-
-To use it, run the `bun test` command from your project directory. The test runner will recursively search for all files in the directory that match the following patterns and execute the tests they contain.
-
-```txt
-*.test.{js|jsx|ts|tsx}
-*_test.{js|jsx|ts|tsx}
-*.spec.{js|jsx|ts|tsx}
-*_spec.{js|jsx|ts|tsx}
-```
-
----
-
-Here's what the output of a typical test run looks like. In this case, there are three tests files (`test.test.js`, `test2.test.js`, and `test3.test.js`) containing two tests each (`add` and `multiply`).
-
-```sh
-$ bun test
-bun test v1.3.2-canary.20251105T140650 (9c68abdb)
-
-test.test.js:
-✓ add [0.87ms]
-✓ multiply [0.02ms]
-
-test2.test.js:
-✓ add [0.72ms]
-✓ multiply [0.01ms]
-
-test3.test.js:
-✓ add [0.54ms]
-✓ multiply [0.01ms]
-
- 6 pass
- 0 fail
- 6 expect() calls
-Ran 6 tests across 3 files. [9.00ms]
-```
-
----
-
-To only run certain test files, pass a positional argument to `bun test`. The runner will only execute files that contain that argument in their path.
-
-```sh
-$ bun test test3
-bun test v1.3.2-canary.20251105T140650 (9c68abdb)
-
-test3.test.js:
-✓ add [1.40ms]
-✓ multiply [0.03ms]
-
- 2 pass
- 0 fail
- 2 expect() calls
-Ran 2 tests across 1 files. [15.00ms]
-```
-
----
-
-All tests have a name, defined using the first parameter to the `test` function. Tests can also be grouped into suites with `describe`.
-
-```ts
-import { test, expect, describe } from "bun:test";
-
-describe("math", () => {
-  test("add", () => {
-    expect(2 + 2).toEqual(4);
-  });
-
-  test("multiply", () => {
-    expect(2 * 2).toEqual(4);
-  });
-});
-```
-
----
-
-To filter which tests are executed by name, use the `-t`/`--test-name-pattern` flag.
-
-Adding `-t add` will only run tests with "add" in the name. This works with test names defined with `test` or test suite names defined with `describe`.
-
-```sh
-$ bun test -t add
-bun test v1.3.2-canary.20251105T140650 (9c68abdb)
-
-test.test.js:
-✓ add [1.79ms]
-» multiply
-
-test2.test.js:
-✓ add [2.30ms]
-» multiply
-
-test3.test.js:
-✓ add [0.32ms]
-» multiply
-
- 3 pass
- 3 skip
- 0 fail
- 3 expect() calls
-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.

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

@@ -1,39 +0,0 @@
----
-name: Skip tests with the Bun test runner
----
-
-To skip a test with the Bun test runner, use the `test.skip` function.
-
-```ts
-import { test } from "bun:test";
-
-test.skip("unimplemented feature", () => {
-  expect(Bun.isAwesome()).toBe(true);
-});
-```
-
----
-
-Running `bun test` will not execute this test. It will be marked as skipped in the terminal output.
-
-```sh
-$ bun test
-
-test.test.ts:
-✓ add [0.03ms]
-✓ multiply [0.02ms]
-» unimplemented feature
-
- 2 pass
- 1 skip
- 0 fail
- 2 expect() calls
-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)