![Simon Høiberg on X: "JavaScript Tip 💡 Use console.trace instead of console. log. It will show you the complete call stack when debugging. https://t.co/xc9p5J7Pyl" / X Simon Høiberg on X: "JavaScript Tip 💡 Use console.trace instead of console. log. It will show you the complete call stack when debugging. https://t.co/xc9p5J7Pyl" / X](https://pbs.twimg.com/media/Eq95MsHW4AIU3On.jpg:large)
Simon Høiberg on X: "JavaScript Tip 💡 Use console.trace instead of console. log. It will show you the complete call stack when debugging. https://t.co/xc9p5J7Pyl" / X
![console.trace — A better alternative to console.log — Amit Merchant — A blog on PHP, JavaScript, and more console.trace — A better alternative to console.log — Amit Merchant — A blog on PHP, JavaScript, and more](https://www.amitmerchant.com/images/console-trace.png)
console.trace — A better alternative to console.log — Amit Merchant — A blog on PHP, JavaScript, and more
The Coder - Do you use javascript's console.log for debugging? I did too. The problem with it is that it doesn't specify the stack track, and instead, it just shows the message
![Firefox DevTools on X: "console.trace() will print the stacktrace that led to the call in the console. It can take arguments that will be printed above the trace so you can also Firefox DevTools on X: "console.trace() will print the stacktrace that led to the call in the console. It can take arguments that will be printed above the trace so you can also](https://pbs.twimg.com/media/E3C0-abXoAEBgLu.jpg:large)