@bun-win32/msi
v3.0.0
Published
Zero-dependency, zero-overhead Win32 MSI bindings for Bun (FFI) on Windows.
Downloads
640
Maintainers
Readme
@bun-win32/msi
Zero-dependency, zero-overhead Win32 MSI bindings for Bun on Windows.
Overview
@bun-win32/msi exposes the msi.dll exports using Bun's FFI. It provides a single class, Msi, which lazily binds native symbols on first use. You can optionally preload a subset or all symbols up-front via Preload().
The bindings are strongly typed for a smooth DX in TypeScript.
Features
- Bun-first ergonomics on Windows 10/11.
- Direct FFI to
msi.dll(product enumeration, install state queries, database access, patching, source lists, and more). - In-source docs in
structs/Msi.tswith links to Microsoft Docs. - Lazy binding on first call; optional eager preload (
Msi.Preload()). - No wrapper overhead; calls map 1:1 to native APIs.
- Strongly-typed Win32 aliases (see
types/Msi.ts).
Requirements
- Bun runtime
- Windows 10 or later
Installation
bun add @bun-win32/msiQuick Start
import Msi, { INSTALLSTATE } from '@bun-win32/msi';
// Enumerate installed products
const productBuf = Buffer.alloc(78); // 39 WCHARs (GUID + NUL)
let index = 0;
while (Msi.MsiEnumProductsW(index, productBuf.ptr) === 0) {
const productCode = new TextDecoder('utf-16le')
.decode(productBuf)
.replace(/\0.*$/, '');
const state = Msi.MsiQueryProductStateW(
Buffer.from(productCode + '\0', 'utf16le').ptr,
);
if (state === INSTALLSTATE.INSTALLSTATE_DEFAULT) {
console.log(productCode);
}
index++;
}[!NOTE] AI agents: see
AI.mdfor the package binding contract and source-navigation guidance. It explains how to use the package without scanning the entire implementation.
Examples
Run the included examples:
bun run example:installer-audit # Full audit of every installed product
bun run example:package-watcher # Live product installation monitorNotes
- Either rely on lazy binding or call
Msi.Preload(). MSIHANDLEisnumber(32-bit), notbigint. Do not confuse with kernelHANDLE.- Windows only. Bun runtime required.
- SAL types & naming: nullability is in the type —
Optional<T>(formally optional, SAL_*opt_) andNullable<T>(plain[in]/[out]the docs say can be NULL), the null sentinel derived fromT(nullfor pointersLP*/P*,0nfor handles/by-value addresses); direction is in the parameter name —_out(_Out_),_in_out(_Inout_),_In_bare. SeeAI.mdand the repoAGENTS.md.
