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

trace-amp

v0.0.4

Published

OpenTelemetry instrumentation for [Amp](https://ampcode.com) CLI.

Downloads

274

Readme

trace-amp

OpenTelemetry instrumentation for Amp CLI.

Amp trace in Axiom

Fully vibe coded, use at your own risk.

Installation

npm install -g trace-amp

Usage

Set the required environment variables:

export OTEL_EXPORTER_OTLP_ENDPOINT="https://api.axiom.co/v1/traces"
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer your-api-token,X-Axiom-Dataset=your-dataset"

Then run:

trace-amp "ask the oracle to add 2+2"

Or use npx without installing globally:

npx trace-amp "ask the oracle to add 2+2"

TypeScript Usage

Standalone (new OTel setup)

import { initTracing, shutdownTracing, createAmpClient } from 'instrument-amp';

initTracing({
  serviceName: 'my-amp-agent',
  otlpEndpoint: process.env.OTEL_EXPORTER_OTLP_ENDPOINT,
});

const amp = createAmpClient();
const result = await amp.invoke('What files are in this directory?');

console.log(result.finalResult);

await shutdownTracing();

With existing OTel setup

If you already have OpenTelemetry configured, skip initTracing() - spans will automatically use your existing provider. Pass parentContext to nest Amp spans under an existing trace:

import { trace, context } from '@opentelemetry/api';
import { createAmpClient } from 'instrument-amp';

const amp = createAmpClient();

// Option 1: Amp spans nest under the current active span automatically
await amp.invoke('prompt');

// Option 2: Explicit parent context (e.g., from incoming request)
const parentContext = trace.setSpanContext(context.active(), {
  traceId: requestTraceId,
  spanId: requestSpanId,
  traceFlags: 1,
});
await amp.invoke('prompt', { parentContext });