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

package/docs/project/building-windows.md

@@ -1,162 +0,0 @@
-This document describes the build process for Windows. If you run into problems, please join the [#contributing channel on our Discord](http://bun.com/discord) for help.
-
-It is strongly recommended to use [PowerShell 7 (`pwsh.exe`)](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows?view=powershell-7.4) instead of the default `powershell.exe`.
-
-## Prerequisites
-
-<!--
-{% details summary="Extra notes for Bun Core Team Members" %}
-
-Here are the extra steps I ran on my fresh windows machine (some of these are a little opiniated)
-
-- Change user to a local account (set username to `window` and 'bun!')
-- Set Windows Terminal as default terminal
-- Install latest version of Powershell
-- Display scale to 100%
-- Remove McAfee and enable Windows Defender (default antivirus, does not nag you)
-- Install Software
-  - OpenSSH server (run these in an elevated terminal)
-    - `Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0`
-    - `Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0`
-    - `Start-Service sshd`
-    - `Set-Service -Name sshd -StartupType 'Automatic'`
-    - `New-ItemProperty -Path "HKLM:\SOFTWARE\OpenSSH" -Name DefaultShell -Value "C:\Program Files\PowerShell\7\pwsh.exe" -PropertyType String -Force`
-    - Configure in `C:\ProgramData\ssh`
-    - Add ssh keys (in ProgramData because it is an admin account)
-  - Tailscale (login with GitHub so it joins the team tailnet)
-  - Visual Studio Code
-- Configure `git`
-  - `git config user.name "your name"`
-  - `git config user.email "your@email"`
-- Disable sleep mode and the lid switch by going to "Power Options" and configuring everything there.
-
-I recommend using VSCode through SSH instead of Tunnels or the Tailscale extension, it seems to be more reliable.
-
-{% /details %} -->
-
-### Enable Scripts
-
-By default, running unverified scripts are blocked.
-
-```ps1
-> Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Unrestricted
-```
-
-### System Dependencies
-
-Bun v1.1 or later. We use Bun to run it's own code generators.
-
-```ps1
-> irm bun.com/install.ps1 | iex
-```
-
-[Visual Studio](https://visualstudio.microsoft.com) with the "Desktop Development with C++" workload. While installing, make sure to install Git as well, if Git for Windows is not already installed.
-
-Visual Studio can be installed graphically using the wizard or through WinGet:
-
-```ps1
-> winget install "Visual Studio Community 2022" --override "--add Microsoft.VisualStudio.Workload.NativeDesktop Microsoft.VisualStudio.Component.Git " -s msstore
-```
-
-After Visual Studio, you need the following:
-
-- LLVM 19.1.7
-- Go
-- Rust
-- NASM
-- Perl
-- Ruby
-- Node.js
-- Ccache
-
-{% callout %}
-**Note** – The Zig compiler is automatically downloaded, installed, and updated by the building process.
-{% /callout %}
-
-[Scoop](https://scoop.sh) can be used to install these remaining tools easily.
-
-{% codetabs group="a" %}
-
-```ps1#Scoop
-> irm https://get.scoop.sh | iex
-> scoop install nodejs-lts go rust nasm ruby perl ccache
-# scoop seems to be buggy if you install llvm and the rest at the same time
-> scoop install llvm@19.1.7
-```
-
-{% /codetabs %}
-
-{% callout %}
-Please do not use WinGet/other package manager for these, as you will likely install Strawberry Perl instead of a more minimal installation of Perl. Strawberry Perl includes many other utilities that get installed into `$Env:PATH` that will conflict with MSVC and break the build.
-{% /callout %}
-
-If you intend on building WebKit locally (optional), you should install these packages:
-
-```ps1#Scoop
-> scoop install make cygwin python
-```
-
-From here on out, it is **expected you use a PowerShell Terminal with `.\scripts\vs-shell.ps1` sourced**. This script is available in the Bun repository and can be loaded by executing it:
-
-```ps1
-> .\scripts\vs-shell.ps1
-```
-
-To verify, you can check for an MSVC-only command line such as `mt.exe`
-
-```ps1
-> Get-Command mt
-```
-
-{% callout %}
-It is not recommended to install `ninja` / `cmake` into your global path, because you may run into a situation where you try to build bun without .\scripts\vs-shell.ps1 sourced.
-{% /callout %}
-
-## Building
-
-```ps1
-> bun run build
-
-# after the initial `bun run build` you can use the following to build
-> ninja -Cbuild/debug
-```
-
-If this was successful, you should have a `bun-debug.exe` in the `build/debug` folder.
-
-```ps1
-> .\build\debug\bun-debug.exe --revision
-```
-
-You should add this to `$Env:PATH`. The simplest way to do so is to open the start menu, type "Path", and then navigate the environment variables menu to add `C:\.....\bun\build\debug` to the user environment variable `PATH`. You should then restart your editor (if it does not update still, log out and log back in).
-
-## Extra paths
-
-- WebKit is extracted to `build/debug/cache/webkit/`
-- Zig is extracted to `build/debug/cache/zig/bin/zig.exe`
-
-## Tests
-
-You can run the test suite either using `bun test <path>` or by using the wrapper script `bun node:test <path>`. The `bun node:test` command runs every test file in a separate instance of bun.exe, to prevent a crash in the test runner from stopping the entire suite.
-
-```ps1
-# Setup
-> bun i --cwd packages\bun-internal-test
-
-# Run the entire test suite with reporter
-# the package.json script "test" uses "build/debug/bun-debug.exe" by default
-> bun run test
-
-# Run an individual test file:
-> bun-debug test node\fs
-> bun-debug test "C:\bun\test\js\bun\resolve\import-meta.test.js"
-```
-
-## Troubleshooting
-
-### .rc file fails to build
-
-`llvm-rc.exe` is odd. don't use it. use `rc.exe`, to do this make sure you are in a visual studio dev terminal, check `rc /?` to ensure it is `Microsoft Resource Compiler`
-
-### failed to write output 'bun-debug.exe': permission denied
-
-you cannot overwrite `bun-debug.exe` if it is already open. you likely have a running instance, maybe in the vscode debugger?

package/docs/project/contributing.md

@@ -1,347 +0,0 @@
-Configuring a development environment for Bun can take 10-30 minutes depending on your internet connection and computer speed. You will need ~10GB of free disk space for the repository and build artifacts.
-
-If you are using Windows, please refer to [this guide](https://bun.com/docs/project/building-windows)
-
-## Using Nix (Alternative)
-
-A Nix flake is provided as an alternative to manual dependency installation:
-
-```bash
-nix develop
-# or explicitly use the pure shell
-# nix develop .#pure
-export CMAKE_SYSTEM_PROCESSOR=$(uname -m)
-bun bd
-```
-
-This provides all dependencies in an isolated, reproducible environment without requiring sudo.
-
-## Install Dependencies (Manual)
-
-Using your system's package manager, install Bun's dependencies:
-
-{% codetabs group="os" %}
-
-```bash#macOS (Homebrew)
-$ brew install automake ccache cmake coreutils gnu-sed go icu4c libiconv libtool ninja pkg-config rust ruby
-```
-
-```bash#Ubuntu/Debian
-$ sudo apt install curl wget lsb-release software-properties-common cargo ccache cmake git golang libtool ninja-build pkg-config rustc ruby-full xz-utils
-```
-
-```bash#Arch
-$ sudo pacman -S base-devel ccache cmake git go libiconv libtool make ninja pkg-config python rust sed unzip ruby
-```
-
-```bash#Fedora
-$ sudo dnf install cargo clang19 llvm19 lld19 ccache cmake git golang libtool ninja-build pkg-config rustc ruby libatomic-static libstdc++-static sed unzip which libicu-devel 'perl(Math::BigInt)'
-```
-
-```bash#openSUSE Tumbleweed
-$ sudo zypper install go cmake ninja automake git icu rustup && rustup toolchain install stable
-```
-
-{% /codetabs %}
-
-> **Note**: The Zig compiler is automatically installed and updated by the build scripts. Manual installation is not required.
-
-Before starting, you will need to already have a release build of Bun installed, as we use our bundler to transpile and minify our code, as well as for code generation scripts.
-
-{% codetabs %}
-
-```bash#Native
-$ curl -fsSL https://bun.com/install | bash
-```
-
-```bash#npm
-$ npm install -g bun
-```
-
-```bash#Homebrew
-$ brew tap oven-sh/bun
-$ brew install bun
-```
-
-{% /codetabs %}
-
-## Install LLVM
-
-Bun requires LLVM 19 (`clang` is part of LLVM). This version requirement is to match WebKit (precompiled), as mismatching versions will cause memory allocation failures at runtime. In most cases, you can install LLVM through your system package manager:
-
-{% codetabs group="os" %}
-
-```bash#macOS (Homebrew)
-$ brew install llvm@19
-```
-
-```bash#Ubuntu/Debian
-$ # LLVM has an automatic installation script that is compatible with all versions of Ubuntu
-$ wget https://apt.llvm.org/llvm.sh -O - | sudo bash -s -- 19 all
-```
-
-```bash#Arch
-$ sudo pacman -S llvm clang lld
-```
-
-```bash#Fedora
-$ sudo dnf install llvm clang lld-devel
-```
-
-```bash#openSUSE Tumbleweed
-$ sudo zypper install clang19 lld19 llvm19
-```
-
-{% /codetabs %}
-
-If none of the above solutions apply, you will have to install it [manually](https://github.com/llvm/llvm-project/releases/tag/llvmorg-19.1.7).
-
-Make sure Clang/LLVM 19 is in your path:
-
-```bash
-$ which clang-19
-```
-
-If not, run this to manually add it:
-
-{% codetabs group="os" %}
-
-```bash#macOS (Homebrew)
-# use fish_add_path if you're using fish
-# use path+="$(brew --prefix llvm@19)/bin" if you are using zsh
-$ export PATH="$(brew --prefix llvm@19)/bin:$PATH"
-```
-
-```bash#Arch
-# use fish_add_path if you're using fish
-$ export PATH="$PATH:/usr/lib/llvm19/bin"
-```
-
-{% /codetabs %}
-
-> ⚠️ Ubuntu distributions (<= 20.04) may require installation of the C++ standard library independently. See the [troubleshooting section](#span-file-not-found-on-ubuntu) for more information.
-
-## Building Bun
-
-After cloning the repository, run the following command to build. This may take a while as it will clone submodules and build dependencies.
-
-```bash
-$ bun run build
-```
-
-The binary will be located at `./build/debug/bun-debug`. It is recommended to add this to your `$PATH`. To verify the build worked, let's print the version number on the development build of Bun.
-
-```bash
-$ build/debug/bun-debug --version
-x.y.z_debug
-```
-
-## VSCode
-
-VSCode is the recommended IDE for working on Bun, as it has been configured. Once opening, you can run `Extensions: Show Recommended Extensions` to install the recommended extensions for Zig and C++. ZLS is automatically configured.
-
-If you use a different editor, make sure that you tell ZLS to use the automatically installed Zig compiler, which is located at `./vendor/zig/zig.exe`. The filename is `zig.exe` so that it works as expected on Windows, but it still works on macOS/Linux (it just has a surprising file extension).
-
-We recommend adding `./build/debug` to your `$PATH` so that you can run `bun-debug` in your terminal:
-
-```sh
-$ bun-debug
-```
-
-## Running debug builds
-
-The `bd` package.json script compiles and runs a debug build of Bun, only printing the output of the build process if it fails.
-
-```sh
-$ bun bd <args>
-$ bun bd test foo.test.ts
-$ bun bd ./foo.ts
-```
-
-Bun generally takes about 2.5 minutes to compile a debug build when there are Zig changes. If your development workflow is "change one line, save, rebuild", you will spend too much time waiting for the build to finish. Instead:
-
-- 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.
-- 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
-
-Several code generation scripts are used during Bun's build process. These are run automatically when changes are made to certain files.
-
-In particular, these are:
-
-- `./src/codegen/generate-jssink.ts` -- Generates `build/debug/codegen/JSSink.cpp`, `build/debug/codegen/JSSink.h` which implement various classes for interfacing with `ReadableStream`. This is internally how `FileSink`, `ArrayBufferSink`, `"type": "direct"` streams and other code related to streams works.
-- `./src/codegen/generate-classes.ts` -- Generates `build/debug/codegen/ZigGeneratedClasses*`, which generates Zig & C++ bindings for JavaScriptCore classes implemented in Zig. In `**/*.classes.ts` files, we define the interfaces for various classes, methods, prototypes, getters/setters etc which the code generator reads to generate boilerplate code implementing the JavaScript objects in C++ and wiring them up to Zig
-- `./src/codegen/cppbind.ts` -- Generates automatic Zig bindings for C++ functions marked with `[[ZIG_EXPORT]]` attributes.
-- `./src/codegen/bundle-modules.ts` -- Bundles built-in modules like `node:fs`, `bun:ffi` into files we can include in the final binary. In development, these can be reloaded without rebuilding Zig (you still need to run `bun run build`, but it re-reads the transpiled files from disk afterwards). In release builds, these are embedded into the binary.
-- `./src/codegen/bundle-functions.ts` -- Bundles globally-accessible functions implemented in JavaScript/TypeScript like `ReadableStream`, `WritableStream`, and a handful more. These are used similarly to the builtin modules, but the output more closely aligns with what WebKit/Safari does for Safari's built-in functions so that we can copy-paste the implementations from WebKit as a starting point.
-
-## Modifying ESM modules
-
-Certain modules like `node:fs`, `node:stream`, `bun:sqlite`, and `ws` are implemented in JavaScript. These live in `src/js/{node,bun,thirdparty}` files and are pre-bundled using Bun.
-
-## Release build
-
-To compile a release build of Bun, run:
-
-```bash
-$ bun run build:release
-```
-
-The binary will be located at `./build/release/bun` and `./build/release/bun-profile`.
-
-### Download release build from pull requests
-
-To save you time spent building a release build locally, we provide a way to run release builds from pull requests. This is useful for manually testing changes in a release build before they are merged.
-
-To run a release build from a pull request, you can use the `bun-pr` npm package:
-
-```sh
-bunx bun-pr <pr-number>
-bunx bun-pr <branch-name>
-bunx bun-pr "https://github.com/oven-sh/bun/pull/1234566"
-bunx bun-pr --asan <pr-number> # Linux x64 only
-```
-
-This will download the release build from the pull request and add it to `$PATH` as `bun-${pr-number}`. You can then run the build with `bun-${pr-number}`.
-
-```sh
-bun-1234566 --version
-```
-
-This works by downloading the release build from the GitHub Actions artifacts on the linked pull request. You may need the `gh` CLI installed to authenticate with GitHub.
-
-## AddressSanitizer
-
-[AddressSanitizer](https://en.wikipedia.org/wiki/AddressSanitizer) helps find memory issues, and is enabled by default in debug builds of Bun on Linux and macOS. This includes the Zig code and all dependencies. It makes the Zig code take about 2x longer to build, if that's stopping you from being productive you can disable it by setting `-Denable_asan=$<IF:$<BOOL:${ENABLE_ASAN}>,true,false>` to `-Denable_asan=false` in the `cmake/targets/BuildBun.cmake` file, but generally we recommend batching your changes up between builds.
-
-To build a release build with Address Sanitizer, run:
-
-```bash
-$ bun run build:release:asan
-```
-
-In CI, we run our test suite with at least one target that is built with Address Sanitizer.
-
-## Building WebKit locally + Debug mode of JSC
-
-WebKit is not cloned by default (to save time and disk space). To clone and build WebKit locally, run:
-
-```bash
-# Clone WebKit into ./vendor/WebKit
-$ git clone https://github.com/oven-sh/WebKit vendor/WebKit
-
-# Check out the commit hash specified in `set(WEBKIT_VERSION <commit_hash>)` in cmake/tools/SetupWebKit.cmake
-$ git -C vendor/WebKit checkout <commit_hash>
-
-# Make a debug build of JSC. This will output build artifacts in ./vendor/WebKit/WebKitBuild/Debug
-# Optionally, you can use `bun run jsc:build` for a release build
-$ bun run jsc:build:debug && rm vendor/WebKit/WebKitBuild/Debug/JavaScriptCore/DerivedSources/inspector/InspectorProtocolObjects.h
-
-# After an initial run of `make jsc-debug`, you can rebuild JSC with:
-$ cmake --build vendor/WebKit/WebKitBuild/Debug --target jsc && rm vendor/WebKit/WebKitBuild/Debug/JavaScriptCore/DerivedSources/inspector/InspectorProtocolObjects.h
-
-# Build bun with the local JSC build
-$ bun run build:local
-```
-
-Using `bun run build:local` will build Bun in the `./build/debug-local` directory (instead of `./build/debug`), you'll have to change a couple of places to use this new directory:
-
-- The first line in [`src/js/builtins.d.ts`](/src/js/builtins.d.ts)
-- The `CompilationDatabase` line in [`.clangd` config](/.clangd) should be `CompilationDatabase: build/debug-local`
-- In [`build.zig`](/build.zig), the `codegen_path` option should be `build/debug-local/codegen` (instead of `build/debug/codegen`)
-- In [`.vscode/launch.json`](/.vscode/launch.json), many configurations use `./build/debug/`, change them as you see fit
-
-Note that the WebKit folder, including build artifacts, is 8GB+ in size.
-
-If you are using a JSC debug build and using VScode, make sure to run the `C/C++: Select a Configuration` command to configure intellisense to find the debug headers.
-
-Note that if you change make changes to our [WebKit fork](https://github.com/oven-sh/WebKit), you will also have to change [`SetupWebKit.cmake`](/cmake/tools/SetupWebKit.cmake) to point to the commit hash.
-
-## Troubleshooting
-
-### 'span' file not found on Ubuntu
-
-> ⚠️ Please note that the instructions below are specific to issues occurring on Ubuntu. It is unlikely that the same issues will occur on other Linux distributions.
-
-The Clang compiler typically uses the `libstdc++` C++ standard library by default. `libstdc++` is the default C++ Standard Library implementation provided by the GNU Compiler Collection (GCC). While Clang may link against the `libc++` library, this requires explicitly providing the `-stdlib` flag when running Clang.
-
-Bun relies on C++20 features like `std::span`, which are not available in GCC versions lower than 11. GCC 10 doesn't have all of the C++20 features implemented. As a result, running `make setup` may fail with the following error:
-
-```
-fatal error: 'span' file not found
-#include <span>
-         ^~~~~~
-```
-
-The issue may manifest when initially running `bun setup` as Clang being unable to compile a simple program:
-
-```
-The C++ compiler
-
-  "/usr/bin/clang++-19"
-
-is not able to compile a simple test program.
-```
-
-To fix the error, we need to update the GCC version to 11. To do this, we'll need to check if the latest version is available in the distribution's official repositories or use a third-party repository that provides GCC 11 packages. Here are general steps:
-
-```bash
-$ sudo apt update
-$ sudo apt install gcc-11 g++-11
-# If the above command fails with `Unable to locate package gcc-11` we need
-# to add the APT repository
-$ sudo add-apt-repository -y ppa:ubuntu-toolchain-r/test
-# Now run `apt install` again
-$ sudo apt install gcc-11 g++-11
-```
-
-Now, we need to set GCC 11 as the default compiler:
-
-```bash
-$ sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-11 100
-$ sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-11 100
-```
-
-### libarchive
-
-If you see an error on macOS when compiling `libarchive`, run:
-
-```bash
-$ brew install pkg-config
-```
-
-### macOS `library not found for -lSystem`
-
-If you see this error when compiling, run:
-
-```bash
-$ xcode-select --install
-```
-
-### Cannot find `libatomic.a`
-
-Bun defaults to linking `libatomic` statically, as not all systems have it. If you are building on a distro that does not have a static libatomic available, you can run the following command to enable dynamic linking:
-
-```bash
-$ bun run build -DUSE_STATIC_LIBATOMIC=OFF
-```
-
-The built version of Bun may not work on other systems if compiled this way.
-
-### ccache conflicts with building TinyCC on macOS
-
-If you run into issues with `ccache` when building TinyCC, try reinstalling ccache
-
-```bash
-brew uninstall ccache
-brew install ccache
-```
-
-## Using bun-debug
-
-- Disable logging: `BUN_DEBUG_QUIET_LOGS=1 bun-debug ...` (to disable all debug logging)
-- Enable logging for a specific zig scope: `BUN_DEBUG_EventLoop=1 bun-debug ...` (to allow `std.log.scoped(.EventLoop)`)
-- Bun transpiles every file it runs, to see the actual executed source in a debug build find it in `/tmp/bun-debug-src/...path/to/file`, for example the transpiled version of `/home/bun/index.ts` would be in `/tmp/bun-debug-src/home/bun/index.ts`

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

@@ -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

@@ -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"!