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

@jennifersoft/jennifer5-instrumentation

v5.6.5

Published

Instrumentation hooks for Jennifer APM

Downloads

52

Readme

@jennifersoft/jennifer5-instrumentation

Node.js APM instrumentation layer for Jennifer5 monitoring system.

Supported Environments

  • Platform: Linux x64 gnu (GLIBC 2.15+), Linux x64 musl
  • Jennifer5 Server: 5.6.5.7 or later
  • Node.js:
    • CommonJS modules: 18.0+
    • ESM modules: 18.19+ or 20.6+
      • This package's ESM setup additionally needs module.register(), which is available from Node.js 20.6.0 and 18.19.0.
      • https://nodejs.org/docs/latest/api/module.html#moduleregisterspecifier-parenturl-options

Installation

Install via NPM

$ # In your Node.js project directory
$ npm install @jennifersoft/jennifer5-instrumentation

Configuration

Copy the jennifer.toml configuration file from the installed package to your Node.js project's working directory:

$ cp node_modules/@jennifersoft/jennifer5-agent/jennifer.toml .

Edit the configuration file with your Jennifer5 server settings:

# jennifer5 server address
server_address = "127.0.0.1"

# jennifer5 server port
server_port = 5000

# domain_id
domain_id = 1000

# instance id, if inst_id is '-1', inst_id will be set by server
inst_id = -1

Running Node.js with Jennifer5 Agent

Option 1: Command Line Arguments

CommonJS application

$ node --require @jennifersoft/jennifer5-instrumentation/auto your_server.js

ESM application

$ node --import @jennifersoft/jennifer5-instrumentation/auto your_server.js

Note (Permission model): If Node.js permission model (--permission) is enabled, add --allow-worker because module.register() requires worker permission.

$ node --permission --allow-worker --import @jennifersoft/jennifer5-instrumentation/auto your_server.js

Option 2: NODE_OPTIONS Environment Variable

CommonJS application

$ export NODE_OPTIONS="--require @jennifersoft/jennifer5-instrumentation/auto"
$ node your_server.js

ESM application

$ export NODE_OPTIONS="--import @jennifersoft/jennifer5-instrumentation/auto"
$ node your_server.js

Note (Permission model): If Node.js permission model (--permission) is enabled, add --allow-worker because module.register() requires worker permission.

$ export NODE_OPTIONS="--permission --allow-worker --import @jennifersoft/jennifer5-instrumentation/auto"
$ node your_server.js

Option 3: Initialize in Entry File

Load Jennifer at the very top of your entry file before other imports.

CommonJS application (your_server.js)

require("@jennifersoft/jennifer5-instrumentation/auto");

ESM application (your_server.js or your_server.mjs)

import "@jennifersoft/jennifer5-instrumentation/auto";

Note (ESM): For the most reliable instrumentation, use Option 1 or Option 2. In ESM, part of the module graph can be resolved or loaded before your entry file body runs. If Jennifer initializes after that point, some modules may be loaded before hooks are registered.