Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP



rodnnr opened this Issue · 8 comments

7 participants


I work in Windows 8.1 64bit with ST3 Build 3047

I have just cloned the web inspector repository into C:\Users\Admin\AppData\Roaming\Sublime Text 3\Packages\Web Inspector

Set the chrome path as follow:
"chrome_path": {
"windows": "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"

Now I open my main.js and click on CRTL+SHIFT+R but nothing happens, the command pallette doesn't open and the "START CHROME WITH REMOTE DEBBUGING PORT 9222" doesn't show.

I have even tried setting my chrome target path with the --remote-debugging-port=9222 without success.

If I fire the command pallette (crtl+shift+p) and I search for web inspector, no SWI command shows

I reinstalled the package a dozen times and I still can't use the web inspector on my machine. I have set this on a Windows 7 as well and the issue is the same.

Please help? What could be the issue? Is there a clear guide to setting and using the web inspector? The video doesn't clearly indicate how this should be set up nor how chrome itself should be configured.

My colleagues have also failed to set this up with the same issues. Please advise.




I'm having the same issue, I thought it has something to do with escaping whitespace in "Program Files (x86)" but apparently json allows spaces. I'm on a win7 machine and also running sublime3.


Try editing your Default.sublime-commands and change the "command": "swi_debug" to "command": "swi_debug_start"


Unfortunately this didn't make any difference.


I am having the same issue with Sublime Text 3 in Ubuntu. CTRL+SHIFT+R does nothing.


Same on OSX, CMD+SHIFT+R does nothing.


Had the same issue with sublime text 3 on windows 8.
Resolved it by doing two things
1. Rename Web Inspector to Web Inspector 3
2. move to the st3 branch by doing "git checkout ST3"


Nice one pgokul..."git checkout ST3" fixes it for me.


fixed packages.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.