HTML5 Zone is brought to you in partnership with:

I live in the sometimes sunny Brighton (it's in the south of the UK, for those across the pond). The south coast is definitely my favourite place to be, but I spent some time on the outskirts of London whilst at University. I'm starting to focus on my own company Left Logic. It's a web development company with strong focus in usability, accessibility, clean design and powerful bespoke applications. Remy is a DZone MVB and is not an employee of DZone and has posted 53 posts at DZone. You can read more from them at their website. View Full User Profile

tracegl for JavaScript debugging

  • submit to reddit

In preparing for my new Node workshop (tickets go on sale Wednesday 10am – set alarm!) my tool of choice used to be node-inspector but development has gone idle (for a year to date) and it’s showing it’s age. However, recently I came across tracegl I was intrigued as it looked to add to my debugging tools for Node.

tracegl was so much more than I realised: it captures full JavaScript state a all points of my application’s execution – both on the server side, but also the client side.

Debugging a real bug with tracegl

Rik Arends includes an introductory video on the site, and the script is €12 – which frankly is a steal for what it provides me. If you’re join my Node workshop – I’m proving a licensed copy for everyone (because I think it should be part of your core stack).

I’ve included a short video of how I’ve used tracegl to debug my server side application. A few important things to note are: the trace is historical – and not blocking execution, which is what I’d normally do if I had to debug: I’d carefully replicate the issue, then either add a conditional breakpoint or debugger statement – but with tracegl, the bug can occur, and if tracegl is running, I can just look back at the state of the problem.

Learning more

I’m running a new crash course in Node on July, and similar the past it’s known to have sold out in a week. Tickets go on sale on Wednesday at 10am (UK) and will be available here.

I’ll be using this tool and many others to give you a fully packed day of knowledge on how to use Node, how to develop sites and real-time applications, and what tools I use for debugging, publishing and deployment.

So grab a ticket if you want my hands on, “knowledge smash & grab” course (or check out more details here).


Published at DZone with permission of Remy Sharp, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)