bun-types 1.2.19-canary.20250714T140751 → 1.2.19-canary.20250716T140648

package/bun.d.ts

@@ -2512,6 +2512,19 @@ declare module "bun" {
      * This defaults to `true`.
      */
     throw?: boolean;
+
+    /**
+     * Custom tsconfig.json file path to use for path resolution.
+     * Equivalent to `--tsconfig-override` in the CLI.
+     * @example
+     * ```ts
+     * await Bun.build({
+     *   entrypoints: ['./src/index.ts'],
+     *   tsconfig: './custom-tsconfig.json'
+     * });
+     * ```
+     */
+    tsconfig?: string;
   }
 
   /**

package/docs/api/fetch.md

@@ -337,7 +337,7 @@ This will print the request and response headers to your terminal:
 ```sh
 [fetch] > HTTP/1.1 GET http://example.com/
 [fetch] > Connection: keep-alive
-[fetch] > User-Agent: Bun/1.2.19-canary.20250714T140751
+[fetch] > User-Agent: Bun/1.2.19-canary.20250716T140648
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br

package/docs/api/spawn.md

@@ -140,7 +140,7 @@ You can read results from the subprocess via the `stdout` and `stderr` propertie
 ```ts
 const proc = Bun.spawn(["bun", "--version"]);
 const text = await proc.stdout.text();
-console.log(text); // => "1.2.19-canary.20250714T140751\n"
+console.log(text); // => "1.2.19-canary.20250716T140648\n"
 ```
 
 Configure the output stream by passing one of the following values to `stdout/stderr`:

package/docs/api/sql.md

@@ -274,6 +274,23 @@ If no connection URL is provided, the system checks for the following individual
 | `PGPASSWORD`         | -                            | (empty)       | Database password |
 | `PGDATABASE`         | -                            | username      | Database name     |
 
+## Runtime Preconnection
+
+Bun can preconnect to PostgreSQL at startup to improve performance by establishing database connections before your application code runs. This is useful for reducing connection latency on the first database query.
+
+```bash
+# Enable PostgreSQL preconnection
+bun --sql-preconnect index.js
+
+# Works with DATABASE_URL environment variable
+DATABASE_URL=postgres://user:pass@localhost:5432/db bun --sql-preconnect index.js
+
+# Can be combined with other runtime flags
+bun --sql-preconnect --hot index.js
+```
+
+The `--sql-preconnect` flag will automatically establish a PostgreSQL connection using your configured environment variables at startup. If the connection fails, it won't crash your application - the error will be handled gracefully.
+
 ## Connection Options
 
 You can configure your database connection manually by passing options to the SQL constructor:

package/docs/cli/pm.md

@@ -8,15 +8,70 @@ To create a tarball of the current workspace:
 $ bun pm pack
 ```
 
-Options for the `pack` command:
+This command creates a `.tgz` file containing all files that would be published to npm, following the same rules as `npm pack`.
 
-- `--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.
+## Examples
+
+Basic usage:
+
+```bash
+$ bun pm pack
+# Creates my-package-1.0.0.tgz in current directory
+```
+
+Quiet mode for scripting:
+
+```bash
+$ TARBALL=$(bun pm pack --quiet)
+$ echo "Created: $TARBALL"
+# Output: Created: my-package-1.0.0.tgz
+```
+
+Custom destination:
+
+```bash
+$ bun pm pack --destination ./dist
+# Saves tarball in ./dist/ directory
+```
+
+## Options
+
+- `--dry-run`: Perform all tasks except writing the tarball to disk. Shows what would be included.
+- `--destination <dir>`: Specify the directory where the tarball will be saved.
+- `--filename <name>`: 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).
+- `--gzip-level <0-9>`: Set a custom compression level for gzip, ranging from 0 to 9 (default is 9).
+- `--quiet`: Only output the tarball filename, suppressing verbose output. Ideal for scripts and automation.
+
+> **Note:** `--filename` and `--destination` cannot be used at the same time.
+
+## Output Modes
+
+**Default output:**
+
+```bash
+$ bun pm pack
+bun pack v1.2.19
+
+packed 131B package.json
+packed 40B index.js
+
+my-package-1.0.0.tgz
+
+Total files: 2
+Shasum: f2451d6eb1e818f500a791d9aace80b394258a90
+Unpacked size: 171B
+Packed size: 249B
+```
 
-> Note `--filename` and `--destination` cannot be used at the same time
+**Quiet output:**
+
+```bash
+$ bun pm pack --quiet
+my-package-1.0.0.tgz
+```
+
+The `--quiet` flag is particularly useful for automation workflows where you need to capture the generated tarball filename for further processing.
 
 ## bin
 
@@ -158,7 +213,7 @@ To display current package version and help:
 
 ```bash
 $ bun pm version
-bun pm version v1.2.19-canary.20250714T140751 (ca7428e9)
+bun pm version v1.2.19-canary.20250716T140648 (ca7428e9)
 Current package version: v1.0.0
 
 Increment:
@@ -193,3 +248,38 @@ v1.0.1
 ```
 
 Supports `patch`, `minor`, `major`, `premajor`, `preminor`, `prepatch`, `prerelease`, `from-git`, or specific versions like `1.2.3`. By default creates git commit and tag unless `--no-git-tag-version` was used to skip.
+
+## pkg
+
+Manage `package.json` data with get, set, delete, and fix operations.
+
+All commands support dot and bracket notation:
+
+```bash
+scripts.build              # dot notation
+contributors[0]            # array access
+workspaces.0               # dot with numeric index
+scripts[test:watch]        # bracket for special chars
+```
+
+Examples:
+
+```bash
+# set
+$ bun pm pkg get name                               # single property
+$ bun pm pkg get name version                       # multiple properties
+$ bun pm pkg get                                    # entire package.json
+$ bun pm pkg get scripts.build                      # nested property
+
+# set
+$ bun pm pkg set name="my-package"                  # simple property
+$ bun pm pkg set scripts.test="jest" version=2.0.0  # multiple properties
+$ bun pm pkg set {"private":"true"} --json          # JSON values with --json flag
+
+# delete
+$ bun pm pkg delete description                     # single property
+$ bun pm pkg delete scripts.test contributors[0]    # multiple/nested
+
+# fix
+$ bun pm pkg fix                                    # auto-fix common issues
+```

package/docs/cli/publish.md

@@ -7,7 +7,7 @@ Use `bun publish` to publish a package to the npm registry.
 $ bun publish
 
 ## Output
-bun publish v1.2.19-canary.20250714T140751 (ca7428e9)
+bun publish v1.2.19-canary.20250716T140648 (ca7428e9)
 
 packed 203B package.json
 packed 224B README.md

package/docs/cli/why.md

@@ -0,0 +1,67 @@
+The `bun why` command explains why a package is installed in your project by showing the dependency chain that led to its installation.
+
+## Usage
+
+```bash
+$ bun why <package>
+```
+
+## Arguments
+
+- `<package>`: The name of the package to explain. Supports glob patterns like `@org/*` or `*-lodash`.
+
+## Options
+
+- `--top`: Show only the top-level dependencies instead of the complete dependency tree.
+- `--depth <number>`: Maximum depth of the dependency tree to display.
+
+## Examples
+
+Check why a specific package is installed:
+
+```bash
+$ bun why react
+react@18.2.0
+  └─ my-app@1.0.0 (requires ^18.0.0)
+```
+
+Check why all packages with a specific pattern are installed:
+
+```bash
+$ bun why "@types/*"
+@types/react@18.2.15
+  └─ dev my-app@1.0.0 (requires ^18.0.0)
+
+@types/react-dom@18.2.7
+  └─ dev my-app@1.0.0 (requires ^18.0.0)
+```
+
+Show only top-level dependencies:
+
+```bash
+$ bun why express --top
+express@4.18.2
+  └─ my-app@1.0.0 (requires ^4.18.2)
+```
+
+Limit the dependency tree depth:
+
+```bash
+$ bun why express --depth 2
+express@4.18.2
+  └─ express-pollyfill@1.20.1 (requires ^4.18.2)
+     └─ body-parser@1.20.1 (requires ^1.20.1)
+     └─ accepts@1.3.8 (requires ^1.3.8)
+        └─ (deeper dependencies hidden)
+```
+
+## Understanding the Output
+
+The output shows:
+
+- The package name and version being queried
+- The dependency chain that led to its installation
+- The type of dependency (dev, peer, optional, or production)
+- The version requirement specified in each package's dependencies
+
+For nested dependencies, the command shows the complete dependency tree by default, with indentation indicating the relationship hierarchy.

package/docs/guides/ecosystem/nuxt.md

@@ -9,7 +9,7 @@ $ bunx nuxi init my-nuxt-app
 ✔ Which package manager would you like to use?
 bun
 ◐ Installing dependencies...
-bun install v1.2.19-canary.20250714T140751 (16b4bf34)
+bun install v1.2.19-canary.20250716T140648 (16b4bf34)
  + @nuxt/devtools@0.8.2
  + nuxt@3.7.0
  785 packages installed [2.67s]

package/docs/guides/ecosystem/prisma.md

@@ -40,6 +40,7 @@ Open `prisma/schema.prisma` and add a simple `User` model.
 ```prisma-diff#prisma/schema.prisma
   generator client {
     provider = "prisma-client-js"
+    output = "../generated/prisma"
   }
 
   datasource db {
@@ -78,7 +79,7 @@ migrations/
 
 Your database is now in sync with your schema.
 
-✔ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 41ms
+✔ Generated Prisma Client (v6.11.1) to ./generated/prisma in 41ms
 ```
 
 ---

package/docs/guides/install/add-peer.md

@@ -15,7 +15,7 @@ This will add the package to `peerDependencies` in `package.json`.
 ```json-diff
 {
   "peerDependencies": {
-+   "@types/bun": "^1.2.19-canary.20250714T140751"
++   "@types/bun": "^1.2.19-canary.20250716T140648"
   }
 }
 ```
@@ -27,7 +27,7 @@ Running `bun install` will install peer dependencies by default, unless marked o
 ```json-diff
 {
   "peerDependencies": {
-    "@types/bun": "^1.2.19-canary.20250714T140751"
+    "@types/bun": "^1.2.19-canary.20250716T140648"
   },
   "peerDependenciesMeta": {
 +   "@types/bun": {

package/docs/guides/install/from-npm-install-to-bun-install.md

@@ -97,7 +97,7 @@ $ bun update
 $ bun update @types/bun --latest
 
 # Update a dependency to a specific version
-$ bun update @types/bun@1.2.19-canary.20250714T140751
+$ bun update @types/bun@1.2.19-canary.20250716T140648
 
 # Update all dependencies to the latest versions
 $ bun update --latest

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

@@ -21,7 +21,7 @@ Here's what the output of a typical test run looks like. In this case, there are
 
 ```sh
 $ bun test
-bun test v1.2.19-canary.20250714T140751 (9c68abdb)
+bun test v1.2.19-canary.20250716T140648 (9c68abdb)
 
 test.test.js:
 ✓ add [0.87ms]
@@ -47,7 +47,7 @@ To only run certain test files, pass a positional argument to `bun test`. The ru
 
 ```sh
 $ bun test test3
-bun test v1.2.19-canary.20250714T140751 (9c68abdb)
+bun test v1.2.19-canary.20250716T140648 (9c68abdb)
 
 test3.test.js:
 ✓ add [1.40ms]
@@ -85,7 +85,7 @@ Adding `-t add` will only run tests with "add" in the name. This works with test
 
 ```sh
 $ bun test -t add
-bun test v1.2.19-canary.20250714T140751 (9c68abdb)
+bun test v1.2.19-canary.20250716T140648 (9c68abdb)
 
 test.test.js:
 ✓ add [1.79ms]

package/docs/guides/test/snapshot.md

@@ -18,7 +18,7 @@ The first time this test is executed, Bun will evaluate the value passed into `e
 
 ```sh
 $ bun test test/snap
-bun test v1.2.19-canary.20250714T140751 (9c68abdb)
+bun test v1.2.19-canary.20250716T140648 (9c68abdb)
 
 test/snap.test.ts:
 ✓ snapshot [1.48ms]
@@ -61,7 +61,7 @@ Later, when this test file is executed again, Bun will read the snapshot file an
 
 ```sh
 $ bun test
-bun test v1.2.19-canary.20250714T140751 (9c68abdb)
+bun test v1.2.19-canary.20250716T140648 (9c68abdb)
 
 test/snap.test.ts:
 ✓ snapshot [1.05ms]
@@ -78,7 +78,7 @@ To update snapshots, use the `--update-snapshots` flag.
 
 ```sh
 $ bun test --update-snapshots
-bun test v1.2.19-canary.20250714T140751 (9c68abdb)
+bun test v1.2.19-canary.20250716T140648 (9c68abdb)
 
 test/snap.test.ts:
 ✓ snapshot [0.86ms]

package/docs/guides/test/update-snapshots.md

@@ -29,7 +29,7 @@ To regenerate snapshots, use the `--update-snapshots` flag.
 
 ```sh
 $ bun test --update-snapshots
-bun test v1.2.19-canary.20250714T140751 (9c68abdb)
+bun test v1.2.19-canary.20250716T140648 (9c68abdb)
 
 test/snap.test.ts:
 ✓ snapshot [0.86ms]

package/docs/guides/util/version.md

@@ -5,7 +5,7 @@ name: Get the current Bun version
 Get the current version of Bun in a semver format.
 
 ```ts#index.ts
-Bun.version; // => "1.2.19-canary.20250714T140751"
+Bun.version; // => "1.2.19-canary.20250716T140648"
 ```
 
 ---

package/docs/install/catalogs.md

@@ -52,6 +52,8 @@ In your root-level `package.json`, add a `catalog` or `catalogs` field within th
 }
 ```
 
+If you put `catalog` or `catalogs` at the top level of the `package.json` file, that will work too.
+
 ### 2. Reference Catalog Versions in Workspace Packages
 
 In your workspace packages, use the `catalog:` protocol to reference versions:

package/docs/installation.md

@@ -14,7 +14,7 @@ Kernel version 5.6 or higher is strongly recommended, but the minimum is 5.1. Us
 ```bash#macOS/Linux_(curl)
 $ curl -fsSL https://bun.com/install | bash # for macOS, Linux, and WSL
 # to install a specific version
-$ curl -fsSL https://bun.com/install | bash -s "bun-v1.2.19-canary.20250714T140751"
+$ curl -fsSL https://bun.com/install | bash -s "bun-v1.2.19-canary.20250716T140648"
 ```
 
 ```bash#npm
@@ -189,10 +189,10 @@ Since Bun is a single binary, you can install older versions of Bun by re-runnin
 
 ### Installing a specific version of Bun on Linux/Mac
 
-To install a specific version of Bun, you can pass the git tag of the version you want to install to the install script, such as `bun-v1.2.0` or `bun-v1.2.19-canary.20250714T140751`.
+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.20250716T140648`.
 
 ```sh
-$ curl -fsSL https://bun.com/install | bash -s "bun-v1.2.19-canary.20250714T140751"
+$ curl -fsSL https://bun.com/install | bash -s "bun-v1.2.19-canary.20250716T140648"
 ```
 
 ### 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.com/install.ps1)} -Version 1.2.19-canary.20250714T140751"
+$ iex "& {$(irm https://bun.com/install.ps1)} -Version 1.2.19-canary.20250716T140648"
 ```
 
 ## Downloading Bun binaries directly

package/docs/runtime/bunfig.md

@@ -195,6 +195,24 @@ Whether to skip test files when computing coverage statistics. Default `false`.
 coverageSkipTestFiles = false
 ```
 
+### `test.coveragePathIgnorePatterns`
+
+Exclude specific files or file patterns from coverage reports using glob patterns. Can be a single string pattern or an array of patterns.
+
+```toml
+[test]
+# Single pattern
+coveragePathIgnorePatterns = "**/*.spec.ts"
+
+# Multiple patterns
+coveragePathIgnorePatterns = [
+  "**/*.spec.ts",
+  "**/*.test.ts",
+  "src/utils/**",
+  "*.config.js"
+]
+```
+
 ### `test.coverageReporter`
 
 By default, coverage reports will be printed to the console. For persistent code coverage reports in CI environments and for other tools use `lcov`.

package/docs/runtime/debugger.md

@@ -124,11 +124,11 @@ await fetch("https://example.com", {
 This prints the `fetch` request as a single-line `curl` command to let you copy-paste into your terminal to replicate the request.
 
 ```sh
