Need private packages and team management tools?Check out npm Orgs. »


1.1.3 • Public • Published

find-callsite NPM version mit license NPM monthly downloads npm total downloads

Finds the correct place where the stack trace was started, not the place where error was thrown

code climate code style linux build windows build code coverage dependency status paypal donate

You might also be interested in stacktrace-metadata.

Table of Contents


Install with npm

$ npm install find-callsite --save

or install using yarn

$ yarn add find-callsite


For more use-cases see the tests

const findCallsite = require('find-callsite')



Find correct callsite where error is started. All that stuff is because you not always need the first line of the stack to understand where and what happened.

In below example we use rimraf.sync to throw some error. That's the case when we need to be informed where is the rimraf.sync call not where it throws. In that case it is on line 6, column 12.


  • error {Error|Object|String}: plain or Error object with stack property, or string stack
  • opts {Object}: optional options object
  • opts.cwd {String}: give current working directory, default to process.cwd()
  • opts.relativePaths {Boolean}: make path relative to opts.cwd, default false
  • returns {String}: single callsite from whole stack trace, e.g. at foo (/home/bar/baz.js:33:4)


var findCallsite = require('find-callsite')
var rimraf = require('rimraf')
function fixture () {
  try {
  } catch (err) {
    var callsiteLine = findCallsite(err)
    // => 'at fixture (/home/charlike/apps/find-callsite/example.js:6:12)'
    var relativeCallsiteLine = findCallsite(err, {
      relativePaths: true
    // => 'at fixture (example.js:6:12)'



Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.
Please read the contributing guidelines for advice on opening issues, pull requests, and coding standards.
If you need some help and can spent some cash, feel free to contact me at too.

In short: If you want to contribute to that project, please follow these things

  1. Please DO NOT edit, and files. See "Building docs" section.
  2. Ensure anything is okey by installing the dependencies and run the tests. See "Running tests" section.
  3. Always use npm run commit to commit changes instead of git commit, because it is interactive and user-friendly. It uses commitizen behind the scenes, which follows Conventional Changelog idealogy.
  4. Do NOT bump the version in package.json. For that we use npm run release, which is standard-version and follows Conventional Changelog idealogy.

Thanks a lot! :)

Building docs

Documentation and that readme is generated using verb-generate-readme, which is a verb generator, so you need to install both of them and then run verb command like that

$ npm install verbose/verb#dev verb-generate-readme --global && verb

Please don't edit the README directly. Any changes to the readme must be made in

Running tests

Clone repository and run the following in that cloned directory

$ npm install && npm test


Charlike Mike Reagent


Copyright © 2017, Charlike Mike Reagent. Released under the MIT License.

This file was generated by verb-generate-readme, v0.4.3, on March 15, 2017.
Project scaffolded using charlike cli.


npm i find-callsite

Downloadsweekly downloads









last publish


  • avatar
  • avatar
Report a vulnerability