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.
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 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 :)
> What You Need: A computer with a Chromium-based browser such as Chrome, Vivaldi, or Brave [...]
I believe the book focuses on client-side TS apps?
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.
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.
How did you enjoy the process?
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 :)
vibe coded?
no