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

stack-utils

v2.0.6

Published

Captures and cleans stack traces

Downloads

111,509,972

Readme

stack-utils

Captures and cleans stack traces.

Linux Build Build status Coverage

Extracted from lib/stack.js in the node-tap project

Install

$ npm install --save stack-utils

Usage

const StackUtils = require('stack-utils');
const stack = new StackUtils({cwd: process.cwd(), internals: StackUtils.nodeInternals()});

console.log(stack.clean(new Error().stack));
// outputs a beautified stack trace

API

new StackUtils([options])

Creates a new stackUtils instance.

options

internals

Type: array of RegularExpressions

A set of regular expressions that match internal stack stack trace lines which should be culled from the stack trace. The default is StackUtils.nodeInternals(), this can be disabled by setting [] or appended using StackUtils.nodeInternals().concat(additionalRegExp). See also ignoredPackages.

ignoredPackages

Type: array of strings

An array of npm modules to be culled from the stack trace. This list will mapped to regular expressions and merged with the internals.

Default ''.

cwd

Type: string

The path to the current working directory. File names in the stack trace will be shown relative to this directory.

wrapCallSite

Type: function(CallSite)

A mapping function for manipulating CallSites before processing. The first argument is a CallSite instance, and the function should return a modified CallSite. This is useful for providing source map support.

StackUtils.nodeInternals()

Returns an array of regular expressions that be used to cull lines from the stack trace that reference common Node.js internal files.

stackUtils.clean(stack, indent = 0)

Cleans up a stack trace by deleting any lines that match the internals passed to the constructor, and shortening file names relative to cwd.

Returns a string with the cleaned up stack (always terminated with a \n newline character). Spaces at the start of each line are trimmed, indentation can be added by setting indent to the desired number of spaces.

stack

Required
Type: string or an array of strings

stackUtils.capture([limit], [startStackFunction])

Captures the current stack trace, returning an array of CallSites. There are good overviews of the available CallSite methods here, and here.

limit

Type: number Default: Infinity

Limits the number of lines returned by dropping all lines in excess of the limit. This removes lines from the stack trace.

startStackFunction

Type: function

The function where the stack trace should start. The first line of the stack trace will be the function that called startStackFunction. This removes lines from the end of the stack trace.

stackUtils.captureString([limit], [startStackFunction])

Captures the current stack trace, cleans it using stackUtils.clean(stack), and returns a string with the cleaned stack trace. It takes the same arguments as stackUtils.capture.

stackUtils.at([startStackFunction])

Captures the first line of the stack trace (or the first line after startStackFunction if supplied), and returns a CallSite like object that is serialization friendly (properties are actual values instead of getter functions).

The available properties are:

  • line: number
  • column: number
  • file: string
  • constructor: boolean
  • evalOrigin: string
  • native: boolean
  • type: string
  • function: string
  • method: string

stackUtils.parseLine(line)

Parses a string (which should be a single line from a stack trace), and generates an object with the following properties:

  • line: number
  • column: number
  • file: string
  • constructor: boolean
  • evalOrigin: string
  • evalLine: number
  • evalColumn: number
  • evalFile: string
  • native: boolean
  • function: string
  • method: string

License

MIT © Isaac Z. Schlueter, James Talmage