Question 1

How to use Stackman with TypeScript and source maps?

Accepted Answer

Ensure your TypeScript is configured to generate source maps, then Stackman will automatically process them when sourcemap option is true. Use stackman.callsites on errors to get mapped stack traces with original source locations.

Question 2

Stackman vs Node.js built-in stack traces: what's better?

Accepted Answer

Stackman provides richer context like source code lines and module classification, while Node.js built-in traces are basic. Choose Stackman for detailed debugging, but stick to built-in if you need minimal overhead or simple error logging.

Question 3

Does Stackman work with ESM modules in Node.js?

Accepted Answer

The README doesn't specify ESM support; it likely relies on V8's stack trace API which may have limitations with ESM. Test compatibility with your Node.js version, as it's primarily designed for CommonJS environments.

Question 4

How to cache source files in Stackman for performance?

Accepted Answer

Set the fileCacheMax option during initialization to control the LRU cache size, defaulting to 500 files. This speeds up repeated error processing by keeping recently accessed source files in memory.

Question 5

Can Stackman be integrated with logging tools like Winston?

Accepted Answer

Yes, parse errors with stackman.callsites to enrich log entries with source context and module info, then pass the enhanced data to your logging framework for more actionable error reports.

Question 6

What happens if a source map is broken in Stackman?

Accepted Answer

Stackman suppresses source map errors and falls back to treating the code as unmapped, so you won't get warnings, but the stack trace will show transpiled code instead of the original source.

stackman

What is stackman?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions