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

@geastack/geatsc-plugin-windows-native

v0.1.3

Published

geatsc compiler plugin that lowers @geastack/windows SDK calls to the Win32 native bridge.

Readme

@geastack/geatsc-plugin-windows-native

The geatsc compiler plugin behind @geastack/windows. It is an external CompilerPlugin; the compiler itself knows nothing about Windows.

Given the SDK's bridge metadata it:

  • declares the @geastack/windows and @geastack/windows/* modules to the compiler and maps every library function, class member, constructor and constant onto a C++ thunk in the gea::windows namespace (host tables);
  • rewrites JSX over the Controls classes (<WinStackView spacing={8}>…) into construction and addArrangedSubview / addSubview calls;
  • writes gea/windows/native_bridge.h and native_bridge.cpp into the build's generated directory, the contract the target's C++ implements.

The bridge is written only for a build that names its metadata (the windows.metadata plugin option or the GEA_WINDOWS_NATIVE_METADATA environment variable, both set by build-windows.mjs). Installed for an app built for the web, the plugin declares the modules and writes nothing.

@geastack/windows re-exports this plugin from its geatsc-plugin entry, which is how the CLI finds it for any app that depends on @geastack/windows.

License

Apache-2.0. See LICENSE.