I've recently tried using Brackets with Theseus debugger and liked it a lot. It doesn't replace node inspector but somewhat complements it with profiler-like functions and is (arguably) better with async debugging in some cases. It doesn't provide step by step execution, it first runs the script to completion and then let's you explore the history of all function calls with their parameters and return values. http://blog.brackets.io/2013/08/28/theseus-javascript-debugger-for-chrome-and-nodejs/
On Wed, Nov 13, 2013 at 11:04 AM, Michal Mocny <mmo...@chromium.org> wrote: > I'm not sure I said anything the official docs don't say better, but I > don't mind putting it in as a short overview. Since you did the writeup > feel free to insert where you think is best (just fix my typos ;). > > -Michal > > > On Wed, Nov 13, 2013 at 10:11 AM, Josh Soref <jso...@blackberry.com> > wrote: > > > John, that's a great question. > > > > Unfortunately I couldn't find a good place to reference for an answer > (the > > Readme has too much irrelevant content) - which is one of the reasons > that > > I sent the announcement. > > > > In short, it's a GUI debugger. It also allows you to do in line editing > of > > the live code. > > > > And yes, the lack of a functional profiler did sound disappointing, > but... > > > > The biggest complaint I have about JavaScript debuggers today is that > they > > don't keep a call chain across promise resolutions. When things unwind to > > the main event loop, you can no longer see how the original request was > > formed. While talking in the W3 about Promises, we all noted that > > eventually the tooling would improve to support that (this was a > conceptual > > concern at the time, and now I get to experience it as a practical > > problem). It isn't there yet, but hopefully someday... > > > > Carlos: thanks for the fixes > > > > Michal: should we just in line that in our page? > > --------------------------------------------------------------------- > > This transmission (including any attachments) may contain confidential > > information, privileged material (including material protected by the > > solicitor-client or other applicable privileges), or constitute > non-public > > information. Any use of this information by anyone other than the > intended > > recipient is prohibited. If you have received this transmission in error, > > please immediately reply to the sender and delete this information from > > your system. Use, dissemination, distribution, or reproduction of this > > transmission by unintended recipients is not authorized and may be > unlawful. > > >
