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

@silyze/coordinator

v1.0.0

Published

A service state coordinator and log collector interface

Readme

Coordinator Interface

A service state coordinator and log collector interface, built on top of an event-driven logging system.

Installation

npm install @silyze/coordinator @silyze/logger @silyze/typed-event-target

Overview

The Coordinator class provides:

  • Typed events for logs (LogEvent) and service status changes (StatusEvent).
  • A scoped logger (CoordinatorLogger) that emits LogEvent instances.
  • Abstract methods to manage and observe service states.

Use it as a base class for any component that needs to coordinate multiple services and collect their logs in a type-safe, event-driven fashion.

Basic Usage

import {
  Coordinator,
  ServiceStatus,
  CoordinatorLog,
} from "@silyze/coordinator";

class MyCoordinator extends Coordinator {
  get url() {
    return "https://api.example.com";
  }

  async setServiceStatus(
    resourceId: string,
    service: string,
    status: ServiceStatus
  ) {
    // update internal state or remote store
    this.dispatchEvent(new StatusEvent(resourceId, service, status));
  }

  async getServiceStatus(
    resourceId: string,
    service: string
  ): Promise<ServiceStatus | null> {
    // retrieve state
    return null;
  }

  async waitForServiceStatus(
    resourceId: string,
    service: string,
    expectedStatus: ServiceStatus
  ) {
    // optional: wait until a StatusEvent matches expectedStatus
  }
}

const coordinator = new MyCoordinator();

// Listen for logs
coordinator.addEventListener("log", (evt) => {
  console.log(`[${evt.log.severity}] ${evt.log.area}: ${evt.log.message}`);
});

// Listen for status changes
coordinator.addEventListener("status", (evt) => {
  console.log(`Service ${evt.service} is now ${evt.status}`);
});

// Create a scoped logger
const logger = coordinator.createLogger("resource-123");
logger.log({
  severity: "info",
  area: "startup",
  message: "Coordinator started",
});

// Emit a service status
await coordinator.setServiceStatus("resource-123", "database", "running");

API Reference

Types

  • ServiceStatus: "running" | "stopped"

  • CoordinatorLog:

    interface CoordinatorLog {
      context: LoggerContext;
      severity: LogSeverity;
      message: string;
      area: string;
      object?: unknown;
    }

Classes

class LogEvent extends Event

Emitted when a log entry is created.

  • Properties:

    • resourceId: string | undefined
    • log: CoordinatorLog
    • shouldDistribute: boolean

class StatusEvent extends Event

Emitted when a service status changes.

  • Properties:

    • resourceId: string
    • service: string
    • status: ServiceStatus

abstract class Coordinator implements TypedEventTarget<LogEvent | StatusEvent, "log" | "status">

Base class for coordinating services and collecting logs.

  • Event Methods:

    • addEventListener(type: "log" | "status", listener): void
    • removeEventListener(type: "log" | "status", listener): void
    • dispatchEvent(event: LogEvent | StatusEvent): boolean
  • Abstract Methods (must be implemented):

    • setServiceStatus(resourceId: string, service: string, status: ServiceStatus): Promise<void>
    • getServiceStatus(resourceId: string, service: string): Promise<ServiceStatus | null>
    • waitForServiceStatus(resourceId: string, service: string, expectedStatus: ServiceStatus): Promise<void>
    • get url(): string
  • Helper:

    • createLogger(resourceId?: string, ...loggers: Logger[]): Logger

      • Returns a combined logger that emits LogEvents and delegates to any provided Logger instances.