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

@inngest/otel

v0.2.1

Published

OpenTelemetry instrumentation helpers for Inngest

Readme

@inngest/otel

OpenTelemetry instrumentation helpers for Inngest.

Use this package when you want a turnkey Node OpenTelemetry setup for Inngest. It installs the supported instrumentation before app code starts.

This isn't the only supported way to use Inngest with OpenTelemetry. It's also valid to configure OpenTelemetry yourself when you need direct control over providers, exporters, sampling, resources, or instrumentation lists.

Instrumentation

This preload registers:

  • Common Node.js library instrumentation from @opentelemetry/auto-instrumentations-node
  • OpenAI instrumentation from @traceloop/instrumentation-openai
  • Anthropic instrumentation from @traceloop/instrumentation-anthropic
  • Google Generative AI instrumentation from @traceloop/instrumentation-google-generativeai

@google/genai v2 isn't currently supported by the Traceloop Google Generative AI instrumentation.

Usage

The supported public entrypoint is @inngest/otel/node, which resolves to the right runtime file for the loader being used.

The recommended preload path is the Node --import flag:

node --import @inngest/otel/node ./app.js

Use --import whenever possible. It loads instrumentation before your app, including CommonJS entrypoints.

To choose a module format explicitly, use the format-specific preload path:

node --import @inngest/otel/node.mjs ./app.js
node --require @inngest/otel/node.cjs ./app.cjs

If --import isn't an option, use a small bootstrap file that loads instrumentation before loading your app:

import "@inngest/otel/node";
await import("./app.js");