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

@windower/sidecar-macos-arm64

v0.1.1

Published

Prebuilt windower-capture-macos + windower-control-macos binaries (arm64) — optionalDependency of @windower/cli, resolved via npm's os/cpu fields.

Readme

@windower/sidecar-macos-arm64

Platform-specific optional dependency of @windower/cli / @windower/mcp-server (esbuild/swc-style pattern): npm resolves this package only on darwin/arm64 hosts via its os/cpu fields, and packages/core's resolveSidecarBinaryPath(surface) finds the binaries at runtime via require.resolve("@windower/sidecar-macos-arm64/bin/<binary>").

Since Phase 21 the macOS sidecar is two binaries, one per protocol surface (contracts/sidecar-protocol.md), and this package ships both:

| Surface | Binary | Methods | | --- | --- | --- | | capture | bin/windower-capture-macos | describe, getPermissions, requestPermission, enumerateTargets, startCapture, stopCapture, cancelCapture, captureFrame | | control | bin/windower-control-macos | describe, getPermissions, requestPermission, performInput, resizeWindow |

Both must be present: a package shipping only one leaves either recording or input synthesis broken at runtime, with nothing at install time to catch it.

Release-build step (not done by this package's own build)

This package ships binary artifacts, not source — there is no build step here that produces bin/. Before pnpm publish (or pnpm -r publish) is run for a release, the release process must copy the codesigned + notarized release binaries into place:

mkdir -p packages/sidecar-macos-arm64/bin
cp native/macos/.build/release/windower-capture-macos packages/sidecar-macos-arm64/bin/windower-capture-macos
cp native/macos/.build/release/windower-control-macos packages/sidecar-macos-arm64/bin/windower-control-macos
chmod +x packages/sidecar-macos-arm64/bin/windower-capture-macos packages/sidecar-macos-arm64/bin/windower-control-macos

(native/macos/.build/release/... is produced by swift build -c release --arch arm64 on an Apple Developer ID–signed/notarized build machine — native/macos's codesign script signs both binaries; see native/macos/CODESIGNING.md and specs/001-windower-mvp/tasks/phase-14-packaging.md.)

Publishing this package without that copy step produces a package with no bin/ payload — CLI users on arm64 would fail sidecar resolution at runtime with a clear "optional dependency not installed" style error rather than a silent wrong binary.