-[fetch] $ curl --http1.1 "https://example.com/" -X POST -H "content-type: application/json" -H "Connection: keep-alive" -H "User-Agent: Bun/1.2.19-canary.20250714T140751" -H "Accept: */*" -H "Host: example.com" -H "Accept-Encoding: gzip, deflate, br" --compressed -H "Content-Length: 13" --data-raw "{\"foo\":\"bar\"}"
+[fetch] $ curl --http1.1 "https://example.com/" -X POST -H "content-type: application/json" -H "Connection: keep-alive" -H "User-Agent: Bun/1.2.19-canary.20250716T140648" -H "Accept: */*" -H "Host: example.com" -H "Accept-Encoding: gzip, deflate, br" --compressed -H "Content-Length: 13" --data-raw "{\"foo\":\"bar\"}"
 [fetch] > HTTP/1.1 POST https://example.com/
 [fetch] > content-type: application/json
 [fetch] > Connection: keep-alive
-[fetch] > User-Agent: Bun/1.2.19-canary.20250714T140751
+[fetch] > User-Agent: Bun/1.2.19-canary.20250716T140648
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br
@@ -170,7 +170,7 @@ This prints the following to the console:
 [fetch] > HTTP/1.1 POST https://example.com/
 [fetch] > content-type: application/json
 [fetch] > Connection: keep-alive
