DevTools feature request: javascript tracer like spyjs
Reported by
serge.za...@gmail.com,
Sep 9 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3211.0 Safari/537.36 Steps to reproduce the problem: It would be very cool to have something like https://blog.jetbrains.com/webstorm/tag/spy-js/ out of the box in dev tools. What is the expected behavior? New panel in dev tools that can capture javascript traces similar to https://blog.jetbrains.com/webstorm/tag/spy-js/ What went wrong? n/a Did this work before? No Chrome version: 63.0.3211.0 Channel: canary OS Version: 10.0 Flash Version:
,
Sep 11 2017
Which part of the tracer functionality is most useful? Added attachment of the application graph. See also https://github.com/adobe-research/theseus and http://blog.brackets.io/2013/08/28/theseus-javascript-debugger-for-chrome-and-nodejs/?lang=en
,
Sep 11 2017
,
Sep 12 2017
,
Sep 16 2017
Thank you, most useful part is to be able to see passed parameters for functions and return values. Consider following scenario - there is a bug in the code, but I have no idea why it is happening. If I can record performance timeline & click through functions and see passed arguments/returned value, it will help me to find a place where state/logic started to behave in a wrong way. I understand that kind of tracking might be expensive - spy.js deals with it by allowing you to specify which files should be monitored and/or excluded. Another good feature is to see which branches executed in functions - spy.js highlights those branches. Thank you.
,
Dec 11 2017
This should be implemented as an DevTools extension! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jmukthavaram@chromium.org
, Sep 11 2017Status: Untriaged (was: Unconfirmed)