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

autotel-devtools

v2.0.3

Published

Standalone OTLP receiver with web UI for local development

Downloads

926

Readme

autotel-devtools

Standalone OTLP receiver with web UI for local development. Think TanStack Devtools for OpenTelemetry.

Overview

autotel-devtools provides two modes:

  1. Standalone OTLP Receiver - Run as CLI to receive OpenTelemetry data
  2. Embeddable Widget - Add a devtools panel to your web app
┌─────────────────────────────────────────────┐
│  Standalone Mode                            │
│                                             │
│  npx autotel-devtools                       │
│  ┌───────────────────────────────────────┐ │
│  │  HTTP Server (port 4318)               │ │
│  │  ├── POST /v1/traces  ← OTLP JSON     │ │
│  │  ├── POST /v1/logs     ← OTLP JSON     │ │
│  │  ├── POST /v1/metrics  ← OTLP JSON     │ │
│  │  ├── GET  /            → Full page UI  │ │
│  │  ├── GET  /widget.js   → Widget bundle │ │
│  │  ├── GET  /healthz     → Health check  │ │
│  │  └── WS   /ws          ←→ WebSocket    │ │
│  └───────────────────────────────────────┘ │
└─────────────────────────────────────────────┘

Quick Start

Standalone Mode

# Run the OTLP receiver
npx autotel-devtools

# Configure your app to send to it
OTEL_EXPORTER_OTLP_PROTOCOL=http/json \
OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318 \
node app.js

Open http://localhost:4318 to see traces, logs, and metrics.

Embedded Widget

Add the widget to your web app:

<script src="http://localhost:4318/widget.js"></script>
<autotel-devtools></autotel-devtools>

Or programmatically:

<script>
  // Mount the widget manually
  const container = document.createElement('div');
  document.body.appendChild(container);

  // Auto-detect WebSocket URL
  const script = document.currentScript;
  const widgetUrl = new URL(script.src);
  const wsUrl = `ws://${widgetUrl.host}/ws`;

  // Widget opens as a floating panel
</script>

Programmatic API

Use in Node.js with autotel:

import { init, trace } from 'autotel';
import { createDevtools } from 'autotel-devtools';

const { server, httpServer, exporter, port, close } = createDevtools({
  port: 4318,
  verbose: true,
});

// Wire up to autotel
init({
  service: 'my-app',
  endpoint: 'http://localhost:4318',
  spanProcessors: [exporter], // Stream to devtools
});

// Your traced code
const myFunction = trace((ctx) => async () => {
  // ... this span appears in devtools
});

Architecture

Server (Node.js)

  • DevtoolsServer - WebSocket server + in-memory data store
  • HTTP Routes - OTLP receivers for traces/logs/metrics
  • Exporters - OpenTelemetry span/log exporters

Widget (Preact)

  • Shadow DOM - Isolated styles, no conflicts with app CSS
  • Preact Signals - Reactive state management
  • Views - Traces, Logs, Metrics, Errors, Resources, Service Map

Features

Implemented

  • ✅ Real-time OTLP ingestion (traces, logs, metrics)
  • ✅ WebSocket streaming with history replay
  • ✅ Traces view with waterfall + flame graph
  • ✅ Logs view with severity/resource filtering
  • ✅ Error aggregation and grouping
  • ✅ Service map visualization
  • ✅ Resources view (derived from telemetry)
  • ✅ Search with debounce (300ms)
  • ✅ Configurable telemetry limits (env vars)
  • ✅ Widget position persistence (localStorage)
  • ✅ Export traces as JSON
  • ✅ Custom element support (<autotel-devtools>)

Configuration

Environment Variables

AUTOTEL_MAX_TRACE_COUNT=10000    # Max traces to keep (default: 100)
AUTOTEL_MAX_LOG_COUNT=10000      # Max logs to keep (default: 100)
AUTOTEL_MAX_METRIC_COUNT=50000   # Max metrics to keep (default: 100)
AUTOTEL_DEVTOOLS_PORT=4318       # Server port (default: 4318)
AUTOTEL_DEVTOOLS_HOST=127.0.0.1  # Bind host (default: 127.0.0.1)
AUTOTEL_DEVTOOLS_TITLE="My App"  # Dashboard title (optional)

CLI Options

npx autotel-devtools --port 4319 --host 0.0.0.0

Options:

  • --port, -p - Port to listen on (default: 4318)
  • --host, -H - Host to bind to (default: 127.0.0.1)
  • --title, -t - Dashboard title

License

MIT