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

@midion/electron

v1.8.2

Published

Install electron binaries for the command-line using npm

Downloads

65

Readme

npm node license

Electron Binaries

Install

Install in your local project

npm install --save-dev @midion/electron

Install globally

npm install -g @midion/electron

Usage

Please, refer to the official electron documentation.

Simple example

import { app, BrowserWindow } from "electron";
import path from "path";
import url from "url";

const DARWIN = process.platform === "darwin";

function initApp () {
    // Keep a global reference of the window object, if you don't, the window will
    // be closed automatically when the JavaScript object is garbage collected.

    if (global.mainWindow) return;

    // Create the browser window.
    global.mainWindow = new BrowserWindow({ width: 400, height: 600 });

    // Emitted when the window is closed.
    global.mainWindow.on("closed", function() {
        // Dereference the window object, usually you would store windows
        // in an array if your app supports multi windows, this is the time
        // when you should delete the corresponding element.
        global.mainWindow = null;
    });

    // and load the index.html of the app.
    global.mainWindow.loadURL(url.format({
        pathname: path.join(__dirname, "../webapp/main.html"),
        protocol: "file:",
        query: { s: 4 }, // url params here
        slashes: true
    }));


    // Open the DevTools.
    //global.mainWindow.webContents.openDevTools();
}

// This method will be called when Electron has finished
// initialization and is ready to create browser windows.
// Some APIs can only be used after this event occurs.
app.on("ready", initApp);

// Quit when all windows are closed.
app.on("window-all-closed", function () {
    // On OS X it is common for applications and their menu bar
    // to stay active until the user quits explicitly with Cmd + Q
    !DARWIN && app.quit();
});

// On OS X it's common to re-create a window in the app when the
// dock icon is clicked and there are no other windows open.
app.on("activate", initApp);

Maintainers

| willchb-avatar | |------------------------------| | Willian Balmant |