AngularJS WebInspector Extension for Chrome
This repository has been archived on 2020-10-11. You can view files and clone it, but cannot push or open issues or pull requests.
Go to file
2012-07-31 18:01:28 -07:00
css feature(deps): deps panel mostly working 2012-07-23 10:20:06 -07:00
img many ui improvements; responsive layout within the plugin, added slider for controlling range of watch expressions 2012-07-12 16:20:26 -07:00
js fixed removing CSS styles 2012-07-31 18:01:28 -07:00
test initial revision 2012-07-02 14:09:51 -07:00
background.html initial revision 2012-07-02 14:09:51 -07:00
devtoolsBackground.html renamed devtools page and js 2012-07-25 15:37:11 -07:00
LICENSE added license 2012-07-19 00:12:14 -07:00
manifest.json incremented version number 2012-07-25 15:37:37 -07:00
panel.html refactored and generalized options tab and related services 2012-07-26 17:13:08 -07:00
README.md added screencast to readme 2012-07-25 11:23:47 -07:00
testacular.conf initial revision 2012-07-02 14:09:51 -07:00

AngularJS Batarang

Installation

You'll need Google Chrome Canary or, if you are using Linux, Google Chrome Dev Channel to use the extension.

  1. Navigate to chrome://flags/ in Canary, and enable "Experimental Extension APIs"
  2. Navigate to chrome://chrome/extensions/ and enable Developer Mode.
  3. Download the packed extension
  4. Open the file (should open with Canary, otherwise try dragging/dropping the file into Canary) and follow the prompts to install.

Screencast

Check out this screencast that walks you through the Batarang's features.

Using the Batarang

First, navigate Chrome Canary to the AngularJS application that you want to debug. Open the Developer Tools. There should be an AngularJS icon. Click on it to open he AngularJS Batarang.

The Batarang has four tabs: Model, Performance, Options, and Help.

Model

Batarang screenshot

Starting at the top of this tab, there is the root selection. If the application has only one ng-app declaration (as most applications do) then you will not see the option to change roots.

Below that is a tree showing how scopes are nested, and which models are attached to them. Clicking on a scope name will take you to the Elements tab, and show you the DOM element associated with that scope. Models and methods attached to each scope are listed with bullet points on the tree. Just the name of methods attached to a scope are shown. Models with a simple value and complex objects are shown as JSON. You can edit either, and the changes will be reflected in the application being debugged.

Performance

Batarang performance tab screenshot

The performance tab must be enabled separately because it causes code to be injected into AngularJS to track and report performance metrics. There is also an option to output performance metrics to the console.

Below that is a tree of watched expressions, showing which expressions are attached to which scopes. Much like the model tree, you can collapse sections by clicking on "toggle" and you can inspect the element that a scope is attached to by clicking on the scope name.

Underneath that is a graph showing the relative performance of all of the application's expressions. This graph will update as you interact with the application.

Options

Batarang options tab screenshot

Last, there is the options tab. The options tab has two checkboxes: one for "show scopes" and one for "show bindings." Each of these options, when enabled, highlights the respective feature of the application being debugged; scopes will have a red outline, and bindings will have a blue outline.

Elements

Batarang console screenshot

The Batarang also hooks into some of the existing features of the Chrome developer tools. For AngularJS applications, there is now a properties pane on in the Elements tab. Much like the model tree in the AngularJS tab, you can use this to inspect the models attached to a given element's scope.

Console

Batarang console screenshot

The Batarang exposes some convenient features to the Chrome developer tools console. To access the scope of an element selected in the Elements tab of the developer tools, in console, you can type $scope. If you change value of some model on $scope and want to have this change reflected in the running application, you need to call $scope.$apply() after making the change.