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

waylandnano

v0.2.0

Published

Wayland Nano CLI — prebuilt native binary via npm

Downloads

695

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

seandonahoeseandonahoe

Keywords

Readme

waylandnano

Wayland Nano is a zero-dependency npm wrapper around prebuilt native CLI binaries. Installation performs no compilation and verifies the selected binary's byte size and SHA-256 digest before making it executable.

Install, run, uninstall

npm install --global waylandnano@next
wayland-nano --version
npm uninstall --global waylandnano

The alpha channel uses npm's next dist-tag. Stable releases use latest. Node.js 18 or newer is required.

Supported platforms are Windows x64, macOS x64/arm64, and Linux x64/arm64. Other platform/architecture pairs fail installation with the typed WAYLAND_NANO_UNSUPPORTED_PLATFORM diagnostic. A missing or altered binary fails closed with an integrity diagnostic; there is no source-build fallback.

Release staging

Stage a freshly built native host binary from target/release:

pwsh packaging/npm/scripts/pack.ps1

An explicit cross target is read from target/<rust-triple>/release:

pwsh packaging/npm/scripts/pack.ps1 -Platform linux-x64 -SkipBuild

The release workflow downloads each native build artifact into this layout:

artifacts/npm-binaries/
├── win32-x64/wayland-nano.exe
├── darwin-arm64/wayland-nano
├── darwin-x64/wayland-nano
├── linux-x64/wayland-nano
└── linux-arm64/wayland-nano

It then assembles the complete package without cross-compiling:

pwsh packaging/npm/scripts/pack.ps1 -Platform all -ArtifactRoot artifacts/npm-binaries

pack.ps1 writes binaries-manifest.json with each platform binary's exact filename, size, and SHA-256 digest. The staged binaries/ tree is ignored by git and must never be hand-committed.

Publishing is restricted to explicit v* tags in .github/workflows/release.yml. The owner supplies NPM_TOKEN as a repository secret at publish time; it is never stored in this package or printed by the workflow.

Package-name readiness

The intended public name is waylandnano. Registry ownership/availability is external state and must be confirmed by the owner immediately before the first publish. The workflow does not claim or reserve the name and performs no publish on branch pushes or merges.