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

stack-slice

v1.0.1

Published

Slice a file or directory from the middle of an Error stack trace

Downloads

1,528

Readme

stack-slice

Slice a file or directory from the middle of an Error stack trace

why

Sometimes you get an error at a point when you are the middle man, and you want to remove your function from the stack.

usualy if you are a masheling function and dont want to litter the stack with your implementation.

It is too late to use captureStackTrace thus this allows you to splice your call sites out of the stack.

usage

###stackSlice(error, path[, allowPartialMatch])


    var stackSlice = require('stack-slice'),
        error = new Error('BANG!!!');

    // Assume error.stack is the following
    // Error: BANG!!!
    //    at run (/foo/bar/myCoolModule/node_modules/someOtherModule/node_modulesrun.js:11:11)
    //    at foo (/foo/bar/myCoolModule/node_modules/someOtherModule/run.js:11:11)
    //    at bar (/foo/bar/myCoolModule/run.js:11:11)
    //    at stuff (/foo/bar/myCoolModule/main.js:11:11)
    //    at processImmediate [as _immediateCallback] (timers.js:11:11)


    stackSlice(error, '/foo/bar/myCoolModule/main.js');


    // error.stack is now
    // Error: BANG!!!
    //    at run (/foo/bar/myCoolModule/node_modules/someOtherModule/node_modulesrun.js:11:11)
    //    at foo (/foo/bar/myCoolModule/node_modules/someOtherModule/run.js:11:11)
    //    at bar (/foo/bar/myCoolModule/run.js:11:11)
    //    at processImmediate [as _immediateCallback] (timers.js:11:11)


    stackSlice(error, '/foo/bar/myCoolModule/node_modules/someOtherModule', true);


    // error.stack is now
    // Error: BANG!!!
    //    at bar (/foo/bar/myCoolModule/run.js:11:11)
    //    at processImmediate [as _immediateCallback] (timers.js:11:11)

more legitimate use


    childModule.run(functionFromParentModule, function(error, result){
        if(error){

            // remove all callsite for this module leaving parent and child
            stackSlice(error, __dirname, true);
            return callback(error);
        }

        callback(null, result);
    });