Bun Runtime
Execute JavaScript/TypeScript files, package.json scripts, and executable packages with Bun's fast runtime.
The Bun Runtime is designed to start fast and run fast.
Bun uses the JavaScriptCore engine, developed by Apple for Safari. JavaScriptCore usually starts and runs faster than V8, the engine used by Node.js and Chromium-based browsers. Bun's transpiler and runtime are written in Rust. On Linux, Bun starts 4x faster than Node.js.
| Command | Time |
|---|---|
bun hello.js | 5.2ms |
node hello.js | 25.1ms |
The benchmark runs a Hello World script on Linux.
Run a file
Use bun run to execute a source file.
bun run index.js
Bun supports TypeScript and JSX with no configuration. Bun transpiles every file on the fly with its native transpiler before running it.
bun run index.js
bun run index.jsx
bun run index.ts
bun run index.tsx
Alternatively, you can omit the run keyword and use the "naked" command; it behaves identically.
bun index.tsx
bun index.js
--watch
To run a file in watch mode, use the --watch flag.
bun --watch run index.tsx
--check
Bun runs TypeScript files without checking their types. To type check a file and everything it imports before Bun runs it, use the --check flag.
bun --check index.tsx
If there is a type error, Bun prints it, exits with code 1, and does not run the file. See bun check.
Run a package.json script
bun [bun flags] run <script> [script flags]
Your package.json can define named "scripts" that correspond to shell commands.
{
// ... other fields
"scripts": {
"clean": "rm -rf dist && echo 'Done.'",
"dev": "bun server.ts"
}
}
Use bun run <script> to execute these scripts.
bun run clean
rm -rf dist && echo 'Done.'
Done.
Bun executes the script command in a subshell. On Linux & macOS, it checks for the following shells in order, using the first one it finds: bash, sh, zsh. On Windows, it uses the Bun Shell to support bash-like syntax and many common commands.
You can also run scripts with the shorter command bun <script>. If a built-in bun command has the same name, the built-in command takes precedence; use the explicit bun run <script> to run your package script instead.
bun run dev
To see a list of available scripts, run bun run without any arguments.
bun run
...
package.json scripts (2 found):
$ bun run clean
rm -rf dist && echo 'Done.'
$ bun run dev
bun server.ts
Bun respects lifecycle hooks. For instance, bun run clean runs preclean and postclean, if defined. If the pre<script> fails, Bun does not run the script itself.
--bun
It's common for package.json scripts to reference locally-installed CLIs like vite or next. These CLIs are often JavaScript files marked with a shebang to indicate that they should be executed with node.
#!/usr/bin/env node
// do stuff
By default, Bun respects this shebang and executes the script with node. The --bun flag overrides it: the CLI runs with Bun instead of Node.js.
bun run --bun vite
Filtering
In a monorepo, the --filter argument runs a script in many packages at once.
bun run --filter <pattern> <script> executes <script> in every package selected by <pattern>. The pattern can be a package name glob, a ./path, a {dir} directory or a dependency relation like foo....
For example, if you have subdirectories containing packages named foo, bar and baz, running
bun run --filter 'ba*' <script>
executes <script> in both bar and baz, but not in foo.
See --filter.
bun run - to pipe code from stdin
bun run - reads JavaScript, TypeScript, TSX, or JSX from stdin and executes it without writing to a temporary file first.
echo "console.log('Hello')" | bun run -
Hello
You can also use bun run - to redirect files into Bun. For example, to run a .js file as if it were a .ts file:
echo "console.log!('This is TypeScript!' as any)" > secretly-typescript.js
bun run - < secretly-typescript.js
This is TypeScript!
bun run - treats all input as TypeScript with JSX support.
bun run --console-depth
Control the depth of object inspection in console output with the --console-depth flag.
bun --console-depth 5 run index.tsx
--console-depth sets how deeply Bun displays nested objects in console.log() output. The default depth is 2. Higher values show more nested properties but may produce verbose output for complex objects.
const nested = { a: { b: { c: { d: "deep" } } } };
console.log(nested);
// With --console-depth 2 (default): { a: { b: { c: [Object] } } }
// With --console-depth 4: { a: { b: { c: { d: 'deep' } } } }
bun run --smol
In memory-constrained environments, use the --smol flag to reduce memory usage at a cost to performance.
bun --smol run index.tsx
--smol makes the garbage collector run more frequently, which can slow down execution. Bun adjusts the garbage collector's heap size based on the available memory (accounting for cgroups and other memory limits) with and without the --smol flag. The flag is therefore mostly useful when you want the heap to grow more slowly.
Resolution order
Bun always executes absolute paths and paths starting with ./ or .\\ as source files. Unless you use bun run, a name with an allowed extension resolves to the file rather than a package.json script.
When a package.json script and a file have the same name, bun run prefers the script. The full resolution order is:
package.jsonscripts:bun run build- Source files:
bun run src/main.js - Binaries from project packages:
bun add eslint && bun run eslint - (
bun runonly) System commands:bun run ls
CLI Usage
bun run <file or script>
General Execution Options
--silentbooleanDon't print the script command
--if-presentbooleanExit without an error if the entrypoint does not exist
--evalstringEvaluate argument as a script. Alias: -e
--printstringEvaluate argument as a script and print the result. Alias: -p
--helpbooleanDisplay this menu and exit. Alias: -h
Workspace Management
--elide-linesnumberdefault 0Truncate each script's output to its last N lines when using --filter. Default 0 shows all lines
--filterstringRun a script in all workspace packages matching the pattern. Alias: -F
--workspacesbooleanRun a script in all workspace packages (from the workspaces field in package.json)
--parallelbooleanRun multiple scripts or workspace scripts concurrently with prefixed output
--sequentialbooleanRun multiple scripts or workspace scripts one after another with prefixed output
--no-exit-on-errorbooleanWhen using --parallel or --sequential, continue running other scripts when one fails
Runtime & Process Control
--bunbooleanForce a script or package to use Bun's runtime instead of Node.js (via symlinking node). Alias: -b
--shellstringControl the shell used for package.json scripts. Supports either bun or system
--interactivebooleanOpen the Node.js-compatible REPL (node:repl). When combined with -e, starts the REPL and
then evaluates the script. Under --interactive, -e is raw JavaScript (matching
node -i -e). Use bun repl for TypeScript. Distinct from bun repl, which is
Bun's native REPL.
--smolbooleanUse less memory, but run garbage collection more often
--expose-gcbooleanExpose gc() on the global object. Has no effect on Bun.gc()
--no-deprecationbooleanSilence all deprecation warnings
--throw-deprecationbooleanThrow deprecation warnings as errors
--titlestringSet the process title
--zero-fill-buffersbooleanForce Buffer.allocUnsafe(size) to be zero-filled
--no-addonsbooleanThrow an error if process.dlopen or bun:ffi cc() is called, and disable export
condition node-addons
--no-ffi-ccbooleanThrow an error if bun:ffi cc() is called (disables the C compiler)
--unhandled-rejectionsstringOne of strict, throw, warn, none, or
warn-with-error-code
--console-depthnumberdefault 2Set the default depth for console.log object inspection (default: 2)
Development Workflow
--checkbooleanType check before running. Nothing runs if there are type errors. See bun check
--watchbooleanAutomatically restart the process on file change
--watch-kill-signalstringdefault SIGTERMSignal whose handlers run when --watch restarts the process
--hotbooleanEnable auto reload in the Bun runtime, test runner, or bundler
--no-clear-screenbooleanDisable clearing the terminal screen on reload when --hot or --watch is enabled
Debugging
--inspectstringActivate Bun's debugger
--inspect-waitstringActivate Bun's debugger, wait for a connection before executing
--inspect-brkstringActivate Bun's debugger, set breakpoint on first line of code and wait
Dependency & Module Resolution
--preloadstringImport a module before Bun loads other modules. Alias: -r
--requirestringAlias of --preload, for Node.js compatibility
--importstringAlias of --preload, for Node.js compatibility
--no-installbooleanDisable auto install in the Bun runtime
--installstringdefault autoConfigure auto-install behavior. One of auto (default, auto-installs when no node_modules),
fallback (missing packages only), force (always)
-ibooleanAuto-install dependencies during execution. Equivalent to --install=fallback
--prefer-offlinebooleanSkip staleness checks for packages in the Bun runtime and resolve from disk
--prefer-latestbooleanUse the latest matching versions of packages in the Bun runtime, always checking npm
--conditionsstringPass custom conditions to resolve
--main-fieldsstringMain fields to lookup in package.json
--preserve-symlinksbooleanPreserve symlinks when resolving files
--preserve-symlinks-mainbooleanPreserve symlinks when resolving the main entry point
--extension-orderstringdefault .tsx,.ts,.jsx,.cts,.cjs,.js,.mjs,.mts,.json,.nodeDefaults to: .tsx,.ts,.jsx,.cts,.cjs,.js,.mjs,.mts,.json,.node
Transpilation & Language Features
--tsconfig-overridestringSpecify custom tsconfig.json. Default $cwd/tsconfig.json
--definestringSubstitute K:V while parsing, e.g. --define process.env.NODE_ENV:"development". Bun parses values as
JSON. Alias: -d
--dropstringRemove function calls, e.g. --drop=console removes all console.* calls
--loaderstringParse files with .ext:loader, e.g. --loader .js:jsx. Valid loaders: js,
jsx, ts, tsx, json, toml, text,
file, wasm, napi. Alias: -l
--no-macrosbooleanDisable macro execution in the bundler, transpiler and runtime
--jsx-factorystringChanges the function called when compiling JSX elements using the classic JSX runtime
--jsx-fragmentstringChanges the function called when compiling JSX fragments
--jsx-import-sourcestringdefault reactDeclares the module specifier used to import the jsx and jsxs factory functions. Default: react
--jsx-runtimestringdefault automaticautomatic (default) or classic
--jsx-side-effectsbooleanTreat JSX elements as having side effects (disable pure annotations)
--ignore-dce-annotationsbooleanIgnore tree-shaking annotations such as @PURE
Networking & Security
--portnumberSet the default port for Bun.serve
--fetch-preconnectstringPreconnect to a URL while code is loading
--max-http-header-sizenumberdefault 16384Set the maximum size of HTTP headers in bytes. Default is 16KiB
--dns-result-orderstringdefault verbatimSet the default order of DNS lookup results. Valid orders: verbatim (default), ipv4first,
ipv6first
--use-system-cabooleanUse the system's trusted certificate authorities
--use-openssl-cabooleanUse OpenSSL's default CA store instead of the bundled one
--use-bundled-cabooleanUse bundled CA store
--redis-preconnectbooleanPreconnect to $REDIS_URL at startup
--sql-preconnectbooleanPreconnect to PostgreSQL at startup
--user-agentstringSet the default User-Agent header for HTTP requests
Global Configuration & Context
--env-filestringLoad environment variables from the specified file(s)
--cwdstringAbsolute path to resolve files & entrypoints from. This only changes the process' cwd
--configstringSpecify path to Bun config file. Default $cwd/bunfig.toml. Alias: -c
Examples
Run a JavaScript or TypeScript file:
bun run ./index.js
bun run ./index.tsx
Run a package.json script:
bun run dev
bun run lint