Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
143 commits
Select commit Hold shift + click to select a range
d008311
docs(guides): tighten index description
alii Jun 29, 2026
c5ece27
docs(typescript): tighten prose
alii Jun 29, 2026
8b459da
docs: run prettier
alii Jun 29, 2026
51cca19
docs(bundler): tighten minifier prose
alii Jun 29, 2026
d42b3a7
docs(fullstack): tighten prose
alii Jun 29, 2026
88b8519
docs(bytecode): tighten prose
alii Jun 29, 2026
4ec05a3
docs(bundler): tighten esbuild migration prose
alii Jun 29, 2026
cd56e2f
docs(guides): tighten vite guide prose
alii Jun 29, 2026
5e1dfd8
docs(guides/binary): tighten prose, fix typos
alii Jun 29, 2026
6fdb345
docs(bundler): tighten plugins and standalone-html prose
alii Jun 29, 2026
29c6f25
docs(bundler): tighten executables prose
alii Jun 29, 2026
63bf2d3
docs(guides): tighten html-rewriter prose
alii Jun 29, 2026
f3554d5
docs(bundler): tighten css page prose
alii Jun 29, 2026
c7313b1
docs(bundler): tighten hot-reloading and html-static prose
alii Jun 29, 2026
961bb01
docs(bundler): tighten loaders and macros prose
alii Jun 29, 2026
1e215dc
docs(guides): tighten ecosystem guide prose
alii Jun 29, 2026
a0f8371
docs: tighten intro, install, quickstart prose
alii Jun 29, 2026
96fb660
docs(guides/install): tighten workspaces and yarnlock prose
alii Jun 29, 2026
54bcb1f
docs(guides): tighten deployment guide prose
alii Jun 29, 2026
73929ff
docs(guides): tighten ecosystem guide prose
alii Jun 29, 2026
8955120
docs(bundler): tighten prose
alii Jun 29, 2026
0dd517b
docs(guides): tighten tanstack-start and upstash prose
alii Jun 29, 2026
2bf38e7
docs(guides/streams): tighten prose
alii Jun 29, 2026
4e0c8af
docs(guides/websocket): tighten prose
alii Jun 29, 2026
1d0c0b1
docs(guides/process): tighten prose
alii Jun 29, 2026
ab04873
docs(guides/http): tighten prose
alii Jun 29, 2026
47b316f
docs(guides/runtime): tighten prose
alii Jun 29, 2026
6c2e802
docs(guides): tighten write-file prose
alii Jun 29, 2026
6cad07b
docs(test): tighten guide prose
alii Jun 29, 2026
1f6195a
docs(pm): tighten update and why prose
alii Jun 29, 2026
f809a24
docs(guides): tighten runtime guide prose
alii Jun 29, 2026
e7587a2
docs(guides/util): tighten prose
alii Jun 29, 2026
fee5d0b
docs(guides/ecosystem): tighten prose
alii Jun 29, 2026
7396d75
docs(guides/install): tighten prose
alii Jun 29, 2026
65f6451
docs(guides/test): tighten prose
alii Jun 29, 2026
21adf3f
docs(pm): tighten cli prose
alii Jun 29, 2026
95d7e88
docs(pm): tighten prose
alii Jun 29, 2026
79a933a
docs(runtime): tighten archive and auto-install prose
alii Jun 29, 2026
8e17adc
docs(pm): tighten prose
alii Jun 29, 2026
b7a2278
docs(pm): tighten cli install/add/audit/info prose
alii Jun 29, 2026
491e3f4
docs(runtime): tighten color, console, cookies prose
alii Jun 29, 2026
da3f1d7
docs(runtime): tighten spawn and cc prose
alii Jun 29, 2026
1de535f
docs(project): tighten prose
alii Jun 29, 2026
489eafa
docs(binary-data): tighten prose
alii Jun 29, 2026
8ab93aa
docs(project): tighten prose
alii Jun 29, 2026
ca02cdb
docs(runtime): tighten file io and loader prose
alii Jun 29, 2026
439d11e
docs(runtime): tighten env vars and ffi prose
alii Jun 29, 2026
22314cd
docs(runtime): tighten bunfig and bun-apis prose
alii Jun 29, 2026
ec43e02
docs(runtime): tighten glob, hashing, html-rewriter prose
alii Jun 29, 2026
bf5efbe
docs(runtime): tighten cron, csrf, debugger prose
alii Jun 29, 2026
9af9c34
docs(redis,repl): tighten prose
alii Jun 29, 2026
ff30c8d
docs(runtime): tighten toml, transpiler, typescript prose
alii Jun 29, 2026
2e2d6f5
docs(runtime): tighten prose
alii Jun 29, 2026
4d790ed
docs(utils): tighten prose
alii Jun 29, 2026
3aaf9d2
docs(s3): tighten prose
alii Jun 29, 2026
2bf3a1b
docs(http): tighten routing, cookies, error prose
alii Jun 29, 2026
25343f8
docs(runtime): tighten node-api, compat, plugins prose
alii Jun 29, 2026
ec39413
docs(runtime): tighten secrets, semver, shell prose
alii Jun 29, 2026
0d6ead4
docs(websockets): tighten prose
alii Jun 29, 2026
5cd7149
docs(runtime): tighten sqlite and streams prose
alii Jun 29, 2026
730f7d1
docs(udp): tighten prose
alii Jun 29, 2026
77da03e
docs(http): tighten server and tls prose
alii Jun 29, 2026
b0174d9
docs(sql): tighten prose
alii Jun 29, 2026
95314c4
docs(test): tighten cli flag prose
alii Jun 29, 2026
b75269b
docs(runtime): tighten prose
alii Jun 29, 2026
fda35e1
docs(runtime): tighten workers and yaml prose
alii Jun 29, 2026
c902907
docs(cli): tighten flag snippet prose
alii Jun 29, 2026
68dff0c
docs(runtime): tighten watch-mode, web-apis, webview prose
alii Jun 29, 2026
1419a51
types(bundle): tighten jsdoc
alii Jun 29, 2026
6817d96
docs(cli): tighten publish and run flag prose
alii Jun 29, 2026
162a572
docs(templating): tighten create and init prose
alii Jun 29, 2026
c508415
types(fetch): tighten jsdoc
alii Jun 29, 2026
2392bb7
docs(test): tighten writing-tests prose
alii Jun 29, 2026
9bd7474
types(devserver): tighten hmr jsdoc
alii Jun 29, 2026
9e75920
types(html-rewriter): tighten jsdoc
alii Jun 29, 2026
c7bc546
docs(networking): tighten prose
alii Jun 29, 2026
3107ca6
docs(test): tighten coverage and configuration prose
alii Jun 29, 2026
0680a13
docs(test): tighten prose
alii Jun 29, 2026
0656ad6
types(jsx): document JSX.Element
alii Jun 29, 2026
418e772
docs(test): tighten reporter, runtime, snapshot prose
alii Jun 29, 2026
0149819
types(jsc): tighten jsdoc
alii Jun 29, 2026
863cf9f
types(overrides): tighten jsdoc
alii Jun 29, 2026
0c7a92e
types(security): tighten scanner jsdoc
alii Jun 29, 2026
cfb1019
types(test-globals): tighten header comment
alii Jun 29, 2026
4556d8e
types(bun): tighten jsdoc on core types and utils
alii Jun 29, 2026
e7da166
types(shell): tighten jsdoc
alii Jun 29, 2026
2d578fc
types(s3): tighten jsdoc prose
alii Jun 29, 2026
541e695
types(ffi): tighten jsdoc
alii Jun 29, 2026
84e6509
types(sqlite): tighten jsdoc prose
alii Jun 29, 2026
82ab611
types(globals): tighten jsdoc
alii Jun 29, 2026
80c8d4d
types(redis): tighten jsdoc prose
alii Jun 29, 2026
db2320e
types(sql): tighten jsdoc
alii Jun 29, 2026
ba60435
types(serve): clean up jsdoc
alii Jun 29, 2026
269ebf2
types(test): tighten jsdoc prose
alii Jun 29, 2026
4002780
docs(bytecode): restore instruction stream detail
alii Jun 29, 2026
f7e801d
docs(bundler): drop unsupported claim from esbuild intro
alii Jun 29, 2026
a570641
docs(executables): restore hedge on baseline-build note
alii Jun 29, 2026
7244bb5
docs(guides): restore compatibility hedge in express guide
alii Jun 29, 2026
a9ecf64
types(redis): tighten redis const jsdoc
alii Jun 29, 2026
1fccc69
docs(index): restore section-structure note
alii Jun 29, 2026
6c92085
docs(css): vary sentence structure
alii Jun 29, 2026
6978efb
docs(guides): keep zero-config claim in mongoose guide
alii Jun 29, 2026
f0483dc
docs(guides): keep deployment feature lists non-exhaustive
alii Jun 29, 2026
70998a3
docs(html-static): restore watch mode info callout
alii Jun 29, 2026
711ab70
docs(http): restore sse generator recommendation
alii Jun 29, 2026
96ba6ff
docs(install): fix add-git tarball note grammar
alii Jun 29, 2026
511e114
docs(pm): restore qualifiers in lifecycle and workspaces
alii Jun 29, 2026
a33d30d
docs(auto-install): fix cache list grammar, restore qualifier
alii Jun 29, 2026
b6da477
docs(project): restore PATH tip and open-ended tool list
alii Jun 29, 2026
cbea4fd
docs(bun-apis): fix overclaim about table links
alii Jun 29, 2026
dcff0c3
docs(file-types): restore loader speed claims and json5 list
alii Jun 29, 2026
b93ce9f
docs(guides/util): drop boilerplate link tails
alii Jun 29, 2026
4500766
docs(project): restore original phrasing in two spots
alii Jun 29, 2026
1846b66
docs(redis): keep url format list open-ended
alii Jun 29, 2026
0343ed2
docs(runtime): smooth out transpiler sentence
alii Jun 29, 2026
bffcdb0
docs(binary-data): narrow buffer table contrast
alii Jun 29, 2026
c0baee4
docs(shell): restore concurrency comparison wording
alii Jun 29, 2026
005f761
docs(s3): drop added gloss on virtual hosted-style
alii Jun 29, 2026
8315071
types(test): clean up matcher and mock jsdoc
alii Jun 29, 2026
6760c39
docs(runtime): restore sqlite, streams wording
alii Jun 29, 2026
0a4a5b4
docs(runtime): restore dropped facts
alii Jun 29, 2026
08128f0
docs(test): keep sourcemap caveat firm
alii Jun 29, 2026
c450304
docs(pm): finish cli prose pass, restore dropped qualifiers
alii Jun 29, 2026
0789368
types(bun): tighten jsdoc for yaml, markdown, json5, write
alii Jun 29, 2026
efccf35
docs(webview): name list items instead of etc., drop via
alii Jun 29, 2026
f05a37a
docs(test): keep original junit adoption claim
alii Jun 29, 2026
935c786
types(security): restore dropped qualifiers in advisory jsdoc
alii Jun 29, 2026
3577b31
types(globals): tighten jsdoc
alii Jun 29, 2026
f8972fb
types(serve): keep hostname/port note a recommendation
alii Jun 29, 2026
683a23c
docs(sql): fix prose regressions and leftover tics
alii Jun 29, 2026
d349b2e
types(sql): finish jsdoc cleanup pass
alii Jun 29, 2026
8cde7f8
types(ffi): fix ptr cross-ref and tinycc phrasing
alii Jun 29, 2026
f82ce96
types(redis): fix copy-paste jsdoc on overloads
alii Jun 29, 2026
754d9dc
types(globals): tighten fetch jsdoc
alii Jun 29, 2026
1a3080e
types(test): finish jsdoc prose pass on matchers
alii Jun 29, 2026
4fc4916
types(bun): tighten jsdoc for password, secrets, build output
alii Jun 29, 2026
0328d9c
types(bun): tighten jsdoc prose
alii Jun 29, 2026
af56a3a
types(bun): tighten crypto, zlib, plugin, socket jsdoc
alii Jun 29, 2026
ea8e4cc
types(socket,spawn): tighten jsdoc
alii Jun 29, 2026
b2c105b
types(bun): tighten spawn, terminal, router jsdoc
alii Jun 29, 2026
715b6c7
types(bun): tidy glob, webview, archive jsdoc
alii Jun 29, 2026
6ef0500
types(bun): tighten archive, uuid, cookie jsdoc
alii Jun 29, 2026
fe890aa
types(bun): finish present-tense pass, restore dropped facts
alii Jun 29, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
4 changes: 2 additions & 2 deletions docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,8 @@ Run the development server:
mint dev
```

The site will be available at `http://localhost:3000`.
The site is served at `http://localhost:3000`.

## Contributing

Contributions are welcome! Please open an issue or submit a pull request.
Contributions are welcome. Open an issue or submit a pull request.
66 changes: 32 additions & 34 deletions docs/bundler/bytecode.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,19 +3,19 @@ title: Bytecode Caching
description: Speed up JavaScript execution with bytecode caching in Bun's bundler
---

Bytecode caching is a build-time optimization that dramatically improves application startup time by pre-compiling your JavaScript to bytecode. For example, when compiling TypeScript's `tsc` with bytecode enabled, startup time improves by **2x**.
Bytecode caching is a build-time optimization that improves startup time by pre-compiling your JavaScript to bytecode. For example, when compiling TypeScript's `tsc` with bytecode enabled, startup time improves by **2x**.

## Usage

### Basic usage (CommonJS)

Enable bytecode caching with the `--bytecode` flag. Without `--format`, this defaults to CommonJS:
Enable bytecode caching with the `--bytecode` flag. Without `--format`, the output format defaults to CommonJS:

```bash terminal icon="terminal"
bun build ./index.ts --target=bun --bytecode --outdir=./dist
```

This generates two files:
The build writes two files:

- `dist/index.js` - Your bundled JavaScript (CommonJS)
- `dist/index.jsc` - The bytecode cache file
Expand All @@ -28,7 +28,7 @@ bun ./dist/index.js # Automatically uses index.jsc

### With standalone executables

When creating executables with `--compile`, bytecode is embedded into the binary. Both ESM and CommonJS formats are supported:
When you create an executable with `--compile`, Bun embeds the bytecode in the binary. Both ESM and CommonJS work:

```bash terminal icon="terminal"
# ESM (requires --compile)
Expand All @@ -38,17 +38,17 @@ bun build ./cli.ts --compile --bytecode --format=esm --outfile=mycli
bun build ./cli.ts --compile --bytecode --outfile=mycli
```

The resulting executable contains both the code and bytecode, giving you maximum performance in a single file.
The resulting executable contains both the code and the bytecode.

### ESM bytecode

ESM bytecode requires `--compile` because Bun embeds module metadata (import/export information) in the compiled binary. This metadata allows the JavaScript engine to skip parsing entirely at runtime.
ESM bytecode requires `--compile` because Bun embeds module metadata (import/export information) in the compiled binary. With this metadata, the JavaScript engine skips parsing entirely at runtime.

Without `--compile`, ESM bytecode would still require parsing the source to analyze module dependencies—defeating the purpose of bytecode caching.
Without `--compile`, ESM bytecode would still require parsing the source to analyze module dependencies, which defeats the purpose of bytecode caching.

### Combining with other optimizations

Bytecode works great with minification and source maps:
Combine bytecode with minification and source maps:

```bash terminal icon="terminal"
bun build --compile --bytecode --minify --sourcemap ./cli.ts --outfile=mycli
Expand Down Expand Up @@ -114,12 +114,14 @@ When you update Bun, you must regenerate bytecode:
bun build --bytecode ./index.ts --outdir=./dist
```

If bytecode doesn't match the current Bun version, it's automatically ignored and your code falls back to parsing the JavaScript source. Your app still runs — the performance optimization is skipped.
If bytecode doesn't match the current Bun version, Bun ignores it and falls back to parsing the JavaScript source.

**Best practice**: Generate bytecode as part of your CI/CD build process. Don't commit `.jsc` files to git. Regenerate them whenever you update Bun.

### Source code still required

Bytecode doesn't replace your JavaScript. You must deploy both files:

- The `.js` file (your bundled source code)
- The `.jsc` file (the bytecode cache)

Expand Down Expand Up @@ -194,21 +196,21 @@ ls -lh dist/

The `.jsc` file should be 2-8x larger than the `.js` file.

To log if bytecode is being used, set `BUN_JSC_verboseDiskCache=1` in your environment.
To log whether the bytecode is used, set `BUN_JSC_verboseDiskCache=1` in your environment.

On success, it will log something like:
On a cache hit, Bun logs:

```txt
[Disk cache] cache hit for sourceCode
```

