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

tnt4j-njstrace-plugin

v1.0.0

Published

njstrace formatter for TNT4J-Streams

Readme

Why njstrace with TNT4J streams

Beyond all advantages JKoolCloud offers, njstrace has a nice ability to instrument your node.js application. njstrace "hijacks" node.js Module._compile() method, and then calls to the original Module._compile() with the instrumented code.

In this way you don't need to change your application code to have analytics in your application.

Installation

Install 'tnt4j-njstrace-plugin' to your application with npm.

npm install tnt4j-njstrace-plugin --save 

Simple use tutorial

Put require in your code. As soon as the inject is called njstrace start to work. Since the instrumentation happens when the Module._compile() is called, only modules that are "required" after the call to njstrace.inject() would get instrumented.

var Tnt4JStremsFormatter = require('../../../njsTraceFormatter-tnt4j.js').Tnt4JStremsFormatter;
var njstrace = require('njstrace').inject({	formatter: new Tnt4JStremsFormatter(), inspectArgs: false,
											files: ['**/*.js', '!**/node_modules/**',  '**/node_modules/http-server/**'],});

NOTE: You may want to deactivate argument inspection by inspectArgs=false, because you may start getting large amount of data otherwise.

In this example instrumentation happens on http-server. Put everything you want to instrument in formatter argument; For more information read the njstrace documentation: (https://github.com/ValYouW/njsTrace)