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

@maciejwojs/screen-capture

v0.2.5

Published

Native screen capture addon for Node.js

Readme

@maciejwojs/screen-capture

Native Node.js addon for screen capture. Packages are published to NPM with provenance (OIDC) and include prebuilt binaries via GitHub Actions.

Current state

  • Windows backend is implemented with Windows.Graphics.Capture + D3D11.
  • Linux backend is implemented with xdg-desktop-portal (D-Bus) and PipeWire stream, supporting modern desktop environments (Wayland/X11).
  • Runtime loading uses node-gyp-build, so local build and prebuilds/ binaries are both supported.

Usage

import { ScreenCapture } from '@maciejwojs/screen-capture';

const capture = new ScreenCapture();
capture.start();

// Get texture structure formatted for Electron's shared-texture API:
const textureInfo = capture.getSharedTextureInfo();

// Or get the raw handle data (legacy):
const rawHandle = capture.getSharedHandle();

capture.stop();

Install

bun install

Local build

bun run build # to compile TypeScript
bun x node-gyp rebuild

Prebuilt binaries (prebuildify)

Build prebuild for current platform:

bun run prebuildify

Build prebuilds for selected platforms:

bun run prebuildify:all

Output goes to prebuilds/ and is loaded automatically by dist/index.js. Scripts are configured to run node-gyp via node-gyp internally and build TypeScript beforehand.

How to add other systems / window managers

Recommended backend mapping:

  • Windows: Windows.Graphics.Capture (already in place)
  • Linux: PipeWire portal (xdg-desktop-portal) with DMA-BUF limits (already in place)
  • macOS: ScreenCaptureKit (or CGDisplayStream as fallback)

Practical architecture:

  • Keep one JS API (ScreenCapture) for all OSes.
  • Keep one addon target in binding.gyp.
  • Keep per-platform backend in separate .cpp files and select in binding.gyp conditions.
  • Current split is:
    • src/addon.cpp - shared N-API wrapper
    • src/serialize.cpp - N-API data serialization logic for Electron and raw handles
    • src/win/platform_capture_win.cpp - Windows backend
    • src/linux/platform_capture_linux.cpp - Linux backend entry point
    • src/platform_capture_stub.cpp - fallback for other systems
    • src/platform_capture.hpp - common backend interface
  • For unsupported combinations, return a clear runtime error (already done).

To add next platform, create next backend file (for example src/macos/platform_capture_macos.cpp) and add it in matching binding.gyp condition branch.

This gives you one npm package with many prebuilt binaries and no user-side compile step.