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

exception-formatter

v2.1.2

Published

[![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg)](https://github.com/semantic-release/semantic-release) [![Build Status](https://travis-ci.org/benbria/exception-formatter.svg?branch=master)](ht

Downloads

251,172

Readme

semantic-release Build Status Coverage Status

What is it?

exception-formatter is an NPM package that takes exceptions or stack traces that would normally look like this:

and makes them look like this:

or, in HTML, like this:

Features

  • Automatically highlights your code (as opposed to included modules or node.js system libraries) since your code is likely where the problem is.
  • Strips leading project paths to make exceptions more readable.
  • Can read longjohn and streamline async stacks.

Installation

npm install --save exception-formatter

Usage

exceptionFormatter = require('exception-formatter');
console.log( exceptionFormatter(err, options) );

Where err is either an Error, a {stack} object, or a string containing a stack trace. options is an optional parameter containing the following:

  • options.format - one of 'ascii', 'ansi', 'html'. 'ascii' and 'ansi' are identical, except that 'ansi' will use ANSI color codes to highlight lines.
  • options.maxLines - The maximum number of lines to print from the exception. 0 or null for unlimited (the default.) "auto" to truncate after the last line in your source code.
  • options.basepath - this is your project's root folder. If you're writing code in src/myFile.js, then this should be path.resolve(__dirname, '..'). This path will be stripped from the start of every filename in the exception, and is also used to help decide which code is "your code" and which is not. If this is not provided, then process.cwd() is used by default.
  • options.basepathReplacement - String used to replace the basepath. Defaults to "./".
  • options.colors - (Only for format = 'ansi') If true (the default) then lines which are "your code" will be bolded and colorized. If false, then lines will only be bolded.
  • options.inlineStyle - (Only for format = 'html') If this option is true, then each line will be styled with inline style attributes. If false, each line will be given a class instead and you can do your own styling. Note that inline styline is usually required if you want to email an exception, since email clients will generally ignore style sheets.

"Your Code"

exception-formatter will mark code as "your code" if it is in options.basepath, and if it does not contain node_modules anywhere in it's path.