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

framedump

v0.0.1

Published

Dump frame variables when uncaughtExceptions are thrown.

Downloads

3

Readme

framedump

Log v8 frame context when Node.js traps an uncaughtException.

Using the process.on('uncaughtException', (err) => {}) handler, we can get notified when an exceptions bubbles to the top of the event loop. The err argument contains the stack trace triggering the exception.

However, we have no access to the local execution context that triggered the exception. It can be useful when debugging to see the values of local variables, function arguments and other references to allow you to find the source of the issue.

framedump will automatically log the contents of the execution frame whenever an uncaughtException is thrown.

usage

// these are the default values, pass in argument to override.
let options = {
  locals: true, // log local variable definitions in frame
  args: true, // log arguments definition in frame
  frames: 1, // number of frames to dump starting from error location
  exprs: [] // log results of evaluating these expressions
}
require('framedump').monitor(options)

See the example.js file for sample usage.

output

[17:27:52 ~/code/v8debugger]$ node example.js
UncaughtException listener triggered, dumping frames...
Frame 0 (/Users/james/code/v8debugger/example.js:8):
local variables =>
    var local = string
    var number = 12345
    var local_arr = [ 1, 2, 3 ]
arguments =>
     arg_a = arg_a_contents
evaluate exprs =>
     process.memoryUsage() = { rss: 23187456, heapTotal: 10619424, heapUsed: 5087904 }

/Users/james/code/v8debugger/example.js:8
  going.to.die()
  ^

ReferenceError: going is not defined
    at broken (/Users/james/code/v8debugger/example.js:8:3)
    at Object.<anonymous> (/Users/james/code/v8debugger/example.js:11:1)
    at Module._compile (module.js:399:26)
    at Object.Module._extensions..js (module.js:406:10)
    at Module.load (module.js:345:32)
    at Function.Module._load (module.js:302:12)
    at Function.Module.runMain (module.js:431:10)
    at startup (node.js:141:18)
    at node.js:977:3

how it works

Using the vm.runInDebugContent() method, we dynamically gain access to the V8 debugger at runtime. This allows us to add an breakpoint handler triggered by uncaught exceptions. This callback is executed with a reference to the current execution frame. Walking the frame stack, we can pull off local variable definitions, function arguments and evaluate JS expressions.