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

@momsfriendlydevco/crash

v0.0.10

Published

Error utilities and prettifier

Downloads

16

Readme

@MomsFriendlyDevCo/Crash

Nicer error reporting with colors and blackboxing.

var crash = require('@momsfriendlydevco/crash');

crash.trace(new Error('Nope!'));

API

crash.trace(error, options)

Output an error or string with colors and stack tracing.

crash.generate(error, options)

Shorthand function for calling trace with {output: false} as a default option. Use this if only the raw text (ANSI wrapped if {colors: true}) is required but not to be immediately output to STDERR.

crash.stop(error, options)

Similar to crash.trace() but immediately terminate the process, halting all execution

crash.decode(error, options)

Decode a string stack trace into its component parts.

crash.defaults

Default options when rendering.

Valid options are:

| Option | Type | Default | Description | |-----------------------|------------|----------------|----------------------------------------------------------------| | logger | function | console.warn | Actual outputter, used when writing the error | | prefix | string | "ERROR" | Prefix string used when outputting the error | | colors | object or boolean | See code | Lookup object of colors used for each part of an error message. If falsy all colors (and ANSI output) is disabled | | text | object | See code | Various text strings used in error messages | | padding | object | See code | Various text padding options | | ignorePaths | RegExp | See code | Path RegExps to blackbox (remove from trace output) | | filterUnknown | boolean | true | Filter out grarbage stack trace lines | | parsers | array <Object> | See code | Collection of parsers, which are executed in order until one matches | | supportBabel | boolean | true | Add support for decoding Babel parser errors | | context | object | See below | Options for configuring code-showing context (preview lines of code) | | context.above | boolean | true | Show an indicator above the target line | | context.below | boolean | true | Show an indicator below the target line | | context.linesBefore | number | 1 | How many lines before the target line to output when showing context | | context.linesAfter | number | 1 | How many lines after the target line to output when showing context | | context.pathRewrite | function | path => path | How to mangle the input file path before reading it to show context |