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

@ron2395/upstream-breaker

v0.1.0

Published

A lightweight, event-driven circuit breaker for async dependencies like services, databases, queues, and SDKs.

Readme

service-fuse

A flexible circuit breaker for async dependencies (services, databases, queues, SDKs)

This library is built for real systems: APIs that sometimes fail, partial outages, maintenance windows, and the need to observe what is happening without guessing.

It is intentionally simple on the surface and flexible underneath.


Why this exists

Most circuit breaker libraries are either too opinionated, hard to observe, hard to extend, or unsafe in strict TypeScript.

This one is designed to be predictable, observable, testable, and safe in both JavaScript and TypeScript.

No background threads. No magic retries. No hidden state.


Features

  • Window‑based failure tracking (default)
  • Pluggable failure tracking strategies
  • In‑memory store by default (custom stores supported)
  • Half‑open / probe recovery
  • Manual trip support
  • Structured events for logging & metrics
  • First‑class TypeScript support
  • Zero‑config JavaScript usage

Installation

npm install @ron2395/service-fuse

Basic usage

import { createCircuitBreaker } from '@ron2395/service-fuse';

const breaker = createCircuitBreaker({
  config: {
    failureThreshold: 5,
    failureWindow: 10_000,
    openWindowMs: 30_000,
    probeAfterMs: 5_000,
    requiredSuccessStreak: 2,
  },
});

await breaker.execute('payments-api', async () => {
  return callUpstream();
});

Handling open circuits

When a circuit opens, calls are short‑circuited and a CircuitOpenError is thrown immediately.

import { CircuitOpenError } from '<your-package-name>';

try {
  await breaker.execute('payments-api', callUpstream);
} catch (err) {
  if (err instanceof CircuitOpenError) {
    console.log('Retry after:', new Date(err.openUntil));
    return;
  }
  throw err;
}

Probe & recovery

After opening, the circuit allows a single probe request. If it succeeds, the circuit closes. If it fails, the circuit opens again.

This allows safe and gradual recovery.


Events & observability

The breaker emits structured events for logging and metrics.

onEvent(event) {
  switch (event.type) {
    case 'open':
      console.log('Circuit opened', event.identifier);
      break;
    case 'failure':
      console.log('Failure count', event.failureCount);
      break;
  }
}

Custom failure logic

By default, every error counts as a failure.

You can customize this easily.

Example: only fail on 5xx

await breaker.execute('api', async () => {
  const res = await callUpstream();
  if (res.status >= 500) {
    throw new Error('Server error');
  }
  return res;
});

Advanced: custom failure tracker

createCircuitBreaker({
  config,
  createFailureTracker: (cfg) => new MyFailureTracker(cfg),
});

Manual trip

breaker.tripImmediately('payments-api', 'manual_trip');

License

MIT