If you see a cache miss, it will log something like:
On a cache miss:

```txt
[Disk cache] cache miss for sourceCode
```

It's normal for it it to log a cache miss multiple times since Bun doesn't currently bytecode cache JavaScript code used in builtin modules.
Several cache-miss lines are normal: Bun doesn't bytecode-cache the JavaScript in its builtin modules.

### Common issues

Expand All @@ -218,7 +220,7 @@ It's normal for it it to log a cache miss multiple times since Bun doesn't curre

- Using `--minify` to reduce code size before bytecode generation
- Compressing `.jsc` files for network transfer (gzip/brotli)
- Evaluating if the startup performance gain is worth the size increase
- Evaluating whether the startup gain is worth the size increase

## What is bytecode?

Expand All @@ -230,13 +232,13 @@ When you run JavaScript, the JavaScript engine doesn't execute your source code

Bytecode is an intermediate representation - it's lower-level than JavaScript source code, but higher-level than machine code. Think of it as assembly language for a virtual machine. Each bytecode instruction represents a single operation like "load this variable," "add two numbers," or "call this function."

This happens **every single time** you run your code. If you have a CLI tool that runs 100 times a day, your code gets parsed 100 times. If you have a serverless function with frequent cold starts, parsing happens on every cold start.
All of this happens **every time** you run your code. A CLI tool that runs 100 times a day gets parsed 100 times; a serverless function gets parsed on every cold start.

With bytecode caching, Bun moves steps 1 and 2 to the build step. At runtime, the engine loads the pre-compiled bytecode and jumps straight to execution.

### Why lazy parsing makes this even better

Modern JavaScript engines use a clever optimization called **lazy parsing**. They don't parse all your code upfront - instead, functions are only parsed when they're first called:
Modern JavaScript engines use an optimization called **lazy parsing**. They don't parse all your code upfront - instead, functions are only parsed when they're first called:

```js
// Without bytecode caching:
Expand All @@ -251,13 +253,13 @@ function main() {
}
```

This means parsing overhead isn't just a startup cost - it happens throughout your application's lifetime as different code paths execute. With bytecode caching, **all functions are pre-compiled**, even the ones that are lazily parsed. The parsing work happens once at build time instead of being distributed throughout your application's execution.
This means parsing overhead isn't just a startup cost - it happens throughout your application's lifetime as different code paths execute. With bytecode caching, **all functions are pre-compiled**, even the ones the engine would otherwise parse lazily.

## The bytecode format

### Inside a .jsc file

A `.jsc` file contains a serialized bytecode structure. Understanding what's inside helps explain both the performance benefits and the file size tradeoff.
A `.jsc` file contains a serialized bytecode structure.

**Header section** (validated on every load):

Expand All @@ -268,18 +270,18 @@ A `.jsc` file contains a serialized bytecode structure. Understanding what's ins

- **Source code hash**: A hash of the original JavaScript source code. Bun verifies this matches before using the bytecode.
- **Source code length**: The exact length of the source, for additional validation.
- **Compilation flags**: Critical compilation context like strict mode, whether it's a script vs module, eval context type, etc. The same source code compiled with different flags produces different bytecode.
- **Compilation flags**: Compilation context such as strict mode, script vs. module, and eval context type. The same source compiled with different flags produces different bytecode.

**Bytecode instructions**:

- **Instruction stream**: The actual bytecode opcodes - the compiled representation of your JavaScript. This is a variable-length sequence of bytecode instructions.
- **Metadata table**: Each opcode has associated metadata - things like profiling counters, type hints, and execution counts (even if not yet populated).
- **Instruction stream**: The bytecode opcodes - the compiled representation of your JavaScript, stored as a variable-length sequence of instructions.
- **Metadata table**: Each opcode has associated metadata such as profiling counters, type hints, and execution counts (even if not yet populated).
- **Jump targets**: Pre-computed addresses for control flow (if/else, loops, switch statements).
- **Switch tables**: Optimized lookup tables for switch statements.

**Constants and identifiers**:

