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 🙏

© 2024 – Pkg Stats / Ryan Hefner

windows-ffi

v0.0.4

Published

NodeJS wrappers around Windows p-invoke/dll functions in user32, gdi32, etc. (based on node-ffi-napi)

Downloads

48

Readme

Windows FFI

NodeJS wrappers around Windows p-invoke/dll functions in user32, gdi32, etc. (based on node-ffi-napi)

Installation

  • 1) Install ffi-napi in your project: npm i ffi-napi
    • 1.1) You may need to install the windows-build-tools first for ffi-napi to be able to build: npm install --global --production windows-build-tools
  • 2) Install: npm i windows-ffi
    • 2.1) If you're using windows-ffi in symlinked mode, supply the parent project's copy of the node-ffi libraries using the init code below:
      // Make sure the code below runs before windows-ffi is imported! (example approach: https://stackoverflow.com/a/42817956)
      import ffi from "ffi-napi";
      import ref from "ref-napi";
      import refStructDI from "ref-struct-di";
      import {SupplyConfig} from "windows-ffi/Dist/@UserSupplied/PreImportConfig.js";
      
      SupplyConfig({ffi, ref, refStructDI});

Usage

While this library is meant to gradually expand to cover more of the Windows API, it will never be 100%, because it's a "develop as you need it" sort of endeavor.

Some of the most common and/or noteworthy functionalities are shown below.

Capture image-data from a region on-screen

import {VRect, CaptureScreenshot, GetForegroundWindowHandle} from "windows-ffi";

// First capture a screenshot of a section of the screen.
const screenshot = CaptureScreenshot({
	windowHandle: GetForegroundWindowHandle(), // comment to screenshot all windows
	rectToCapture: new VRect(0, 0, 800, 600),
});

// The image-data is now stored in the `screenshot.buffer` Buffer object.
// Access it directly (and cheaply) using the helper functions on `screenshot`.
for (let x = 0; x < 800; x++) {
	console.log(`Pixel color at [${x}, 0] is:`, screenshot.GetPixel(x, 0).ToHex_RGB());
}

Performance:

  • Full-screen (2560x1440), all windows (ie. "desktop" window): ~80ms
  • Full-screen (2560x1440), single window: ~20ms
  • Region (700x200), all windows (ie. "desktop" window): ~50ms
  • Region (700x200), single window: ~4ms

Tasks

General:

  • Create an accompanying library for Windows-specific functionalities that do not require the ffi-napi dependency. (I've had pains with ffi-related building during NodeJS updates, so things that can be done without that dependency is beneficial to bundle separately)