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

v2.0.1

Published

Shared base class, runtime extensions, and fundamental Win32 types for @bun-win32 packages.

Readme

@bun-win32/core

Shared base class, runtime extensions, and fundamental Win32 types for @bun-win32 packages.

Overview

@bun-win32/core provides the foundation that all @bun-win32 DLL packages build on:

  • Win32 base class — Abstract class that handles lazy dlopen loading and symbol memoization. Every DLL package (kernel32, user32, etc.) extends this class.
  • Runtime extensions — Installs a .ptr getter on all ArrayBuffer, Buffer, DataView, and typed array prototypes, giving direct access to native pointers for Bun FFI calls.
  • Win32 type aliases — Strongly-typed aliases (HANDLE, DWORD, LPVOID, BOOL, etc.) that map Win32 C types to their TypeScript equivalents.

Requirements

  • Bun runtime
  • Windows 10 or later

Installation

bun add @bun-win32/core

You typically do not need to install this directly — it is pulled in as a dependency of each DLL package.

[!NOTE] AI agents: see AI.md for the package contract and runtime behavior. It explains how @bun-win32/core differs from the DLL binding packages.

Usage

Extending Win32 for a new DLL

import { FFIType, type FFIFunction } from 'bun:ffi';
import { Win32 } from '@bun-win32/core';

class MyDll extends Win32 {
  protected static override name = 'mydll.dll';
  protected static override readonly Symbols = {
    MyFunction: { args: [FFIType.u32], returns: FFIType.i32 },
  } as const satisfies Record<string, FFIFunction>;

  public static MyFunction(value: number): number {
    return MyDll.Load('MyFunction')(value);
  }
}

Runtime pointer extensions

import '@bun-win32/core';

const buffer = new Uint8Array([1, 2, 3]);
nativeFunction(buffer.ptr, buffer.length);

Win32 type aliases

import type { DWORD, HANDLE, BOOL } from '@bun-win32/core';

Notes

  • This package is a dependency of all @bun-win32 DLL packages.
  • 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.