- Total 45K
- Win 25K
- OS X 14K
- Linux 6K
|Jan 20||Jan 19||Jan 18||Jan 17||Jan 16||Jan 15||Jan 14||Jan 13||Jan 12||Jan 11||Jan 10||Jan 9||Jan 8||Jan 7||Jan 6||Jan 5||Jan 4||Jan 3||Jan 2||Jan 1||Dec 31||Dec 30||Dec 29||Dec 28||Dec 27||Dec 26||Dec 25||Dec 24||Dec 23||Dec 22||Dec 21||Dec 20||Dec 19||Dec 18||Dec 17||Dec 16||Dec 15||Dec 14||Dec 13||Dec 12||Dec 11||Dec 10||Dec 9||Dec 8||Dec 7||Dec 6|
Sublime Web Inspector
Because of the nature of Sublime, all information is presented as text, however this turns out to work well enough. You can click on objects from console or stack trace to evaluate them. You can also click on a file name to goto the file and line. All clickable zones have borders to appear like buttons. Because it supports Source Maps, you can step in your originally authored code, such as Coffeescript or Typescript.
This package aims to keep you in Sublime a little more, and jump to your browser tools a little less. The philosophy is, if you can find a simple error using Sublime, you're already where you need to be to fix it. For anything more complicated, drop into the browser tools in the normal way.
To use against:
- Chrome – just works
- Internet Explorer 11 – start up IE, then start the IE Diagnostics Adapter. Web Inspector should detect it and offer to Start Debugging. Soon, Web Inspector will detect IE and offer to launch it as well. Note that you cannot use the Chrome tools and Web Inspector at the same time, but you /can/ use the Internet Explorer F12 tools (perhaps for the DOM explorer) and Web Inspector (for debugging) at the same time.
- Edge – start up Edge, then start the Edge Diagnostics Adapter. Web Inspector should detect it and offer to Start Debugging. Soon, Web Inspector will detect Edge and offer to launch it as well
- Debugger stepping and breakpoints.
- Console with colorized messages.
- Navigable stack trace.
- Inspect and expand objects.
- Evaluate expressions.
- Step directly through your originally authored code, such as Typescript, if source maps are available
- Support for styles editing, making it easy to see which styles in your CSS files are in use, and edit them in place.
- Better support for Internet Explorer (for now, via the IE Diagnostics Adapter) including potentially working against both browsers at once.
Please help us prioritize. We would welcome collaboration. You can add feature requests or bugs to the Issues List here.
- Make sure the Sublime Package Manager is installed in Sublime.
- Run “Package Control: Install Package” command and choose “Web Inspector”
- Open your web site root with “Open Folder” in Sublime. (This will allow Web Inspector to map a file on disk to a file in the browser.)
- If your target is Chrome, make sure any existing instances are closed.
- Press CTRL+SHIFT+R (⌘ + SHIFT + R) and select “Start Google Chrome with remote debug port 9222”. (If CTRL+SHIFT+R didn't work, do CTRL+SHIFT+P and choose Web Inspector. Also, check the Sublime console for error messages.)
- After starting Chrome navigate to your site. (Or, set “chrome_url” in Web Inspector settings, see below.)
- Go to Sublime press CTRL+SHIFT+R and select “Start debugging” and select your tab in the list provided. It will select it automatically if there is only one open.
If it won't get past “Start Google Chrome”
If Chrome was already open when Sublime launches it with the debugger flag, Chrome won't open the port, so the debugger can't attach. Close all instances of Chrome and try again.
CTRL+SHIFT+R (⌘ + SHIFT + R) and: - Pause execution (or F8 to toggle) - Resume execution (or F8 or F5) - Step into (or F11) - Step out (or Shift+F11) - Step over (or F10) - Evaluate selection (if paused on call frame)
CTRL+SHIFT+R (⌘ + SHIFT + R) and Toggle breakpoints
Breakpoints toggled when not debugging should bind when you start debugging. Breakpoints are persisted between sessions in your user settings.
CTRL+SHIFT+R (⌘ + SHIFT + R) and Reload page
CTRL+SHIFT+R (⌘ + SHIFT + R) and: - Start debugging (may offer a choice of page) - Stop debugging
You may stop and start debugging without restarting your browser.
If Web Inspector won't bind breakpoints
If Web Inspector can't resolve original sources
To debug original sources, Web Inspector must find a
You can change layouts for the debugger, color options, and path to Google Chrome in settings. See list of settings here.
By default, after “Start Chrome” you must navigate to your site. To do this automatically, add a setting like this to your user settings for the plugin:
To receive pre-release versions, instead of blessed versions, add Web Inspector to your install_prereleases section of your Package Control user settings, for example:
"install_prereleases": [ "Web Inspector" ]
Thanks XDebug Authors for inspiration