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

@nanotrace/sdk

v0.1.2

Published

TypeScript SDK for sending traces, logs, metrics, and spans to Nanotrace.

Readme

Nanotrace TypeScript SDK

The SDK shapes application events into Nanotrace's /v1/events contract.

It uses camelCase public parameters and emits schema fields such as event_type, trace_id, duration_ms, and http.status_code. OpenTelemetry-style dotted attributes can be passed directly.

Event methods are fire-and-forget. The client batches events in process by count, byte size, or a short flush interval, then posts a JSON array to the ingest API. Call flush() when you need to wait for delivery.

import { createNanotrace, httpTransport } from '@nanotrace/sdk'

const nt = createNanotrace({
  transport: httpTransport({
    url: process.env.NANOTRACE_URL!,
    key: process.env.NANOTRACE_KEY!
  }),
  service: 'checkout-api',
  environment: 'prod'
})

const span = nt.span('POST /checkout')
try {
  nt.counter('checkout.attempts')
  nt.measure('checkout.latency', 183, {
    metricUnit: 'ms',
    plan: 'pro',
    country: 'US',
    llm: { model: 'gpt-4.1-mini' }
  })
  nt.info('checkout started')
  span.end({ spanStatusCode: 'ok' })
} catch (error) {
  span.end({ spanStatusCode: 'error', isError: 1 })
  throw error
}

await nt.flush()

measure(name, value, fields) is a convenience alias for a histogram metric event. SDK calls emit facts only; tenant definitions choose whether those facts materialize into metric rollups, measure cubes, funnels, cohorts, or raw/KV query paths.

Use the UDP transport with the Rust sidecar:

import { createNanotrace, udpTransport } from '@nanotrace/sdk'

const nt = createNanotrace({
  transport: udpTransport({ port: 4319 })
})

Use local HTTP with the Rust sidecar when UDP is not convenient:

import { createNanotrace, sidecarHttpTransport } from '@nanotrace/sdk'

const nt = createNanotrace({
  transport: sidecarHttpTransport({ url: 'http://127.0.0.1:4320' })
})

Use the sidecar when you need local disk spool, host-level enrichment, egress control, or shared fleet policy. For most server apps, direct httpTransport is the easiest starting point because batching, retry surfacing through flush(), and endpoint shape are handled by the SDK.