System libraries

System library bindings are shipped as direct subpath imports. They use the same schema inference and lifecycle as dlopen, but the common library path, symbol schema, and open* helper are already defined.

import { openCoreFoundation } from 'unffi/macos/CoreFoundation'
import { openLibc } from 'unffi/linux/libc'
import { openKernel32 } from 'unffi/windows/kernel32'

await using cf = await openCoreFoundation()
const cfStringType = cf.symbols.CFStringGetTypeID()

await using libc = await openLibc()
const pid = libc.symbols.getpid()

await using kernel32 = await openKernel32()
const windowsPid = kernel32.symbols.GetCurrentProcessId()

What you get

• One import per native library, for example unffi/macos/Security or unffi/windows/user32.
• Typed open*() helpers that return an AsyncDisposable library handle.
• Exported *Schema and *LibraryPaths constants for inspection or manual composition.
• UNFFI_*_PATH environment overrides and open*(pathOverride) for custom library locations.

Shipped modules

Conservative by design

The shipped surface is intentionally focused. APIs that need C++ classes, Objective-C messaging, COM vtables, variadic functions, bitfields, or ownership-heavy structs are skipped until UnFFI can model them safely.

Use the platform pages for runnable snippets, or see the repository examples/ folder for scripts grouped by OS.