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

require-stack

v1.0.2

Published

Returns syntax error while requiring modules under try/catch, which is missing by default

Downloads

20,648

Readme

Require Stack

Nodejs require method does not provide filename or line number for syntax errors when requiring modules under try/catch statement. Ideally it is not the problem with Node Js, it has something to do with v8 itself.

Require Stack is a wrapper around require method, which makes it easier to get syntax error with proper error stack when wrapping require call under try/catch block.

Using Node Js

try{
  require('./module/with/syntax/error')
}catch(e){
  console.log(e.stack)
}

above prints

SyntaxError: Unexpected token {
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:413:25)
    at Object.Module._extensions..js (module.js:452:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/Users/harmindervirk/workspace/personal/active-packages/require-stack/index.js:11:3)
    at Module._compile (module.js:434:26)
    at Object.Module._extensions..js (module.js:452:10)

Which is no reference to the filename or linenumber where syntax error has occured. File reference on line number 9 is the file from where code is executed.

Using require stack

var requireStack = require('require-stack')
try{
  requireStack('./module/with/syntax/error')
}catch(e){
  console.log(e.stack)
}

above prints

/Users/harmindervirk/workspace/personal/active-packages/require-stack/test/modules/index.js:2
  return {
         ^
ParseError: Unexpected token

Which has reference to the filename with exact line number

Bonus

It does all the hard work required to setup error stack which can be parsed by https://www.npmjs.com/package/stack-trace.