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

singletron

v0.0.5

Published

Inter-process communication hub for Electron apps

Readme

Singletron

This is a thin wrapper around node-ipc to simplify inter-process communication among Electron apps. The main aim is to allow apps to share a single instance of Electron, to minimize memory foot-print.

Currently, this is just a proof-of-concept, and not meant for production use. Please refer to on-going discussion in the Electron repo about sharing a runtime among apps.

Usage

For a working demonstration, see singletron-example.

Below is an example of how to set up the server/clients. Please note that startApp and createWindow are defined earlier in the file.

In main.js (main process):

const singletron = require('singletron')

// Share single instance of Electron

singletron.createClient().then(({ client, config }) => {

  console.log('Connected to singletron server', config)

  client.on('loaded', () => app.quit())

  client.emit('load', path.join(__dirname, 'index.html'))

}).catch((e) => {

  // Start the app instance
  startApp()

  // Start singletron server

  singletron.createServer().then(({ server, config }) => {

    console.log('Singletron server started', config)

    // Request from client
    server.on('load', (data, socket) => {

      console.log('Request for new window', data)

      // Create window for new app
      createWindow(data)

      server.emit(socket, 'loaded')
    })

  }).catch((e) => {
    console.log('Error creating singletron server')
  })
})

Methods

createClient( options )

options = {
  clientId: 'singletronClient',
  serverId: 'singletronServer'
}

Returns a promise that resolves if connected to an existing server.

On success, the then() handler will receive an object with two properties:

  • client is an instance of node-ipc.
    • client.emit( eventName, data ) - Send a message to server
    • client.on( eventName, (data, socket) => {} ) - Listen to message from server
  • config is an object that the server sent
    • id - server ID
    • versions - { node, chrome, electron }

It's up to the app how to negotiate with the server. In the example above, the client requests to open a new window with its index.html, then quits when it's loaded.

If no server is found, it throws: you can catch() it and start a server.

createServer( options )

options = {
  serverId: 'singletronServer'
}

Returns a promise that resolves if server was created successfully.

On success, the then() handler will receive an object with two properties:

  • server is an instance of node-ipc.
    • server.emit( socket, eventName, data ) - Send a message to client specified by socket
    • server.on( eventName, (data, socket) => {} ) - Listen to message from client
  • config is the same object as described for client above

It's up to the app how to negotiate with the client. In the example above, the server listens for a request to open a new window with given URL.