-[fetch] > User-Agent: Bun/1.2.19-canary.20250714T140751
+[fetch] > User-Agent: Bun/1.2.19-canary.20250716T140648
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br

package/docs/test/configuration.md

@@ -71,6 +71,26 @@ coverageThreshold = { lines = 0.9, functions = 0.8, statements = 0.85 }
 
 Setting any of these enables `fail_on_low_coverage`, causing the test run to fail if coverage is below the threshold.
 
+#### coveragePathIgnorePatterns
+
+Exclude specific files or file patterns from coverage reports using glob patterns:
+
+```toml
+[test]
+# Single pattern
+coveragePathIgnorePatterns = "**/*.spec.ts"
+
+# Multiple patterns
+coveragePathIgnorePatterns = [
+  "**/*.spec.ts",
+  "**/*.test.ts",
+  "src/utils/**",
+  "*.config.js"
+]
+```
+
+Files matching any of these patterns will be excluded from coverage calculation and reporting. See the [coverage documentation](./coverage.md) for more details and examples.
+
 #### coverageIgnoreSourcemaps
 
 Internally, Bun transpiles every file. That means code coverage must also go through sourcemaps before they can be reported. We expose this as a flag to allow you to opt out of this behavior, but it will be confusing because during the transpilation process, Bun may move code around and change variable names. This option is mostly useful for debugging coverage issues.

