Contributing to Augury

First things first, thank you for contributing. We know it takes a lot of time and effort. Everything in this document is meant to provide you with as much insight as possible with regards to our contribution standards. As you read it, it is important to remember that these are just guidelines and not rules. Please use your best judgement when applying them.

Table of Contents

I'm new. Anything I should know?

Hello and welcome! Before diving into any code, there are a few things you should look over. To help, here are few resources below we thought you might find useful. We'll update these from time to time so make sure you regularly skim this section, even if you've been contributing for a while.

The Manual


The first thing you should do is read the README. We have put a lot of love and care in writing it and it should provide you with the context you need for contributing to this project. Really, you should read it.

Code of conduct

Code of conduct

In the interest of making the Augury project a safe and friendly place for people from diverse backgrounds, we will be adhering to a Contributor Code of Conduct. As a contributor, you will be expected to uphold this code as well as report unacceptable behaviour to

How to contribute

Remember, no contribution is too small and no issue is too trivial. If you see a typo, we'd love to get a PR. We do not like typos, find them embarrassing, if you spot any please submit a correction.


Developer wiki

To contribute to Augury you should have a good understanding of Angular and TypeScript. Each build of Augury is done with npm and then imported into Chrome as an extension. We have a README just for developers, as well an ARCHITECTURE guide with a detailed technical overview. Jumping into a new codebase can be daunting, so the ARCHITECTURE guide is your best friend.

Coding style

  • Use semicolons;
  • Commas last,
  • 2 spaces for indentation (no tabs)
  • Prefer ' over "
  • 80 character line length
  • Try to use array operations (map, reduce, find, etc) instead of traditional while or for loops.
  • Use the ES6 arrow function syntax when defining your functions
  • Try and use appropriate types for your data

More information on some of these coding styles can be found in tslint.json file of this repository.

TypeScript linter is part of our build task and will run in either npm run build or npm start

Pull requests

The core team will be monitoring for pull requests.

Before submitting a pull request, please make sure the following is done…

  1. Fork the repo and create your branch from master.

  2. If you've added code that should be tested, add tests.

  3. If you've changed APIs, development workflow or aspects of the architecrure, update the corresponding documentation.

  4. TypeScript linter is part of our build task, make sure your code lints before submitting your PRs.


We are using GitHub Issues for our public bugs. We will follow up with any issues and report on when we have a fix in progress. Before filing for a new task, try to make sure your problem does not already exist.

If you do find a new issue, the best way to get a bug fixed is to provide a test case with either one of the example apps bundled in the repo, or by making your own Angular application illustrating the reduced use case. You can also include code snippets, though only if they illustrate the issue in a concise way. Do not forget to include the version of Angular app you are using!

*At the moment, we offer limited backwards compatibility until Angular stabilizes. Please check README for the version Augury currently supports.

How to Get in Touch

The Chat room


Okay, manuals and textbooks are great and all but they make for poor conversation. Feel free to join us on Slack! Whether you are looking for answers to technical questions, suggestion of a new feature, or just want to share funny pictures, there is a channel for that. You can also ask us questions in private. We can not wait to hear from you.