Easy debugging, profiling and tracing extension for Xdebug
Xdebug helper Extension
This extension is very useful for PHP developers that are using PHP tools with Xdebug support like PHPStorm, Eclipse with PDT, Netbeans and MacGDBp or any other Xdebug compatible profiling tool like KCacheGrind, WinCacheGrind or Webgrind.
By default the extension icon will show up on all pages, but to keep your browser as clean as possible, the extension can be configured to be only visible at the pages you want in the settings panel.
Hotkeys:
- Ctrl+Shift+X (Cmd+Shift+X on Mac) opens the popup.
- Alt+Shift+X toggles the debugging state.
---
Feel free to submit ideas, bugs and pull request to our Github project: https://github.com/wrep/xdebug-helper-for-chrome
Source Manifest.json
How to download and manually install Xdebug helper extension for Chrome
Looking for a way to install Xdebug helper extensions for Chrome, you can search for them in the Chrome Web Store, clicking the "Add to Chrome" button, and following the straightforward process.
However, you may need to install Xdebug helper extensions manually, this article outlines two simple methods to effortlessly install Xdebug helper extensions, whether they come as unpacked folders in compressed formats like .zip or as .crx files.
Method 1: Download Xdebug helper extension and manually install through Drag &Drop
If you ever need to manually install a Xdebug helper extension for Chrome, don't worry, it's a simple process. Just follow these easy steps, and you will have your extension ready to use in no time.
Step 1: Download the Xdebug helper Extension by clicking the "Download CRX" button on the website.
Look for the Xdebug helper extension you wish to install. Go to the website and download the Xdebug helper extension package, which is usually a .CRX file and comes in a zipped file. Here ".crx" file is the format for Xdebug helper extension that contains all the data.
Step 2: Extract &Arrange Files
Once the file is downloaded, extract that file into its own folder. Similarly, give that extension files a permanent home. In other words, keep it in a folder that you don't accidentally delete it because these files will be needed to make that extension work.
Step 3: Go to the Chrome Extensions Page
Open Google Chrome and in the address bar, type chrome://extensions; it will open the Google Chrome extensions page. Make sure that "My extensions" is selected in the sidebar.
Step 4: Drag and Drop the Extension
Now, go to the folder where you extracted the Xdebug helper extension and drag &drop the extension file from there anywhere onto the extension page within Google Chrome.
Step 5: Complete the Installation
Once you drag and drop the extension file, follow the steps that Google Chrome takes you through. Similarly, if the extension file is of .crx file format, you will be required to review the permissions and then add the extension.
Now, you can manage that added extension as you would like to with any other Chrome extension that you added through Chrome Webstore. Its icon will also appear in the Google Chrome Menu on the right side of the address bar once you activate it.
Method 2: Download Xdebug helper extension for Chrome and install in Developer Mode
This is another method to install Xdebug helper extension manually, but the twist is that here, you install by enabling the developer mode option provided in Google Chrome. This mode is commonly used for testing extensions or running unpublished tools.
Step 1: Download the Xdebug helper extension file
Select and download the Xdebug helper extension by clicking the 'Download CRX' button on the website.
Step 2: Extract the downloaded contents
Convert the file to a ZIP file if it is in CRX format then extract the Xdebug helper extension zip file or folder that you downloaded. Make sure you extract it using the same folder name and keep it safely in another folder, so you don't delete it by mistake. The extracted folder will be needed to keep your Xdebug helper extension running.
Step 3: Open Chrome Extension Setting Page
In the address bar of Google Chrome, type chrome://extensions and open the Chrome Extension Page.
Step 4: Enable Developer Mode
After opening the Chrome Extension page, look at the top right side, and you will find the toggle option of "Developer mode."Simply enable that developer mode option.
Step 5: Load the Unpacked Extension
Once you enable the developer mode option, you will see the menu of Load Unpacked, Pack Extensions and Update. From that, select the option "Load unpacked."
Step 6: Select the Extension Folder
Once the pop-up opens upon clicking Load unpacked, select the Xdebug helper extension directory and click on the "Select Folder "button.
Step 7: Confirm and Install
After you select an extension folder of a Google Chrome extension you're installing manually, confirm its installation for the final time and let the installation complete.
Conclusion
Here we've made a step-by-step guide on How to manually install Xdebug helper extension in 2 ways. We hope this guide proves helpful.
Similar Extensions
PHPView 300,000+ 40 ★ 88.99KiB
Xdebug Chrome Extension 300,000+ 3 ★ 169KiB
Laravel TestTools 300,000+ 67 ★ 449KiB
JetBrains Toolbox Extension 300,000+ 119 ★ 243KiB
Vue.js devtools 300,000+ 2131 ★ 2.57MiB
Chrome Logger 300,000+ 132 ★ 21.02KiB
jQuery Debugger 300,000+ 110 ★ 88.52KiB

zDebug 300,000+ 15 ★ 102KiB
Blackfire Profiler 300,000+ 24 ★ 1.62MiB
var_masterpiece 300,000+ 70 ★ 68.72KiB
LiveReload 300,000+ 808 ★ 60.78KiB
Alpine.js devtools 300,000+ 34 ★ 67.78KiB
Postman Interceptor 300,000+ 957 ★ 478KiB
Clockwork 300,000+ 74 ★ 2.26MiB
Vue.js devtools (beta) 300,000+ 149 ★ 2.54MiB
ChromeiQL 300,000+ 32 ★ 682KiB
JSONVue 300,000+ 2651 ★ 181KiB
Altair GraphQL Client 300,000+ 68 ★ 6.78MiB
JSON Formatter 300,000+ 1859 ★ 19.86KiB
Validity 300,000+ 210 ★ 108KiB
Elasticvue 300,000+ 73 ★ 3.43MiB
NetBeans Connector 300,000+ 1338 ★ 102KiB
Apollo Client Devtools 300,000+ 266 ★ 490KiB
PerfectPixel by WellDoneCode (pixel perfect) 300,000+ 605 ★ 732KiB
User reviews
Илья Ященко (ID: 000000bf06d6ef66) Voted 5 ★ - Updated 10/12/2022
Lee McCall (ID: 000000a1cecc8468) Voted 5 ★ - Updated 08/07/2022
Jeremy Simkins (ID: 00000028cb6ce392) Voted 2 ★ - Updated 06/09/2022
Patrick Henninger (ID: 0000003a83fd348d) Voted 2 ★ - Updated 06/07/2022
Yunhui Deng (ID: 00000023f24b9d5a) Voted 2 ★ - Updated 05/30/2022