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

git-stack-expander

v1.0.5

Published

> Java Stack Trace + Git Commit ID = Useful Crash Report

Downloads

5

Readme

Git Stack Expander

Java Stack Trace + Git Commit ID = Useful Crash Report

Screenshot

Synopsis

Suppose you're given a stack trace of a crash that occurred in your app, but it originated from a slightly older version of your app. The line numbers of this stack trace won't match up to the current state of your app's source code so it can be difficult to see how to fix the bug that caused the stack trace. The solution is to check out the old revisions of your source code and compare the stack trace to that source code. Doing this is tedious and time-consuming.

Git Stack Expander is a simple tool designed to solve this problem in a simpler way. You simply paste the stack trace into Git Stack Expander, optionally provide the Git commit ID corresponding to the stack trace, and it will expand the stack trace with the actual content that appears on each line of the stack trace.

Requirements

  • NodeJS
  • Git

NOTE: Git must be in the CLI environment path. On OS X it is like this by default. On Windows, it will be in the path by default if you use the Git Bash (recommended).

Installation

$ sudo npm install -g git-stack-expander

Features

  • Converts stack trace into a hybrid stack trace + the lines of code that appears on each line of the stack trace at a given commit ID.
  • Specify number of lines before and after each stack frame to display.
  • Specify commit ID of any project in the workspace to load source for all projects at that point in time.
  • Omit commit ID to simply display the source code at the local projects' current state.

Usage instructions

Basic Usage:

$ cd /path/to/workspace
$ git-stack-expander

See Wiki