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

@art-suite/art-core-errors

v0.1.4

Published

The Standard Library for JavaScript that aught to be.

Readme

@art-suite/art-core-errors

ErrorWithInfo class for all those times when you need to include data with your thrown error. Also some helpful tools for getting useful information of out stack traces.

Features

  • Access to raw call stack information
  • Parsed stack trace information with file, line, column, and function details
  • Configurable stack trace limit
  • Works in both Node.js and browsers
  • TypeScript definitions for complete type safety

Installation

npm install @art-suite/art-core-errors

API Overview

Stack Trace Functions

// Get the raw stack trace as an array of strings
rawCallStack(ignoreTop?: number): string[]

// Get parsed stack trace information
callStack(ignoreTop?: number): CallStackLine[]

// Get or set the maximum number of stack frames to capture
stackTraceLimit: number

CallStackLine Interface

interface CallStackLine {
  original: string; // Original stack trace line
  function?: string; // Function name if available
  source?: string; // Full source URL
  class?: string; // Class name if function is a method
  classPath?: string[]; // Path to class if nested
  sourceFileName?: string; // Source file name
  sourcePath?: string; // Source path
  sourceHostWithPort?: string; // Source host and port
  sourceLine: number; // Source line number
  sourceColumn: number; // Source column number
  toString(): string; // Returns original stack trace line
}

Examples

import {
  rawCallStack,
  callStack,
  stackTraceLimit,
} from "@art-suite/art-core-errors";

// Get raw stack trace lines
const rawStack = rawCallStack();
console.log(rawStack[0]); // "at myFunction (file.js:10:20)"

// Get parsed stack trace information
const stack = callStack();
const firstFrame = stack[0];
console.log(firstFrame.function); // "myFunction"
console.log(firstFrame.sourceLine); // 10
console.log(firstFrame.sourceColumn); // 20
console.log(firstFrame.sourceFileName); // "file.js"

// Configure stack trace limit
stackTraceLimit = 20; // Capture up to 20 stack frames

License

MIT