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 🙏

© 2025 – Pkg Stats / Ryan Hefner

examination

v0.1.0

Published

Thoroughly examine the state of a Node.js process

Downloads

7

Readme

examination

Current Version Build Status via Travis CI Dependencies

belly-button-style

Thoroughly examine the state of a Node.js process. examination allows a heap snapshot, diagnostics report, and core dump to be generated and written to an output directory with a single function call.

Basic Usage

'use strict';
const Examination = require('examination');

// Dump the report, core, and heap snapshot to the __dirname directory.
Examination({
  directory: __dirname,
  heapdump: true,
  report: true,
  core: true
}, (err) => {
  if (err) {
    // Handle error
  }
});

// Alternatively...

// Create a reusable bound function that only writes a heap snapshot and
// diagnostics report to /tmp/foo.
const bound = Examination.bind(null, {
  directory: '/tmp/foo',
  heapdump: true,
  report: true
}, (err) => { /* Ignore error */ });

bound();

API

examination(options, callback)

  • Arguments
    • options (object) - A configuration object supporting the following schema.
      • directory (string) - The directory where the output files will be written. If this directory (including any parent directories) does not exist, it will be created.
      • heapdump (boolean) - If true, a heap snapshot will be written to directory. Defaults to false.
      • report (boolean) - If true, a diagnostics report will be written to directory. Defaults to false.
      • core (boolean) - If true, an archive containing a core file and all loaded native libraries will be written to directory. Defaults to false. Note that generating these files in particular will take time and consume considerable disk space.
      • error (error) -
    • callback (function) - A function that is called after all artifacts have been created. This function takes the following arguments.
      • err (error) - Represents any error that occurs. Note that the artifacts are created in parallel, so it is possible to receive an error here and still have one or more output files written.
  • Returns
    • Nothing