To give a context, there is this short period of time where you cannot debug or log any console messages after you drag/drop your test extensions into Chrome to see where and why the code is throwing errors. You have to manually click on the Inspect Page link in the chrome://extensions to see the background script console messages and utilize the debugger keyword, and other things. I would like to avoid not being able to log console errors and messages during that short time period.
I am looking for something that is equivalent to the following feature that Firefox has. For Firefox, Mozilla devs published and released an external tool called web-ext, a tool that is for aiding the developers when debugging Firefox WebExtensions add-ons.
A feature I adore from web-ext is the ability to launch Firefox and open Firefox's Browser Console at the same time. This helps with debugging the initial installation processes of the add-ons, as well as debugging issues that appears in the short window from initial loading of the background scripts and other things.
Unfortunately, I have no idea how to integrate web-ext with Chrome, despite that it saying by creating this new tool, it can be "interoperated" into Chrome, as quoted here:
- By creating a new tool that focuses on the [emerging] web extension standard, we have a better chance of interoperating with other platforms, such as Google Chrome or Opera. It would be hard to do that while preserving compatibility in jpm.
I am looking to see if Chrome allows the developers to launch the DevTools upon starting up the browser, and if so, allow developers to launch the DevTools mainly inspecting the background scripts on the extensions that is dragged/dropped into chrome://extensions.
That would be great if something like that exists out there. If anyone can find it for me, please let me know. If anyone else knows how to integrate web-ext with Chrome, please also let me know, so I can learn how to do this.