Skip to content
DocsGuidesReferenceBlog
Install
HomeDocsGuidesReferenceBlog
Install Bun v1.4.4
Reference
Modules/Bun/CompileBuildOptions/aotLogTypeMismatches
  • PaotLogTypeMismatches

Modules

  • Bun
  • bun:bundle
  • bun:ffi
  • bun:jsc
  • bun:sqlite
  • bun:test
  • Globals
  • node:assert
  • node:async_hooks
  • node:buffer
  • node:child_process
  • node:cluster
  • node:crypto
  • node:dgram
  • node:diagnostics_channel
  • node:dns
  • node:dns/promises
  • node:events
  • node:ffi
  • node:fs
  • node:fs/promises
  • node:http
  • node:http2
  • node:https
  • node:inspector
  • node:inspector/promises
  • node:module
  • node:net
  • node:os
  • node:path
  • node:perf_hooks
  • node:punycode
  • node:querystring
  • node:quic
  • node:readline
  • node:readline/promises
  • node:stream
  • node:stream/consumers
  • node:stream/iter
  • node:stream/promises
  • node:stream/web
  • node:string_decoder
  • node:test
  • node:test/reporters
  • node:timers/promises
  • node:tls
  • node:trace_events
  • node:tty
  • node:url
  • node:util
  • node:util/types
  • node:v8
  • node:vfs
  • node:vm
  • node:wasi
  • node:worker_threads
  • node:zlib
  • node:zlib/iter

property

CompileBuildOptions.aotLogTypeMismatches

aotLogTypeMismatches?: boolean

With aot: log every value that doesn't match its declared type.

A mismatch never changes what the program does: the function falls back to its slow path and behaves as it does under bun run. Each log line has the location, the expected type and the kind of value it got, never the value itself. Lines go to stderr, or to the file in the BUN_AOT_TYPE_MISMATCH_LOG environment variable.

Equivalent CLI flag: --aot-log-type-mismatches