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

intellim-node-sdk

v1.1.0

Published

One-line auto-instrumentation for Node.js/Express apps — traces, metrics, and error logs sent to an IntelliM backend, with distributed trace propagation across services.

Readme

intellim-node-sdk

One-line auto-instrumentation for Node.js / Express applications, reporting to a IntelliM backend.

Install

npm install intellim-node-sdk

Usage

const intellim = require("intellim-node-sdk");

const { middleware } = intellim.init({
  serviceName: "my-app",
  backendUrl: "https://your-intellim-backend.example.com",
  apiKey: "your-api-key",   // or set INTELLIM_API_KEY in the environment
});

app.use(middleware);

That's it — every request handled after this point is automatically traced.

What gets captured automatically

  • Per request: route, method, status, duration → sent as a trace
  • Per request: response time → sent as a metric
  • Errors and slow requests (4xx/5xx, or over 1s) → sent as log lines
  • Every 10 seconds: app-level rollups — memory usage, average response time, request throughput, error rate

Distributed tracing across services

If this app calls another IntelliM-instrumented service over HTTP, the current request's trace ID is automatically propagated onto that outgoing call — no extra code needed. The two services' spans show up correlated under one trace in the IntelliM dashboard, instead of two disconnected traces.

This works by patching Node's core http/https modules (not by patching whatever HTTP client library your app happens to use) — the two SDK instances a service and the app it calls each have their own separate copy of a package like axios, but there is only ever one http module in a given Node process, so that's what reliably carries the trace context across the boundary regardless of which library made the actual call.

Configuration

| Option | Required | Default | Notes | |---------------|----------|-----------------------------|---------------------------------------------| | serviceName | No | "unknown-service" | Shows up as this service's name everywhere | | backendUrl | No | http://localhost:3001 | Your IntelliM backend's URL | | apiKey | No* | process.env.INTELLIM_API_KEY | *Required for any data to actually be accepted — falls back to the env var if not passed explicitly | | debug | No | false | Logs [NexusRUM]-style debug lines to the console |

License

MIT