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

nodexh

v3.1.0

Published

a wrapper around the `node` executable for better stacktraces with sourcemaps, sourcecode excerpts

Downloads

60

Readme

NodeXH: NodeJS With a Better Exception Handler

Table of Contents generated with DocToc

What It Is

NodeXH is a drop-in wrapper for the NodeJS executable hat provides better stacktraces.

How to Install

npm install -g nodexh

How to Use

Use nodexh path/to/file.js instead of node path/to/file.js, and you're good to go.

What to Expect

  • Stack trace items will be reversed, so most recent calls will be shown last, i.e. also closest to where the cursor of your terminal is.
  • Stack traces will show source contexts (3 lines by default) except where files can not be opened or are NodeJS internals.
  • Source code shown will honor sourcemaps, which is great when you're using the likes of CoffeeScript or TypeScript.
  • The error message will be repeated to avoid having to scroll up when stack traces get longer.
  • Colors!

Related

  • https://github.com/mozilla/source-map/
  • https://sokra.github.io/source-map-visualization/
  • https://medium.com/@nodejs/source-maps-in-node-js-482872b56116:
    • "In v13.7.0 a public API was introduced for interacting with source maps."—link
    • "You can start using Node.js’ source map functionality today: make sure you have an up-to-date version of Node.js installed, and run your programs with the flag --enable-source-maps."

To Do

  • [ ] Add error.name, error.code; where node reports TypeError: TEMPLATES.main_2 is not a function, nodexh only reports EXCEPTION: TEMPLATES.main_2 is not a function
  • [ ] visually indicate spot of error (e.g. by reversing)
  • [ ] fix async stacktraces (probably not yet handled correctly; might be issue with stackman?)
  • [ ] consider utf8ize-sourcemaps in case there should be problems w/ 32bit characters
  • [ ] truncate long lines in context
  • [ ] offer capabilities of NodeXH as API so applications (such as test libraries) can easily retrieve source code, display source lines with contexts