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

v2.0.1

Published

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

Readme

@bun-win32/wininet

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

Overview

@bun-win32/wininet exposes the wininet.dll exports using Bun's FFI. It provides a single class, Wininet, 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.

WinINet predates and is distinct from WinHTTP. It is the Internet stack Internet Explorer and the legacy Edge engine were built on. It still exposes things winhttp does not: FTP, the persistent URL cache (CommitUrlCacheEntry*, FindFirstUrlCacheEntry*), the IE/Edge-legacy cookie jar (InternetGetCookie*, InternetSetCookieEx2), and IE-style per-site cookie decisions.

Features

  • Bun-first ergonomics on Windows 10/11.
  • Direct FFI to wininet.dll — HTTP/HTTPS client, FTP client, persistent URL cache, cookie jar, autodial, proxy/auto-detect, and IE-compatible session options.
  • In-source docs in structs/Wininet.ts with links to Microsoft Docs.
  • Lazy binding on first call; optional eager preload (Wininet.Preload()).
  • No wrapper overhead; calls map 1:1 to native APIs.
  • Strongly-typed Win32 aliases (see types/Wininet.ts).

Requirements

  • Bun runtime
  • Windows 10 or later

Installation

bun add @bun-win32/wininet

Quick Start

import Wininet, { InternetOpenType, InternetService, InternetFlag, HttpQuery } from '@bun-win32/wininet';

Wininet.Preload(['InternetOpenW', 'InternetConnectW', 'HttpOpenRequestW', 'HttpSendRequestW', 'HttpQueryInfoW', 'InternetReadFile', 'InternetCloseHandle']);

const agent = Buffer.from('bun-win32/1.0\0', 'utf16le');
const hSession = Wininet.InternetOpenW(agent.ptr!, InternetOpenType.PRECONFIG, null, null, 0);

const host = Buffer.from('learn.microsoft.com\0', 'utf16le');
const hConnect = Wininet.InternetConnectW(hSession, host.ptr!, 443, null, null, InternetService.HTTP, 0, 0n);

const verb = Buffer.from('GET\0', 'utf16le');
const path = Buffer.from('/en-us/windows/win32/wininet/about-wininet\0', 'utf16le');
const hRequest = Wininet.HttpOpenRequestW(hConnect, verb.ptr!, path.ptr!, null, null, null, InternetFlag.SECURE, 0n);

Wininet.HttpSendRequestW(hRequest, null, 0, null, 0);

// Read the HTTP status code as a number.
const statusBuf = Buffer.alloc(4);
const lenBuf = Buffer.alloc(4);
lenBuf.writeUInt32LE(4, 0);
Wininet.HttpQueryInfoW(hRequest, HttpQuery.STATUS_CODE | HttpQuery.FLAG_NUMBER, statusBuf.ptr!, lenBuf.ptr!, null);
console.log('Status:', statusBuf.readUInt32LE(0));

Wininet.InternetCloseHandle(hRequest);
Wininet.InternetCloseHandle(hConnect);
Wininet.InternetCloseHandle(hSession);

[!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:cache-heatmap
bun run example:http-inspector

Notes

  • Either rely on lazy binding or call Wininet.Preload().
  • Windows only. Bun runtime required.
  • Handles returned by InternetOpenW, InternetConnectW, HttpOpenRequestW, FtpOpenFileW, and the cache enumerators are HINTERNET / HANDLE (bigint). Always close them with InternetCloseHandle (for HINTERNET) or FindCloseUrlCache (for URL-cache enumerators).
  • Strings are UTF-16LE (LPCWSTR); allocate with Buffer.from('...\0', 'utf16le') and pass .ptr.
  • InternetSetStatusCallback requires a JSCallback whose pointer remains live for the lifetime of the handle. Free it only after InternetCloseHandle returns.
  • The URL cache APIs operate on the Windows-wide WinINet/IE legacy cache (%LOCALAPPDATA%\Microsoft\Windows\INetCache). Modern Chromium-based Edge does not write to it.
  • CommitUrlCacheEntry* takes FILETIME by value; use the packFILETIME(low, high) helper from types/Wininet.ts.
  • 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.