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

call-trace

v1.1.0

Published

trace call stack from location

Readme

Call-Trace

This is a really simple module to allow you to see the call stack from the place where the function is executed. This is mostly useful

Essentially it is the same as writing console.log(new Error.stack).

But a (tiny) bit more convenient.

Usage

const trace = require('call-trace');


// somewhere in your code
trace();

You can also provide unlimited arguments, which will cause trace to only log when the argument asserts to a truthy value.

This is particularly useful when debugging because you may wish to only log the call stack when you arrive in a method with a particular set of arguments so you can determine how you got there. e.g.


const weirdValue = 123;

// This will log the function call stack
trace(weirdValue === 123);


const expectedValue = true;

// This will noop
trace(!expectedValue);

Licence

MIT