Sublime Web Inspector works on top of WebInspectorProtocol. All information is displayed in console and text files. 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 instantly. All clickable zones have borders to simply vizualize them.
You can add feature requests or bugs to https://github.com/sokolovstas/SublimeWebInspector/issues
Thanks XDebug Authors for inspiration
Find "Web Inspector" package in Package Manager
- Close Google Chrome!
- Press CTRL+SHIFT+R and select "Start Google Chrome with remote debug port 9222"
- After starting google chrome open new tab with your application in browser (you need to open url with your application, site or just file)
- Go to sublime press CTRL+SHIFT+R and select "Start debugging" and select your tab in list
- Breakpoints for project stored in user settings with absolute paths.
- Console.
- Debugger steps and breakpoints.
- Stack trace.
- You can see object properties and values in console and stack trace.
You can find all commands in the "Sublime Web Inspector" namespace. Here is a complete list:
- swi_debug_resume: Resume from pause
- swi_debug_step_into: Step into debugger
- swi_debug_step_out: Step out debugger
- swi_debug_step_over: Step over debugger
- swi_debug_evaluate: Evaluate selection (if paused on call frame)
- swi_debug_breakpoint: Add remove breakpoints
- swi_debug_reload: Reload connected page
- swi_debug_start: Start debugger
- swi_debug_stop: Stop debugger
- swi_debug_start_chrome: Start Google Chrome
- swi_show_file_mapping: Show mapping local file to url
You can change layouts for the debugger, color options, and path to Google Chrome in settings.