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

tmp-debug

v0.12.5

Published

Debug node applications with tmp files.

Readme

tmp-debug NPM version Downloads Build Status Coveralls Status

Debug node applications with tmp files.

Motivation

While trying to understand how a daemon application worked, I wasn't able to debug with node-inspector very easily. The daemon also detached io streams, making console log/error a non starter. I ended up writing to a tmp file and decided to publish a module around it.

Here's some sample output that was written to a file:

Installing

It's recommended to install tmp-debug globally:

npm install -g tmp-debug

Usage

Programatically

var tmpDebug = require('tmp-debug')('log.txt');

tmpDebug.logStackTrace();
tmpDebug.log('foo');
function someFn() {
  tmpDebug.logArgs(arguments);
}
someFn();

Instrumenting

tmp-debug ./some/directory

All javascript files found in the directory will be instrumented with tmpDebug.logArgs(arguments); in every function found therein.

Viewing

Once you're logging, you can view the file output in the following ways:

  • tail -f /tmp/log.txt
  • less -R /tmp/log.txt

Configuring

Place .tmpdebugrc on your path.

Example Config File

{
  "enabled": true,
  "filters": [
    {
      "file": "optional/path/some-file.js",
      "functionName": "someFunctionName",
      "line": 50,
      "column": 30
    }
  ],
  "outputDepth": 3
}

filters

An array of filter objects that control what gets logged.

  • file filters files that end with it's value.
  • functionName filters functions that end with it's value.
  • line filters functions that occor on this line.
  • column filters functions that occur on this column.

outputDepth

An integer controlling how many levels deep inspected objects will be logged.

##LICENSE

The MIT License (MIT)

Copyright (c) 2015 jsdevel

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.