javascript-debugger

Although I used pretty code and had set up the breakpoints in "Pretty code" tab, debugger keeps working in minified code. (I can't see exactly where I am and need to continuously switch between source and "pretty code"). On same pages with same script it sometimes work and sometimes don't. I can't find the cause or any difference in the way I activate it. Is there any way to force debugger to use "pretty code"? Any Ideas or additional questions? Should this be reported as a bug? EDIT: I still don't understand what is going on but there is a fix for it. So when this situation happens, just edit

Reference: Using the new code snippets feature in google chrome I am using the code snippets in google chrome, so say I have a snippet file. check_consistency.js Is there an api or a global object through which we can run the snippet directly from the command line, something like: window.runSnippet('check_consistency.js') or maybe call methods defined in the snippet directly. cwd Workflow Tip 1 I also want to see this functionality added. Meanwhile, perhaps try opening the Sources where (as you know) you can select a snippet and right click it to run it. You may or may not know that you can

I have been using Google Chrome's dev tool kit (element inspection, stack trace, javascript debugging, etc.) for some time with great success. However, about two weeks ago, it suddenly became VERY sluggish. For example, when I right-click an element in the UI and then click "Inspect Element", or when I simply press F12, the code window takes 30-45 seconds to come up. It used to happen in less than a second. Has anyone else run into this problem? If so, were you able to correct it? How? Thanks in advance! Matt I've had the same problem, tried the same solutions without luck, until I fired

I can easily do this: console.time('mytimer'); doSomeWork(); console.timeEnd('mytimer'); But is it possible to calculate time in multiple functions. I need to define the script's start time in a global variable. Then inside multiple functions I will write how many miliseconds passed since the start of the time. And write the name of the function Something like this: console.time('mytimer'); doSomeWork() { // console.log(difference between now and "mytimer"s start time) // console.log(name of the function: doSomeWork()) }; doSomeWork2() { // console.log(difference between now and "mytimer"s

Some variables can be "optimized out" during Javascript execution. Thus values of such variables are not available for inspection while debugging ( User documentation ). Variables view shows (optimized away) message and console throws following error if the variable is tried to be evaluated: Error: variable has been optimized out Is there any way to enforce evaluation of such variable or disable this optimization in Firefox? Use the variable in a way that prevents this optimisation. function NOP() {} // then in the optimised code NOP(myvar); // debugging here should now show `myvar` When a