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 🙏

© 2024 – Pkg Stats / Ryan Hefner

instrument

v1.0.7

Published

Tool to capture calls to Node.js native modules

Downloads

265

Readme

Instrument

npm node-current GitHub license PRs Welcome Language grade: JavaScript

A tool that collects information about calls made to Node.js native modules.

Installation

To add it as a development dependency run:

npm i instrument --save-dev

Usage

Loading it programatically (using default configuration):

require('instrument')()

You can also include it by using the -r or --require flag in your command:

$ node -r instrument/config my-app.js

Configuration

instrument accepts a configuration object if it's being loaded programatically or you could create a instrument.config.js file in case you're including it via the --require flag.

Example of a instrument.config.js file:

module.exports = {
  summary: true,
  frequency: true,
  output: 'my-instrumentation-logs.txt'
}

Configuration properties

dependencies

Specifies if dependencies should be instrumented. Default value is false.

summary

Enable this property to print a summary of the instrumented calls that were captured. Default value is true.

structured

It changes the log output to be JSON formatted. Default value is false.

frequency

In case "summary" property is set to true, then also prints a frequency indicator for each call.

output

If you want to avoid printing the output to stdout you can specify a file to be used for logging.

modules

It accepts an array of the native modules you want to be instrumented. Default values are ["child_process","http","https","fs","require"].

runtimeLogs

Enables or disables the logging at runtime for instrumented calls. Default value is false.

License

MIT