- **Constant pool**: All literal values in your code - numbers, strings, booleans, null, undefined. These are stored as actual JavaScript values (JSValues) so they don't need to be parsed from source at runtime.
- **Constant pool**: All literal values in your code - numbers, strings, booleans, null, undefined. These are stored as JavaScript values (JSValues) so they don't need to be parsed from source at runtime.
- **Identifier table**: All variable and function names used in the code. Stored as deduplicated strings.
- **Source code representation markers**: Flags indicating how constants should be represented (as integers, doubles, big ints, etc.).

Expand All @@ -298,17 +300,17 @@ A `.jsc` file contains a serialized bytecode structure. Understanding what's ins

### What bytecode does NOT contain

Importantly, **bytecode does not embed your source code**. Instead:
**Bytecode does not embed your source code**. Instead:

- The JavaScript source is stored separately (in the `.js` file)
- The bytecode only stores a hash and length of the source
- At load time, Bun validates the bytecode matches the current source code

This is why you need to deploy both the `.js` and `.jsc` files. The `.jsc` file is useless without its corresponding `.js` file.
This is why you need to deploy both the `.js` and `.jsc` files: the `.jsc` file is useless without its corresponding `.js` file.

## The tradeoff: file size

Bytecode files are significantly larger than source code - typically 2-8x larger.
Bytecode files are typically 2-8x larger than the source code.

### Why is bytecode so much larger?

Expand Down Expand Up @@ -361,7 +363,7 @@ Jump targets, switch tables, and exception handler boundaries are all pre-comput
### Mitigation strategies

**Compression**:
Bytecode compresses extremely well with gzip/brotli (60-70% compression). The repetitive structure and metadata compress efficiently.
Bytecode compresses well with gzip/brotli (60-70% compression). The repetitive structure and metadata compress efficiently.

**Minification first**:
Using `--minify` before bytecode generation helps:
Expand Down Expand Up @@ -390,7 +392,7 @@ The bytecode contains abstract instructions that work on any architecture. Archi
Bytecode is **not stable across Bun versions**. Here's why:

**Bytecode format changes**:
JavaScriptCore's bytecode format evolves. New opcodes get added, old ones get removed or changed, metadata structures change. Each version of JavaScriptCore has a different bytecode format.
JavaScriptCore's bytecode format changes from version to version. New opcodes get added, old ones get removed or changed, metadata structures change.

**Version validation**:
The cache version in the `.jsc` file header is a hash of the JavaScriptCore framework. When Bun loads bytecode:
Expand All @@ -400,14 +402,12 @@ The cache version in the `.jsc` file header is a hash of the JavaScriptCore fram
3. If they don't match, the bytecode is **silently rejected**
4. Bun falls back to parsing the `.js` source code

Your application still runs — the performance optimization is skipped.

**Graceful degradation**:
This design means bytecode caching "fails open" - if anything goes wrong (version mismatch, corrupted file, missing file), your code still runs normally. You might see slower startup, but you won't see errors.

## Unlinked vs. linked bytecode

JavaScriptCore makes a crucial distinction between "unlinked" and "linked" bytecode. This separation is what makes bytecode caching possible:
JavaScriptCore distinguishes between "unlinked" and "linked" bytecode. This separation is what makes bytecode caching possible:

### Unlinked bytecode (what's cached)

Expand Down Expand Up @@ -436,12 +436,10 @@ When Bun runs bytecode, it "links" it - creating a runtime wrapper that adds:
- **JIT compilation state**: References to baseline JIT or optimizing JIT (DFG/FTL) compiled versions of hot code.
- **Runtime objects**: Pointers to actual JavaScript objects, prototypes, scopes, etc.

This linked representation is created fresh every time you run your code. This allows:
This linked representation is created fresh every time you run your code. This separation allows:

1. **Caching the expensive work** (parsing and compilation to unlinked bytecode)
2. **Still collecting runtime profiling data** to guide optimizations
3. **Still applying JIT optimizations** based on actual execution patterns

Bytecode caching moves expensive work (parsing and compiling to bytecode) from runtime to build time. For applications that start frequently, this can halve your startup time at the cost of larger files on disk.

For production CLIs and serverless deployments, the combination of `--bytecode --minify --sourcemap` gives you the best performance while maintaining debuggability.
For production CLIs and serverless deployments, the combination of `--bytecode --minify --sourcemap` gives you the best startup time while keeping errors mapped to your original source.
Loading
Loading