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

@pvorona/throw-error

v0.0.3

Published

Throw errors with clean stack traces pointing at the caller, not the internals.

Downloads

423

Readme

@pvorona/throw-error

Throw errors with clean stack traces pointing at the caller, not the internals.

Install

npm i @pvorona/throw-error

Usage

import { throwError } from '@pvorona/throw-error';

function parsePort(input: string): number {
  const port = Number(input);

  if (!Number.isInteger(port) || port <= 0 || port >= 65536) {
    throwError(new RangeError(`Invalid port: ${input}`));
    // Stack trace points here ^, not inside throwError
  }

  return port;
}

Skipping extra stack frames

function validateEmail(input: string): string {
  if (!input.includes('@')) {
    // Stack trace will skip validateEmail and point at its caller
    throwError(new Error('Invalid email'), validateEmail);
  }

  return input;
}

API

throwError(error: Error, functionToSkipStackFrames?: Function): never

Throws error, attempting to make its stack trace point at the caller (instead of the throwError internals).

  • error: the error to throw
  • functionToSkipStackFrames: a function to pass as the “stack start” (defaults to throwError)
    • Use this when you have a helper wrapper and want to hide that wrapper from the stack trace.

Notes:

  • Uses Error.captureStackTrace when available (Node/V8). In other runtimes, it simply throws.
  • The return type is never, so it plays nicely with guard-clause control flow.

Example (wrapping):

import { throwError } from '@pvorona/throw-error';

export function invariant(condition: unknown, message: string): asserts condition {
  if (condition) return;
  throwError(new Error(message), invariant);
}