npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@bun-win32/wimgapi

v2.0.1

Published

Zero-dependency, zero-overhead Win32 WIMGAPI bindings for Bun (FFI) on Windows.

Readme

@bun-win32/wimgapi

Zero-dependency, zero-overhead Win32 WIMGAPI bindings for Bun on Windows.

Overview

@bun-win32/wimgapi exposes the wimgapi.dll exports using Bun's FFI. It provides a single class, Wimgapi, which lazily binds native symbols on first use. You can optionally preload a subset or all symbols up-front via Preload().

The Windows Imaging Interface (WIMGAPI) is the supported, in-process API for Windows image (.wim) files — create/open archives, capture a directory tree, apply or enumerate an image, mount/unmount, split, export, set references, and stream live progress through a message callback. It is the same engine DISM.exe and ImageX drive, with no process spawn. It complements @bun-win32/dismapi (image servicing).

The bindings are strongly typed for a smooth DX in TypeScript.

Features

  • Bun-first ergonomics on Windows 10/11.
  • Direct FFI to wimgapi.dll (image capture/apply/mount/split/export, message callbacks).
  • In-source docs in structs/Wimgapi.ts with links to Microsoft Docs.
  • Lazy binding on first call; optional eager preload (Wimgapi.Preload()).
  • No wrapper overhead; calls map 1:1 to native APIs.
  • Strongly-typed Win32 aliases and the full WIM flag/message enums (see types/Wimgapi.ts).

Requirements

  • Bun runtime
  • Windows 10 or later
  • An elevated process for capture/apply/mount (WIMCaptureImage/WIMApplyImage/WIMMountImage need SeBackupPrivilege/SeRestorePrivilege). Opening a .wim read-only and enumerating it (WIMApplyImage with WIM_FLAG_NO_APPLY) needs no privilege.

Installation

bun add @bun-win32/wimgapi

Quick Start

import Wimgapi, { WIMCreationDisposition, WIMDesiredAccess } from '@bun-win32/wimgapi';

const wide = (s: string) => Buffer.from(s + '\0', 'utf16le');

// Open an existing .wim read-only and read its header + image count.
const result = Buffer.alloc(4);
const hWim = Wimgapi.WIMCreateFile(wide('C:\\images\\install.wim').ptr!, WIMDesiredAccess.WIM_GENERIC_READ, WIMCreationDisposition.WIM_OPEN_EXISTING, 0, 0, result.ptr!);

if (hWim !== 0n) {
  console.log('images in archive:', Wimgapi.WIMGetImageCount(hWim));

  const wimInfo = Buffer.alloc(560); // WIM_INFO
  if (Wimgapi.WIMGetAttributes(hWim, wimInfo.ptr!, 560)) {
    console.log('compression type:', wimInfo.readUInt32LE(540));
  }

  Wimgapi.WIMCloseHandle(hWim); // always pair create/open with close
}

[!NOTE] AI agents: see AI.md for 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 (run elevated, or pass an existing .wim path, for full output):

bun run example/wim-inspector.ts [path\to\image.wim]
bun run example/wim-xray.ts      [path\to\image.wim]
  • wim-inspector — a thorough diagnostic: decoded WIM_INFO header (GUID, compression, parts, attributes), per-image XML manifest, and the live system-wide mounted-image table.
  • wim-xray — a live truecolor X-ray of an image's file tree, driven by the real imaging engine calling back into a bun:ffi JSCallback (registered via WIMRegisterMessageCallback, enumerated with WIMApplyImage(hImage, NULL, WIM_FLAG_NO_APPLY)).

Notes

  • Either rely on lazy binding or call Wimgapi.Preload().
  • All WIM functions are wide-only (no A/W split); strings are UTF-16LE NUL-terminated buffers.
  • Handles (WIMCreateFile/WIMLoadImage/WIMCaptureImage returns) are bigint; failure is 0n. Always release them with WIMCloseHandle.
  • WIMGetImageInformation returns a WIM-allocated UTF-16 buffer via a PVOID* out-pointer plus a DWORD byte count; read the count from your own buffer, then free the buffer with Kernel32.LocalFree.
  • Sizing pattern: WIMGetMountedImages(NULL, &cb) / WIMGetMountedImageInfo(level, &count, NULL, 0, &cb) return the required buffer size; allocate, then call again.
  • Register a WIMMessageCallback (a bun:ffi JSCallback passed as FARPROC) for live progress; return WIM_MSG_SUCCESS to continue or WIM_MSG_ABORT_IMAGE to cancel. Keep the JSCallback alive for the duration of the operation.
  • Seven exported file-IO/enumeration functions (WIMReadImageFile, WIMCreateImageFile, WIMFindFirstImageFile, WIMFindNextImageFile, WIMEnumImageFiles, WIMInitFileIOCallbacks, WIMSetFileIOCallbackTemporaryPath) and the Dll* server entries are undocumented internals and intentionally not bound.
  • Windows only. Bun runtime required.
  • SAL types & naming: nullability is in the typeOptional<T> (formally optional, SAL _*opt_) and Nullable<T> (plain [in]/[out] the docs say can be NULL), the null sentinel derived from T (null for pointers LP*/P*, 0n for handles/by-value addresses); direction is in the parameter name_out (_Out_), _in_out (_Inout_), _In_ bare. See AI.md and the repo AGENTS.md.