## Summary - Fixes #22596 where Nuxt crashes when building with rolldown-vite - Aligns Bun's NAPI GC safety checks with Node.js behavior by only enforcing them for experimental NAPI modules ## The Problem Bun was incorrectly enforcing GC safety checks (`NAPI_CHECK_ENV_NOT_IN_GC`) for ALL NAPI modules, regardless of version. This caused crashes when regular production NAPI modules called `napi_reference_unref` from finalizers, which is a common pattern in the ecosystem (e.g., rolldown-vite). The crash manifested as: ``` panic: Aborted - napi.h:306: napi_reference_unref ``` ## Root Cause: What We Did Wrong Our previous implementation always enforced the GC check for all NAPI modules: **Before (incorrect):** ```cpp // src/bun.js/bindings/napi.h:304-311 void checkGC() const { NAPI_RELEASE_ASSERT(!inGC(), "Attempted to call a non-GC-safe function inside a NAPI finalizer..."); // This was called for ALL modules, not just experimental ones } ``` This was overly restrictive and didn't match Node.js's behavior, causing legitimate use cases to crash. ## The Correct Solution: How Node.js Does It After investigating Node.js source code, we found that Node.js **only enforces GC safety checks for experimental NAPI modules**. Regular production modules are allowed to call functions like `napi_reference_unref` from finalizers for backward compatibility. ### Evidence from Node.js Source Code **1. The CheckGCAccess implementation** (`vendor/node/src/js_native_api_v8.h:132-143`): ```cpp void CheckGCAccess() { if (module_api_version == NAPI_VERSION_EXPERIMENTAL && in_gc_finalizer) { // Only fails if BOTH conditions are true: // 1. Module is experimental (version 2147483647) // 2. Currently in GC finalizer v8impl::OnFatalError(...); } } ``` **2. NAPI_VERSION_EXPERIMENTAL definition** (`vendor/node/src/js_native_api.h:9`): ```cpp #define NAPI_VERSION_EXPERIMENTAL 2147483647 // INT_MAX ``` **3. How it's used in napi_reference_unref** (`vendor/node/src/js_native_api_v8.cc:2814-2819`): ```cpp napi_status NAPI_CDECL napi_reference_unref(napi_env env, napi_ref ref, uint32_t* result) { CHECK_ENV_NOT_IN_GC(env); // This check only fails for experimental modules // ... rest of implementation } ``` ## Our Fix: Match Node.js Behavior Exactly **After (correct):** ```cpp // src/bun.js/bindings/napi.h:304-315 void checkGC() const { // Only enforce GC checks for experimental NAPI versions, matching Node.js behavior // See: https://github.com/nodejs/node/blob/main/src/js_native_api_v8.h#L132-L143 if (m_napiModule.nm_version == NAPI_VERSION_EXPERIMENTAL) { NAPI_RELEASE_ASSERT(!inGC(), ...); } // Regular modules (version <= 8) can call napi_reference_unref from finalizers } ``` This change means: - **Regular NAPI modules** (version 8 and below): ✅ Can call `napi_reference_unref` from finalizers - **Experimental NAPI modules** (version 2147483647): ❌ Cannot call `napi_reference_unref` from finalizers ## Why This Matters Many existing NAPI modules in the ecosystem were written before the stricter GC rules and rely on being able to call functions like `napi_reference_unref` from finalizers. Node.js maintains backward compatibility by only enforcing the stricter rules for modules that explicitly opt into experimental features. By not matching this behavior, Bun was breaking existing packages that work fine in Node.js. ## Test Plan Added comprehensive tests that verify both scenarios: ### 1. test_reference_unref_in_finalizer.c (Regular Module) - Uses default NAPI version (8) - Creates 100 objects with finalizers that call `napi_reference_unref` - **Expected:** Works without crashing - **Result:** ✅ Passes with both Node.js and Bun (with fix) ### 2. test_reference_unref_in_finalizer_experimental.c (Experimental Module) - Uses `NAPI_VERSION_EXPERIMENTAL` (2147483647) - Creates objects with finalizers that call `napi_reference_unref` - **Expected:** Crashes with GC safety assertion - **Result:** ✅ Correctly fails with both Node.js and Bun (with fix) ## Verification The tests prove our fix is correct: ```bash # Regular module - should work $ bun-debug --expose-gc main.js test_reference_unref_in_finalizer '[]' ✅ SUCCESS: napi_reference_unref worked in finalizers without crashing # Experimental module - should fail $ bun-debug --expose-gc main.js test_reference_unref_in_finalizer_experimental '[]' ✅ ASSERTION FAILED: Attempted to call a non-GC-safe function inside a NAPI finalizer ``` Both behaviors now match Node.js exactly. ## Impact This fix: 1. Resolves crashes with rolldown-vite and similar packages 2. Maintains backward compatibility with the Node.js ecosystem 3. Still enforces safety for experimental NAPI features 4. Aligns Bun's behavior with Node.js's intentional design decisions 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude Bot <claude-bot@bun.sh> Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com> Co-authored-by: Jarred Sumner <jarred@jarredsumner.com> Co-authored-by: Zack Radisic <zack@theradisic.com>
Bun
Read the docs →
What is Bun?
Bun is an all-in-one toolkit for JavaScript and TypeScript apps. It ships as a single executable called bun.
At its core is the Bun runtime, a fast JavaScript runtime designed as a drop-in replacement for Node.js. It's written in Zig and powered by JavaScriptCore under the hood, dramatically reducing startup times and memory usage.
bun run index.tsx # TS and JSX supported out-of-the-box
The bun command-line tool also implements a test runner, script runner, and Node.js-compatible package manager. Instead of 1,000 node_modules for development, you only need bun. Bun's built-in tools are significantly faster than existing options and usable in existing Node.js projects with little to no changes.
bun test # run tests
bun run start # run the `start` script in `package.json`
bun install <pkg> # install a package
bunx cowsay 'Hello, world!' # execute a package
Install
Bun supports Linux (x64 & arm64), macOS (x64 & Apple Silicon) and Windows (x64).
Linux users — Kernel version 5.6 or higher is strongly recommended, but the minimum is 5.1.
x64 users — if you see "illegal instruction" or similar errors, check our CPU requirements
# with install script (recommended)
curl -fsSL https://bun.com/install | bash
# on windows
powershell -c "irm bun.com/install.ps1 | iex"
# with npm
npm install -g bun
# with Homebrew
brew tap oven-sh/bun
brew install bun
# with Docker
docker pull oven/bun
docker run --rm --init --ulimit memlock=-1:-1 oven/bun
Upgrade
To upgrade to the latest version of Bun, run:
bun upgrade
Bun automatically releases a canary build on every commit to main. To upgrade to the latest canary build, run:
bun upgrade --canary
Quick links
-
Intro
-
Templating
-
CLI
-
Runtime
-
Package manager
-
Bundler
-
Test runner
-
Package runner
-
API
- HTTP server (
Bun.serve) - WebSockets
- Workers
- Binary data
- Streams
- File I/O (
Bun.file) - import.meta
- SQLite (
bun:sqlite) - PostgreSQL (
Bun.sql) - Redis (
Bun.redis) - S3 Client (
Bun.s3) - FileSystemRouter
- TCP sockets
- UDP sockets
- Globals
- $ Shell
- Child processes (spawn)
- Transpiler (
Bun.Transpiler) - Hashing
- Colors (
Bun.color) - Console
- FFI (
bun:ffi) - C Compiler (
bun:fficc) - HTMLRewriter
- Testing (
bun:test) - Cookies (
Bun.Cookie) - Utils
- Node-API
- Glob (
Bun.Glob) - Semver (
Bun.semver) - DNS
- fetch API extensions
- HTTP server (
Guides
-
Binary
- Convert a Blob to a string
- Convert a Buffer to a blob
- Convert a Blob to a DataView
- Convert a Buffer to a string
- Convert a Blob to a ReadableStream
- Convert a Blob to a Uint8Array
- Convert a DataView to a string
- Convert a Uint8Array to a Blob
- Convert a Blob to an ArrayBuffer
- Convert an ArrayBuffer to a Blob
- Convert a Buffer to a Uint8Array
- Convert a Uint8Array to a Buffer
- Convert a Uint8Array to a string
- Convert a Buffer to an ArrayBuffer
- Convert an ArrayBuffer to a Buffer
- Convert an ArrayBuffer to a string
- Convert a Uint8Array to a DataView
- Convert a Buffer to a ReadableStream
- Convert a Uint8Array to an ArrayBuffer
- Convert an ArrayBuffer to a Uint8Array
- Convert an ArrayBuffer to an array of numbers
- Convert a Uint8Array to a ReadableStream
-
Ecosystem
- Use React and JSX
- Use EdgeDB with Bun
- Use Prisma with Bun
- Add Sentry to a Bun app
- Create a Discord bot
- Run Bun as a daemon with PM2
- Use Drizzle ORM with Bun
- Build an app with Nuxt and Bun
- Build an app with Qwik and Bun
- Build an app with Astro and Bun
- Build an app with Remix and Bun
- Build a frontend using Vite and Bun
- Build an app with Next.js and Bun
- Run Bun as a daemon with systemd
- Deploy a Bun application on Render
- Build an HTTP server using Hono and Bun
- Build an app with SvelteKit and Bun
- Build an app with SolidStart and Bun
- Build an HTTP server using Elysia and Bun
- Build an HTTP server using StricJS and Bun
- Containerize a Bun application with Docker
- Build an HTTP server using Express and Bun
- Use Neon Postgres through Drizzle ORM
- Server-side render (SSR) a React component
- Read and write data to MongoDB using Mongoose and Bun
- Use Neon's Serverless Postgres with Bun
-
HTMLRewriter
-
HTTP
- Hot reload an HTTP server
- Common HTTP server usage
- Write a simple HTTP server
- Configure TLS on an HTTP server
- Send an HTTP request using fetch
- Proxy HTTP requests using fetch()
- Start a cluster of HTTP servers
- Stream a file as an HTTP Response
- fetch with unix domain sockets in Bun
- Upload files via HTTP using FormData
- Streaming HTTP Server with Async Iterators
- Streaming HTTP Server with Node.js Streams
-
Install
- Add a dependency
- Add a Git dependency
- Add a peer dependency
- Add a trusted dependency
- Add a development dependency
- Add a tarball dependency
- Add an optional dependency
- Generate a yarn-compatible lockfile
- Configuring a monorepo using workspaces
- Install a package under a different name
- Install dependencies with Bun in GitHub Actions
- Using bun install with Artifactory
- Configure git to diff Bun's lockb lockfile
- Override the default npm registry for bun install
- Using bun install with an Azure Artifacts npm registry
- Migrate from npm install to bun install
- Configure a private registry for an organization scope with bun install
-
Process
-
Read file
-
Runtime
- Delete files
- Run a Shell Command
- Import a JSON file
- Import a TOML file
- Set a time zone in Bun
- Set environment variables
- Re-map import paths
- Delete directories
- Read environment variables
- Import a HTML file as text
- Install and run Bun in GitHub Actions
- Debugging Bun with the web debugger
- Install TypeScript declarations for Bun
- Debugging Bun with the VS Code extension
- Inspect memory usage using V8 heap snapshots
- Define and replace static globals & constants
- Codesign a single-file JavaScript executable on macOS
-
Streams
- Convert a ReadableStream to JSON
- Convert a ReadableStream to a Blob
- Convert a ReadableStream to a Buffer
- Convert a ReadableStream to a string
- Convert a ReadableStream to a Uint8Array
- Convert a ReadableStream to an array of chunks
- Convert a Node.js Readable to JSON
- Convert a ReadableStream to an ArrayBuffer
- Convert a Node.js Readable to a Blob
- Convert a Node.js Readable to a string
- Convert a Node.js Readable to an Uint8Array
- Convert a Node.js Readable to an ArrayBuffer
-
Test
- Spy on methods in
bun test - Bail early with the Bun test runner
- Mock functions in
bun test - Run tests in watch mode with Bun
- Use snapshot testing in
bun test - Skip tests with the Bun test runner
- Using Testing Library with Bun
- Update snapshots in
bun test - Run your tests with the Bun test runner
- Set the system time in Bun's test runner
- Set a per-test timeout with the Bun test runner
- Migrate from Jest to Bun's test runner
- Write browser DOM tests with Bun and happy-dom
- Mark a test as a "todo" with the Bun test runner
- Re-run tests multiple times with the Bun test runner
- Generate code coverage reports with the Bun test runner
- import, require, and test Svelte components with bun test
- Set a code coverage threshold with the Bun test runner
- Spy on methods in
-
Util
- Generate a UUID
- Hash a password
- Escape an HTML string
- Get the current Bun version
- Encode and decode base64 strings
- Compress and decompress data with gzip
- Sleep for a fixed number of milliseconds
- Detect when code is executed with Bun
- Check if two objects are deeply equal
- Compress and decompress data with DEFLATE
- Get the absolute path to the current entrypoint
- Get the directory of the current file
- Check if the current file is the entrypoint
- Get the file name of the current file
- Convert a file URL to an absolute path
- Convert an absolute path to a file URL
- Get the absolute path of the current file
- Get the path to an executable bin file
-
WebSocket
-
Write file
Contributing
Refer to the Project > Contributing guide to start contributing to Bun.
License
Refer to the Project > License page for information about Bun's licensing.