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 🙏

© 2025 – Pkg Stats / Ryan Hefner

electron-windows-ipc-manager

v0.0.3

Published

Simplify and add type safety to IPC communication between the main process and renderer processes in an Electron application.

Readme

Electron IPC

Simplify and add type safety to IPC communication between the main process and renderer processes in an Electron application.

Scoped IPC

This library exposes a WindowIPC abstract class that you can extend to create a new window manager. You can then use the @mainHandler decorator to define a ipc handler for a method. When the manager start, it will send informations to the renderer in the web window so that the renderer can call the methods. With that, you can make sure that the renderer is talking to the right window.

Example Usage

Main process side:

@windowName("ExampleWindow")
class ExampleWindow extends Window {
@mainHandler("greeting")
  greeting(name: string) {
    return `Hello, ${name}`;
  }
}

Generate the types:

npm run generate-ipc-types

Then you can use the library front-end side:

Preload side:

import { electronHandler, exposeApiToGlobalWindow } from './ipc';

const handler = electronHandler((id: string) => ({
  ...exposeApiToGlobalWindow(id, 'ExampleWindow', [
    'greeting',
  ])
}), 'MyAPI'); 

type ExampleWindowAPIType = typeof handler;

declare global {
  interface Window  {
    MyAPI: Awaited<ExampleWindowAPIType>;
  }
}

You can now use the electron object in the window to call the methods defined in the ExampleWindow class.

window.MyAPI.ExampleWindow.greeting("John");

Using renderer directly:

import { IPCClient } from './ipc';

async function example(windowId: string) {
  const ipc = new IPCClient(windowId, 'ExampleWindow');

  // Fully type-safe!
  const greeting = await ipc.invoke('greeting', 'q');
  const data = await ipc.invoke('getData', { id: 123 });
} 

Using response handlers:

You can use the responseHandler decorator to define a response handler for a method.

@mainHandler('getData')
@responseHandler<{ id: number; }>()
async getData(data: { id: number; }) {
  return data;
}

The getData invoker will now wait for the response handler to be called before resolving.

You can use the getDataResponse function to call the response handler anywhere in front-end where this function is available.

await window.MyAPI.ExampleWindow.getDataResponse({ id: 123 });