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/dcomp

v2.0.1

Published

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

Readme

@bun-win32/Dcomp

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

Overview

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

It covers the documented Microsoft DirectComposition flat surface (dcomp.h): device creation (DCompositionCreateDevice/2/3), composition surface handles, the Windows-11 compositor-clock frame/statistics APIs (DCompositionGetFrameId, DCompositionGetStatistics, DCompositionWaitForCompositorClock, DCompositionBoostCompositorClock), mouse-input redirection, and the COM in-proc-server entry points. The rest of DirectComposition — the IDCompositionDevice/IDCompositionVisual object graph — rides the COM vtable on top of the device created here.

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

Features

  • Bun-first ergonomics on Windows 10/11.
  • Direct FFI to dcomp.dll (DirectComposition device, surfaces, compositor clock).
  • In-source docs in structs/Dcomp.ts with links to Microsoft Docs.
  • Lazy binding on first call; optional eager preload (Dcomp.Preload()).
  • No wrapper overhead; calls map 1:1 to native APIs.
  • Strongly-typed Win32 aliases (see types/Dcomp.ts).

Requirements

  • Bun runtime
  • Windows 10 or later (compositor-clock APIs require Windows 11 build 22000+)

Installation

bun add @bun-win32/dcomp

Quick Start

import Dcomp, { COMPOSITION_FRAME_ID_TYPE } from '@bun-win32/dcomp';

// Create a device-only DirectComposition device (NULL renderer is allowed).
// IID_IDCompositionDevice = {C37EA93A-E7AA-450D-B16F-9746CB0407F3} (dcomp.h)
const iid = Buffer.from([0x3a, 0xe9, 0x7e, 0xc3, 0xaa, 0xe7, 0x0d, 0x45, 0xb1, 0x6f, 0x97, 0x46, 0xcb, 0x04, 0x07, 0xf3]);
const deviceOut = Buffer.alloc(8);
if (Dcomp.DCompositionCreateDevice2(null, iid.ptr!, deviceOut.ptr!) === 0) {
  const device = deviceOut.readBigUInt64LE(0); // IDCompositionDevice* — drive via the COM vtable

  // Read the latest completed compositor frame id.
  const frameId = Buffer.alloc(8);
  Dcomp.DCompositionGetFrameId(COMPOSITION_FRAME_ID_TYPE.COMPOSITION_FRAME_ID_COMPLETED, frameId.ptr!);
  console.log('latest composited frame', frameId.readBigUInt64LE(0));
}

[!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:

bun run example/compositor-clock-scope.ts
bun run example/composition-device-diagnostic.ts
  • compositor-clock-scope.ts — a live ANSI oscilloscope of the Windows desktop compositor's heartbeat: paces on DCompositionWaitForCompositorClock, reads the frame period from DCompositionGetStatistics, and plots a scrolling waveform with the measured effective refresh rate.
  • composition-device-diagnostic.ts — creates a real DirectComposition device, proves it via its IUnknown vtable refcount, mints a composition surface handle, and reads the full compositor-clock frame-id/statistics surface into an aligned report.

Notes

  • Either rely on lazy binding or call Dcomp.Preload().
  • 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.