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

@traceai/vercel

v0.1.0

Published

OpenTelemetry instrumentation for Vercel

Downloads

92

Readme

@traceai/vercel

Future Instrumentation (FI) integration for the Vercel AI SDK.

This package provides a drop-in SpanProcessor that converts Vercel AI SDK spans into the FI OpenTelemetry semantic conventions, ready to be exported to TraceAI or any OpenTelemetry backend.

Installation

npm install @traceai/vercel
# or
yarn add @traceai/vercel
# or
pnpm add @traceai/vercel

Quick-start (Next.js)

1. Create a one-time instrumentation.ts

// instrumentation.ts – import this **once** on the server (e.g. in _app.tsx)
// eslint-disable-next-line @typescript-eslint/ban-ts-comment
// @ts-ignore   @vercel/otel ships without types
import { registerOTel } from "@vercel/otel";
import type { SpanExporter } from "@opentelemetry/sdk-trace-base";

import { diag, DiagConsoleLogger, DiagLogLevel } from "@opentelemetry/api";
import { FISimpleSpanProcessor, isFISpan } from "@traceai/vercel";
import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-grpc";
import { Metadata } from "@grpc/grpc-js";

diag.setLogger(new DiagConsoleLogger(), DiagLogLevel.DEBUG);

export function register() {
  registerOTel({
    attributes: {
      "service.name": "vercel-project",
      project_name: "vercel-project",
      project_type: "observe",
    },
    spanProcessors: [
      new FISimpleSpanProcessor({
        exporter: (() => {
          const metadata = new Metadata();
          metadata.set("x-api-key", process.env.FI_API_KEY as string);
          metadata.set("x-secret-key", process.env.FI_SECRET_KEY as string);

          return new OTLPTraceExporter({
            url: "grpc://grpc.futureagi.com",
            metadata,
          }) as unknown as SpanExporter;
        })(),

        // Export only FI spans produced by the Vercel AI SDK
        spanFilter: isFISpan,
      }),
    ],
  });

  diag.info("OTLP gRPC span processor registered via @vercel/otel");
}

2. Use the tracer in your API / Route handlers

// pages/api/story.ts
import type { NextApiRequest, NextApiResponse } from "next";
import { register as registerTracing } from "../../instrumentation";

import { generateText } from "ai";
import { openai } from "@ai-sdk/openai";

export default async function handler(
  req: NextApiRequest,
  res: NextApiResponse,
) {
  // Safe – subsequent calls are a no-op inside the same runtime
  registerTracing();

  const result = await generateText({
    model: openai("gpt-4o-mini"),
    prompt: "Say hello from a traced function!",
    experimental_telemetry: { isEnabled: true },
  });

  res.status(200).json({ text: result.text });
}

That’s it! Every invocation will emit FI-compliant OpenTelemetry spans you can inspect in the TraceAI dashboard.

Environment variables

# TraceAI telemetry credentials
FI_API_KEY=your_api_key
FI_SECRET_KEY=your_secret_key

API

FISimpleSpanProcessor

new FISimpleSpanProcessor({ exporter, spanFilter? })

Wraps the underlying Vercel AI SDK spans with FI semantic conventions and forwards them to the provided exporter.

Parameters

exporter (required) – any OpenTelemetry SpanExporter
spanFilter? – predicate (span) => boolean to decide which spans to export. Use the exported helper isFISpan to export only FI spans.

isFISpan(span)

Utility predicate that returns true if the span already contains FI semantic conventions.

Support

For support, please open an issue in our GitHub repository.