That's great feedback, thank you!

We'll go through screenshots, check their readability and crop or re-create them before going to print.

Can you point to particular screenshots that feel the worst?

Pragmatic has an inhouse book compiler. Most authors write in markdown and there's some special XML features you can use as well for it. Of course code linking is a first class feature.

It's a pretty nice system, actually.

I did, thank you! It was hard and long, though. Much harder and longer than I expected it to be. The book ended up being very different from what I initially conceived (for the better, I hope.) I have too much to say to fit it all in one comment, to be honest :)

I build a "wrapper" for this (not public, quick&dirty code). Transfer everything that could be logged via websocket to console and output and colorize it like I do it with a node app. Reduces the time that I need to spend in browser for debugging (click, scroll, open trees, etc.), has same format and it saves much time.

I am sure somebody created a good lib for that on github.

Node.js uses the same JavaScript engine as chrome and chrome dev tools can be connected to node to debug and profile.

node --inspect

chrome://inspector

Mostly yes. It touches upon debugging unit tests and server-side code, as well as methodologies applicable to debugging in general, but the practical parts are almost exclusively client-side.

I totally agree.

At first, I started writing a book about very practical, hands-on debugging practices, but quickly realized that the "mix of tools and best practices" you're talking about is a much more valuable skill, as well as bug prioritization, and even bug reporting.

So, as a result, catching errors early, type guarding, logging to debug asynchronous operations, and error tracking are all major parts of the book.

no