package/docs/test/coverage.md

@@ -57,7 +57,18 @@ coverageThreshold = { lines = 0.9, functions = 0.9, statements = 0.9 }
 
 Setting any of these thresholds enables `fail_on_low_coverage`, causing the test run to fail if coverage is below the threshold.
 
-### Exclude test files from coverage
+### Sourcemaps
+
+Internally, Bun transpiles all files by default, so Bun automatically generates an internal [source map](https://web.dev/source-maps/) that maps lines of your original source code onto Bun's internal representation. If for any reason you want to disable this, set `test.coverageIgnoreSourcemaps` to `true`; this will rarely be desirable outside of advanced use cases.
+
+```toml
+[test]
+coverageIgnoreSourcemaps = true   # default false
+```
+
+### Exclude files from coverage
+
+#### Skip test files
 
 By default, test files themselves are included in coverage reports. You can exclude them with:
 
@@ -68,15 +79,33 @@ coverageSkipTestFiles = true   # default false
 
 This will exclude files matching test patterns (e.g., _.test.ts, _\_spec.js) from the coverage report.
 
-### Sourcemaps
+#### Ignore specific paths and patterns
 
-Internally, Bun transpiles all files by default, so Bun automatically generates an internal [source map](https://web.dev/source-maps/) that maps lines of your original source code onto Bun's internal representation. If for any reason you want to disable this, set `test.coverageIgnoreSourcemaps` to `true`; this will rarely be desirable outside of advanced use cases.
+You can exclude specific files or file patterns from coverage reports using `coveragePathIgnorePatterns`:
 
 ```toml
 [test]
-coverageIgnoreSourcemaps = true   # default false
+# Single pattern
+coveragePathIgnorePatterns = "**/*.spec.ts"
+
+# Multiple patterns
+coveragePathIgnorePatterns = [
+  "**/*.spec.ts",
+  "**/*.test.ts",
+  "src/utils/**",
+  "*.config.js"
+]
 ```
 
+This option accepts glob patterns and works similarly to Jest's `collectCoverageFrom` ignore patterns. Files matching any of these patterns will be excluded from coverage calculation and reporting in both text and LCOV outputs.
+
+Common use cases:
+
+- Exclude utility files: `"src/utils/**"`
+- Exclude configuration files: `"*.config.js"`
+- Exclude specific test patterns: `"**/*.spec.ts"`
+- Exclude build artifacts: `"dist/**"`
+
 ### Coverage defaults
 
 By default, coverage reports:
@@ -84,6 +113,7 @@ By default, coverage reports:
 1. Exclude `node_modules` directories
 2. Exclude files loaded via non-JS/TS loaders (e.g., .css, .txt) unless a custom JS loader is specified
 3. Include test files themselves (can be disabled with `coverageSkipTestFiles = true` as shown above)
+4. Can exclude additional files with `coveragePathIgnorePatterns` as shown above
 
 ### Coverage reporters
 

package/docs/test/dom.md

@@ -55,7 +55,7 @@ Let's run this test with `bun test`:
 
 ```bash
 $ bun test
-bun test v1.2.19-canary.20250714T140751
+bun test v1.2.19-canary.20250716T140648
 
 dom.test.ts:
 ✓ dom test [0.82ms]

package/package.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.2.19-canary.20250714T140751",
+  "version": "1.2.19-canary.20250716T140648",
   "name": "bun-types",
   "license": "MIT",
   "types": "./index.d.ts",