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

web-ipc

v1.3.0

Published

A TypeScript library for IPC communication in web applications and browser extensions

Downloads

13

Readme

Web IPC

npm version

A TypeScript library for IPC (Inter-Process Communication) between different contexts (e.g. chrome extension's content.js and background.js) in web. It provides a native-like calling experience between different contexts.

Features

  • Native-like method invocation between different contexts
  • Full TypeScript support ensuring type safety
  • Promise-based async method call support
  • Context-based service registration and invocation

Installation

npm install web-ipc

Usage

1. define an interface

export interface BackgroundNotificationInterface {
    // must return a Promise
    notify(title: string, message: string): Promise<string>
}

2. implement the interface in background script and register it

class BackgroundNotification implements BackgroundNotificationInterface {
    async notify(title: string, message: string): Promise<string> {
        let notificationId = `notification-${Date.now()}`;
        chrome.notifications.create(notificationId, {
            type: 'basic',
            title: title,
            message: message
        });
        return notificationId;
    }
}

import {chromeRuntimeMessageIpcProviderRegister} from "web-ipc";
chromeRuntimeMessageIpcProviderRegister("BackgroundNotificationInterface", new BackgroundNotification())

3. call the interface in content script or popup script by creating a proxy

import {chromeRuntimeIpcInvoker} from "web-ipc";
const backgroundNotification = chromeRuntimeIpcInvoker.createProxy<BackgroundNotificationInterface>("BackgroundNotificationInterface")

let notificationId = await backgroundNotification.notify("hello", "this is a notification from content script")
console.log(notificationId)

The examples above use chrome.runtime for communication

For communication via window.postMessage, use windowMessageIpcProviderRegister and windowMessageIpcInvoker.

Advanced Usage

Access Raw Communication Info with $rawInfos

You can access the raw communication information (such as sender info in Chrome extensions) by adding a parameter named $rawInfos to your method. This parameter will be automatically injected with the underlying communication details.

export interface BackgroundNotificationInterface {
    notify(title: string, message: string, $rawInfos?: any): Promise<string>
}

class BackgroundNotification implements BackgroundNotificationInterface {
    async notify(title: string, message: string, $rawInfos?: any): Promise<string> {
        // For chrome.runtime, $rawInfos contains the sender object
        console.log('Sender tab ID:', $rawInfos?.sender?.tab?.id);
        console.log('Sender URL:', $rawInfos?.sender?.url);
        
        let notificationId = `notification-${Date.now()}`;
        chrome.notifications.create(notificationId, {
            type: 'basic',
            title: title,
            message: message
        });
        return notificationId;
    }
}

Note: The $rawInfos parameter is optional and will be automatically injected by the framework. You don't need to pass it when calling the method from the client side.

License

MIT