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

@bluecadet/launchpad-observability

v4.0.1

Published

Observability plugin for @bluecadet/launchpad — exports logs and metrics to external backends

Readme

@bluecadet/launchpad-observability

Exports Launchpad logs and current-state gauges to endpoints you control. Built-in destinations support OTLP/HTTP JSON or protobuf and Grafana Loki; the legacy transport API remains available.

Documentation

See the observability documentation for configuration, the signal catalog, privacy limits, delivery semantics, and migration guidance.

Installation

npm install @bluecadet/launchpad

OTLP quick start

import { defineConfig } from '@bluecadet/launchpad/cli';
import { observability } from '@bluecadet/launchpad/observability';
import { createOtlpDestination } from '@bluecadet/launchpad/observability/destinations/otlp';

const endpoint = process.env.LAUNCHPAD_OBSERVABILITY_ENDPOINT;
if (!endpoint) throw new Error('LAUNCHPAD_OBSERVABILITY_ENDPOINT is required');

export default defineConfig({
  plugins: [
    observability({
      // Optional. Omit resource to use service.name = 'launchpad'.
      resource: { 'service.name': 'museum-kiosk' },
      destinations: [
        createOtlpDestination({
          endpoint,
          encoding: 'protobuf',
          token: process.env.LAUNCHPAD_OBSERVABILITY_TOKEN,
        }),
      ],
    }),
  ],
});

resource is an optional flat record of string, finite number, and boolean attributes. Launchpad defaults service.name to launchpad and generates service.instance.id at runtime. Other attributes are caller-defined.

The OTLP destination uses native fetch and sends logs and metrics to /v1/logs and /v1/metrics. The example selects binary OTLP/HTTP protobuf, not gRPC; the recipient must support that encoding. Omit encoding to use the default JSON encoding. JSON requests and responses use Content-Type: application/json, while protobuf requests and responses use Content-Type: application/x-protobuf. Both encodings use the same endpoint paths, authentication, batching, resources, partial-success handling, and retries. Selecting an encoding does not enable payload compression or configure global OpenTelemetry providers.

The destination defaults to both signals. Metrics default to a 30-second observation interval and are independent of log event filters.

No telemetry is sent to Bluecadet automatically. Configured destinations use the controller's retained canonical JSONL and atomic checkpoints by default, preserving original timestamps and resource snapshots across replay. New destinations backfill from the oldest retained record, which can increase ingestion costs or encounter backend timestamp rejection. Set logStorage: { type: 'memory' } for ephemeral delivery or custom exporters without replay support. File delivery captures canonical records, not every raw custom bus event, and never falls back to memory if the source is unavailable. It is not exactly once or lossless: ambiguous acknowledgements can duplicate records, and retention, disk failures, or backend rejection can lose them. Metrics remain latest-state in-memory snapshots. Review application logs and destination retention before enabling export; key-based redaction cannot detect every secret.

Loki

Use createLokiDestination from @bluecadet/launchpad-observability/destinations/loki for structured, versioned JSON log lines. It maps only service.name to the service_name stream label by default; configure resourceLabels to replace that map. Use createLokiTransport from @bluecadet/launchpad-observability/transports/loki to preserve the legacy plain-text format.

Destination mode and legacy { transports } mode cannot be combined in one plugin configuration.

License

ISC