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

testdesktophelloworldapp

v1.0.0

Published

A minimal Electron Hello World app distributed as a global npm command.

Readme

testDesktopHelloWorldApp

A minimal Electron proof of concept that is packaged with its own Electron runtime, published through npm, and launched by a global terminal command.

Project structure

bin/testDesktopHelloWorldApp.js  Global CLI launcher
src/main.js                      Electron main process source
src/index.html                   Hello World renderer
scripts/                         Small build/verification helpers
build/                           Minified intermediate output (generated)
release/mac-universal/           Self-contained macOS app (generated)
payload/                         Symlink-safe npm payload zip (generated)

Only the launcher, installer, package.json, README, and generated macOS app archive are included in the npm package. Source, build scripts, and development dependencies are excluded. The application code inside the .app is stored in Electron's app.asar archive; the JavaScript main process is bundled and minified first.

The .app is zipped with macOS ditto because npm tarballs do not preserve the framework symlinks inside an Electron application. npm's postinstall extracts it to the package's runtime directory; the CLI also performs this check as a fallback.

Build locally

Requirements: macOS, Node.js 18 or newer, and npm.

npm install
npm run build
npm run verify:package

The build creates a universal macOS application at release/mac-universal/testDesktopHelloWorldApp.app. Code signing and notarization are disabled for this proof of concept.

Test the global npm installation locally

npm run build
npm pack
npm install -g ./testdesktophelloworldapp-1.0.0.tgz
cd /tmp
testDesktopHelloWorldApp

Remove the local test with npm uninstall -g testdesktophelloworldapp.

If macOS blocks the unsigned app, allow it in System Settings → Privacy & Security, or Control-click the app and choose Open. This is expected because the POC is neither signed nor notarized.

Publish to npm

The unscoped npm name must be available and your npm account must be logged in:

npm login
npm run build
npm pack --dry-run
npm publish

npm package names are lowercase, so the canonical install command is:

npm install -g testdesktophelloworldapp

The requested mixed-case spelling normally resolves to the same registry package:

npm install -g testDesktopHelloWorldApp

After installation, from any directory, run exactly:

testDesktopHelloWorldApp

No separate Electron installation and no electron . or npm start command is required.