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

@obtrace/sdk

v2.1.0

Published

Obtrace backend JavaScript SDK for Node.js and Bun

Downloads

36

Readme

@obtrace/sdk

Backend JavaScript SDK for Obtrace — Node.js, Bun, and Supabase Edge Functions.

Install

npm install @obtrace/sdk

Exports

| Entry point | Function | Runtime | |---|---|---| | @obtrace/sdk/node | initNodeSDK | Node.js, Bun | | @obtrace/sdk/supabase | initSupabaseSDK (auto-init) | Supabase Edge Functions (Deno) |

Browser SDK: @obtrace/browser

Node.js / Bun

import { initNodeSDK } from "@obtrace/sdk/node";

const sdk = initNodeSDK({
  apiKey: process.env.OBTRACE_API_KEY!,
  serviceName: "my-api",
});

Supabase Edge Functions

One-line auto-init

Add a single import to each edge function — the SDK reads OBTRACE_API_KEY and OBTRACE_SERVICE_NAME from Deno env automatically:

// supabase/functions/my-function/index.ts
import "@obtrace/sdk/supabase";

Deno.serve(async (req) => {
  // your function code — telemetry is captured automatically
  return new Response("ok");
});

Set the secrets in Supabase dashboard (Project Settings > Edge Functions > Secrets):

OBTRACE_API_KEY=obt_live_xxxxx
OBTRACE_SERVICE_NAME=my-edge

Explicit init

For full control over configuration:

import { initSupabaseSDK } from "@obtrace/sdk/supabase";

const sdk = initSupabaseSDK({
  apiKey: Deno.env.get("OBTRACE_API_KEY")!,
  serviceName: "my-edge",
});

sdk.log("info", "function invoked");

Shared init file pattern

For multiple edge functions, create a shared init file:

// supabase/functions/_shared/obtrace.ts
import "@obtrace/sdk/supabase";

Then import in each function:

// supabase/functions/process-sale/index.ts
import "../_shared/obtrace.ts";

Deno.serve(async (req) => { /* ... */ });

API

sdk.log(level, message, context?)
sdk.metric(name, value, unit?, context?)
sdk.span({ name, attrs?, statusCode?, statusMessage? })
sdk.captureError(error, context?)
sdk.shutdown()

Canonical Metrics

Use SemanticMetrics for metric names normalized by the platform:

import { SemanticMetrics } from "@obtrace/sdk/node";

sdk.metric(SemanticMetrics.runtimeCpuUtilization, 0.42);

Backend Wrappers

Express, Fastify, Hono, Elysia, NestJS, Next.js route handlers.

Docs