javascript-debugger

Bearing in mind that I have only the loosest understanding of what a debugger is really doing, I need help setting up the WebStorm npm debug configuration for an express.js application. Here's me so far-- I click debug with my settings as I think they should be (below): /Users/me/.nvm/versions/node/v4.4.1/bin/node --debug=8090 /Users/me/.nvm/versions/node/v4.4.1/lib/node_modules/npm/bin/npm-cli.js run-script start To debug "start" script, make sure $NODE_DEBUG_OPTION string is specified as the first argument for node command you'd like to debug. For example: { "start": "node $NODE_DEBUG_OPTION

Is it possible to run JSLint on one or more .js files by having JSLint loaded afterwards in the header from debugging/developer console in chrome or firefox? The reason that I want to do that is that I want to print in console.log() the parsing of JSLint in JSON ,it says in documentation: // You can obtain the parse tree that JSLint constructed while parsing. The // latest tree is kept in JSLINT.tree. A nice stringication can be produced // with // JSON.stringify(JSLINT.tree, [ // 'string', 'arity', 'name', 'first', // 'second', 'third', 'block', 'else' // ], 4)); Cracker You can run JSLint on

I'm trying to debug a web page that makes heavy use of events, and so I need to monitor all events that are fired. Most of the events are bound using jQuery. Hence, it would be particularly useful if there was a way to specifically monitor only those events. Of course you can do just fine with Firebug , the console and the scripts tab where you can add breakpoints and watches, but you want to do it smarter / easier obviously. There is a neat Firebug plugin called EventBug that just logs all the events and groups them by event type so you can expand and see what triggered them. EventBug doesn't

This question already has an answer here: How to use Firebug's debugger functions? 1 answer I am new to FireBug Debugger can anyone say what is step into,step over and step out Step into will cause the debugger to descend into any method calls on the current line. If there are multiple method calls, they'll be visited in order of execution; if there are no method calls, this is same as step over. This is broadly equivalent to following every individual line of execution as would be seen by the interpreter. Step over proceeds to the next line in your current scope (i.e. it goes to the next line

Possible Duplicate: Is Chrome's JavaScript console lazy about evaluating arrays? I try the following code: var myList = new Object(); var item = new Object(); item.text = "item-1"; myList[3] = item; console.log(myList); console.log(myList[3].text); // Assign another object to the same entry var item2 = new Object(); item2.text = "item-2"; myList[3] = item2; console.log(myList); console.log(myList[3].text); The result is quite odd: * Object * 3: Object text: "item-2" item-1 * Object * 3: Object text: "item-2" item-2 BUT - if i execute the second part after some time (using setTimeout), and

If I get Chrome to show me document.cookie by going into the console and typing document.cookie; it'll give me, say: "name=John; gender=male"; But then if I type in, say, document.cookie = 5; all it does is add 5; to the start of the string, so I get: "5; name=John; gender=male"; If I try document.cookie = null; then it doesn't even do anything. How can this be? It's a variable, isn't it? So why isn't the assignment operator working the way it should? Is it actually just a bit of syntactic sugar rather than a real variable? And if so, what precisely is the sugar covering up? document.cookie

I can't believe that neither a Google or SO search has turned up a definitive answer or even much discussion for this, but: Is it possible to edit/customize keyboard shortcuts in the Google Chrome JavaScript debugger? if so, how? I'm used to Eclipse's F5 / F6 / F7 / F8 debugger step into/over/out of/resume keys, and want the same bindings in Google Chrome. F10 / F11 are default Expose keys for OSX and therefore not ideal for debugger control. I'm open to unorthodox solutions, e.g. Quicksilver/AppleScript. Related, but not-quite-helpful, pages: Google Chrome's Javascript console keyboard