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

wkinterop

v2.0.0

Published

JS counterpart to https://github.com/randymarsh77/wkinterop

Readme

wkinteropJS

JS counterpart to wkinterop, a Swift package for talking to WKWebViews. Install with npm install wkinterop.

license codebeat badge

Overview

WKWebView provides an api for executing JS code, and receiving messages from JS running in the view's execution environment. However, any nontrivial amount of communication requires boiler plate interop code. Then, there are other considerations like asynchronicity and cancellation.

WKInterop facilitates communication by providing an api to both Swift code, and JS code for publishing events and making asynchronous requests. Each execution environment can register to receive events and process requests.

Usage

Given that we are in the context of a WKWebView created using WKInterop (see Swift Example), you can import and use the interop functions:

import { useInterop } from 'wkinterop';

const { registerEventHandler, registerRequestHandler, publish, request } = useInterop();

Or use the individual hook functions:

import { useInteropEventHandler, useInteropRequestHandler, useInterop } from 'wkinterop';

Available functions:

  • registerEventHandler(route, handler) - Register a handler for events from Swift
  • registerRequestHandler(route, handler) - Register a handler for requests from Swift
  • publish(route, content) - Publish an event to Swift
  • request(route, content) - Make a request to Swift (returns a Promise)

Requests are promise-based, so a handler should return a promise that fulfills the request and making a request will return a promise.

All communications can provide a value as an argument and choose to handle or ignore an argument that has been provided. Requests must return a value.

Handler registration functions return an unsubscribe function that can be called to remove the handler.

Example

import { useInterop, useInteropEventHandler, useInteropRequestHandler } from 'wkinterop';

const { publish, request } = useInterop();

// Register event handler using the hook
const unsubscribeEvent = useInteropEventHandler('example.route.swift-published-event', (data) => {
  console.log('This is the event published by Swift provided with some argument/data/context what have you: ', data);
});

// Register request handler using the hook
const unsubscribeRequest = useInteropRequestHandler('example.route.swift-initiated-request', (request) => {
  console.log('This is the request argument: ', request);
  return Promise.resolve({ prop: 'this is my response' });
});

// Or register handlers using the main useInterop hook
const { registerEventHandler, registerRequestHandler } = useInterop();

const removeEventHandler = registerEventHandler('another.event.route', (data) => {
  console.log('Another event handler:', data);
});

const removeRequestHandler = registerRequestHandler('another.request.route', async (request) => {
  return { result: 'processed request' };
});

// Publish an event to Swift
publish('example.route.js-published-event', {
  prop: 'providing some context',
});

// Make a request to Swift
request('example.route.js-initiated-request', { prop: 'JS is requesting data from Swift' })
  .then((response) => {
    console.log('received this response from Swift: ', response);
  });

// Clean up handlers when needed
// unsubscribeEvent();
// unsubscribeRequest();
// removeEventHandler();
// removeRequestHandler();