2.0.4 • Public • Published

stacktrace-metadata NPM version mit license NPM monthly downloads npm total downloads

Modify given err object to be more useful - adds at, line, column, place and filename properties and also cleans stack traces.

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

You might also be interested in clean-stacktrace.


  • Works on Windows and Node.js >= 0.10
  • Always normalizes Windows paths to be Unix-style
  • Customizable through options
  • Cleans stack trace using clean-stacktrace, opts.cleanStack: false to disable
  • Passing different current working directory to use, opts.cwd, using clean-stacktrace-relative-paths
  • Makes paths relative against opts.cwd, opts.relativePaths: false to disable
  • Makes stack trace short - top 4, opts.shortStack: false to disable
  • Allow hiding the stack trace (making it empty string), opts.showStack: false to enable
  • Adds useful properties like line, column and filename, using clean-stacktrace-metadata

Table of Contents

(TOC generated by verb using markdown-toc)


Install with npm

$ npm install stacktrace-metadata --save

or install using yarn

$ yarn add stacktrace-metadata


For more use-cases see the tests

const stacktraceMetadata = require('stacktrace-metadata')



Cleans stack trace and attaches few more metadata properties, such as at, line, column, filename and place. By default it cleans stack, makes is short (4 length) and makes paths relative. But all this is controllable through options object. Throws TypeError if error is not an instance of Error.


  • error {Error}: real error object, checked against instanceof Error
  • options {Object}: optional options object for more control
  • options.cleanStack {Boolean}: if false won't clean stack trace from node internals
  • options.shortStack {Boolean}: if false full stack traces, otherwise they are just four
  • options.showStack {Boolean}: if false the error.stack will be empty string
  • options.relativePaths {Boolean}: if false paths in stack traces will be absolute
  • options.mapper {Function}: called on each line of the stack with (line, index) signature
  • options.cwd {String}: current working directory, default process.cwd()
  • returns {Error}: same error object, but modified


const metadata = require('stacktrace-metadata')
const error = new Error('foo quxie')
error.stack = `Error: foo quxie
    at zazz (/home/charlike/apps/alwa.js:8:10)
    at module.exports (/home/charlike/apps/foo.js:6:3)
    at Object.<anonymous> (/home/charlike/apps/dush.js:45:3)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Function.Module.runMain (module.js:441:10)
    at startup (node.js:139:18)
const err = metadata(error)
console.log(err.line) // => 8
console.log(err.column) // => 10
console.log(err.filename) // => 'alwa.js'
console.log( // => 'zazz'
console.log( // => 'zazz (alwa.js:8:10)'
// =>
// Error: foo quxie
//     at zazz (alwa.js:8:10)
//     at module.exports (foo.js:6:3)
//     at Object.<anonymous> (dush.js:45:3)



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 © 2015, 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.

Package Sidebar


npm i stacktrace-metadata

Weekly Downloads






Last publish


  • vanchoy
  • tunnckocore