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

@pumped-fn/lite-extension-otel

v1.0.0

Published

OpenTelemetry extension for @pumped-fn/lite with tracing and context propagation

Readme

@pumped-fn/lite-extension-otel

OpenTelemetry tracing extension for @pumped-fn/lite with self-contained provider management.

Installation

pnpm add @pumped-fn/lite-extension-otel

Usage

import { createScope, flow } from "@pumped-fn/lite"
import { otel, otelConfig } from "@pumped-fn/lite-extension-otel"

const scope = createScope({
  extensions: [otel()]
})

scope.setTag(otelConfig.name, "my-app")
scope.setTag(otelConfig.url, "http://localhost:4318/v1/traces")
scope.setTag(otelConfig.type, "http")

await scope.ready

const myFlow = flow({
  name: "processOrder",
  factory: async (ctx) => {
    return { orderId: "123" }
  }
})

const ctx = scope.createContext()
await ctx.exec({ flow: myFlow })
await ctx.close()

Configuration Tags

| Tag | Type | Default | Description | |-----|------|---------|-------------| | otelConfig.name | string | "default-app" | Service name for spans | | otelConfig.url | string | "http://localhost:4318/v1/traces" | OTLP collector URL | | otelConfig.type | "http" \| "grpc" \| "console" | "console" | Exporter type | | otelConfig.captureResults | boolean | true | Capture operation results in spans | | otelConfig.redact | boolean | false | Redact sensitive data (per-execution) |

Redacting Sensitive Data

Set the redact tag on the execution context to prevent result capture:

const ctx = scope.createContext()
ctx.data.setTag(otelConfig.redact, true)
await ctx.exec({ flow: sensitiveFlow })

Architecture

sequenceDiagram
    participant Scope
    participant Ext as otel Extension
    participant ALS as AsyncLocalStorage
    participant Provider as TracerProvider

    Scope->>Ext: init(scope)
    Ext->>Ext: Read config from tags
    Ext->>Provider: Create provider + exporter

    Scope->>Ext: wrapExec(next, target, ctx)
    Ext->>ALS: getStore() → parent context
    Ext->>Provider: startSpan(name, parent)
    Ext->>ALS: run(newContext, next)
    ALS-->>Ext: result
    Ext->>Provider: span.end()

    Scope->>Ext: dispose()
    Ext->>Provider: shutdown()