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

@selfage/service_handler

v7.5.6

Published

Http-based service handlers on top of expressjs.

Downloads

62

Readme

@selfage/service_handler

Implement a fully typed Express service without touching raw request parsing.

Why @selfage/service_handler

@selfage/service_handler is the runtime companion to @selfage/generator_cli. The generator emits strongly typed TypeScript interfaces that describe your remote calls, and this package gives you the glue to implement and register them in production in two simple moves:

  1. Implement a strongly typed handler – extend the generated base class and focus solely on business logic.
  2. Register handlers and start the service – mount them on Express without writing any serialization or routing boilerplate.

The @selfage/generator_cli README shows how a single YAML definition yields service descriptors, handler interfaces, and message types. Once you have that output, this package handles everything else.

Install

npm install @selfage/service_handler

Step 1: Implement your handler with strong types

import {
  GetCommentsHandlerInterface,
  GetCommentsRequestBody,
  GetCommentsResponse,
} from "./generated/node_handlers";

class GetCommentsHandler extends GetCommentsHandlerInterface {
  public async handle(
    loggingPrefix: string,
    body: GetCommentsRequestBody,
  ): Promise<GetCommentsResponse> {
    return { texts: ["aaaa", "bbb", "cc"] };
  }
}

The generated interface enforces the request and response schema at compile time and at runtime. You never call JSON.parse, handle headers manually, or guess the shape of the payload—the BaseRemoteCallHandler inside this package deserializes it for you.

Step 2: Register handlers and start your service

import express = require("express");
import http = require("http");
import { ServiceHandler } from "@selfage/service_handler";
import { NODE_SERVICE } from "./generated/node_service";

async function main() {
  const app = express();
  const httpServer = http.createServer();

  const service = ServiceHandler.create(httpServer, "*", app)
    .addCorsAllowedPreflightHandler()
    .addMetricsHandler()
    .addHealthCheckHandler()
    .addReadinessHandler()
    .addHandlerRegister(NODE_SERVICE)
    .add(new GetCommentsHandler());

  await service.start(8080);
}

main();

ServiceHandler wires the generated descriptors into Express, attaches CORS headers, collects metrics, and exposes health endpoints.

What you get out of the box

  • Typed request handling – JSON, streaming, metadata, and auth headers are all parsed and validated using the generated descriptors.
  • Production diagnostics – Prometheus counters (remote_calls_total, remote_calls_failure) plus optional /metricsz, /healthz, and /readiness routes.
  • Express integration – leverage familiar middleware while keeping your RPC layer type-safe.
  • Logging and error handling – every request carries a unique log prefix and converts unexpected failures into structured HTTP responses.

You can browse service_handler_test.ts and the fixtures in test_data/ for end-to-end scenarios covering uploads, JSON clients, and metadata-authenticated calls.