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

@autter/runtime-node

v1.0.0

Published

Autter Runtime for Node.js: same-origin browser relay handler + curated OpenTelemetry server tracker

Readme

@autter/runtime-node

Autter Runtime for Node.js — two halves in one package:

  1. Same-origin browser relay for @autter/runtime-browser
  2. Curated OpenTelemetry server tracker exporting OTLP/HTTP JSON

Install

npm install @autter/runtime-node

1. Browser relay

The browser tracker posts to your backend; this handler validates and whitelist-sanitises the payload, attaches your private ingest key server-side, forwards asynchronously, and returns 202 immediately.

Express / Node http:

import { createBrowserRelayHandler } from "@autter/runtime-node";

app.post(
  "/api/autter-runtime",
  createBrowserRelayHandler({ apiKey: process.env.AUTTER_RUNTIME_KEY! }),
);

Next.js App Router / any fetch-style runtime:

import { createBrowserRelayFetchHandler } from "@autter/runtime-node";

export const POST = createBrowserRelayFetchHandler({
  apiKey: process.env.AUTTER_RUNTIME_KEY!,
});

Options: endpoint (default https://otlp.autter.dev), maxBodyBytes (default 64 KB), onError.

2. Server tracker

// instrument.ts — must run before anything else creates connections
import { initAutterServer } from "@autter/runtime-node";

const autter = initAutterServer({
  apiKey: process.env.AUTTER_RUNTIME_KEY!,
  service: "payments-api",
  environment: process.env.NODE_ENV,
  release: process.env.GIT_SHA,
});

// handled errors — always recorded, never sampled out:
autter.captureException(err, { "order.id": "…" });

// warnings/info without an exception — same grouping+aggregation as
// errors, just a lower severity ("fatal" | "error" | "warning" | "info"):
autter.captureMessage("Legacy /orders lookup used", "warning");

// graceful shutdown flushes exporters:
await autter.shutdown();

Run it first: node --require ./instrument.cjs server.js (CJS), or for pure-ESM apps add OTel's loader hook (node --import ./instrument.mjs --experimental-loader=@opentelemetry/instrumentation/hook.mjs server.js) so http auto-instrumentation can patch ESM imports.

Defaults (cheap by construction):

| Signal | Default | | --- | --- | | Captured/unhandled exceptions | 100% (dedicated always-on tracer) | | Traces | 1% head sampling (traceSampleRate) | | Request metrics | exported every 60 s | | Logs | not collected |

Crashes are observed via process.uncaughtExceptionMonitor, which does not change your process's exit behaviour; the final flush is best-effort. Framework instrumentations are opt-in:

import { ExpressInstrumentation } from "@opentelemetry/instrumentation-express";
initAutterServer({ ..., instrumentations: [new ExpressInstrumentation()] });

Note on usage rollups: requests are counted from the http.server.duration metric (100% accurate) and additionally from sampled server spans. At the default 1% sampling the span contribution is negligible; if you set traceSampleRate: 1 in development, expect request counts roughly doubled.