Add --resolve-extensions flag and bunfig.toml property for custom test file patterns

This change allows users to customize which file name patterns are recognized
as test files, providing flexibility for projects with different naming conventions.

Features:
- CLI flag: --resolve-extensions <STR>... (can specify multiple)
- bunfig.toml: [test] resolveExtensions = ".check" or [".check", ".verify"]
- CLI flag takes precedence over bunfig.toml configuration
- Dynamic error messages show configured extensions when no tests found
- Works with all JavaScript/TypeScript file extensions (.ts, .tsx, .js, .jsx, etc.)

Default behavior (unchanged):
- .test, _test, .spec, _spec suffixes continue to work when no custom config

Implementation:
- Modified Scanner.zig to accept custom test name suffixes
- Added resolve_extensions field to TestOptions in cli.zig
- Added CLI argument parsing in Arguments.zig
- Added bunfig.toml parsing in bunfig.zig with CLI override logic
- Updated error messages in test_command.zig to show custom extensions
- Added comprehensive test suite covering CLI, bunfig, and override scenarios

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

.aikido

@@ -0,0 +1,19 @@
+exclude:
+  paths:
+    - test
+    - scripts
+    - bench
+    - packages/bun-lambda
+    - packages/bun-release
+    - packages/bun-wasm
+    - packages/bun-vscode
+    - packages/bun-plugin-yaml
+    - packages/bun-plugin-svelte
+    - packages/bun-native-plugin-rs
+    - packages/bun-native-bundler-plugin-api
+    - packages/bun-inspector-protocol
+    - packages/bun-inspector-frontend
+    - packages/bun-error
+    - packages/bun-debug-adapter-protocol
+    - packages/bun-build-mdx-rs
+    - packages/@types/bun

CONTRIBUTING.md

@@ -201,7 +201,7 @@ Bun generally takes about 2.5 minutes to compile a debug build when there are Zi
 - Batch up your changes
 - Ensure zls is running with incremental watching for LSP errors (if you use VSCode and install Zig and run `bun run build` once to download Zig, this should just work)
 - Prefer using the debugger ("CodeLLDB" in VSCode) to step through the code.
-- Use debug logs. `BUN_DEBUG_<scope>=1` will enable debug logging for the corresponding `Output.scoped(.<scope>, .hidden)` logs. You can also set `BUN_DEBUG_QUIET_LOGS=1` to disable all debug logging that isn't explicitly enabled. To dump debug lgos into a file, `BUN_DEBUG=<path-to-file>.log`. Debug logs are aggressively removed in release builds.
+- Use debug logs. `BUN_DEBUG_<scope>=1` will enable debug logging for the corresponding `Output.scoped(.<scope>, .hidden)` logs. You can also set `BUN_DEBUG_QUIET_LOGS=1` to disable all debug logging that isn't explicitly enabled. To dump debug logs into a file, `BUN_DEBUG=<path-to-file>.log`. Debug logs are aggressively removed in release builds.
 - src/js/\*\*.ts changes are pretty much instant to rebuild. C++ changes are a bit slower, but still much faster than the Zig code (Zig is one compilation unit, C++ is many).
 
 ## Code generation scripts

LATEST

@@ -1 +1 @@
-1.3.2
+1.3.3

README.md

@@ -54,7 +54,7 @@ Bun supports Linux (x64 & arm64), macOS (x64 & Apple Silicon) and Windows (x64).
 curl -fsSL https://bun.com/install | bash
 
 # on windows
-powershell -c "irm bun.com/install.ps1 | iex"
+powershell -c "irm bun.sh/install.ps1 | iex"
 
 # with npm
 npm install -g bun
@@ -104,13 +104,13 @@ bun upgrade --canary
   - [File types (Loaders)](https://bun.com/docs/runtime/loaders)
   - [TypeScript](https://bun.com/docs/runtime/typescript)
   - [JSX](https://bun.com/docs/runtime/jsx)
-  - [Environment variables](https://bun.com/docs/runtime/env)
+  - [Environment variables](https://bun.com/docs/runtime/environment-variables)
   - [Bun APIs](https://bun.com/docs/runtime/bun-apis)
   - [Web APIs](https://bun.com/docs/runtime/web-apis)
-  - [Node.js compatibility](https://bun.com/docs/runtime/nodejs-apis)
+  - [Node.js compatibility](https://bun.com/docs/runtime/nodejs-compat)
   - [Single-file executable](https://bun.com/docs/bundler/executables)
   - [Plugins](https://bun.com/docs/runtime/plugins)
-  - [Watch mode / Hot Reloading](https://bun.com/docs/runtime/hot)
+  - [Watch mode / Hot Reloading](https://bun.com/docs/runtime/watch-mode)
   - [Module resolution](https://bun.com/docs/runtime/modules)
   - [Auto-install](https://bun.com/docs/runtime/autoimport)
   - [bunfig.toml](https://bun.com/docs/runtime/bunfig)

bench/runner.mjs

@@ -13,7 +13,4 @@ export function run(opts = {}) {
 }
 
 export const bench = Mitata.bench;
-
-export function group(_name, fn) {
-  return Mitata.group(fn);
-}
+export const group = Mitata.group;

bench/snippets/compression-streams.mjs

@@ -0,0 +1,156 @@
+import { bench, group, run } from "../runner.mjs";
+
+const runAll = !process.argv.includes("--simple");
+
+const small = new Uint8Array(1024);
+const medium = new Uint8Array(1024 * 100);
+const large = new Uint8Array(1024 * 1024);
+
+for (let i = 0; i < large.length; i++) {
+  const value = Math.floor(Math.sin(i / 100) * 128 + 128);
+  if (i < small.length) small[i] = value;
+  if (i < medium.length) medium[i] = value;
+  large[i] = value;
+}
+
+const format = new Intl.NumberFormat("en-US", { notation: "compact", unit: "byte" });
+
+async function compress(data, format) {
+  const cs = new CompressionStream(format);
+  const writer = cs.writable.getWriter();
+  const reader = cs.readable.getReader();
+
+  writer.write(data);
+  writer.close();
+
+  const chunks = [];
+  while (true) {
+    const { done, value } = await reader.read();
+    if (done) break;
+    chunks.push(value);
+  }
+
+  const result = new Uint8Array(chunks.reduce((acc, chunk) => acc + chunk.length, 0));
+  let offset = 0;
+  for (const chunk of chunks) {
+    result.set(chunk, offset);
+    offset += chunk.length;
+  }
+  return result;
+}
+
+async function decompress(data, format) {
+  const ds = new DecompressionStream(format);
+  const writer = ds.writable.getWriter();
+  const reader = ds.readable.getReader();
+
+  writer.write(data);
+  writer.close();
+
+  const chunks = [];
+  while (true) {
+    const { done, value } = await reader.read();
+    if (done) break;
+    chunks.push(value);
+  }
+
+  const result = new Uint8Array(chunks.reduce((acc, chunk) => acc + chunk.length, 0));
+  let offset = 0;
+  for (const chunk of chunks) {
+    result.set(chunk, offset);
+    offset += chunk.length;
+  }
+  return result;
+}
+
+async function roundTrip(data, format) {
+  const compressed = await compress(data, format);
+  return await decompress(compressed, format);
+}
+
+const formats = ["deflate", "gzip", "deflate-raw"];
+if (runAll) formats.push("brotli", "zstd");
+
+// Small data benchmarks (1KB)
+group(`CompressionStream ${format.format(small.length)}`, () => {
+  for (const fmt of formats) {
+    try {
+      new CompressionStream(fmt);
+      bench(fmt, async () => await compress(small, fmt));
+    } catch (e) {
+      // Skip unsupported formats
+    }
+  }
+});
+
+// Medium data benchmarks (100KB)
+group(`CompressionStream ${format.format(medium.length)}`, () => {
+  for (const fmt of formats) {
+    try {
+      new CompressionStream(fmt);
+      bench(fmt, async () => await compress(medium, fmt));
+    } catch (e) {}
+  }
+});
+
+// Large data benchmarks (1MB)
+group(`CompressionStream ${format.format(large.length)}`, () => {
+  for (const fmt of formats) {
+    try {
+      new CompressionStream(fmt);
+      bench(fmt, async () => await compress(large, fmt));
+    } catch (e) {
+      // Skip unsupported formats
+    }
+  }
+});
+
+const compressedData = {};
+for (const fmt of formats) {
+  try {
+    compressedData[fmt] = {
+      small: await compress(small, fmt),
+      medium: await compress(medium, fmt),
+      large: await compress(large, fmt),
+    };
+  } catch (e) {
+    // Skip unsupported formats
+  }
+}
+
+group(`DecompressionStream ${format.format(small.length)}`, () => {
+  for (const fmt of formats) {
+    if (compressedData[fmt]) {
+      bench(fmt, async () => await decompress(compressedData[fmt].small, fmt));
+    }
+  }
+});
+
+group(`DecompressionStream ${format.format(medium.length)}`, () => {
+  for (const fmt of formats) {
+    if (compressedData[fmt]) {
+      bench(fmt, async () => await decompress(compressedData[fmt].medium, fmt));
+    }
+  }
+});
+
+group(`DecompressionStream ${format.format(large.length)}`, () => {
+  for (const fmt of formats) {
+    if (compressedData[fmt]) {
+      bench(fmt, async () => await decompress(compressedData[fmt].large, fmt));
+    }
+  }
+});
+
+group(`roundtrip ${format.format(large.length)}`, () => {
+  for (const fmt of formats) {
+    try {
+      new CompressionStream(fmt);
+      bench(fmt, async () => await roundTrip(large, fmt));
+    } catch (e) {
+      // Skip unsupported formats
+    }
+  }
+});
+
+await run();

build.zig

@@ -32,6 +32,7 @@ const BunBuildOptions = struct {
     /// enable debug logs in release builds
     enable_logs: bool = false,
     enable_asan: bool,
+    enable_fuzzilli: bool,
     enable_valgrind: bool,
     use_mimalloc: bool,
     tracy_callstack_depth: u16,
@@ -81,6 +82,7 @@ const BunBuildOptions = struct {
         opts.addOption(bool, "baseline", this.isBaseline());
         opts.addOption(bool, "enable_logs", this.enable_logs);
         opts.addOption(bool, "enable_asan", this.enable_asan);
+        opts.addOption(bool, "enable_fuzzilli", this.enable_fuzzilli);
         opts.addOption(bool, "enable_valgrind", this.enable_valgrind);
         opts.addOption(bool, "use_mimalloc", this.use_mimalloc);
         opts.addOption([]const u8, "reported_nodejs_version", b.fmt("{f}", .{this.reported_nodejs_version}));
@@ -255,6 +257,7 @@ pub fn build(b: *Build) !void {
         .tracy_callstack_depth = b.option(u16, "tracy_callstack_depth", "") orelse 10,
         .enable_logs = b.option(bool, "enable_logs", "Enable logs in release") orelse false,
         .enable_asan = b.option(bool, "enable_asan", "Enable asan") orelse false,
+        .enable_fuzzilli = b.option(bool, "enable_fuzzilli", "Enable fuzzilli instrumentation") orelse false,
         .enable_valgrind = b.option(bool, "enable_valgrind", "Enable valgrind") orelse false,
         .use_mimalloc = b.option(bool, "use_mimalloc", "Use mimalloc as default allocator") orelse false,
         .llvm_codegen_threads = b.option(u32, "llvm_codegen_threads", "Number of threads to use for LLVM codegen") orelse 1,
@@ -490,6 +493,7 @@ fn addMultiCheck(
                 .no_llvm = root_build_options.no_llvm,
                 .enable_asan = root_build_options.enable_asan,
                 .enable_valgrind = root_build_options.enable_valgrind,
+                .enable_fuzzilli = root_build_options.enable_fuzzilli,
                 .use_mimalloc = root_build_options.use_mimalloc,
                 .override_no_export_cpp_apis = root_build_options.override_no_export_cpp_apis,
             };
@@ -605,13 +609,20 @@ fn configureObj(b: *Build, opts: *BunBuildOptions, obj: *Compile) void {
 
     obj.no_link_obj = opts.os != .windows;
 
+
     if (opts.enable_asan and !enableFastBuild(b)) {
         if (@hasField(Build.Module, "sanitize_address")) {
+            if (opts.enable_fuzzilli) {
+                obj.sanitize_coverage_trace_pc_guard = true;
+            }
             obj.root_module.sanitize_address = true;
         } else {
             const fail_step = b.addFail("asan is not supported on this platform");
             obj.step.dependOn(&fail_step.step);
         }
+    } else if (opts.enable_fuzzilli) {
+        const fail_step = b.addFail("fuzzilli requires asan");
+        obj.step.dependOn(&fail_step.step);
     }
     obj.bundle_compiler_rt = false;
     obj.bundle_ubsan_rt = false;

cmake/CompilerFlags.cmake

@@ -51,6 +51,23 @@ if(ENABLE_ASAN)
   )
 endif()
 
+if(ENABLE_FUZZILLI)
+  register_compiler_flags(
+    DESCRIPTION "Enable coverage instrumentation for fuzzing"
+    -fsanitize-coverage=trace-pc-guard
+  )
+
+  register_linker_flags(
+    DESCRIPTION "Link coverage instrumentation"
+    -fsanitize-coverage=trace-pc-guard
+  )
+
+  register_compiler_flags(
+    DESCRIPTION "Enable fuzzilli-specific code"
+    -DFUZZILLI_ENABLED
+  )
+endif()
+
 # --- Optimization level ---
 if(DEBUG)
   register_compiler_flags(

cmake/Options.cmake

@@ -127,6 +127,8 @@ if (NOT ENABLE_ASAN)
   set(ENABLE_ZIG_ASAN OFF)
 endif()
 
+optionx(ENABLE_FUZZILLI BOOL "If fuzzilli support should be enabled" DEFAULT OFF)
+
 if(RELEASE AND LINUX AND CI AND NOT ENABLE_ASSERTIONS AND NOT ENABLE_ASAN)
   set(DEFAULT_LTO ON)
 else()

cmake/analysis/RunClangFormat.cmake

@@ -34,26 +34,6 @@ register_command(
   ALWAYS_RUN
 )
 
-if(GIT_CHANGED_SOURCES)
-  set(CLANG_FORMAT_CHANGED_SOURCES)
-  foreach(source ${CLANG_FORMAT_SOURCES})
-    list(FIND GIT_CHANGED_SOURCES ${source} index)
-    if(NOT ${index} EQUAL -1)
-      list(APPEND CLANG_FORMAT_CHANGED_SOURCES ${source})
-    endif()
-  endforeach()
-endif()
-
-if(CLANG_FORMAT_CHANGED_SOURCES)
-  set(CLANG_FORMAT_DIFF_COMMAND ${CLANG_FORMAT_PROGRAM}
-    -i # edits files in-place
-    --verbose
-    ${CLANG_FORMAT_CHANGED_SOURCES}
-  )
-else()
-  set(CLANG_FORMAT_DIFF_COMMAND ${CMAKE_COMMAND} -E echo "No changed files for clang-format")
-endif()
-
 register_command(
   TARGET
     clang-format-diff

cmake/analysis/RunClangTidy.cmake

@@ -3,7 +3,7 @@
 set(CLANG_TIDY_SOURCES ${BUN_C_SOURCES} ${BUN_CXX_SOURCES})
 
 set(CLANG_TIDY_COMMAND ${CLANG_TIDY_PROGRAM}
-  -p ${BUILD_PATH}  
+  -p ${BUILD_PATH}
   --config-file=${CWD}/.clang-tidy
 )
 
@@ -40,27 +40,6 @@ register_command(
   ALWAYS_RUN
 )
 
-if(GIT_CHANGED_SOURCES)
-  set(CLANG_TIDY_CHANGED_SOURCES)
-  foreach(source ${CLANG_TIDY_SOURCES})
-    list(FIND GIT_CHANGED_SOURCES ${source} index)
-    if(NOT ${index} EQUAL -1)
-      list(APPEND CLANG_TIDY_CHANGED_SOURCES ${source})
-    endif()
-  endforeach()
-endif()
-
-if(CLANG_TIDY_CHANGED_SOURCES)
-  set(CLANG_TIDY_DIFF_COMMAND ${CLANG_TIDY_PROGRAM}
-    ${CLANG_TIDY_CHANGED_SOURCES}
-    --fix
-    --fix-errors
-    --fix-notes
-  )
-else()
-  set(CLANG_TIDY_DIFF_COMMAND ${CMAKE_COMMAND} -E echo "No changed files for clang-tidy")
-endif()
-
 register_command(
   TARGET
     clang-tidy-diff

cmake/analysis/RunPrettier.cmake

@@ -92,26 +92,6 @@ register_command(
   ALWAYS_RUN
 )
 
-if(GIT_CHANGED_SOURCES)
-  set(PRETTIER_CHANGED_SOURCES)
-  foreach(source ${PRETTIER_SOURCES})
-    list(FIND GIT_CHANGED_SOURCES ${source} index)
-    if(NOT ${index} EQUAL -1)
-      list(APPEND PRETTIER_CHANGED_SOURCES ${source})
-    endif()
-  endforeach()
-endif()
-
-if(PRETTIER_CHANGED_SOURCES)
-  set(PRETTIER_DIFF_COMMAND ${PRETTIER_COMMAND}
-    --write
-    --plugin=prettier-plugin-organize-imports
-    ${PRETTIER_CHANGED_SOURCES}
-  )
-else()
-  set(PRETTIER_DIFF_COMMAND ${CMAKE_COMMAND} -E echo "No changed files for prettier")
-endif()
-
 register_command(
   TARGET
     prettier-diff

cmake/analysis/RunZigFormat.cmake

@@ -25,25 +25,6 @@ register_command(
   ALWAYS_RUN
 )
 
-if(GIT_CHANGED_SOURCES)
-  set(ZIG_FORMAT_CHANGED_SOURCES)
-  foreach(source ${ZIG_FORMAT_SOURCES})
-    list(FIND GIT_CHANGED_SOURCES ${source} index)
-    if(NOT ${index} EQUAL -1)
-      list(APPEND ZIG_FORMAT_CHANGED_SOURCES ${source})
-    endif()
-  endforeach()
-endif()
-
-if(ZIG_FORMAT_CHANGED_SOURCES)
-  set(ZIG_FORMAT_DIFF_COMMAND ${ZIG_EXECUTABLE}
-    fmt
-    ${ZIG_FORMAT_CHANGED_SOURCES}
-  )
-else()
-  set(ZIG_FORMAT_DIFF_COMMAND ${CMAKE_COMMAND} -E echo "No changed files for zig-format")
-endif()
-
 register_command(
   TARGET
     zig-format-diff

cmake/targets/BuildBun.cmake

@@ -695,6 +695,7 @@ register_command(
       -Dcpu=${ZIG_CPU}
       -Denable_logs=$<IF:$<BOOL:${ENABLE_LOGS}>,true,false>
       -Denable_asan=$<IF:$<BOOL:${ENABLE_ZIG_ASAN}>,true,false>
+      -Denable_fuzzilli=$<IF:$<BOOL:${ENABLE_FUZZILLI}>,true,false>
       -Denable_valgrind=$<IF:$<BOOL:${ENABLE_VALGRIND}>,true,false>
       -Duse_mimalloc=$<IF:$<BOOL:${USE_MIMALLOC_AS_DEFAULT_ALLOCATOR}>,true,false>
       -Dllvm_codegen_threads=${LLVM_ZIG_CODEGEN_THREADS}

cmake/tools/SetupGit.cmake

@@ -4,41 +4,9 @@ find_command(
   COMMAND
     git
   REQUIRED
-    OFF
+    ${CI}
 )
 
 if(NOT GIT_PROGRAM)
   return()
 endif()
-
-set(GIT_DIFF_COMMAND ${GIT_PROGRAM} diff --no-color --name-only --diff-filter=AMCR origin/main HEAD)
-
-execute_process(
-  COMMAND
-    ${GIT_DIFF_COMMAND}
-  WORKING_DIRECTORY
-    ${CWD}
-  OUTPUT_STRIP_TRAILING_WHITESPACE
-  OUTPUT_VARIABLE
-    GIT_DIFF
-  ERROR_STRIP_TRAILING_WHITESPACE
-  ERROR_VARIABLE
-    GIT_DIFF_ERROR
-  RESULT_VARIABLE
-    GIT_DIFF_RESULT
-)
-
-if(NOT GIT_DIFF_RESULT EQUAL 0)
-  message(WARNING "Command failed: ${GIT_DIFF_COMMAND} ${GIT_DIFF_ERROR}")
-  return()
-endif()
-
-string(REPLACE "\n" ";" GIT_CHANGED_SOURCES "${GIT_DIFF}")
-
-if(CI)
-  set(GIT_CHANGED_SOURCES "${GIT_CHANGED_SOURCES}")
-  message(STATUS "Set GIT_CHANGED_SOURCES: ${GIT_CHANGED_SOURCES}")
-endif()
-
-list(TRANSFORM GIT_CHANGED_SOURCES PREPEND ${CWD}/)
-list(LENGTH GIT_CHANGED_SOURCES GIT_CHANGED_SOURCES_COUNT)

cmake/tools/SetupZig.cmake

@@ -55,13 +55,7 @@ optionx(ZIG_OBJECT_FORMAT "obj|bc" "Output file format for Zig object files" DEF
 optionx(ZIG_LOCAL_CACHE_DIR FILEPATH "The path to local the zig cache directory" DEFAULT ${CACHE_PATH}/zig/local)
 optionx(ZIG_GLOBAL_CACHE_DIR FILEPATH "The path to the global zig cache directory" DEFAULT ${CACHE_PATH}/zig/global)
 
-if(CI)
-  set(ZIG_COMPILER_SAFE_DEFAULT ON)
-else()
-  set(ZIG_COMPILER_SAFE_DEFAULT OFF)
-endif()
-
-optionx(ZIG_COMPILER_SAFE BOOL "Download a ReleaseSafe build of the Zig compiler." DEFAULT ${ZIG_COMPILER_SAFE_DEFAULT})
+optionx(ZIG_COMPILER_SAFE BOOL "Download a ReleaseSafe build of the Zig compiler." DEFAULT ${CI})
 
 setenv(ZIG_LOCAL_CACHE_DIR ${ZIG_LOCAL_CACHE_DIR})
 setenv(ZIG_GLOBAL_CACHE_DIR ${ZIG_GLOBAL_CACHE_DIR})

docs/bundler/css.mdx

@@ -72,7 +72,7 @@ Bun's CSS bundler automatically converts this nested syntax into traditional fla
 
 You can also nest media queries and other at-rules inside selectors, eliminating the need to repeat selector patterns:
 
-```css title="styles.css" icon="file-code"
+```scss title="styles.css" icon="file-code"
 .responsive-element {
   display: block;
 

docs/bundler/executables.mdx

@@ -90,7 +90,7 @@ The order of the `--target` flag does not matter, as long as they're delimited b
 | bun-linux-x64         | Linux            | x64          | ✅     | ✅       | glibc |
 | bun-linux-arm64       | Linux            | arm64        | ✅     | N/A      | glibc |
 | bun-windows-x64       | Windows          | x64          | ✅     | ✅       | -     |
-| ~~bun-windows-arm64~~ | Windows          | arm64        | ❌     | ❌       | -     |
+| ~~bun-windows-arm64~~ | ~~Windows~~      | ~~arm64~~    | ❌     | ❌       | -     |
 | bun-darwin-x64        | macOS            | x64          | ✅     | ✅       | -     |
 | bun-darwin-arm64      | macOS            | arm64        | ✅     | N/A      | -     |
 | bun-linux-x64-musl    | Linux            | x64          | ✅     | ✅       | musl  |
@@ -118,7 +118,7 @@ These constants are embedded directly into your compiled binary at build time, p
 
 <Note>
   For comprehensive examples and advanced patterns, see the [Build-time constants
-  guide](https://bun.com/guides/runtime/build-time-constants).
+  guide](/guides/runtime/build-time-constants).
 </Note>
 
 ---
@@ -183,6 +183,35 @@ console.log(process.execArgv); // ["--smol", "--user-agent=MyBot"]
 
 ---
 
+## Disabling automatic config loading
+
+By default, standalone executables look for `.env` and `bunfig.toml` files in the directory where the executable is run. You can disable this behavior at build time for deterministic execution regardless of the user's working directory.
+
+```bash icon="terminal" terminal
+# Disable .env loading
+bun build --compile --no-compile-autoload-dotenv ./app.ts --outfile myapp
+
+# Disable bunfig.toml loading
+bun build --compile --no-compile-autoload-bunfig ./app.ts --outfile myapp
+
+# Disable both
+bun build --compile --no-compile-autoload-dotenv --no-compile-autoload-bunfig ./app.ts --outfile myapp
+```
+
+You can also configure this via the JavaScript API:
+
+```ts
+await Bun.build({
+  entrypoints: ["./app.ts"],
+  compile: {
+    autoloadDotenv: false, // Disable .env loading
+    autoloadBunfig: false, // Disable bunfig.toml loading
+  },
+});
+```
+
+---
+
 ## Act as the Bun CLI
 
 <Note>New in Bun v1.2.16</Note>
@@ -259,12 +288,12 @@ console.log(`Server running at http://localhost:${server.port}`);
   </head>
   <body>
     <h1>Hello World</h1>
-    <script src="./app.js"></script>
+    <script src="./app.ts"></script>
   </body>
 </html>
 ```
 
-```ts app.js icon="file-code"
+```ts app.ts icon="file-code"
 console.log("Hello from the client!");
 ```
 
@@ -524,12 +553,46 @@ codesign -vvv --verify ./myapp
 
 ---
 
+## Code splitting
+
+Standalone executables support code splitting. Use `--compile` with `--splitting` to create an executable that loads code-split chunks at runtime.
+
+```bash
+bun build --compile --splitting ./src/entry.ts --outdir ./build
+```
+
+<CodeGroup>
+
+```ts src/entry.ts icon="/icons/typescript.svg"
+console.log("Entrypoint loaded");
+const lazy = await import("./lazy.ts");
+lazy.hello();
+```
+
+```ts src/lazy.ts icon="/icons/typescript.svg"
+export function hello() {
+  console.log("Lazy module loaded");
+}
+```
+
+</CodeGroup>
+
+```bash terminal icon="terminal"
+./build/entry
+```
+
+```txt
+Entrypoint loaded
+Lazy module loaded
+```
+
+---
+
 ## Unsupported CLI arguments
 
 Currently, the `--compile` flag can only accept a single entrypoint at a time and does not support the following flags:
 
-- `--outdir` — use `outfile` instead.
-- `--splitting`
+- `--outdir` — use `outfile` instead (except when using with `--splitting`).
 - `--public-path`
 - `--target=node` or `--target=browser`
 - `--no-bundle` - we always bundle everything into the executable.

docs/bundler/fullstack.mdx

@@ -632,7 +632,7 @@ const server = serve({
 console.log(`🚀 Server running on ${server.url}`);
 ```
 
-```html title="public/index.html"
+```html title="public/index.html" icon="file-code"
 <!DOCTYPE html>
 <html>
   <head>
@@ -757,7 +757,7 @@ export function App() {
 }
 ```
 
-```css title="src/styles.css"
+```css title="src/styles.css" icon="file-code"
 * {
   margin: 0;
   padding: 0;
@@ -999,7 +999,7 @@ CMD ["bun", "index.js"]
 
 ### Environment Variables
 
-```bash title=".env.production" icon="file-code"
+```ini title=".env.production" icon="file-code"
 NODE_ENV=production
 PORT=3000
 DATABASE_URL=postgresql://user:pass@localhost:5432/myapp

docs/bundler/hot-reloading.mdx

@@ -9,7 +9,7 @@ Hot Module Replacement (HMR) allows you to update modules in a running applicati
 
 ## `import.meta.hot` API Reference
 
-Bun implements a client-side HMR API modeled after [Vite's `import.meta.hot` API](https://vitejs.dev/guide/api-hmr.html). It can be checked for with `if (import.meta.hot)`, tree-shaking it in production.
+Bun implements a client-side HMR API modeled after [Vite's `import.meta.hot` API](https://vite.dev/guide/api-hmr). It can be checked for with `if (import.meta.hot)`, tree-shaking it in production.
 
 ```ts title="index.ts" icon="/icons/typescript.svg"
 if (import.meta.hot) {
@@ -144,7 +144,7 @@ Indicates that multiple dependencies' modules can be accepted. This variant acce
 
 `import.meta.hot.data` maintains state between module instances during hot replacement, enabling data transfer from previous to new versions. When `import.meta.hot.data` is written into, Bun will also mark this module as capable of self-accepting (equivalent of calling `import.meta.hot.accept()`).
 
-```jsx title="index.ts" icon="/icons/typescript.svg"
+```tsx title="index.tsx" icon="/icons/typescript.svg"
 import { createRoot } from "react-dom/client";
 import { App } from "./app";
 

docs/bundler/html-static.mdx

@@ -25,7 +25,7 @@ bun ./index.html
 ```
 
 ```
-Bun v1.3.2
+Bun v1.3.3
 ready in 6.62ms
 → http://localhost:3000/
 Press h + Enter to show shortcuts
@@ -51,7 +51,7 @@ bun index.html
 ```
 
 ```
-Bun v1.3.2
+Bun v1.3.3
 ready in 6.62ms
 → http://localhost:3000/
 Press h + Enter to show shortcuts
@@ -81,7 +81,7 @@ bun ./index.html ./about.html
 ```
 
 ```txt
-Bun v1.3.2
+Bun v1.3.3
 ready in 6.62ms
 → http://localhost:3000/
 Routes:
@@ -104,7 +104,7 @@ bun ./**/*.html
 ```
 
 ```
-Bun v1.3.2
+Bun v1.3.3
 ready in 6.62ms
 → http://localhost:3000/
 Routes:
@@ -122,7 +122,7 @@ bun ./index.html ./about/index.html ./about/foo/index.html
 ```
 
 ```
-Bun v1.3.2
+Bun v1.3.3
 ready in 6.62ms
 → http://localhost:3000/
 Routes:
@@ -164,7 +164,7 @@ For example:
 }
 ```
 
-```css abc.css
+```css abc.css icon="file-code"
 body {
   background-color: red;
 }
@@ -174,7 +174,7 @@ body {
 
 This outputs:
 
-```css
+```css styles.css icon="file-code"
 body {
   background-color: red;
 }
@@ -273,7 +273,7 @@ bun ./index.html --console
 ```
 
 ```
-Bun v1.3.2
+Bun v1.3.3
 ready in 6.62ms
 → http://localhost:3000/
 Press h + Enter to show shortcuts
@@ -385,7 +385,8 @@ All paths are resolved relative to your HTML file, making it easy to organize yo
 - Need more configuration options for things like asset handling
 - Need a way to configure CORS, headers, etc.
 
-If you want to submit a PR, most of the code is [here](https://github.com/oven-sh/bun/blob/main/src/bun.js/api/bun/html-rewriter.ts). You could even copy paste that file into your project and use it as a starting point.
+{/* todo: find the correct link to link to as this 404's and there isn't any similar files */}
+{/* If you want to submit a PR, most of the code is [here](https://github.com/oven-sh/bun/blob/main/src/bun.js/api/bun/html-rewriter.ts). You could even copy paste that file into your project and use it as a starting point. */}
 
 </Warning>
 

docs/bundler/index.mdx

@@ -106,7 +106,7 @@ For each file specified in `entrypoints`, Bun will generate a new bundle. This b
 
 The contents of `out/index.js` will look something like this:
 
-```ts title="out/index.js" icon="/icons/javascript.svg"
+```js title="out/index.js" icon="/icons/javascript.svg"
 // out/index.js
 // ...
 // ~20k lines of code
@@ -527,7 +527,7 @@ Injects environment variables into the bundled output by converting `process.env
 
 For the input below:
 
-```ts title="input.js" icon="/icons/javascript.svg"
+```js title="input.js" icon="/icons/javascript.svg"
 // input.js
 console.log(process.env.FOO);
 console.log(process.env.BAZ);
@@ -535,7 +535,7 @@ console.log(process.env.BAZ);
 
 The generated bundle will contain the following code:
 
-```ts title="output.js" icon="/icons/javascript.svg"
+```js title="output.js" icon="/icons/javascript.svg"
 // output.js
 console.log("bar");
 console.log("123");
@@ -580,7 +580,7 @@ console.log(process.env.BAZ);
 
 The generated bundle will contain the following code:
 
-```ts title="output.js" icon="/icons/javascript.svg"
+```js title="output.js" icon="/icons/javascript.svg"
 console.log(process.env.FOO);
 console.log("https://acme.com");
 console.log(process.env.BAZ);
@@ -722,7 +722,7 @@ Normally, bundling `index.tsx` would generate a bundle containing the entire sou
 
 The generated bundle will look something like this:
 
-```ts title="out/index.js" icon="/icons/javascript.svg"
+```js title="out/index.js" icon="/icons/javascript.svg"
 import { z } from "zod";
 
 // ...
@@ -1026,7 +1026,7 @@ Setting `publicPath` will prefix all file paths with the specified value.
 
 The output file would now look something like this.
 
-```ts title="out/index.js" icon="/icons/javascript.svg"
+```js title="out/index.js" icon="/icons/javascript.svg"
 var logo = "https://cdn.example.com/logo-a7305bdef.svg";
 ```
 
@@ -1356,10 +1356,12 @@ interface BuildConfig {
    * JSX configuration object for controlling JSX transform behavior
    */
   jsx?: {
+    runtime?: "automatic" | "classic";
+    importSource?: string;
     factory?: string;
     fragment?: string;
-    importSource?: string;
-    runtime?: "automatic" | "classic";
+    sideEffects?: boolean;
+    development?: boolean;
   };
   naming?:
     | string
@@ -1376,7 +1378,7 @@ interface BuildConfig {
   publicPath?: string;
   define?: Record<string, string>;
   loader?: { [k in string]: Loader };
-  sourcemap?: "none" | "linked" | "inline" | "external" | "linked" | boolean; // default: "none", true -> "inline"
+  sourcemap?: "none" | "linked" | "inline" | "external" | boolean; // default: "none", true -> "inline"
   /**
    * package.json `exports` conditions used when resolving imports
    *
@@ -1443,13 +1445,20 @@ interface BuildConfig {
   drop?: string[];
 
   /**
-   * When set to `true`, the returned promise rejects with an AggregateError when a build failure happens.
-   * When set to `false`, the `success` property of the returned object will be `false` when a build failure happens.
+   * - When set to `true`, the returned promise rejects with an AggregateError when a build failure happens.
+   * - When set to `false`, returns a {@link BuildOutput} with `{success: false}`
    *
-   * This defaults to `false` in Bun 1.1 and will change to `true` in Bun 1.2
-   * as most usage of `Bun.build` forgets to check for errors.
+   * @default true
    */
   throw?: boolean;
+
+  /**
+   * Custom tsconfig.json file path to use for path resolution.
+   * Equivalent to `--tsconfig-override` in the CLI.
+   */
+  tsconfig?: string;
+
+  outdir?: string;
 }
 
 interface BuildOutput {

docs/bundler/loaders.mdx

@@ -312,7 +312,7 @@ The `html` loader processes HTML files and bundles any referenced assets. It wil
 
 For example, given this HTML file:
 
-```html title="src/index.html"
+```html title="src/index.html" icon="file-code"
 <!DOCTYPE html>
 <html>
   <body>
@@ -325,7 +325,7 @@ For example, given this HTML file:
 
 It will output a new HTML file with the bundled assets:
 
-```html title="dist/index.html"
+```html title="dist/index.html" icon="file-code"
 <!DOCTYPE html>
 <html>
   <body>

docs/bundler/macros.mdx

@@ -87,7 +87,7 @@ macro();
 
 When shipping a library containing a macro to npm or another package registry, use the `"macro"` export condition to provide a special version of your package exclusively for the macro environment.
 
-```json title="package.json" icon="file-code"
+```json title="package.json" icon="file-json"
 {
   "name": "my-package",
   "exports": {

docs/docs.json

@@ -188,7 +188,7 @@
           {
             "group": "Publishing & Analysis",
             "icon": "upload",
-            "pages": ["/pm/cli/publish", "/pm/cli/outdated", "/pm/cli/why", "/pm/cli/audit"]
+            "pages": ["/pm/cli/publish", "/pm/cli/outdated", "/pm/cli/why", "/pm/cli/audit", "/pm/cli/info"]
           },
           {
             "group": "Workspace Management",
@@ -464,6 +464,7 @@
               "/guides/test/update-snapshots",
               "/guides/test/coverage",
               "/guides/test/coverage-threshold",
+              "/guides/test/concurrent-test-glob",
               "/guides/test/skip-tests",
               "/guides/test/todo-tests",
               "/guides/test/timeout",

docs/feedback.mdx

@@ -4,13 +4,9 @@ description: Share feedback, bug reports, and feature requests
 mode: center
 ---
 
-import Feedback from "/snippets/cli/feedback.mdx";
-
 Whether you've found a bug, have a performance issue, or just want to suggest an improvement, here's how you can open a helpful issue:
 
-<Callout icon="discord">
-  For general questions, please join our [Discord](https://discord.com/invite/CXdq2DP29u).
-</Callout>
+<Callout icon="discord">For general questions, please join our [Discord](https://bun.com/discord).</Callout>
 
 ## Reporting Issues
 
@@ -56,9 +52,7 @@ Whether you've found a bug, have a performance issue, or just want to suggest an
     		<Note>
     			- For MacOS and Linux: copy the output of `uname -mprs`
     		  - For Windows: copy the output of this command in the powershell console:
-    				```powershell
-    					"$([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" })"
-    				```
+    				`"$([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" })"`
     		</Note>
     </Step>
 
@@ -79,7 +73,3 @@ echo "please document X" | bun feedback --email you@example.com
 ```
 
 You can provide feedback as text arguments, file paths, or piped input.
-
----
-
-<Feedback />

docs/guides/binary/arraybuffer-to-array.mdx

@@ -26,4 +26,4 @@ const regularArr = Array.from(uintArr);
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/arraybuffer-to-blob.mdx

@@ -23,4 +23,4 @@ blob.type; // => "application/octet-stream"
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/arraybuffer-to-buffer.mdx

@@ -24,4 +24,4 @@ const nodeBuffer = Buffer.from(arrBuffer, 0, 16); // view first 16 bytes
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/arraybuffer-to-string.mdx

@@ -14,4 +14,4 @@ const str = decoder.decode(buf);
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/arraybuffer-to-typedarray.mdx

@@ -38,4 +38,4 @@ const arr = new Uint8Array(buffer, 0, 16); // view first 16 bytes
 
 ---
 
-See [Docs > API > Utils](https://bun.com/docs/api/utils) for more useful utilities.
+See [Docs > API > Utils](/runtime/utils) for more useful utilities.

docs/guides/binary/blob-to-arraybuffer.mdx

@@ -13,4 +13,4 @@ const buf = await blob.arrayBuffer();
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/blob-to-dataview.mdx

@@ -13,4 +13,4 @@ const arr = new DataView(await blob.arrayBuffer());
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/blob-to-stream.mdx

@@ -13,4 +13,4 @@ const stream = await blob.stream();
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/blob-to-string.mdx

@@ -14,4 +14,4 @@ const str = await blob.text();
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/blob-to-typedarray.mdx

@@ -13,4 +13,4 @@ const arr = new Uint8Array(await blob.arrayBuffer());
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/buffer-to-arraybuffer.mdx

@@ -13,4 +13,4 @@ const arrBuf = nodeBuf.buffer;
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/buffer-to-blob.mdx

@@ -13,4 +13,4 @@ const blob = new Blob([buf]);
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/buffer-to-readablestream.mdx

@@ -40,4 +40,4 @@ const stream = blob.stream(1024);
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/buffer-to-string.mdx

@@ -24,4 +24,4 @@ const str = buf.toString("utf8", 0, 5);
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/buffer-to-typedarray.mdx

@@ -13,4 +13,4 @@ buf instanceof Uint8Array; // => true
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/dataview-to-string.mdx

@@ -14,4 +14,4 @@ const str = decoder.decode(dv);
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/typedarray-to-arraybuffer.mdx

@@ -24,4 +24,4 @@ arr.byteLength; // => 32
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/typedarray-to-blob.mdx

@@ -15,4 +15,4 @@ console.log(await blob.text());
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/typedarray-to-buffer.mdx

@@ -13,4 +13,4 @@ const buf = Buffer.from(arr);
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/typedarray-to-dataview.mdx

@@ -13,4 +13,4 @@ const dv = new DataView(arr.buffer, arr.byteOffset, arr.byteLength);
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/typedarray-to-readablestream.mdx

@@ -40,4 +40,4 @@ const stream = blob.stream(1024);
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/binary/typedarray-to-string.mdx

@@ -15,4 +15,4 @@ const str = decoder.decode(arr);
 
 ---
 
-See [Docs > API > Binary Data](https://bun.com/docs/api/binary-data#conversion) for complete documentation on manipulating binary data with Bun.
+See [Docs > API > Binary Data](/runtime/binary-data#conversion) for complete documentation on manipulating binary data with Bun.

docs/guides/deployment/vercel.mdx

@@ -4,8 +4,6 @@ sidebarTitle: Deploy on Vercel
 mode: center
 ---
 
-import { ProductCard } from "/snippets/product-card.mdx";
-
 [Vercel](https://vercel.com/) is a cloud platform that lets you build, deploy, and scale your apps.
 
 <Warning>
@@ -81,7 +79,7 @@ import { ProductCard } from "/snippets/product-card.mdx";
     	console.log("runtime", process.versions.bun);
     	```
     	```txt
-    	runtime 1.3.2
+    	runtime 1.3.3
     	```
 
     	[See the Vercel Bun Runtime documentation for feature support →](https://vercel.com/docs/functions/runtimes/bun#feature-support)

docs/guides/ecosystem/discordjs.mdx

@@ -22,7 +22,7 @@ bun add discord.js
 
 ---
 
-Before we go further, we need to go to the [Discord developer portal](https://discord.com/developers/applications), login/signup, create a new _Application_, then create a new _Bot_ within that application. Follow the [official guide](https://discordjs.guide/preparations/setting-up-a-bot-application.html#creating-your-bot) for step-by-step instructions.
+Before we go further, we need to go to the [Discord developer portal](https://discord.com/developers/applications), login/signup, create a new _Application_, then create a new _Bot_ within that application. Follow the [official guide](https://discordjs.guide/legacy/preparations/app-setup#creating-your-bot) for step-by-step instructions.
 
 ---
 
@@ -30,7 +30,7 @@ Once complete, you'll be presented with your bot's _private key_. Let's add this
 
 <Note>This is an example token that has already been invalidated.</Note>
 
-```txt .env.local icon="settings"
+```ini .env.local icon="settings"
 DISCORD_TOKEN=NzkyNzE1NDU0MTk2MDg4ODQy.X-hvzA.Ovy4MCQywSkoMRRclStW4xAYK7I
 ```
 

docs/guides/ecosystem/express.mdx

@@ -7,8 +7,8 @@ mode: center
 Express and other major Node.js HTTP libraries should work out of the box. Bun implements the [`node:http`](https://nodejs.org/api/http.html) and [`node:https`](https://nodejs.org/api/https.html) modules that these libraries rely on.
 
 <Note>
-  Refer to the [Runtime > Node.js APIs](https://bun.com/docs/runtime/nodejs-apis#node-http) page for more detailed
-  compatibility information.
+  Refer to the [Runtime > Node.js APIs](/runtime/nodejs-compat#node-http) page for more detailed compatibility
+  information.
 </Note>
 
 ```sh terminal icon="terminal"

docs/guides/ecosystem/mongoose.mdx

@@ -89,4 +89,4 @@ Moo!
 
 ---
 
-This is a simple introduction to using Mongoose with TypeScript and Bun. As you build your application, refer to the official [MongoDB](https://docs.mongodb.com/) and [Mongoose](https://mongoosejs.com/docs/) sites for complete documentation.
+This is a simple introduction to using Mongoose with TypeScript and Bun. As you build your application, refer to the official [MongoDB](https://www.mongodb.com/docs) and [Mongoose](https://mongoosejs.com/docs/) sites for complete documentation.

docs/guides/ecosystem/neon-drizzle.mdx

@@ -20,7 +20,7 @@ bun add -D drizzle-kit
 
 Create a `.env.local` file and add your [Neon Postgres connection string](https://neon.tech/docs/connect/connect-from-any-app) to it.
 
-```txt .env.local icon="settings"
+```ini .env.local icon="settings"
 DATABASE_URL=postgresql://usertitle:password@ep-adj-noun-guid.us-east-1.aws.neon.tech/neondb?sslmode=require
 ```
 
@@ -33,7 +33,7 @@ import { neon } from "@neondatabase/serverless";
 import { drizzle } from "drizzle-orm/neon-http";
 
 // Bun automatically loads the DATABASE_URL from .env.local
-// Refer to: https://bun.com/docs/runtime/env for more information
+// Refer to: https://bun.com/docs/runtime/environment-variables for more information
 const sql = neon(process.env.DATABASE_URL!);
 
 export const db = drizzle(sql);

docs/guides/ecosystem/neon-serverless-postgres.mdx

@@ -21,7 +21,7 @@ bun add @neondatabase/serverless
 
 Create a `.env.local` file and add your [Neon Postgres connection string](https://neon.tech/docs/connect/connect-from-any-app) to it.
 
-```sh .env.local icon="settings"
+```ini .env.local icon="settings"
 DATABASE_URL=postgresql://usertitle:password@ep-adj-noun-guid.us-east-1.aws.neon.tech/neondb?sslmode=require
 ```
 
@@ -33,7 +33,7 @@ Paste the following code into your project's `index.ts` file.
 import { neon } from "@neondatabase/serverless";
 
 // Bun automatically loads the DATABASE_URL from .env.local
-// Refer to: https://bun.com/docs/runtime/env for more information
+// Refer to: https://bun.com/docs/runtime/environment-variables for more information
 const sql = neon(process.env.DATABASE_URL);
 
 const rows = await sql`SELECT version()`;

docs/guides/ecosystem/nextjs.mdx

@@ -4,54 +4,100 @@ sidebarTitle: Next.js with Bun
 mode: center
 ---
 
-Initialize a Next.js app with `create-next-app`. This will scaffold a new Next.js project and automatically install dependencies.
-
-```sh terminal icon="terminal"
-bun create next-app
-```
-
-```txt
-✔ What is your project named? … my-app
-✔ Would you like to use TypeScript with this project? … No / Yes
-✔ Would you like to use ESLint with this project? … No / Yes
-✔ Would you like to use Tailwind CSS? ... No / Yes
-✔ Would you like to use `src/` directory with this project? … No / Yes
-✔ Would you like to use App Router? (recommended) ... No / Yes
-✔ What import alias would you like configured? … @/*
-Creating a new Next.js app in /path/to/my-app.
-```
+[Next.js](https://nextjs.org/) is a React framework for building full-stack web applications. It supports server-side rendering, static site generation, API routes, and more. Bun provides fast package installation and can run Next.js development and production servers.
 
 ---
 
-You can specify a starter template using the `--example` flag.
+<Steps>
+  <Step title="Create a new Next.js app">
+    Use the interactive CLI to create a new Next.js app. This will scaffold a new Next.js project and automatically install dependencies.
 
-```sh
-bun create next-app --example with-supabase
-```
+    ```sh terminal icon="terminal"
+    bun create next-app@latest my-bun-app
+    ```
 
-```txt
-✔ What is your project named? … my-app
-...
-```
+  </Step>
+  <Step title="Start the dev server">
+    Change to the project directory and run the dev server with Bun.
+
+    ```sh terminal icon="terminal"
+    cd my-bun-app
+    bun --bun run dev
+    ```
+
+    This starts the Next.js dev server with Bun's runtime.
+
+    Open [`http://localhost:3000`](http://localhost:3000) with your browser to see the result. Any changes you make to `app/page.tsx` will be hot-reloaded in the browser.
+
+  </Step>
+  <Step title="Update scripts in package.json">
+    Modify the scripts field in your `package.json` by prefixing the Next.js CLI commands with `bun --bun`. This ensures that Bun executes the Next.js CLI for common tasks like `dev`, `build`, and `start`.
+
+    ```json package.json icon="file-json"
+    {
+      "scripts": {
+        "dev": "bun --bun next dev", // [!code ++]
+        "build": "bun --bun next build", // [!code ++]
+        "start": "bun --bun next start", // [!code ++]
+      }
+    }
+    ```
+
+  </Step>
+</Steps>
 
 ---
 
-To start the dev server with Bun, run `bun --bun run dev` from the project root.
+## Hosting
 
-```sh terminal icon="terminal"
-cd my-app
-bun --bun run dev
-```
+Next.js applications on Bun can be deployed to various platforms.
+
+<Columns cols={3}>
+  <Card title="Vercel" href="/guides/deployment/vercel" icon="/icons/ecosystem/vercel.svg">
+    Deploy on Vercel
+  </Card>
+  <Card title="Railway" href="/guides/deployment/railway" icon="/icons/ecosystem/railway.svg">
+    Deploy on Railway
+  </Card>
+  <Card title="DigitalOcean" href="/guides/deployment/digital-ocean" icon="/icons/ecosystem/digitalocean.svg">
+    Deploy on DigitalOcean
+  </Card>
+  <Card title="AWS Lambda" href="/guides/deployment/aws-lambda" icon="/icons/ecosystem/aws.svg">
+    Deploy on AWS Lambda
+  </Card>
+  <Card title="Google Cloud Run" href="/guides/deployment/google-cloud-run" icon="/icons/ecosystem/gcp.svg">
+    Deploy on Google Cloud Run
+  </Card>
+  <Card title="Render" href="/guides/deployment/render" icon="/icons/ecosystem/render.svg">
+    Deploy on Render
+  </Card>
+</Columns>
 
 ---
 
-To run the dev server with Node.js instead, omit `--bun`.
+## Templates
 
-```sh terminal icon="terminal"
-cd my-app
-bun run dev
-```
+<Columns cols={2}>
+  <Card
+    title="Bun + Next.js Basic Starter"
+    img="/images/templates/bun-nextjs-basic.png"
+    href="https://github.com/bun-templates/bun-nextjs-basic"
+    arrow="true"
+    cta="Go to template"
+  >
+    A simple App Router starter with Bun, Next.js, and Tailwind CSS.
+  </Card>
+  <Card
+    title="Todo App with Next.js + Bun"
+    img="/images/templates/bun-nextjs-todo.png"
+    href="https://github.com/bun-templates/bun-nextjs-todo"
+    arrow="true"
+    cta="Go to template"
+  >
+    A full-stack todo application built with Bun, Next.js, and PostgreSQL.
+  </Card>
+</Columns>
 
 ---
 
-Open [http://localhost:3000](http://localhost:3000) with your browser to see the result. Any changes you make to `(pages/app)/index.tsx` will be hot-reloaded in the browser.
+[→ See Next.js's official documentation](https://nextjs.org/docs) for more information on building and deploying Next.js applications.

docs/guides/ecosystem/nuxt.mdx

@@ -14,7 +14,7 @@ bunx nuxi init my-nuxt-app
 ✔ Which package manager would you like to use?
 bun
 ◐ Installing dependencies...
-bun install v1.3.2 (16b4bf34)
+bun install v1.3.3 (16b4bf34)
  + @nuxt/devtools@0.8.2
  + nuxt@3.7.0
  785 packages installed [2.67s]

docs/guides/ecosystem/prisma-postgres.mdx

@@ -62,7 +62,7 @@ mode: center
     <Step title="Configure database connection">
     	Set up your Postgres database URL in the `.env` file.
 
-    	```env .env icon="settings"
+    	```ini .env icon="settings"
     	DATABASE_URL="postgresql://username:password@localhost:5432/mydb?schema=public"
     	```
     </Step>

docs/guides/ecosystem/prisma.mdx

@@ -161,4 +161,4 @@ mode: center
 
 ---
 
-That's it! Now that you've set up Prisma using Bun, we recommend referring to the [official Prisma docs](https://www.prisma.io/docs/concepts/components/prisma-client) as you continue to develop your application.
+That's it! Now that you've set up Prisma using Bun, we recommend referring to the [official Prisma docs](https://www.prisma.io/docs/orm/prisma-client) as you continue to develop your application.

docs/guides/ecosystem/qwik.mdx

@@ -65,14 +65,14 @@ bun create qwik
 │  bun qwik add                                        │
 │                                                      │
 │  Relevant docs:                                      │
-│  https://qwik.builder.io/docs/getting-started/       │
+│  https://qwik.dev/docs/getting-started/              │
 │                                                      │
 │  Questions? Start the conversation at:               │
-│  https://qwik.builder.io/chat                        │
+│  https://qwik.dev/chat                               │
 │  https://twitter.com/QwikDev                         │
 │                                                      │
 │  Presentations, Podcasts and Videos:                 │
-│  https://qwik.builder.io/media/                      │
+│  https://qwik.dev/media/                             │
 │                                                      │
 │  Next steps:                                         │
 │  cd my-app                                           │
@@ -111,4 +111,4 @@ Open [http://localhost:5173](http://localhost:5173) with your browser to see the
 
 ---
 
-Refer to the [Qwik docs](https://qwik.builder.io/docs/getting-started/) for complete documentation.
+Refer to the [Qwik docs](https://qwik.dev/docs/getting-started/) for complete documentation.

docs/guides/ecosystem/sentry.mdx

@@ -20,7 +20,7 @@ bun add @sentry/bun
 
 Then, initialize the Sentry SDK with your Sentry DSN in your app's entry file. You can find your DSN in your Sentry project settings.
 
-```js sentry.ts icon="/icons/typescript.svg"
+```ts sentry.ts icon="/icons/typescript.svg"
 import * as Sentry from "@sentry/bun";
 
 // Ensure to call this before importing any other modules!
@@ -37,7 +37,7 @@ Sentry.init({
 
 You can verify that Sentry is working by capturing a test error:
 
-```js sentry.ts icon="/icons/typescript.svg"
+```ts sentry.ts icon="/icons/typescript.svg"
 setTimeout(() => {
   try {
     foo();

docs/guides/ecosystem/sveltekit.mdx

@@ -88,7 +88,7 @@ To build for production, you'll need to add the right SvelteKit adapter. Current
 
 Now, make the following changes to your `svelte.config.js`.
 
-```ts svelte.config.js icon="file-code"
+```js svelte.config.js icon="file-code"
 import adapter from "@sveltejs/adapter-auto"; // [!code --]
 import adapter from "svelte-adapter-bun"; // [!code ++]
 import { vitePreprocess } from "@sveltejs/vite-plugin-svelte";

docs/guides/ecosystem/tanstack-start.mdx

@@ -98,7 +98,6 @@ To host your TanStack Start app, you can use [Nitro](https://nitro.build/) or a
           }
         ```
 
-
         <Note>
           You do **not** need the custom `start` script when deploying to Vercel.
         </Note>
@@ -755,4 +754,38 @@ To host your TanStack Start app, you can use [Nitro](https://nitro.build/) or a
 
 ---
 
+## Templates
+
+<Columns cols={2}>
+  <Card
+    title="Todo App with Tanstack + Bun"
+    img="/images/templates/bun-tanstack-todo.png"
+    href="https://github.com/bun-templates/bun-tanstack-todo"
+    arrow="true"
+    cta="Go to template"
+  >
+    A Todo application built with Bun, TanStack Start, and PostgreSQL.
+  </Card>
+  <Card
+    title="Bun + TanStack Start Application"
+    img="/images/templates/bun-tanstack-basic.png"
+    href="https://github.com/bun-templates/bun-tanstack-basic"
+    arrow="true"
+    cta="Go to template"
+  >
+    A TanStack Start template using Bun with SSR and file-based routing.
+  </Card>
+  <Card
+    title="Basic Bun + Tanstack Starter"
+    img="/images/templates/bun-tanstack-start.png"
+    href="https://github.com/bun-templates/bun-tanstack-start"
+    arrow="true"
+    cta="Go to template"
+  >
+    The basic TanStack starter using the Bun runtime and Bun's file APIs.
+  </Card>
+</Columns>
+
+---
+
 [→ See TanStack Start's official documentation](https://tanstack.com/start/latest/docs/framework/react/guide/hosting) for more information on hosting.

docs/guides/ecosystem/upstash.mdx

@@ -34,7 +34,7 @@ mode: center
 
     Set the `REDIS_URL` environment variable in your `.env` file using the Redis endpoint (not the REST URL):
 
-    ```env .env icon="settings"
+    ```ini .env icon="settings"
     REDIS_URL=rediss://********@********.upstash.io:6379
     ```
 

docs/guides/ecosystem/vite.mdx

@@ -74,4 +74,4 @@ bunx --bun vite build
 
 ---
 
-This is a stripped down guide to get you started with Vite + Bun. For more information, see the [Vite documentation](https://vitejs.dev/guide/).
+This is a stripped down guide to get you started with Vite + Bun. For more information, see the [Vite documentation](https://vite.dev/guide/).

docs/guides/html-rewriter/extract-links.mdx

@@ -6,7 +6,7 @@ mode: center
 
 ## Extract links from a webpage
 
-Bun's [HTMLRewriter](https://bun.com/docs/api/html-rewriter) API can be used to efficiently extract links from HTML content. It works by chaining together CSS selectors to match the elements, text, and attributes you want to process. This is a simple example of how to extract links from a webpage. You can pass `.transform` a `Response`, `Blob`, or `string`.
+Bun's [HTMLRewriter](/runtime/html-rewriter) API can be used to efficiently extract links from HTML content. It works by chaining together CSS selectors to match the elements, text, and attributes you want to process. This is a simple example of how to extract links from a webpage. You can pass `.transform` a `Response`, `Blob`, or `string`.
 
 ```ts extract-links.ts icon="/icons/typescript.svg"
 async function extractLinks(url: string) {
@@ -37,6 +37,7 @@ await extractLinks("https://bun.com");
 
 When scraping websites, you often want to convert relative URLs (like `/docs`) to absolute URLs. Here's how to handle URL resolution:
 
+{/* prettier-ignore */}
 ```ts extract-links.ts icon="/icons/typescript.svg"
 async function extractLinksFromURL(url: string) {
   const response = await fetch(url);
@@ -47,13 +48,11 @@ async function extractLinksFromURL(url: string) {
       const href = el.getAttribute("href");
       if (href) {
         // Convert relative URLs to absolute // [!code ++]
-        try {
-          // [!code ++]
+        try { // [!code ++]
           const absoluteURL = new URL(href, url).href; // [!code ++]
-          links.add(absoluteURL); // [!code ++]
-        } catch {
-          // [!code ++]
-          links.add(href);
+          links.add(absoluteURL);
+        } catch { // [!code ++]
+          links.add(href); // [!code ++]
         } // [!code ++]
       }
     },
@@ -69,4 +68,4 @@ const websiteLinks = await extractLinksFromURL("https://example.com");
 
 ---
 
-See [Docs > API > HTMLRewriter](https://bun.com/docs/api/html-rewriter) for complete documentation on HTML transformation with Bun.
+See [Docs > API > HTMLRewriter](/runtime/html-rewriter) for complete documentation on HTML transformation with Bun.

docs/guides/html-rewriter/extract-social-meta.mdx

@@ -6,7 +6,7 @@ mode: center
 
 ## Extract social share images and Open Graph tags
 
-Bun's [HTMLRewriter](https://bun.com/docs/api/html-rewriter) API can be used to efficiently extract social share images and Open Graph metadata from HTML content. This is particularly useful for building link preview features, social media cards, or web scrapers. We can use HTMLRewriter to match CSS selectors to HTML elements, text, and attributes we want to process.
+Bun's [HTMLRewriter](/runtime/html-rewriter) API can be used to efficiently extract social share images and Open Graph metadata from HTML content. This is particularly useful for building link preview features, social media cards, or web scrapers. We can use HTMLRewriter to match CSS selectors to HTML elements, text, and attributes we want to process.
 
 ```ts extract-social-meta.ts icon="/icons/typescript.svg"
 interface SocialMetadata {

docs/guides/http/file-uploads.mdx

@@ -63,8 +63,9 @@ Our form will send a `POST` request to the `/action` endpoint with the form data
 
 First we use the [`.formData()`](https://developer.mozilla.org/en-US/docs/Web/API/Request/formData) method on the incoming `Request` to asynchronously parse its contents to a `FormData` instance. Then we can use the [`.get()`](https://developer.mozilla.org/en-US/docs/Web/API/FormData/get) method to extract the value of the `name` and `profilePicture` fields. Here `name` corresponds to a `string` and `profilePicture` is a `Blob`.
 
-Finally, we write the `Blob` to disk using [`Bun.write()`](https://bun.com/docs/api/file-io#writing-files-bun-write).
+Finally, we write the `Blob` to disk using [`Bun.write()`](/runtime/file-io#writing-files-bun-write).
 
+{/* prettier-ignore */}
 ```ts index.ts icon="/icons/typescript.svg"
 const server = Bun.serve({
   port: 4000,
@@ -80,8 +81,7 @@ const server = Bun.serve({
       });
 
     // parse formdata at /action // [!code ++]
-    if (url.pathname === "/action") {
-      // [!code ++]
+    if (url.pathname === "/action") { // [!code ++]
       const formdata = await req.formData(); // [!code ++]
       const name = formdata.get("name"); // [!code ++]
       const profilePicture = formdata.get("profilePicture"); // [!code ++]

docs/guides/http/hot.mdx

@@ -4,7 +4,7 @@ sidebarTitle: Hot reload an HTTP server
 mode: center
 ---
 
-Bun supports the [`--hot`](https://bun.com/docs/runtime/hot#hot-mode) flag to run a file with hot reloading enabled. When any module or file changes, Bun re-runs the file.
+Bun supports the [`--hot`](/runtime/watch-mode#hot-mode) flag to run a file with hot reloading enabled. When any module or file changes, Bun re-runs the file.
 
 ```sh terminal icon="terminal"
 bun --hot run index.ts

docs/guides/http/server.mdx

@@ -6,7 +6,7 @@ mode: center
 
 This starts an HTTP server listening on port `3000`. It demonstrates basic routing with a number of common responses and also handles POST data from standard forms or as JSON.
 
-See [`Bun.serve`](https://bun.com/docs/api/http) for details.
+See [`Bun.serve`](/runtime/http/server) for details.
 
 ```ts server.ts icon="/icons/typescript.svg"
 const server = Bun.serve({

docs/guides/http/simple.mdx

@@ -6,7 +6,7 @@ mode: center
 
 This starts an HTTP server listening on port `3000`. It responds to all requests with a `Response` with status `200` and body `"Welcome to Bun!"`.
 
-See [`Bun.serve`](https://bun.com/docs/api/http) for details.
+See [`Bun.serve`](/runtime/http/server) for details.
 
 ```ts server.ts icon="/icons/typescript.svg"
 const server = Bun.serve({

docs/guides/http/stream-file.mdx

@@ -4,7 +4,7 @@ sidebarTitle: Stream file response
 mode: center
 ---
 
-This snippet reads a file from disk using [`Bun.file()`](https://bun.com/docs/api/file-io#reading-files-bun-file). This returns a `BunFile` instance, which can be passed directly into the `new Response` constructor.
+This snippet reads a file from disk using [`Bun.file()`](/runtime/file-io#reading-files-bun-file). This returns a `BunFile` instance, which can be passed directly into the `new Response` constructor.
 
 ```ts server.ts icon="/icons/typescript.svg"
 const path = "/path/to/file.txt";
@@ -32,7 +32,7 @@ new Response(Bun.file("./img.png")).headers.get("Content-Type");
 
 ---
 
-Putting it all together with [`Bun.serve()`](https://bun.com/docs/api/http#bun-serve).
+Putting it all together with [`Bun.serve()`](/runtime/http/server).
 
 ```ts server.ts icon="/icons/typescript.svg"
 // static file server
@@ -47,4 +47,4 @@ Bun.serve({
 
 ---
 
-See [Docs > API > File I/O](https://bun.com/docs/api/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.
+See [Docs > API > File I/O](/runtime/file-io#writing-files-bun-write) for complete documentation of `Bun.write()`.

docs/guides/http/tls.mdx

@@ -4,7 +4,7 @@ sidebarTitle: Configure TLS
 mode: center
 ---
 
-Set the `tls` key to configure TLS. Both `key` and `cert` are required. The `key` should be the contents of your private key; `cert` should be the contents of your issued certificate. Use [`Bun.file()`](https://bun.com/docs/api/file-io#reading-files-bun-file) to read the contents.
+Set the `tls` key to configure TLS. Both `key` and `cert` are required. The `key` should be the contents of your private key; `cert` should be the contents of your issued certificate. Use [`Bun.file()`](/runtime/file-io#reading-files-bun-file) to read the contents.
 
 ```ts server.ts icon="/icons/typescript.svg"
 const server = Bun.serve({

docs/guides/install/add-dev.mdx

@@ -25,4 +25,4 @@ This will add the package to `devDependencies` in `package.json`.
 
 ---
 
-See [Docs > Package manager](https://bun.com/docs/cli/install) for complete documentation of Bun's package manager.
+See [Docs > Package manager](/pm/cli/install) for complete documentation of Bun's package manager.

docs/guides/install/add-git.mdx

@@ -37,4 +37,4 @@ bun add github:colinhacks/zod
 
 ---
 
-See [Docs > Package manager](https://bun.com/docs/cli/install) for complete documentation of Bun's package manager.
+See [Docs > Package manager](/pm/cli/install) for complete documentation of Bun's package manager.

docs/guides/install/add-optional.mdx

@@ -24,4 +24,4 @@ This will add the package to `optionalDependencies` in `package.json`.
 
 ---
 
-See [Docs > Package manager](https://bun.com/docs/cli/install) for complete documentation of Bun's package manager.
+See [Docs > Package manager](/pm/cli/install) for complete documentation of Bun's package manager.

docs/guides/install/add-peer.mdx

@@ -17,7 +17,7 @@ This will add the package to `peerDependencies` in `package.json`.
 ```json package.json icon="file-json"
 {
   "peerDependencies": {
-    "@types/bun": "^1.3.2" // [!code ++]
+    "@types/bun": "^1.3.3" // [!code ++]
   }
 }
 ```
@@ -26,14 +26,14 @@ This will add the package to `peerDependencies` in `package.json`.
 
 Running `bun install` will install peer dependencies by default, unless marked optional in `peerDependenciesMeta`.
 
+{/* prettier-ignore */}
 ```json package.json icon="file-json"
 {
   "peerDependencies": {
-    "@types/bun": "^1.3.2"
+    "@types/bun": "^1.3.3"
   },
   "peerDependenciesMeta": {
-    "@types/bun": {
-      // [!code ++]
+    "@types/bun": { // [!code ++]
       "optional": true // [!code ++]
     } // [!code ++]
   }
@@ -42,4 +42,4 @@ Running `bun install` will install peer dependencies by default, unless marked o
 
 ---
 
-See [Docs > Package manager](https://bun.com/docs/cli/install) for complete documentation of Bun's package manager.
+See [Docs > Package manager](/pm/cli/install) for complete documentation of Bun's package manager.

docs/guides/install/add-tarball.mdx

@@ -32,4 +32,4 @@ import { z } from "zod";
 
 ---
 
-See [Docs > Package manager](https://bun.com/docs/cli/install) for complete documentation of Bun's package manager.
+See [Docs > Package manager](/pm/cli/install) for complete documentation of Bun's package manager.

docs/guides/install/add.mdx

@@ -41,4 +41,4 @@ bun add zod@next
 
 ---
 
-See [Docs > Package manager](https://bun.com/docs/cli/install) for complete documentation of Bun's package manager.
+See [Docs > Package manager](/pm/cli/install) for complete documentation of Bun's package manager.

docs/guides/install/azure-artifacts.mdx

@@ -31,9 +31,9 @@ password = "$NPM_PASSWORD"
 
 ---
 
-Then assign your Azure Personal Access Token to the `NPM_PASSWORD` environment variable. Bun [automatically reads](https://bun.com/docs/runtime/env) `.env` files, so create a file called `.env` in your project root. There is no need to base-64 encode this token! Bun will do this for you.
+Then assign your Azure Personal Access Token to the `NPM_PASSWORD` environment variable. Bun [automatically reads](/runtime/environment-variables) `.env` files, so create a file called `.env` in your project root. There is no need to base-64 encode this token! Bun will do this for you.
 
-```txt .env icon="settings"
+```ini .env icon="settings"
 NPM_PASSWORD=<paste token here>
 ```
 
@@ -43,7 +43,7 @@ NPM_PASSWORD=<paste token here>
 
 ---
 
-To configure Azure Artifacts without `bunfig.toml`, you can set the `NPM_CONFIG_REGISTRY` environment variable. The URL should include `:username` and `:_password` as query parameters. Replace `<USERNAME>` and `<PASSWORD>` with the apprropriate values.
+To configure Azure Artifacts without `bunfig.toml`, you can set the `NPM_CONFIG_REGISTRY` environment variable. The URL should include `:username` and `:_password` as query parameters. Replace `<USERNAME>` and `<PASSWORD>` with the appropriate values.
 
 ```bash terminal icon="terminal"
 NPM_CONFIG_REGISTRY=https://pkgs.dev.azure.com/my-azure-artifacts-user/_packaging/my-azure-artifacts-user/npm/registry/:username=<USERNAME>:_password=<PASSWORD>

docs/guides/install/custom-registry.mdx

@@ -20,7 +20,7 @@ registry = "https://usertitle:password@registry.npmjs.org"
 
 ---
 
-Your `bunfig.toml` can reference environment variables. Bun automatically loads environment variables from `.env.local`, `.env.[NODE_ENV]`, and `.env`. See [Docs > Environment variables](https://bun.com/docs/runtime/env) for more information.
+Your `bunfig.toml` can reference environment variables. Bun automatically loads environment variables from `.env.local`, `.env.[NODE_ENV]`, and `.env`. See [Docs > Environment variables](/runtime/environment-variables) for more information.
 
 ```toml bunfig.toml icon="settings"
 [install]
@@ -29,4 +29,4 @@ registry = { url = "https://registry.npmjs.org", token = "$npm_token" }
 
 ---
 
-See [Docs > Package manager](https://bun.com/docs/cli/install) for complete documentation of Bun's package manager.
+See [Docs > Package manager](/pm/cli/install) for complete documentation of Bun's package manager.

docs/guides/install/from-npm-install-to-bun-install.mdx

@@ -99,7 +99,7 @@ bun update
 bun update @types/bun --latest
 
 # Update a dependency to a specific version
-bun update @types/bun@1.3.2
+bun update @types/bun@1.3.3
 
 # Update all dependencies to the latest versions
 bun update --latest

docs/guides/install/git-diff-bun-lockfile.mdx

@@ -6,7 +6,8 @@ mode: center
 
 <Note>
   Bun v1.1.39 introduced `bun.lock`, a JSONC formatted lockfile. `bun.lock` is human-readable and git-diffable without
-  configuration, at no cost to performance. [**Learn more.**](https://bun.com/docs/install/lockfile#text-based-lockfile)
+  configuration, at no cost to performance. In 1.2.0+ it is the default format used for new projects. [**Learn
+  more.**](/pm/lockfile#text-based-lockfile)
 </Note>
 
 ---

docs/guides/install/npm-alias.mdx

@@ -22,4 +22,4 @@ z.string();
 
 ---
 
-See [Docs > Package manager](https://bun.com/docs/cli/install) for complete documentation of Bun's package manager.
+See [Docs > Package manager](/pm/cli/install) for complete documentation of Bun's package manager.

docs/guides/install/registry-scope.mdx

@@ -4,7 +4,7 @@ sidebarTitle: Configure a scoped registry
 mode: center
 ---
 
-Private registries can be configured using either [`.npmrc`](https://bun.com/docs/install/npmrc) or [`bunfig.toml`](https://bun.com/docs/runtime/bunfig#install-registry). While both are supported, we recommend using **bunfig.toml** for enhanced flexibility and Bun-specific options.
+Private registries can be configured using either [`.npmrc`](/pm/npmrc) or [`bunfig.toml`](/runtime/bunfig#install-registry). While both are supported, we recommend using **bunfig.toml** for enhanced flexibility and Bun-specific options.
 
 To configure a registry for a particular npm scope:
 
@@ -28,7 +28,7 @@ To configure a registry for a particular npm scope:
 
 ---
 
-Your `bunfig.toml` can reference environment variables. Bun automatically loads environment variables from `.env.local`, `.env.[NODE_ENV]`, and `.env`. See [Docs > Environment variables](https://bun.com/docs/runtime/env) for more information.
+Your `bunfig.toml` can reference environment variables. Bun automatically loads environment variables from `.env.local`, `.env.[NODE_ENV]`, and `.env`. See [Docs > Environment variables](/runtime/environment-variables) for more information.
 
 ```toml bunfig.toml icon="settings"
 [install.scopes]
@@ -37,4 +37,4 @@ Your `bunfig.toml` can reference environment variables. Bun automatically loads
 
 ---
 
-See [Docs > Package manager](https://bun.com/docs/cli/install) for complete documentation of Bun's package manager.
+See [Docs > Package manager](/pm/cli/install) for complete documentation of Bun's package manager.

docs/guides/install/trusted.mdx

@@ -47,4 +47,4 @@ bun install
 
 ---
 
-See [Docs > Package manager > Trusted dependencies](https://bun.com/docs/install/lifecycle) for complete documentation of trusted dependencies.
+See [Docs > Package manager > Trusted dependencies](/pm/lifecycle) for complete documentation of trusted dependencies.

docs/guides/install/workspaces.mdx

@@ -67,4 +67,4 @@ bun add zod
 
 ---
 
-See [Docs > Package manager](https://bun.com/docs/cli/install) for complete documentation of Bun's package manager.
+See [Docs > Package manager](/pm/cli/install) for complete documentation of Bun's package manager.

docs/guides/install/yarnlock.mdx

@@ -6,12 +6,13 @@ mode: center
 
 <Note>
   Bun v1.1.39 introduced `bun.lock`, a JSONC formatted lockfile. `bun.lock` is human-readable and git-diffable without
-  configuration, at no cost to performance. [**Learn more.**](https://bun.com/docs/install/lockfile#text-based-lockfile)
+  configuration, at no cost to performance. In 1.2.0+ it is the default format used for new projects. [**Learn
+  more.**](/pm/lockfile#text-based-lockfile)
 </Note>
 
 ---
 
-Use the `--yarn` flag to generate a Yarn-compatible `yarn.lock` file (in addition to `bun.lock`).
+Use the `--yarn` flag to generate a Yarn-compatible `yarn.lock` file (in addition to `bun.lock{b}`).
 
 ```sh terminal icon="terminal"
 bun install --yarn
@@ -47,4 +48,4 @@ abab@^2.0.6:
 
 ---
 
-See [Docs > Package manager](https://bun.com/docs/cli/install) for complete documentation of Bun's package manager.
+See [Docs > Package manager](/pm/cli/install) for complete documentation of Bun's package manager.

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](/runtime/utils) for more useful utilities.

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()`](/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](/runtime/child-process) for complete documentation.

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](/runtime/utils) for more useful utilities.

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](/runtime/utils) for more useful utilities.

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()`](/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](/runtime/child-process) for complete documentation.

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()`](/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](/runtime/child-process) for complete documentation.

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()`](/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](/runtime/child-process) for complete documentation.

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](/runtime/utils) for more useful utilities.

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()`](/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](/runtime/binary-data#typedarray) docs for more information on working with typed arrays in Bun.

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](/runtime/binary-data#buffer) for more information on working with `Buffer` and other binary data formats in Bun.

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](/runtime/file-io) for more information on working with `BunFile`.

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](/runtime/file-io) for more information on working with `BunFile`.

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](/runtime/streams) documentation for more information on working with streams in Bun.