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

@reforged/plugin-launcher

v0.1.0

Published

(WIP) Provide an executable wrapper for your Electron software.

Readme

@reforged/plugin-launcher

An Electron Forge plugin to wrap Electron applications into shebang-prefixed script files and native OS executables. At the current state, application developers are responsible for resolving path to your Electron application and handling script real path when it is being symlinked. Plugin also only deals with Linux only for the time being.

[!CAUTION] We are currently at initial release cycle, therefore no API stability guarantees are made! Far more code infrastructure needs implementation as well, including but not exclusively: unit tests, documentation, use case consideration, multiplatform and multiarch packaging support, logging and planned feature definition.

Mature stable release will begin at v1 versioning, as defined by SemVer specification.

Usage:

Currently, plugin configuration supports one property that must be set: launcher. It is a multi-type property and can be:

  • a string, pointing to a file that will replace the binary when starting application,
  • a shebang-prefixed string or string[] (where array contains individual lines), to provide an inline script that will be used as an entrypoint of your application,
  • an ArrayBufferView (e.g. Uint8Array, Buffer instances), that represents an embedded version of your binary.

Example relevant Electron Forge configuration:

/// forge.config.mjs
import PluginLauncher from "@reforged/plugin-launcher"

const config = {
    /* (…) */
    plugins: [
        /* Note: PluginLauncher has to be the last element! */
        new PluginLauncher({ launcher: [
            '#!/bin/sh',
            'ME="$(readlink -f "$0")"',
            'echo "Hello, plugin world!"',
            'exec "$ME.bin" "$@"'
        ]})
    ]
}