Node: increase stack trace limit
See original GitHub issue- Review the documentation: https://docs.sentry.io/
- Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
- Use the latest release: https://github.com/getsentry/sentry-javascript/releases
- Provide a link to the affected event from your Sentry account
Package + Version
-
@sentry/browser
-
@sentry/node
-
raven-js
-
raven-node
(raven for node) - other:
Version:
5.13.2
Description
I noticed that my Node stack traces appear very short in Sentry, which makes errors hard to debug.
IIUC, raven-node
used to set Error.stackTraceLimit = Infinity
. https://github.com/getsentry/raven-node/blob/6dbb5ef37ccd536360d5f73b601a42faee23b2f4/index.js#L10
@sentry/browser
still sets this, but @sentry/node
does not. Is there a reason for that?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
More than 10 lines in a node.js stack error?
You can pass stack trace limit as a command line param to node : ... You can increase the stack size with: node...
Read more >Enhancing stack trace output | Node Cookbook - Third Edition
The --stack-trace-limit flag instructs the V8 JavaScript engine to retain more stacks on each tick (each time round) of the event loop. When...
Read more >You can configure the logged error stack trace length in ...
For easier error debugging you can increase the stack trace limit in Chrome (V8) and Node.js.
Read more >Show More Lines in a Node.js Error Stack Trace | egghead.io
... Nodejs displays only a handful of lines. In this lesson, you will learn how to increase the stack trace limit to show...
Read more >Stack trace API - V8 JavaScript engine
All internal errors thrown in V8 capture a stack trace when they are created. This stack trace can be accessed from JavaScript through...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Makes sense, thank you. It might be worth adding a note about this to the docs, as the default stack trace size is pretty useless IMO.
We just didn’t want to enforce it, as this change can be applied by everyone manually.
This will work just fine.