npm - bun-types - Versions diffs - 1.3.2-canary.20251105T140650 → 1.3.2 - Mend

bun-types 1.3.2-canary.20251105T140650 → 1.3.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (370) hide show

package/docs/installation.md DELETED Viewed

@@ -1,327 +0,0 @@
-Bun ships as a single executable with no dependencies that can be installed a few different ways.
-## Installing
-### macOS and Linux
-{% callout %}
-**Linux users** — The `unzip` package is required to install Bun. Use `sudo apt install unzip` to install `unzip` package.
-Kernel version 5.6 or higher is strongly recommended, but the minimum is 5.1. Use `uname -r` to check Kernel version.
-{% /callout %}
-{% codetabs %}
-```bash#macOS/Linux_(curl)
-$ curl -fsSL https://bun.com/install | bash # for macOS, Linux, and WSL
-# to install a specific version
-$ curl -fsSL https://bun.com/install | bash -s "bun-v1.3.2-canary.20251105T140650"
-```
-```bash#npm
-$ npm install -g bun # the last `npm` command you'll ever need
-```
-```bash#Homebrew
-$ brew install oven-sh/bun/bun # for macOS and Linux
-```
-```bash#Docker
-$ docker pull oven/bun
-$ docker run --rm --init --ulimit memlock=-1:-1 oven/bun
-```
-{% /codetabs %}
-### Windows
-To install, paste this into a terminal:
-{% codetabs %}
-```powershell#PowerShell/cmd.exe
-> powershell -c "irm bun.sh/install.ps1|iex"
-```
-```powershell#npm
-> npm install -g bun # the last `npm` command you'll ever need
-```
-```powershell#Scoop
-> scoop install bun
-```
-{% /codetabs %}
-{% callout %}
-Bun requires a minimum of Windows 10 version 1809
-{% /callout %}
-For support and discussion, please join the [#windows channel on our Discord](http://bun.com/discord).
-## Docker
-Bun provides a [Docker image](https://hub.docker.com/r/oven/bun/tags) that supports both Linux x64 and arm64.
-```bash
-$ docker pull oven/bun
-$ docker run --rm --init --ulimit memlock=-1:-1 oven/bun
-```
-There are also image variants for different operating systems.
-```bash
-$ docker pull oven/bun:debian
-$ docker pull oven/bun:slim
-$ docker pull oven/bun:distroless
-$ docker pull oven/bun:alpine
-```
-## Checking installation
-To check that Bun was installed successfully, open a new terminal window and run `bun --version`.
-```sh
-$ bun --version
-1.x.y
-```
-To see the precise commit of [oven-sh/bun](https://github.com/oven-sh/bun) that you're using, run `bun --revision`.
-```sh
-$ bun --revision
-1.x.y+b7982ac13189
-```
-If you've installed Bun but are seeing a `command not found` error, you may have to manually add the installation directory (`~/.bun/bin`) to your `PATH`.
-### How to add your `PATH`
-{% details summary="Linux / Mac" %}
-First, determine what shell you're using:
-```sh
-$ echo $SHELL
-/bin/zsh # or /bin/bash or /bin/fish
-```
-Then add these lines below to bottom of your shell's configuration file.
-{% codetabs %}
-```bash#~/.zshrc
-# add to ~/.zshrc
-export BUN_INSTALL="$HOME/.bun"
-export PATH="$BUN_INSTALL/bin:$PATH"
-```
-```bash#~/.bashrc
-# add to ~/.bashrc
-export BUN_INSTALL="$HOME/.bun"
-export PATH="$BUN_INSTALL/bin:$PATH"
-```
-```sh#~/.config/fish/config.fish
-# add to ~/.config/fish/config.fish
-export BUN_INSTALL="$HOME/.bun"
-export PATH="$BUN_INSTALL/bin:$PATH"
-```
-{% /codetabs %}
-Save the file. You'll need to open a new shell/terminal window for the changes to take effect.
-{% /details %}
-{% details summary="Windows" %}
-First, determine if the bun binary is properly installed on your system:
-```pwsh
-& "$env:USERPROFILE\.bun\bin\bun" --version
-```
-If the command runs successfully but `bun --version` is not recognized, it means that bun is not in your system's `PATH`. To fix this, open a Powershell terminal and run the following command:
-```pwsh
-[System.Environment]::SetEnvironmentVariable(
-    "Path",
-    [System.Environment]::GetEnvironmentVariable("Path", "User") + ";$env:USERPROFILE\.bun\bin",
-    [System.EnvironmentVariableTarget]::User
-)
-```
-After running the command, restart your terminal and test with `bun --version`
-{% /details %}
-## Upgrading
-Once installed, the binary can upgrade itself.
-```sh
-$ bun upgrade
-```
-{% callout %}
-**Homebrew users** — To avoid conflicts with Homebrew, use `brew upgrade bun` instead.
-**Scoop users** — To avoid conflicts with Scoop, use `scoop update bun` instead.
-{% /callout %}
-## Canary builds
-Bun automatically releases an (untested) canary build on every commit to `main`. To upgrade to the latest canary build:
-```sh
-$ bun upgrade --canary
-```
-The canary build is useful for testing new features and bug fixes before they're released in a stable build. To help the Bun team fix bugs faster, canary builds automatically upload crash reports to Bun's team.
-[View canary build](https://github.com/oven-sh/bun/releases/tag/canary)
-{% callout %}
-**Note** — To switch back to a stable release from canary, run `bun upgrade --stable`.
-{% /callout %}
-## Installing older versions of Bun
-Since Bun is a single binary, you can install older versions of Bun by re-running the installer script with a specific version.
-### 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.3.2-canary.20251105T140650`.
-```sh
-$ curl -fsSL https://bun.com/install | bash -s "bun-v1.3.2-canary.20251105T140650"
-```
-### Installing a specific version of Bun on Windows
-On Windows, you can install a specific version of Bun by passing the version number to the Powershell install script.
-```sh
-# PowerShell:
-$ iex "& {$(irm https://bun.com/install.ps1)} -Version 1.3.2-canary.20251105T140650"
-```
-## Downloading Bun binaries directly
-To download Bun binaries directly, you can visit the [releases page](https://github.com/oven-sh/bun/releases) on GitHub.
-For convenience, here are download links for the latest version:
-- [`bun-linux-x64.zip`](https://github.com/oven-sh/bun/releases/latest/download/bun-linux-x64.zip)
-- [`bun-linux-x64-baseline.zip`](https://github.com/oven-sh/bun/releases/latest/download/bun-linux-x64-baseline.zip)
-- [`bun-linux-x64-musl.zip`](https://github.com/oven-sh/bun/releases/latest/download/bun-linux-x64-musl.zip)
-- [`bun-linux-x64-musl-baseline.zip`](https://github.com/oven-sh/bun/releases/latest/download/bun-linux-x64-musl-baseline.zip)
-- [`bun-windows-x64.zip`](https://github.com/oven-sh/bun/releases/latest/download/bun-windows-x64.zip)
-- [`bun-windows-x64-baseline.zip`](https://github.com/oven-sh/bun/releases/latest/download/bun-windows-x64-baseline.zip)
-- [`bun-darwin-aarch64.zip`](https://github.com/oven-sh/bun/releases/latest/download/bun-darwin-aarch64.zip)
-- [`bun-linux-aarch64.zip`](https://github.com/oven-sh/bun/releases/latest/download/bun-linux-aarch64.zip)
-- [`bun-linux-aarch64-musl.zip`](https://github.com/oven-sh/bun/releases/latest/download/bun-linux-aarch64-musl.zip)
-- [`bun-darwin-x64.zip`](https://github.com/oven-sh/bun/releases/latest/download/bun-darwin-x64.zip)
-The `musl` binaries are built for distributions that do not ship with the glibc libraries by default, instead relying on musl. The two most popular distros are Void Linux and Alpine Linux, with the latter is used heavily in Docker containers. If you encounter an error like the following: `bun: /lib/x86_64-linux-gnu/libm.so.6: version GLIBC_2.29' not found (required by bun)`, try using the musl binary. Bun's install script automatically chooses the correct binary for your system.
-### CPU requirements and `baseline` builds
-Bun's `x64` binaries target the Haswell CPU architecture, which means they require AVX and AVX2 instructions. For Linux and Windows, the `x64-baseline` binaries are also available which target the Nehalem architecture. If you run into an "Illegal Instruction" error when running Bun, try using the `baseline` binaries instead. Bun's install script automatically chooses the correct binary for your system which helps avoid this issue. Baseline builds are slower than regular builds, so use them only if necessary.
-| Build        | Intel requirement                                                  | AMD requirement    |
-| ------------ | ------------------------------------------------------------------ | ------------------ |
-| x64          | Haswell (4th generation Core) or newer, except some low-end models | Excavator or newer |
-| x64-baseline | Nehalem (1st generation Core) or newer                             | Bulldozer or newer |
-Bun does not currently support any CPUs older than the `baseline` target, which mandates the SSE4.2 extension.
-Bun also publishes `darwin-x64-baseline` binaries, but these are just a copy of the `darwin-x64` ones so they still have the same CPU requirement. We only maintain these since some tools expect them to exist. Bun requires macOS 13.0 or later, which does not support any CPUs that don't meet our requirement.
-<!--
-## Native
-Works on macOS x64 & Silicon, Linux x64, Windows Subsystem for Linux.
-```sh
-$ curl -fsSL https://bun.com/install | bash
-```
-Once installed, the binary can upgrade itself.
-```sh
-$ bun upgrade
-```
-Bun automatically releases an (untested) canary build on every commit to `main`. To upgrade to the latest canary build:
-```sh
-$ bun upgrade --canary
-```
-## Homebrew
-Works on macOS and Linux
-```sh
-$ brew tap oven-sh/bun
-$ brew install bun
-```
-Homebrew recommends using `brew upgrade <package>` to install newer versions.
-## Docker
-Works on Linux x64
-```sh
-# this is a comment
-$ docker pull oven/bun:edge
-this is some output
-$ docker run --rm --init --ulimit memlock=-1:-1 oven/bun:edge
-$ docker run --rm --init --ulimit memlock=-1:-1 oven/bun:edge
-this is some output
-``` -->
-<!-- ## Completions
-Shell auto-completion should be configured automatically when Bun is installed!
-If not, run the following command. It uses `$SHELL` to determine which shell you're using and writes a completion file to the appropriate place on disk. It's automatically re-run on every `bun upgrade`.
-```bash
-$ bun completions
-```
-To write the completions to a custom location:
-```bash
-$ bun completions > path-to-file      # write to file
-$ bun completions /path/to/directory  # write into directory
-``` -->
-## Uninstall
-If you need to remove Bun from your system, use the following commands.
-{% codetabs %}
-```bash#macOS/Linux_(curl)
-$ rm -rf ~/.bun # for macOS, Linux, and WSL
-```
-```powershell#Windows
-> powershell -c ~\.bun\uninstall.ps1
-```
-```powershell#Scoop
-> scoop uninstall bun
-```
-```bash#npm
-$ npm uninstall -g bun
-```
-```bash#Homebrew
-$ brew uninstall bun
-```
-{% /codetabs %}

package/docs/project/asan.md DELETED Viewed

@@ -1,124 +0,0 @@
-# ASAN Builds for Bun
-This document explains how to use and configure ASAN (Address Sanitizer) builds for Bun.
-> **Note**: ASAN builds are available in CI for Linux and are configured to help identify memory issues in release builds.
-## What is ASAN?
-ASAN (Address Sanitizer) is a memory error detector for C/C++ and Zig code. It can detect:
-- Use-after-free
-- Heap buffer overflow
-- Stack buffer overflow
-- Global buffer overflow
-- Use-after-return
-- Use-after-scope
-- Initialization order bugs
-- Memory leaks
-## ASAN Builds in CI
-Bun CI includes ASAN builds to catch memory errors. These builds are configured with:
-- Release optimizations for speed
-- ASAN instrumentation for memory error detection
-- Assertions enabled for both Bun and WebKit
-The CI pipeline automatically:
-- Builds a special ASAN-enabled release build for Linux
-- Runs all tests to thoroughly check for memory issues
-- Uses reduced parallelism to avoid memory pressure during testing
-- Applies suppressions for known false positives
-- Extends test timeouts to accommodate ASAN overhead
-- Includes ASAN builds in release artifacts for debugging purposes
-## Local ASAN Builds
-To build Bun with ASAN locally, you can use the npm script:
-```bash
-# Build a release build with ASAN and assertions (recommended)
-bun run build:asan
-```
-Or manually with CMake:
-```bash
-# Debug build with ASAN
-cmake -B build -DCMAKE_BUILD_TYPE=Debug -DENABLE_ASAN=ON
-# Release build with ASAN
-cmake -B build -DCMAKE_BUILD_TYPE=Release -DENABLE_ASAN=ON
-# Release build with ASAN and assertions
-cmake -B build -DCMAKE_BUILD_TYPE=Release -DENABLE_ASAN=ON -DENABLE_ASSERTIONS=ON
-```
-## Running with ASAN
-When running an ASAN build, you can configure behavior with environment variables:
-```bash
-# Basic ASAN options - leak detection disabled (recommended)
-ASAN_OPTIONS=detect_leaks=0:halt_on_error=0:detect_odr_violation=0 ./build/bun-asan
-# If you really need leak detection (will produce A LOT of noise)
-# ASAN_OPTIONS=detect_leaks=1:leak_check_at_exit=1:halt_on_error=0 ./build/bun-asan
-# LSAN_OPTIONS=suppressions=lsan.supp:print_suppressions=1 ./build/bun-asan
-```
-> **Warning**: Enabling leak detection will generate excessive noise due to deliberately uncollected memory in WebKit and other components. It's recommended to keep leak detection disabled and focus on other memory errors like use-after-free, buffer overflows, etc.
-## Other Memory Error Types
-ASAN can detect several types of memory errors:
-1. **Use-after-free**: When a program continues to use memory after it's been freed
-2. **Buffer overflow**: When a program writes beyond the bounds of allocated memory
-3. **Stack overflow**: When a function's stack usage exceeds available space
-4. **Memory corruption**: Often caused by writing to invalid memory locations
-5. **Use-after-return**: When a function returns a pointer to stack memory that's no longer valid
-When an error is detected, ASAN will print a helpful report showing:
-- The type of error
-- The memory address where the error occurred
-- A stack trace showing the code path that led to the error
-- Information about the memory allocation/deallocation (if relevant)
-Example error output:
-```
-==1234==ERROR: AddressSanitizer: heap-use-after-free on address 0x614000000044 at pc 0x55d8e2ac1f14...
-READ of size 4 at 0x614000000044 thread T0
-    #0 0x55d8e2ac1f14 in main example.c:10
-    #1 0x7f91e6f5e0b2 in __libc_start_main...
-```
-## Understanding ASAN Reports
-ASAN reports contain detailed information about memory errors:
-```
-==12345==ERROR: AddressSanitizer: heap-use-after-free on address 0x7f7ddab8c084
-READ of size 4 at 0x7f7ddab8c084 thread T0
-    #0 0x43b45a in Function source/file.cpp:123:45
-    #1 0x44af90 in AnotherFunction source/file.cpp:234:10
-    ...
-```
-Key components of the report:
-- Error type (heap-use-after-free, heap-buffer-overflow, etc.)
-- Operation (READ/WRITE) and size
-- Stack trace showing where the error occurred
-- Information about the allocated/freed memory
-## Best Practices
-1. Run tests with ASAN builds regularly
-2. Add suppressions only for well-understood false positives
-3. Fix real issues promptly - ASAN errors indicate real problems
-4. Consider using ASAN in debug builds during development

package/docs/project/internals/build-process-for-ci.md DELETED Viewed

@@ -1,75 +0,0 @@
-There are four parts to the CI build:
-- Dependencies: should be cached across builds as much as possible, it depends on git submodule hashes
-- Zig Object: depends on \*.zig and src/js
-- C++ Object: depends on \*.cpp and src/js
-- Linking: depends on the above three
-Utilizing multiple GitHub Action runners allows us to do a lot of work in parallel.
-## Dependencies
-```sh
-BUN_DEPS_OUT_DIR="/optional/out/dir" bash ./scripts/all-dependencies.sh
-```
-## Zig Object
-This does not have a dependency on WebKit or any of the dependencies at all. It can be compiled without checking out submodules, but you will need to have bun install run. It can be very easily cross compiled. Note that the zig object is always `bun-zig.o`.
-```sh
-BUN_REPO=/path/to/oven-sh/bun
-cd tmp1
-cmake $BUN_REPO \
-  -G Ninja \
-  -DCMAKE_BUILD_TYPE=Release \
-  -DCPU_TARGET="native" \
-  -DZIG_TARGET="native" \
-  -DBUN_ZIG_OBJ_DIR="./build"
-ninja ./build/bun-zig.o
-# -> bun-zig.o
-```
-## C++ Object
-Note: if WEBKIT_DIR is not passed, it is automatically downloaded from GitHub releases. This depends on the headers from submodules but not necessarily the build copies of them, .a files, etc.
-```sh
-cd tmp2
-cmake $BUN_REPO \
-  -G Ninja \
-  -DCMAKE_BUILD_TYPE=Release \
-  -DBUN_CPP_ONLY=1 \
-bash compile-cpp-only.sh
-# -> bun-cpp-objects.a
-```
-## Linking
-The goal is you run both stages from above on different machines, so that they can build in parallel. Zig build is slow, and MacOS build runners are slower on average than the linux ones. With both artifacts from above, you can link them together:
-```sh
-cd tmp3
-cmake $BUN_REPO \
-  -G Ninja \
-  -DCMAKE_BUILD_TYPE=Release \
-  -DBUN_LINK_ONLY=1 \
-  -DBUN_ZIG_OBJ_DIR="/path/to/bun-zig-dir" \
-  -DBUN_CPP_ARCHIVE="/path/to/bun-cpp-objects.a"
-ninja
-# optional:
-#   -DBUN_DEPS_OUT_DIR=... custom deps dir, use this to cache the built deps between rebuilds
-#   -DWEBKIT_DIR=... same thing, but it's probably fast enough to pull from github releases
-# -> bun
-# -> bun-profile
-# -> bun.dSYM/
-```

package/docs/project/licensing.md DELETED Viewed

@@ -1,73 +0,0 @@
-Bun itself is MIT-licensed.
-## JavaScriptCore
-Bun statically links JavaScriptCore (and WebKit) which is LGPL-2 licensed. WebCore files from WebKit are also licensed under LGPL2. Per LGPL2:
-> (1) If you statically link against an LGPL’d library, you must also provide your application in an object (not necessarily source) format, so that a user has the opportunity to modify the library and relink the application.
-You can find the patched version of WebKit used by Bun here: <https://github.com/oven-sh/webkit>. If you would like to relink Bun with changes:
-- `git submodule update --init --recursive`
-- `make jsc`
-- `zig build`
-This compiles JavaScriptCore, compiles Bun’s `.cpp` bindings for JavaScriptCore (which are the object files using JavaScriptCore) and outputs a new `bun` binary with your changes.
-## Linked libraries
-Bun statically links these libraries:
-| Library | License |
-|---------|---------|
-| [`boringssl`](https://boringssl.googlesource.com/boringssl/) | [several licenses](https://boringssl.googlesource.com/boringssl/+/refs/heads/master/LICENSE) |
-| [`brotli`](https://github.com/google/brotli) | MIT |
-| [`libarchive`](https://github.com/libarchive/libarchive) | [several licenses](https://github.com/libarchive/libarchive/blob/master/COPYING) |
-| [`lol-html`](https://github.com/cloudflare/lol-html/tree/master/c-api) | BSD 3-Clause |
-| [`mimalloc`](https://github.com/microsoft/mimalloc) | MIT |
-| [`picohttp`](https://github.com/h2o/picohttpparser) | dual-licensed under the Perl License or the MIT License |
-| [`zstd`](https://github.com/facebook/zstd) | dual-licensed under the BSD License or GPLv2 license |
-| [`simdutf`](https://github.com/simdutf/simdutf) | Apache 2.0 |
-| [`tinycc`](https://github.com/tinycc/tinycc) | LGPL v2.1 |
-| [`uSockets`](https://github.com/uNetworking/uSockets) | Apache 2.0 |
-| [`zlib-cloudflare`](https://github.com/cloudflare/zlib) | zlib |
-| [`c-ares`](https://github.com/c-ares/c-ares) | MIT licensed |
-| [`libicu`](https://github.com/unicode-org/icu) 72 | [license here](https://github.com/unicode-org/icu/blob/main/icu4c/LICENSE) |
-| [`libbase64`](https://github.com/aklomp/base64/blob/master/LICENSE) | BSD 2-Clause |
-| [`libuv`](https://github.com/libuv/libuv) (on Windows) | MIT |
-| [`libdeflate`](https://github.com/ebiggers/libdeflate) | MIT |
-| A fork of [`uWebsockets`](https://github.com/jarred-sumner/uwebsockets) | Apache 2.0 licensed |
-| Parts of [Tigerbeetle's IO code](https://github.com/tigerbeetle/tigerbeetle/blob/532c8b70b9142c17e07737ab6d3da68d7500cbca/src/io/windows.zig#L1) | Apache 2.0 licensed |
-## Polyfills
-For compatibility reasons, the following packages are embedded into Bun's binary and injected if imported.
-| Package | License |
-|---------|---------|
-| [`assert`](https://npmjs.com/package/assert) | MIT |
-| [`browserify-zlib`](https://npmjs.com/package/browserify-zlib) | MIT |
-| [`buffer`](https://npmjs.com/package/buffer) | MIT |
-| [`constants-browserify`](https://npmjs.com/package/constants-browserify) | MIT |
-| [`crypto-browserify`](https://npmjs.com/package/crypto-browserify) | MIT |
-| [`domain-browser`](https://npmjs.com/package/domain-browser) | MIT |
-| [`events`](https://npmjs.com/package/events) | MIT |
-| [`https-browserify`](https://npmjs.com/package/https-browserify) | MIT |
-| [`os-browserify`](https://npmjs.com/package/os-browserify) | MIT |
-| [`path-browserify`](https://npmjs.com/package/path-browserify) | MIT |
-| [`process`](https://npmjs.com/package/process) | MIT |
-| [`punycode`](https://npmjs.com/package/punycode) | MIT |
-| [`querystring-es3`](https://npmjs.com/package/querystring-es3) | MIT |
-| [`stream-browserify`](https://npmjs.com/package/stream-browserify) | MIT |
-| [`stream-http`](https://npmjs.com/package/stream-http) | MIT |
-| [`string_decoder`](https://npmjs.com/package/string_decoder) | MIT |
-| [`timers-browserify`](https://npmjs.com/package/timers-browserify) | MIT |
-| [`tty-browserify`](https://npmjs.com/package/tty-browserify) | MIT |
-| [`url`](https://npmjs.com/package/url) | MIT |
-| [`util`](https://npmjs.com/package/util) | MIT |
-| [`vm-browserify`](https://npmjs.com/package/vm-browserify) | MIT |
-## Additional credits
-- Bun's JS transpiler, CSS lexer, and Node.js module resolver source code is a Zig port of [@evanw](https://github.com/evanw)’s [esbuild](https://github.com/evanw/esbuild) project.
-- Credit to [@kipply](https://github.com/kipply) for the name "Bun"!

package/docs/project/roadmap.md DELETED Viewed

@@ -1,87 +0,0 @@
-Bun is a project with an incredibly large scope and is still in its early days. Long-term, Bun aims to provide an all-in-one toolkit to replace the complex, fragmented toolchains common today: Node.js, Jest, Webpack, esbuild, Babel, yarn, PostCSS, etc.
-Refer to [Bun's Roadmap](https://github.com/oven-sh/bun/issues/159) on GitHub to learn more about the project's long-term plans and priorities.
-<!--
-{% table %}
-- Feature
-- Implemented in
----
-- Web Streams with HTMLRewriter
-- Bun.js
----
-- Source Maps (unbundled is supported)
-- JS Bundler
----
-- Source Maps
-- CSS
----
-- JavaScript Minifier
-- JS Transpiler
----
-- CSS Minifier
-- CSS
----
-- CSS Parser (it only bundles)
-- CSS
----
-- Tree-shaking
-- JavaScript
----
-- Tree-shaking
-- CSS
----
-- [TypeScript Decorators](https://www.typescriptlang.org/docs/handbook/decorators.html)
-- TS Transpiler
----
-- `@jsxPragma` comments
-- JS Transpiler
----
-- Sharing `.bun` files
-- Bun
----
-- Dates & timestamps
-- TOML parser
----
-- [Hash components for Fast Refresh](https://github.com/oven-sh/bun/issues/18)
-- JSX Transpiler
-{% /table %} -->
-<!-- ## Limitations & intended usage
-Today, Bun is mostly focused on Bun.js: the JavaScript runtime.
-While you could use Bun's bundler & transpiler separately to build for browsers or node, Bun doesn't have a minifier or support tree-shaking yet. For production browser builds, you probably should use a tool like esbuild or swc.
-## Upcoming breaking changes
-- Bun's CLI flags will change to better support Bun as a JavaScript runtime. They were chosen when Bun was just a frontend development tool.
-- Bun's bundling format will change to accommodate production browser bundles and on-demand production bundling -->