Google Chrome v48.0.2564.116 (64-bit) for Mac OS seems to retain all console commands indefinitely. None of the following have any affect:
clear()
console.clear()
Command-K
turning off "preserve log" and "show all messages"
Clear browsing data, from the beginning of time, all options check marked - removing all cookies
quitting and restarting or shutting down and rebooting.
Any combo of the above.
Unable to locate a chrome_debug.log file anywhere on the system (i.e. logging is not check marked).
Trashing Google Chrome and the associated library files then re-installing got rid of the console history, but the new version nonetheless holds all console subsequent console entries indefinitely.
Any insights? Any idea where this information gets stored?
If you are using windows 10. Just Simply go the console and right click then click on clear console
Thanks to Karmiphuc and the following link:
How to remove all recent console command
which mostly answers the question.
It's slightly understated there that, on Mac OS at least, you have to call the developer tools twice consecutively.
So 1st pull up a browser window, and do Command-Shift-I (Mac shortcut).
Then, making sure the Developer Tools window is undocked, do a second Command-Shift-I which pulls up yet another Developer Tools window.
Now look under Local Storage > chrome-devtools://devtools > consoleHistory.
Related
Trying to view my test localStorage, I see nothing in the Storage section under Applications in the Developer Tools.
However, using the console, I can access it, meaning its clearly there.
Am I missing something or does this seem to be a bug I couldn't find anything about?
I am using Chromium Version 57.0.2978.0 (64-bit)
Its a known Bug (#701413)
They fixed it in version 59.0.3069.0 (#718482)
I can see the localStorage of different domains like FB, but not from the current domain. When starting up developer tools it appears, but disappears after a reload.
I have been encountering the same issue. Not a great solution, but if one closes the developer tools and reopens the developer tools, one will find the domain showing again under Local Storage with all the local storage name value pairs. At least I found a nice shortcut to open and close the developer tools researching this issue. cmd + option + i for mac. I hope this helps my fellow coders. Chrome Version 57.0.2987.133 (64-bit) MacOS.
Workaround: re-open the Dev Tool, that is press F12 twice. Tested on Ubuntu Chrome 58.
I have encountered the same issue on my MAC. Open settings in dev tools and restore to the default view.
Once a node.js program has run to completion in the context of an --inspect session (i.e. via the Chrome dev tools debugger) is it possible to re-start it without having to re-issue the --inspect command from the command-line?
The issue with re-issuing an --inspect command is that it generates a different chrome url every time and one has to then copy-paste this into Chrome each time. Ideally I want to be able to push F5 to re-start the chrome debug session.
So two issues:
I cannot restart the debug session without killing the current (i.e. no way to just refresh).
I have to copy paste the url into chrome each time I start a new session. (not as bad as issue 1.)
Here's a couple of options for you, though neither will provide you with a simple F5 refresh, both are significantly better than copy/pasting the new URL generated by the --inspect flag.
The most optimal solution is installing this extension for Chrome or Opera: https://chrome.google.com/webstore/detail/nim-node-inspector-manage/gnhhdgbaldcilmgcpfddgdbkhjohddkj
This will manage the node inspector for you. Just click the resulting toolbar icon and select "Auto" from the toggle switch. Your browser will then open the Chrome DevTools in inspection mode whenever your node server generates an inspection URL.
If you want to go the low-tech (and more manual) route, or don't want to install a Chrome extension, just open your Chrome to "chrome://inspect", wait a moment, and you'll get a list under Remote Target that will include your Node server. Just click the "inspect" link there, and the DevTools will open with the current URL. The downside of this method is you'll need to reclick that "inspect" link every time your server restarts. It avoids copy/pasting URLs, but still involves manual labor.
It's also significant to note that if you simply update the url of your inspector with the new ID, it will also work.
When you restart node, you'll get something like this:
Debugger listening on ws://127.0.0.1:9222/72c791b7-178f-47e8-93b1-d1be4d5ffe1e
The bit after the port/ is what you want. Replace that code in your inspector's url and it will connect to the latest session.
Now that Firebug has been subsumed into Firefox, how can I configure the browser to bring Javascript errors to my attention without having the console open all the time, as Firebug used to do by showing an error count on its toolbar icon?
The Firefox DevTools provide a so-called "Developer Toolbar" aka GCLI (openable via Firefox menu > Developer > Developer Toolbar or Shift + F2), which displays the number of errors on the page (besides providing many useful commands):
Update:
The DevTools team obviously plans to remove the Developer Toolbar, because of low usage and because it's unmaintained and for most of it's features are available somewhere else.
There is no replacement yet for the error count, though, but a comment on the related bug report indicates that it will be added back.
Another options is to use Chrome extension JavaScript Errors Notifier.
To install it in Firefox, you'll first have to install another extension Chrome Store Foxified, which enables you to install any Chrome extension from Chrome Web Store to Firefox. You can follow the instructions of Chrome Store Foxified to install the extensions you like. (Note that not all Chrome extensions will work in Firefox.)
If you want to install the Chrome extension permanently, you'll have to sign up with Mozilla to get the extension signed.
If the JavaScript Errors Notifier extension is successfully installed in Firefox, you'll see an icon appearing at the right end of the address bar.
And when there's any JavaScript error in the page, the icon will turn red. To see the details of the errors, you can click on the icon. And the extension have quite some options to tune the errors that you want to get alerted.
Windonws 7 64-bit and VS2010
In F12 developer tools for IE11 on Windonws 7 64-bit and VS2010, when I click the Debugger tool icon or press Ctrl + 3 to open the tool, I'm not able to debug my java-script files.
When I click the Debugger tool icon, i'm presented with the message in the screenshot above & I can't see the javacsript files my current page calls, so I'm unable to debug my javascript code.
Any one knows why I could be getting this message? I have tried everything mentioned at the following link with out success. VS2010 and IE10 Attaching the Script debugger to process iexplore.exe failed
I was encountering this problem with VS 2012 & Win 7 and also VS2013 and Win8.1:
Perplexed for half a day, looking up things online, finally figured it out myself.
Learn the difference between these in Visual Studio: F5 vs (Ctr+Shift+W)
F5 will engage VS debugger and you will get the:
"The script debugger failed to connect to the target process. A debugger is already attached"
when using the F12 Developer Tool in I.E. 11 or whatever version.
However, if you use the V.S. command: View in Browser(Ctrl+Shift+W) this will run the script and allow I.E's script debugger(F12 Dev Tool) to engage and work.
The easier way for me was:
Run project(F5) in Firefox (or any other browser, not IE).
Copy adress.
Close Firefox (project will keep running, atleast did in myn).
Open IE and input address manually (ex: http://localhost:58100/) by pasting what you copied in '2.'.
IE Debugger should work at this point.
You should use ctrl+F5 instead of F5 so your application runs without debugging
I see this post is referred to Windonws 7 64-bit and VS2010, but I am using Windows 10 32 bit and VS Professional 2012 along with IE 11. I got the same message as shown in screenshot:
IE 11 Error message
How I resolved this problem(after starting Debugging):
went to debug tab in VS
then windows
select processes
There you will see two processes attached one will be "IIS" and second will be "IE.exe" with description "script". Detach the second one and then hit F12 in IE where your code is running.
When I did iisreset from command prompt, I could resolve this issue.
Open CMD in admin mode -> type IISRESET -> enter
I need to save Firebug's or the Google Chrome Console panel's log. I tried console.log() to play with printing logs, but what I need is to programatically save these developer tools logs into files.
Firebug has an extension called ConsoleExport, which does exactly that.
This extension exports the messages logged to Firebug's console in XML format. In the current released version 0.5b5 it only auto-exports to a server URL. Though, in the meantime code landed already (see issue 9) to auto-export to the file system, which will (hopefully) be released soon (see issue 21).