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

@tonycletus/wails-release-kit

v0.1.0

Published

CLI scaffolding for Wails desktop GitHub Releases with Windows, macOS, Linux, icons, and stable asset URLs.

Readme

@tonycletus/wails-release-kit

Scaffold release automation for Go/Wails desktop apps.

This CLI creates the release files a Wails project usually needs when you want GitHub Actions to build desktop installers for Windows, macOS, and Linux from the same source repository.

It generates:

  • GitHub Actions workflow for Windows .exe installer, macOS .dmg, Linux .deb
  • Inno Setup script
  • Windows icon resource script
  • Stable latest release asset names for download pages
  • Versioned release assets for traceability

Install

npm install -D @tonycletus/wails-release-kit
pnpm add -D @tonycletus/wails-release-kit
yarn add -D @tonycletus/wails-release-kit

Init a Wails project

npx wails-release-kit init --app "My App" --binary "my-app" --repo your-name/my-app

Run that command in the root of an existing Wails project. It writes:

  • .github/workflows/desktop-release.yml
  • installer/windows/App.iss
  • scripts/prepare-windows-icon-resource.ps1
  • RELEASE-DOWNLOADS.md

Then commit and push. Every push to main builds desktop packages and creates or updates a GitHub Release for the current package.json version.

Requirements

  • A Wails v2 app written in Go
  • Node.js 20 or newer
  • A working npm run build:desktop script
  • A public/icon-512.png source icon for Windows installer/icon generation
  • GitHub Actions enabled on the repository

The generated workflow installs the operating system dependencies it needs on GitHub-hosted runners.

Stable Download URLs

Use these on your app's download page:

https://github.com/<owner>/<repo>/releases/latest/download/<AppName>Setup.exe
https://github.com/<owner>/<repo>/releases/latest/download/<AppName>-macos-arm64.dmg
https://github.com/<owner>/<repo>/releases/latest/download/<app-name>-linux-amd64.deb

Each release also includes versioned assets so you can keep permanent links for older builds.

What It Does Not Do

This kit does not buy or configure code signing certificates. It also does not complete Apple notarization for you. The generated workflow is intended as a practical unsigned/community release baseline that you can extend when your app needs commercial distribution requirements.

Notes

Always review generated workflow files before publishing a production app. They are meant to give you a strong starting point, not hide your release process.