CompileBuildOptions

interface CompileBuildOptions

• assets?: string[]

  Files or directories to embed into the executable under their original relative paths. At runtime they are reachable via node:fs and Bun.file() relative to import.meta.dir.

  Equivalent CLI flag: --asset (repeatable)

• autoloadBunfig?: boolean

  Whether the standalone executable loads bunfig.toml when it runs

  Equivalent CLI flags: --compile-autoload-bunfig, --no-compile-autoload-bunfig

• autoloadDotenv?: boolean

  Whether the standalone executable loads .env files when it runs

  Equivalent CLI flags: --compile-autoload-dotenv, --no-compile-autoload-dotenv

• autoloadPackageJson?: boolean

  Whether the standalone executable loads package.json when it runs

  Equivalent CLI flags: --compile-autoload-package-json, --no-compile-autoload-package-json

• autoloadTsconfig?: boolean

  Whether the standalone executable loads tsconfig.json when it runs

  Equivalent CLI flags: --compile-autoload-tsconfig, --no-compile-autoload-tsconfig

• execArgv?: string[]
• executablePath?: string
• jitPolicy?: number

  The JIT policy the executable starts with (see Bun.unsafe.setJITPolicy). 1 is the normal policy. A value > 1 multiplies JavaScriptCore's tier-up thresholds so code that only runs during startup stays in the interpreter longer; the app should call Bun.unsafe.setJITPolicy(1) once it is interactive.

  Equivalent CLI flag: --compile-jit-policy <n>

• outfile?: string
• target?: CompileTarget
• windows?: { copyright: string; description: string; hideConsole: boolean; icon: string; publisher: string; title: string; version: string }