bun-types 1.2.3-canary.20250209T140621 → 1.2.3-canary.20250210T140549

package/bun.d.ts

@@ -3822,7 +3822,17 @@ declare module "bun" {
 		 * Render contextual errors? This enables bun's error page
 		 * @default process.env.NODE_ENV !== 'production'
 		 */
-		development?: boolean;
+		development?:
+			| boolean
+			| {
+					/**
+					 * Enable Hot Module Replacement for routes (including React Fast Refresh, if React is in use)
+					 *
+					 * @default true if process.env.NODE_ENV !== 'production'
+					 *
+					 */
+					hmr?: boolean;
+			  };
 
 		error?: (
 			this: Server,

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.3-canary.20250209T140621
+[fetch] > User-Agent: Bun/1.2.3-canary.20250210T140549
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br

package/docs/api/spawn.md

@@ -110,7 +110,7 @@ You can read results from the subprocess via the `stdout` and `stderr` propertie
 ```ts
 const proc = Bun.spawn(["bun", "--version"]);
 const text = await new Response(proc.stdout).text();
-console.log(text); // => "1.2.3-canary.20250209T140621"
+console.log(text); // => "1.2.3-canary.20250210T140549"
 ```
 
 Configure the output stream by passing one of the following values to `stdout/stderr`:

package/docs/bundler/executables.md

@@ -196,6 +196,8 @@ import icon from "./icon.png" with { type: "file" };
 import { file } from "bun";
 
 const bytes = await file(icon).arrayBuffer();
+// await fs.promises.readFile(icon)
+// fs.readFileSync(icon)
 ```
 
 ### Embed SQLite databases

package/docs/bundler/loaders.md

@@ -192,8 +192,6 @@ Otherwise, the database to embed is copied into the `outdir` with a hashed filen
 
 ### `html`
 
-**HTML loader**. Default for `.html` after Bun v1.2.0.
-
 The html loader processes HTML files and bundles any referenced assets. It will:
 
 - Bundle and hash referenced JavaScript files (`<script src="...">`)

package/docs/cli/bun-create.md

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

package/docs/cli/outdated.md

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

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.3-canary.20250209T140621 (ca7428e9)
+bun publish v1.2.3-canary.20250210T140549 (ca7428e9)
 
 packed 203B package.json
 packed 224B README.md

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.3-canary.20250209T140621 (16b4bf34)
+bun install v1.2.3-canary.20250210T140549 (16b4bf34)
  + @nuxt/devtools@0.8.2
  + nuxt@3.7.0
  785 packages installed [2.67s]

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

@@ -16,7 +16,7 @@ This will add the package to `peerDependencies` in `package.json`.
 ```json-diff
 {
   "peerDependencies": {
-+   "@types/bun": "^1.2.3-canary.20250209T140621"
++   "@types/bun": "^1.2.3-canary.20250210T140549"
   }
 }
 ```
@@ -28,7 +28,7 @@ Running `bun install` will install peer dependencies by default, unless marked o
 ```json-diff
 {
   "peerDependencies": {
-    "@types/bun": "^1.2.3-canary.20250209T140621"
+    "@types/bun": "^1.2.3-canary.20250210T140549"
   },
   "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.3-canary.20250209T140621
+$ bun update @types/bun@1.2.3-canary.20250210T140549
 
 # 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.3-canary.20250209T140621 (9c68abdb)
+bun test v1.2.3-canary.20250210T140549 (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.3-canary.20250209T140621 (9c68abdb)
+bun test v1.2.3-canary.20250210T140549 (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.3-canary.20250209T140621 (9c68abdb)
+bun test v1.2.3-canary.20250210T140549 (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.3-canary.20250209T140621 (9c68abdb)
+bun test v1.2.3-canary.20250210T140549 (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.3-canary.20250209T140621 (9c68abdb)
+bun test v1.2.3-canary.20250210T140549 (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.3-canary.20250209T140621 (9c68abdb)
+bun test v1.2.3-canary.20250210T140549 (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.3-canary.20250209T140621 (9c68abdb)
+bun test v1.2.3-canary.20250210T140549 (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.3-canary.20250209T140621"
+Bun.version; // => "1.2.3-canary.20250210T140549"
 ```
 
 ---

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.sh/install | bash # for macOS, Linux, and WSL
 # to install a specific version
-$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.3-canary.20250209T140621"
+$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.3-canary.20250210T140549"
 ```
 
 ```bash#npm
@@ -166,10 +166,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.3-canary.20250209T140621`.
+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.3-canary.20250210T140549`.
 
 ```sh
-$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.3-canary.20250209T140621"
+$ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.3-canary.20250210T140549"
 ```
 
 ### Installing a specific version of Bun on Windows
@@ -178,7 +178,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.3-canary.20250209T140621"
+$ iex "& {$(irm https://bun.sh/install.ps1)} -Version 1.2.3-canary.20250210T140549"
 ```
 
 ## Downloading Bun binaries directly

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.3-canary.20250209T140621" -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.3-canary.20250210T140549" -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.3-canary.20250209T140621
+[fetch] > User-Agent: Bun/1.2.3-canary.20250210T140549
 [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.3-canary.20250209T140621
+[fetch] > User-Agent: Bun/1.2.3-canary.20250210T140549
 [fetch] > Accept: */*
 [fetch] > Host: example.com
 [fetch] > Accept-Encoding: gzip, deflate, br

package/docs/test/dom.md

@@ -55,7 +55,7 @@ Let's run this test with `bun test`:
 
 ```bash
 $ bun test
-bun test v1.2.3-canary.20250209T140621
+bun test v1.2.3-canary.20250210T140549
 
 dom.test.ts:
 ✓ dom test [0.82ms]

package/package.json

@@ -1,5 +1,5 @@
 {
-	"version": "1.2.3-canary.20250209T140621",
+	"version": "1.2.3-canary.20250210T140549",
 	"name": "bun-types",
 	"license": "MIT",
 	"main": "",

package/docs/cli/bun-dev.md

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