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

@service-broker/webclient

v2.0.2

Published

Browser ESM client library for communicating with the service broker

Readme

@service-broker/webclient

Browser ESM client library for communicating with a Service Broker

Install

npm install @service-broker/webclient

Connect

Connect to the Service Broker at the specified WebSocket URL.

import { ServiceBroker } from "@service-broker/webclient"

const sb = new ServiceBroker("wss://sb.mydomain.com")

Request

Send a service request. The broker will select a qualified provider based on service name and requested capabilities. The parameter request contains the actual message that'll be delivered to the service provider.

interface Message {
  header: {
    from: string      // the endpointId of the sender
    to: string        // the endpointId of the recipient
  },
  payload: string     // the message payload, usually JSON
}

sb.request(
  service: {
    name: string,
    capabilities?: string[]
  },
  request: Message,
  timeout?: number
): Promise<Message>

Notify

A notification is like a request except no response will be sent back.

sb.notify(
  service: {
    name: string,
    capabilities?: string[]
  },
  notification: Message
): Promise<void>

RequestTo

Send a service request directly to an endpoint.

sb.requestTo(
  endpointId: string,
  serviceName: string,
  request: Message,
  timeout?: number
): Promise<Message>

NotifyTo

Send a notification directly to an endpoint.

sb.notifyTo(
  endpointId: string,
  serviceName: string,
  notification: Message
): Promise<void>

SetServiceHandler

The requestTo and notifyTo methods can be used to send direct messages to an endpoint. For example, a chat service provider may publish a client's endpointId to other clients and allow them to send direct messages to one another.

This method sets a handler for incoming requests and notifications.

sb.setServiceHandler(
  serviceName: string,
  handler: (request: Message) => Message|void|Promise<Message|void>
): void

Publish/Subscribe

sb.publish(
  topic: string,
  text: string
): Promise<void>

sb.subscribe(
  topic: string,
  handler: (text: string) => void
): Promise<void>

sb.unsubscribe(
  topic: string
): Promise<void>