improved fix for non-TS syntax

Conflicts:
	gulpfile.js

.bowerrc

@@ -1,3 +0,0 @@
-{
-  "directory" : "bower_components"
-}

.clang-format

@@ -1,3 +0,0 @@
-Language:        JavaScript
-BasedOnStyle:    Google
-ColumnLimit:     100

.gitattributes

@@ -1,9 +1,5 @@
 # Auto detect text files and perform LF normalization
 * text=auto
 
-# JS and TS files must always use LF for tools to work
+# JS files must always use LF for tools to work
 *.js eol=lf
-*.ts eol=lf
-
-# Must keep Windows line ending to be parsed correctly
-scripts/windows/packages.txt eol=crlf

.github/ISSUE_TEMPLATE.md

@@ -1,39 +0,0 @@
-<!--
-IF YOU DON'T FILL OUT THE FOLLOWING INFORMATION WE MIGHT CLOSE YOUR ISSUE WITHOUT INVESTIGATING
--->
-
-**I'm submitting a ...**  (check one with "x")
-```
-[ ] bug report => search github for a similar issue or PR before submitting
-[ ] feature request
-[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
-```
-
-**Current behavior**
-<!-- Describe how the bug manifests. -->
-
-**Expected behavior**
-<!-- Describe what the behavior would be without the bug. -->
-
-**Minimal reproduction of the problem with instructions**
-<!--
-If the current behavior is a bug or you can illustrate your feature request better with an example, 
-please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem via
-https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
--->
-
-**What is the motivation / use case for changing the behavior?**
-<!-- Describe the motivation or the concrete use case -->
-
-**Please tell us about your environment:**
-<!-- Operating system, IDE, package manager, HTTP server, ... -->
-
-* **Angular version:** 2.0.X
-<!-- Check whether this is still an issue in the most recent Angular version -->
-
-* **Browser:** [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
-<!-- All browsers where this could be reproduced -->
- 
-* **Language:** [all | TypeScript X.X | ES6/7 | ES5]
-
-* **Node (for AoT issues):** `node --version` =   

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,36 +0,0 @@
-**Please check if the PR fulfills these requirements**
-- [ ] The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
-- [ ] Tests for the changes have been added (for bug fixes / features)
-- [ ] Docs have been added / updated (for bug fixes / features)
-
-
-**What kind of change does this PR introduce?** (check one with "x")
-```
-[ ] Bugfix
-[ ] Feature
-[ ] Code style update (formatting, local variables)
-[ ] Refactoring (no functional changes, no api changes)
-[ ] Build related changes
-[ ] CI related changes
-[ ] Other... Please describe:
-```
-
-**What is the current behavior?** (You can also link to an open issue here)
-
-
-
-**What is the new behavior?**
-
-
-
-**Does this PR introduce a breaking change?** (check one with "x")
-```
-[ ] Yes
-[ ] No
-```
-
-If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
-
-
-**Other information**:
-

.gitignore

@@ -1,32 +1,26 @@
-.DS_STORE
-
+# Don’t commit the following directories created by pub.
 /dist/
+packages/
+.buildlog
 node_modules
 bower_components
-angular.io/dist
+.pub
+.DS_STORE
+
+# Or the files created by dart2js.
+*.dart.js
+*.dart.precompiled.js
+*.js_
+*.js.deps
+*.js.map
 
 # Include when developing application packages.
 pubspec.lock
 .c9
 .idea/
-.settings/
 *.swo
-modules/.settings
-.vscode
-modules/.vscode
 
 # Don't check in secret files
 *secret.js
 
-# Ignore npm debug log
-npm-debug.log
-
-# build-analytics
-.build-analytics
-
-# rollup-test output
-/modules/rollup-test/dist/
-
-# angular.io
-/angular.io/node_modules/
-/angular.io/dist/
+/docs/bower_components/

.nvmrc

@@ -1 +0,0 @@
-6.6.0

.pullapprove.yml

@@ -1,233 +0,0 @@
-# Configuration for pullapprove.com
-#
-# Approval access and primary role is determined by info in the project ownership spreadsheet:
-# https://docs.google.com/spreadsheets/d/1-HIlzfbPYGsPr9KuYMe6bLfc4LXzPjpoALqtYRYTZB0/edit?pli=1#gid=0&vpid=A5
-#
-# === GitHub username to Full name map ===
-#
-# alexeagle - Alex Eagle
-# alxhub - Alex Rickabaugh
-# chuckjaz - Chuck Jazdzewski
-# gkalpak - George Kalpakas
-# IgorMinar - Igor Minar
-# kara - Kara Erickson
-# matsko - Matias Niemelä
-# mhevery - Misko Hevery
-# petebacondarwin - Pete Bacon Darwin
-# pkozlowski-opensource - Pawel Kozlowski
-# robwormald - Rob Wormald
-# tbosch - Tobias Bosch
-# vicb - Victor Berchet
-# vikerman - Vikram Subramanian
-
-version: 2
-
-group_defaults:
-  required: 1
-  reset_on_reopened:
-    enabled: true
-  approve_by_comment:
-    enabled: false
-
-groups:
-  root:
-    conditions:
-      files:
-        include:
-          - "*"
-        exclude:
-          - "angular.io/*"
-          - "integration/*"
-          - "modules/*"
-          - "tools/*"
-    users:
-      - IgorMinar
-      - mhevery
-
-  build-and-ci:
-    conditions:
-      files:
-        include:
-          - "*.yml"
-          - "*.json"
-          - "*.lock"
-          - "tools/*"
-        exclude:
-          - "tools/@angular/tsc-wrapped/*"
-    users:
-      - IgorMinar #primary
-      - mhevery
-
-  integration:
-    conditions:
-      files:
-        - "integration/*"
-    users:
-      - alexeagle
-      - mhevery
-      - tbosch
-      - vicb
-      - IgorMinar #fallback
-
-
-  core:
-    conditions:
-      files:
-        - "modules/@angular/core/*"
-    users:
-      - tbosch #primary
-      - mhevery
-      - vicb
-      - IgorMinar #fallback
-
-  compiler/animations:
-    conditions:
-      files:
-        - "modules/@angular/compiler/src/animation/*"
-    users:
-      - matsko #primary
-      - tbosch
-      - IgorMinar #fallback
-      - mhevery #fallback
-
-  compiler/i18n:
-    conditions:
-      files:
-        - "modules/@angular/compiler/src/i18n/*"
-    users:
-      - vicb #primary
-      - tbosch
-      - IgorMinar #fallback
-      - mhevery #fallback
-
-  compiler:
-    conditions:
-      files:
-        - "modules/@angular/compiler/*"
-    users:
-      - tbosch #primary
-      - mhevery
-      - IgorMinar #fallback
-
-  compiler-cli:
-    conditions:
-      files:
-        - "tools/@angular/tsc-wrapped/*"
-        - "modules/@angular/compiler-cli/*"
-    users:
-      - alexeagle
-      - chuckjaz
-      - tbosch
-      - IgorMinar #fallback
-      - mhevery #fallback
-
-  common:
-    conditions:
-      files:
-        - "modules/@angular/common/*"
-    users:
-      - pkozlowski-opensource #primary
-      - vicb
-      - IgorMinar #fallback
-      - mhevery #fallback
-
-  forms:
-    conditions:
-      files:
-        - "modules/@angular/forms/*"
-    users:
-      - kara #primary
-      # needs secondary
-      - IgorMinar #fallback
-      - mhevery #fallback
-
-  http:
-    conditions:
-      files:
-        - "modules/@angular/http/*"
-    users:
-      - vikerman #primary
-      - alxhub
-      - IgorMinar #fallback
-      - mhevery #fallback
-
-  language-service:
-    conditions:
-      files:
-        - "modules/@angular/language-service/*"
-    users:
-      - chuckjaz #primary
-      # needs secondary
-      - IgorMinar #fallback
-      - mhevery #fallback
-
-  router:
-    conditions:
-      files:
-        - "modules/@angular/router/*"
-    users:
-      - vicb #primary
-      # needs secondary
-      - IgorMinar #fallback
-      - mhevery #fallback
-
-  upgrade:
-    conditions:
-      files:
-        - "modules/@angular/upgrade/*"
-    users:
-      - petebacondarwin #primary
-      - gkalpak
-      - IgorMinar #fallback
-      - mhevery #fallback
-
-  platform-browser:
-    conditions:
-      files:
-        - "modules/@angular/platform-browser/*"
-    users:
-      - tbosch #primary
-      - vicb
-      - IgorMinar #fallback
-      - mhevery #fallback
-
-  platform-server:
-    conditions:
-      files:
-        - "modules/@angular/platform-server/*"
-    users:
-      - vikerman #primary
-      - alxhub
-      - IgorMinar #fallback
-      - mhevery #fallback
-
-  platform-webworker:
-    conditions:
-      files:
-        - "modules/@angular/platform-webworker/*"
-    users:
-      - vicb #primary
-      # needs secondary
-      - IgorMinar #fallback
-      - mhevery #fallback
-
-
-
-  benchpress:
-    conditions:
-      files:
-        - "modules/@angular/benchpress/*"
-    users:
-      - tbosch #primary
-      # needs secondary
-      - IgorMinar #fallback
-      - mhevery #fallback
-
-  angular.io:
-    conditions:
-      files:
-        - "angular.io/*"
-    users:
-      - IgorMinar
-      - robwormald
-      - mhevery #fallback

.travis.yml

@@ -1,65 +1,38 @@
 language: node_js
 sudo: false
 node_js:
-  - '6.6.0'
-git:
-  # Increased from default (50) to ensure last release tag is in this range
-  depth: 150
-
-addons:
-#  firefox: "38.0"
-  apt:
-    sources:
-      # needed to install g++ that is used by npms's native modules
-      - ubuntu-toolchain-r-test
-    packages:
-      - g++-4.8
-
-branches:
-  except:
-    - g3_v2_0
-
-cache:
-  yarn: true
-  directories:
-     - ./node_modules
-     - ./.chrome/chromium
-     - ./angular.io/node_modules
-
+- '0.10'
 env:
   global:
-    # GITHUB_TOKEN_ANGULAR
-    # This is needed for the e2e Travis matrix task to publish packages to github for continuous packages delivery.
-    - secure: "fq/U7VDMWO8O8SnAQkdbkoSe2X92PVqg4d044HmRYVmcf6YbO48+xeGJ8yOk0pCBwl3ISO4Q2ot0x546kxfiYBuHkZetlngZxZCtQiFT9kyId8ZKcYdXaIW9OVdw3Gh3tQyUwDucfkVhqcs52D6NZjyE2aWZ4/d1V4kWRO/LMgo="
-    # FIREBASE_TOKEN
-    # This is needed for publishing builds to the "aio-staging" firebase site.
-    # TODO(i): the token was generated using the iminar@google account, we should switch to a shared/role-base account.
-    - secure: "MPx3UM77o5IlhT75PKHL0FXoB5tSXDc3vnCXCd1sRy4XUTZ9vjcV6nNuyqEf+SOw659bGbC1FI4mACGx1Q+z7MQDR85b1mcA9uSgHDkh+IR82CnCVdaX9d1RXafdJIArahxfmorbiiPPLyPIKggo7ituRm+2c+iraoCkE/pXxYg="
+  - KARMA_BROWSERS=DartiumWithWebPlatform
+  - E2E_BROWSERS=Dartium
+  - LOGS_DIR=/tmp/angular-build/logs
+  - ARCH=linux-x64
   matrix:
-    # Order: a slower build first, so that we don't occupy an idle travis worker waiting for others to complete.
-    - CI_MODE=e2e EXPERIMENTAL_ES2015_DISTRO=1
-    - CI_MODE=js
-    - CI_MODE=saucelabs_required
-    - CI_MODE=browserstack_required
-    - CI_MODE=saucelabs_optional
-    - CI_MODE=browserstack_optional
-    - CI_MODE=docs_test
-    - CI_MODE=aio
-
-matrix:
-  fast_finish: true
-  allow_failures:
-    - env: "CI_MODE=saucelabs_optional"
-    - env: "CI_MODE=browserstack_optional"
-
-install:
-  - ./scripts/ci-lite/install.sh
+  - MODE=js DART_CHANNEL=dev
+# Dissabled until Dart v1.9 hits stable
+#  - MODE=dart DART_CHANNEL=stable
+  - MODE=dart DART_CHANNEL=dev
 
+before_install:
+- export DISPLAY=:99.0
+- export GIT_SHA=$(git rev-parse HEAD)
+- ./scripts/ci/init_android.sh
+- ./scripts/ci/install_dart.sh ${DART_CHANNEL} ${ARCH}
+- sh -e /etc/init.d/xvfb start
+- if [[ -e SKIP_TRAVIS_TESTS ]]; then { cat SKIP_TRAVIS_TESTS ; exit 0; } fi
+before_script:
+- mkdir -p $LOGS_DIR
 script:
-  - ./scripts/ci-lite/build.sh && ./scripts/ci-lite/test.sh
-
-after_success:
-  - ./scripts/ci-lite/deploy_aio_staging.sh
-
+- ./scripts/ci/build_and_test.sh ${MODE}
 after_script:
-  - ./scripts/ci-lite/cleanup.sh
+- ./scripts/ci/print-logs.sh
+notifications:
+  webhooks:
+    urls:
+    - https://webhooks.gitter.im/e/1ef62e23078036f9cee4
+    on_success: change  # options: [always|never|change] default: always
+    on_failure: always  # options: [always|never|change] default: always
+    on_start: false     # default: false
+  slack:
+    secure: EP4MzZ8JMyNQJ4S3cd5LEPWSMjC7ZRdzt3veelDiOeorJ6GwZfCDHncR+4BahDzQAuqyE/yNpZqaLbwRWloDi15qIUsm09vgl/1IyNky1Sqc6lEknhzIXpWSalo4/T9ZP8w870EoDvM/UO+LCV99R3wS8Nm9o99eLoWVb2HIUu0=

COMMITTER.md

@@ -1,21 +0,0 @@
-# Pushing changes into the Angular tree
-
-Please see [Using git with Angular repositories](https://docs.google.com/document/d/1h8nijFSaa1jG_UE8v4WP7glh5qOUXnYtAtJh_gwOQHI/edit)
-for details about how we maintain a linear commit history, and the rules for committing.
-
-As a contributor, just read the instructions in [CONTRIBUTING.md](CONTRIBUTING.md) and send a pull request.
-Someone with committer access will do the rest.
-
-# Change approvals
-
-Change approvals in our monorepo are managed via [pullapprove.com](https://about.pullapprove.com/) and are configured via the `.pullapprove.yaml` file.
-
-
-# Merging
-
-Once a change has all the approvals either the last approver or the PR author (if PR author has the project collaborator status) should mark the PR with "PR: merge" label.
-This signals to the caretaker that the PR should be merged.
-
-# Who is the Caretaker?
-
-See [this explanation](https://twitter.com/IgorMinar/status/799365744806854656).

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to Angular
+# Contributing to Angular 2
 
-We would love for you to contribute to Angular and help make it even better than it is
+We would love for you to contribute to Angular 2 and help make it even better than it is
 today! As a contributor, here are the guidelines we would like you to follow:
 
  - [Code of Conduct](#coc)
@@ -17,59 +17,61 @@ Help us keep Angular open and inclusive. Please read and follow our [Code of Con
 
 ## <a name="question"></a> Got a Question or Problem?
 
-Please, do not open issues for the general support questions as we want to keep GitHub issues for bug reports and feature requests. You've got much better chances of getting your question answered on [StackOverflow](https://stackoverflow.com/questions/tagged/angular) where the questions should be tagged with tag `angular`.
+If you have questions about how to *use* Angular, please direct them to the [Google Group][angular-group]
+discussion list or [StackOverflow][stackoverflow]. We are also available on [Gitter][gitter].
 
-StackOverflow is a much better place to ask questions since:
-
-- there are thousands of people willing to help on StackOverflow
-- questions and answers stay available for public viewing so your question / answer might help someone else
-- StackOverflow's voting system assures that the best answers are prominently visible.
-
-To save your and our time we will be systematically closing all the issues that are requests for general support and redirecting people to StackOverflow.
-
-If you would like to chat about the question in real-time, you can reach out via [our gitter channel][gitter].
-
-## <a name="issue"></a> Found a Bug?
-If you find a bug in the source code, you can help us by
+## <a name="issue"></a> Found an Issue?
+If you find a bug in the source code or a mistake in the documentation, you can help us by
 [submitting an issue](#submit-issue) to our [GitHub Repository][github]. Even better, you can
 [submit a Pull Request](#submit-pr) with a fix.
 
-## <a name="feature"></a> Missing a Feature?
-You can *request* a new feature by [submitting an issue](#submit-issue) to our GitHub
-Repository. If you would like to *implement* a new feature, please submit an issue with
-a proposal for your work first, to be sure that we can use it.
-Please consider what kind of change it is:
+## <a name="feature"></a> Want a Feature?
+You can *request* a new feature by [submitting an issue](#submit-issue) to our [GitHub
+Repository][github]. If you would like to *implement* a new feature then consider what kind of
+change it is:
 
 * For a **Major Feature**, first open an issue and outline your proposal so that it can be
 discussed. This will also allow us to better coordinate our efforts, prevent duplication of work,
 and help you to craft the change so that it is successfully accepted into the project.
 * **Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr).
 
+## <a name="docs"></a> Want a Doc Fix?
+If you want to help improve the docs, then consider what kind of improvement it is:
+
+* For **Major Changes**, it's a good idea to let others know what you're working on to
+minimize duplication of effort. Before starting, check out the issue queue for
+issues labeled [#docs](https://github.com/angular/angular/labels/%23docs).
+Comment on an issue to let others know what you're working on, or [create a new issue](#submit-issue)
+if your work doesn't fit within the scope of any of the existing doc issues.
+Please build and test the documentation before [submitting the Pull Request](#submit-pr), to be sure
+you haven't accidentally introduced any layout or formatting issues.  Also ensure that your commit
+message is labeled "docs" and follows the [Commit Message Guidelines](#commit) given below.
+* For **Small Changes**, there is no need to file an issue first. Simply [submit a Pull Request](#submit-pr).
+
 ## <a name="submit"></a> Submission Guidelines
 
 ### <a name="submit-issue"></a> Submitting an Issue
+Before you submit an issue, search the archive, maybe your question was already answered.
 
-Before you submit an issue, please search the issue tracker, maybe an issue for your problem already exists and the discussion might inform you of workarounds readily available.
-
-We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs we will systematically ask you to provide a minimal reproduction scenario using http://plnkr.co. Having a live, reproducible scenario gives us wealth of important information without going back & forth to you with additional questions like:
-
-- version of Angular used
-- 3rd-party libraries and their versions
-- and most importantly - a use-case that fails
-
-A minimal reproduce scenario using http://plnkr.co/ allows us to quickly confirm a bug (or point out coding problem) as well as confirm that we are fixing the right problem. If plunker is not a suitable way to demonstrate the problem (for example for issues related to our npm packaging), please create a standalone git repository demonstrating the problem.
-
-We will be insisting on a minimal reproduce scenario in order to save maintainers time and ultimately be able to fix more bugs. Interestingly, from our experience users often find coding problems themselves while preparing a minimal plunk. We understand that sometimes it might be hard to extract essentials bits of code from a larger code-base but we really need to isolate the problem before we can fix it.
-
-Unfortunately we are not able to investigate / fix bugs without a minimal reproduction, so if we don't hear back from you we are going to close an issue that don't have enough info to be reproduced.
-
-You can file new issues by filling out our [new issue form](https://github.com/angular/angular/issues/new).
+If your issue appears to be a bug, and hasn't been reported, open a new issue.
+Help us to maximize the effort we can spend fixing issues and adding new
+features, by not reporting duplicate issues.  Providing the following information will increase the
+chances of your issue being dealt with quickly:
 
+* **Overview of the Issue** - if an error is being thrown a non-minified stack trace helps
+* **Motivation for or Use Case** - explain why this is a bug for you
+* **Angular Version(s)** - is it a regression?
+* **Browsers and Operating System** - is this a problem with all browsers?
+* **Reproduce the Error** - provide a live example (using [Plunker][plunker],
+  [JSFiddle][jsfiddle] or [Runnable][runnable]) or a unambiguous set of steps.
+* **Related Issues** - has a similar issue been reported before?
+* **Suggest a Fix** - if you can't fix the bug yourself, perhaps you can point to what might be
+  causing the problem (line of code or commit)
 
 ### <a name="submit-pr"></a> Submitting a Pull Request (PR)
 Before you submit your Pull Request (PR) consider the following guidelines:
 
-* Search [GitHub](https://github.com/angular/angular/pulls) for an open or closed PR
+* Search [GitHub](https://github.com/angular/angular.dart/pulls) for an open or closed PR
   that relates to your submission. You don't want to duplicate effort.
 * Please sign our [Contributor License Agreement (CLA)](#cla) before sending PRs.
   We cannot accept code without this.
@@ -101,7 +103,7 @@ Before you submit your Pull Request (PR) consider the following guidelines:
 * In GitHub, send a pull request to `angular:master`.
 * If we suggest changes then:
   * Make the required updates.
-  * Re-run the Angular test suites to ensure tests are still passing.
+  * Re-run the Angular 2 test suites for JS and Dart to ensure tests are still passing.
   * Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
 
     ```shell
@@ -145,9 +147,9 @@ To ensure consistency throughout the source code, keep these rules in mind as yo
 
 * All features or bug fixes **must be tested** by one or more specs (unit-tests).
 * All public API methods **must be documented**. (Details TBC).
-* We follow [Google's JavaScript Style Guide][js-style-guide], but wrap all code at
-  **100 characters**. An automated formatter is available, see
-  [DEVELOPER.md](DEVELOPER.md#clang-format).
+* With the exceptions listed below, we follow the rules contained in
+  [Google's JavaScript Style Guide][js-style-guide]:
+    * Wrap all code at **100 characters**.
 
 ## <a name="commit"></a> Commit Message Guidelines
 
@@ -167,68 +169,26 @@ format that includes a **type**, a **scope** and a **subject**:
 <footer>
 ```
 
-The **header** is mandatory and the **scope** of the header is optional.
-
 Any line of the commit message cannot be longer 100 characters! This allows the message to be easier
 to read on GitHub as well as in various git tools.
 
-Footer should contain a [closing reference to an issue](https://help.github.com/articles/closing-issues-via-commit-messages/) if any.
-
-Samples: (even more [samples](https://github.com/angular/angular/commits/master))
-
-```
-docs(changelog): update change log to beta.5
-```
-```
-fix(release): need to depend on latest rxjs and zone.js
-
-The version in our package.json gets copied to the one we publish, and users need the latest of these.
-```
-
-### Revert
-If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit. In the body it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
-
 ### Type
 Must be one of the following:
 
-* **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
-* **ci**: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
-* **docs**: Documentation only changes
 * **feat**: A new feature
 * **fix**: A bug fix
-* **perf**: A code change that improves performance
-* **refactor**: A code change that neither fixes a bug nor adds a feature
+* **docs**: Documentation only changes
 * **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing
   semi-colons, etc)
-* **test**: Adding missing tests or correcting existing tests
+* **refactor**: A code change that neither fixes a bug or adds a feature
+* **perf**: A code change that improves performance
+* **test**: Adding missing tests
+* **chore**: Changes to the build process or auxiliary tools and libraries such as documentation
+  generation
 
 ### Scope
-The scope should be the name of the npm package affected (as perceived by person reading changelog generated from commit messages.
-
-The following is the list of supported scopes:
-
-* **common**
-* **compiler**
-* **compiler-cli**
-* **core**
-* **forms**
-* **http**
-* **language-service**
-* **platform-browser**
-* **platform-browser-dynamic**
-* **platform-server**
-* **platform-webworker**
-* **platform-webworker-dynamic**
-* **router**
-* **upgrade**
-* **tsc-wrapped**
-
-There is currently few exception to the "use package name" rule:
-
-* **packaging**: used for changes that change the npm package layout in all of our packages, e.g. public path changes, package.json changes done to all packages, d.ts file/format changes, changes to bundles, etc.
-* **changelog**: used for updating the release notes in CHANGELOG.md
-* **aio**: used for angular.io changes within the /angular.io directory of the repo
-* none/empty string: useful for `style`, `test` and `refactor` changes that are done across all packages (e.g. `style: add missing semicolons`)
+The scope could be anything specifying place of the commit change. For example 
+`Compiler`, `ElementInjector`, etc.
 
 ### Subject
 The subject contains succinct description of the change:
@@ -245,7 +205,6 @@ The body should include the motivation for the change and contrast this with pre
 The footer should contain any information about **Breaking Changes** and is also the place to
 reference GitHub issues that this commit **Closes**.
 
-**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.
 
 A detailed explanation can be found in this [document][commit-message-format].
 
@@ -267,8 +226,8 @@ changes to be accepted, the CLA must be signed. It's a quick process, we promise
 [github]: https://github.com/angular/angular
 [gitter]: https://gitter.im/angular/angular
 [individual-cla]: http://code.google.com/legal/individual-cla-v1.0.html
-[js-style-guide]: https://google.github.io/styleguide/jsguide.html
-[jsfiddle]: http://jsfiddle.net
+[js-style-guide]: http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml
+[jsfiddle]: http://jsfiddle.net/
 [plunker]: http://plnkr.co/edit
-[runnable]: http://runnable.com
+[runnable]: http://runnable.com/
 [stackoverflow]: http://stackoverflow.com/questions/tagged/angular

DEVELOPER.md

@@ -1,47 +1,58 @@
-# Building and Testing Angular
+# Building and Testing Angular 2 for JS and Dart
 
-This document describes how to set up your development environment to build and test Angular.
-It also explains the basic mechanics of using `git`, `node`, and `npm`.
+This document describes how to set up your development environment to build and test Angular, both
+JS and Dart versions. It also explains the basic mechanics of using `git`, `node`, and `npm`.
 
-* [Prerequisite Software](#prerequisite-software)
-* [Getting the Sources](#getting-the-sources)
-* [Installing NPM Modules](#installing-npm-modules)
-* [Building](#building)
-* [Running Tests Locally](#running-tests-locally)
+See the [contributing guidelines](https://github.com/angular/angular/blob/master/CONTRIBUTING.md)
+for how to contribute your own code to
 
-See the [contribution guidelines](https://github.com/angular/angular/blob/master/CONTRIBUTING.md)
-if you'd like to contribute to Angular.
+1. [Prerequisite Software](#prerequisite-software)
+2. [Getting the Sources](#getting-the-sources)
+3. [Environment Variable Setup](#environment-variable-setup)
+4. [Installing NPM Modules and Dart Packages](#installing-npm-modules-and-dart-packages)
+5. [Running Tests Locally](#running-tests-locally)
+6. [Project Information](#project-information)
+7. [CI using Travis](#ci-using-travis)
+8. [Debugging](#debugging)
 
 ## Prerequisite Software
 
 Before you can build and test Angular, you must install and configure the
 following products on your development machine:
 
-* [Git](http://git-scm.com) and/or the **GitHub app** (for [Mac](http://mac.github.com) or
-  [Windows](http://windows.github.com)); [GitHub's Guide to Installing
+* [Dart](https://www.dartlang.org) (version `>=1.9.0-dev.8.0`), specifically the Dart-SDK and
+  Dartium (a version of [Chromium](http://www.chromium.org) with native support for Dart through
+  the Dart VM). One of the **simplest** ways to get both is to install the **Dart Editor bundle**,
+  which includes the editor, SDK and Dartium. See the [Dart tools](https://www.dartlang.org/tools)
+  download [page for instructions](https://www.dartlang.org/tools/download.html); note that you can
+  download both **stable** and **dev** channel versions from the [download
+  archive](https://www.dartlang.org/tools/download-archive).
+
+* [Git](http://git-scm.com) and/or the **Github app** (for [Mac](http://mac.github.com) or
+  [Windows](http://windows.github.com)): the [Github Guide to Installing
   Git](https://help.github.com/articles/set-up-git) is a good source of information.
 
-* [Node.js](http://nodejs.org), (version `>=5.4.1 <6`) which is used to run a development web server,
-  run tests, and generate distributable files. We also use Node's Package Manager, `npm`
-  (version `>=3.5.3 <4.0`), which comes with Node. Depending on your system, you can install Node either from
-  source or as a pre-packaged bundle.
+* [Node.js](http://nodejs.org) which is used to run a development web server, run tests, and
+  generate distributable files. We also use Node's Package Manager (`npm`). Depending on your
+  system, you can install Node either from source or as a pre-packaged bundle.
+
+* [Chrome Canary](https://www.google.com/chrome/browser/canary.html), a version of Chrome with
+  bleeding edge functionality, built especially for developers (and early adopters).
 
-* [Java Development Kit](http://www.oracle.com/technetwork/es/java/javase/downloads/index.html) which is used
-  to execute the selenium standalone server for e2e testing.
 
 ## Getting the Sources
 
-Fork and clone the Angular repository:
+Forking and cloning the Angular repository:
 
-1. Login to your GitHub account or create one by following the instructions given
+1. Login to your Github account or create one by following the instructions given
    [here](https://github.com/signup/free).
 2. [Fork](http://help.github.com/forking) the [main Angular
    repository](https://github.com/angular/angular).
 3. Clone your fork of the Angular repository and define an `upstream` remote pointing back to
-   the Angular repository that you forked in the first place.
+   the Angular repository that you forked in the first place:
 
 ```shell
-# Clone your GitHub repository:
+# Clone your Github repository:
 git clone git@github.com:<github username>/angular.git
 
 # Go to the Angular directory:
@@ -50,141 +61,175 @@ cd angular
 # Add the main Angular repository as an upstream remote to your repository:
 git remote add upstream https://github.com/angular/angular.git
 ```
-## Installing NPM Modules
 
-Next, install the JavaScript modules needed to build and test Angular:
+## Environment Variable Setup
+
+Define the environment variables listed below. These are mainly needed for the testing. The
+notation shown here is for [`bash`](http://www.gnu.org/software/bash); adapt as appropriate for
+your favorite shell.
+
+Examples given below of possible values for initializing the environment variables assume **Mac OS
+X** and that you have installed the Dart Editor in the directory named by
+`DART_EDITOR_DIR=/Applications/dart`. This is only for illustrative purposes.
+
+```shell
+# DARTIUM_BIN: path to a Dartium browser executable; used by Karma to run Dart tests
+export DARTIUM_BIN="$DART_EDITOR_DIR/chromium/Chromium.app/Contents/MacOS/Chromium"
+```
+
+Add the Dart SDK `bin` directory to your path and/or define `DART_SDK` (this is also detailed
+[here](https://www.dartlang.org/tools/pub/installing.html)):
+
+```shell
+# DART_SDK: path to a Dart SDK directory
+export DART_SDK="$DART_EDITOR_DIR/dart-sdk"
+
+# Update PATH to include the Dart SDK bin directory
+PATH+=":$DART_SDK/bin"
+```
+
+## Installing NPM Modules and Dart Packages
+
+Next, install the modules and packages needed to build Angular and run tests:
 
 ```shell
 # Install Angular project dependencies (package.json)
 npm install
+
+# Ensure protractor has the latest webdriver
+$(npm bin)/webdriver-manager update
+
+# Install Dart packages
+pub get
 ```
 
 **Optional**: In this document, we make use of project local `npm` package scripts and binaries
 (stored under `./node_modules/.bin`) by prefixing these command invocations with `$(npm bin)`; in
-particular `gulp` and `protractor` commands. If you prefer, you can drop this path prefix by either:
-
-*Option 1*: globally installing these two packages as follows:
+particular `gulp` and `protractor` commands. If you prefer, you can drop this path prefix by
+globally installing these two packages as follows:
 
 * `npm install -g gulp` (you might need to prefix this command with `sudo`)
 * `npm install -g protractor` (you might need to prefix this command with `sudo`)
 
-Since global installs can become stale, and required versions can vary by project, we avoid their
-use in these instructions.
+Since global installs can become stale, we avoid their use in these instructions.
 
-*Option 2*: globally installing the package `npm-run` by running `npm install -g npm-run`
-(you might need to prefix this command with `sudo`). You will then be able to run locally installed
-package scripts by invoking: e.g., `npm-run gulp build`
-(see [npm-run project page](https://github.com/timoxley/npm-run) for more details).
+## Build commands
 
-
-*Option 3*: defining a bash alias like `alias nbin='PATH=$(npm bin):$PATH'` as detailed in this
-[Stackoverflow answer](http://stackoverflow.com/questions/9679932/how-to-use-package-installed-locally-in-node-modules/15157360#15157360) and used like this: e.g., `nbin gulp build`.
-
-## Installing Bower Modules
-
-Now run `bower` to install additional dependencies:
+To build Angular and prepare tests run
 
 ```shell
-# Install other Angular project dependencies (bower.json)
-bower install
+$(npm bin)/gulp build
 ```
 
-## Windows only
+Notes:
+* Results are put in the `dist` folder.
+* This will also run `pub get` for the subfolders in `modules` and run `dartanalyzer` for
+  every file that matches `<module>/src/<module>.dart`, e.g. `di/src/di.dart`
 
-In order to create the right symlinks, run **as administrator**:
+To clean out the `dist` folder use:
 ```shell
-./scripts/windows/create-symlinks.sh
+$(npm bin)/gulp clean
 ```
 
-Before submitting a PR, do not forget to remove them:
-```shell
- ./scripts/windows/remove-symlinks.sh
- ```
-
-## Building
-
-To build Angular run:
-
-```shell
-./build.sh
-```
-
-* Results are put in the dist folder.
-
 ## Running Tests Locally
 
-To run tests:
+### Basic tests
 
-```shell
-$ ./test.sh node             # Run all angular tests on node
+1. `$(npm bin)/gulp test.unit.js`: JS tests in a browser; runs in **watch mode** (i.e. karma
+  watches the test files for changes and re-runs tests when files are updated).
+2. `$(npm bin)/gulp test.unit.cjs`: JS tests in NodeJS; runs in **watch mode**
+3. `$(npm bin)/gulp test.unit.dart`: Dart tests in Dartium; runs in **watch mode**.
 
-$ ./test.sh browser          # Run all angular tests in browser
-$ ./test.sh browserNoRouter  # Optionally run all angular tests without router in browser
+If you prefer running tests in "single-run" mode rather than watch mode use
 
-$ ./test.sh tools            # Run angular tooling (not framework) tests
-```
+* `$(npm bin)/gulp test.unit.js/ci`
+* `$(npm bin)/gulp test.unit.dart/ci`
 
-You should execute the 3 test suites before submitting a PR to github.
+**Note**: If you want to only run a single test you can alter the test you wish
+to run by changing `it` to `iit` or `describe` to `ddescribe`. This will only
+run that individual test and make it much easier to debug. `xit` and `xdescribe`
+can also be useful to exclude a test and a group of tests respectively.
 
-All the tests are executed on our Continuous Integration infrastructure and a PR could only be merged once the tests pass.
+**Note** for transpiler tests: The karma preprocessor is setup in a way so that after every test
+run the transpiler is reloaded. With that it is possible to make changes to the preprocessor and
+run the tests without exiting karma (just touch a test file that you would like to run).
 
-- CircleCI fails if your code is not formatted properly,
-- Travis CI fails if any of the test suites described above fails.
+### E2e tests
 
-## Update the public API tests
+1. `$(npm bin)/gulp build.js.cjs` (builds benchpress and tests into `dist/js/cjs` folder).
+2. `$(npm bin)/gulp serve.js.prod serve.js.dart2js` (runs local webserver).
+3. `$(npm bin)/protractor protractor-js.conf.js`: JS e2e tests.
+4. `$(npm bin)/protractor protractor-dart2js.conf.js`: Dart2JS e2e tests.
 
-If you happen to modify the public API of Angular, API golden files must be updated using:
+Angular specific command line options when running protractor:
+  - `$(npm bin)/protractor protractor-{js|dart2js}-conf.js --ng-help`
 
-``` shell
-$ gulp public-api:update
-```
+### Performance tests
 
-Note: The command `gulp public-api:enforce` fails when the API doesn't match the golden files. Make sure to rebuild
-the project before trying to verify after an API change.
+1. `$(npm bin)/gulp build.js.cjs` (builds benchpress and tests into `dist/js/cjs` folder)
+2. `$(npm bin)/gulp serve.js.prod serve.js.dart2js` (runs local webserver)
+3. `$(npm bin)/protractor protractor-js.conf.js --benchmark`: JS performance tests
+4. `$(npm bin)/protractor protractor-dart2js.conf.js --benchmark`: Dart2JS performance tests
 
-## <a name="clang-format"></a> Formatting your source code
+Angular specific command line options when running protractor (e.g. force gc, ...):
+`$(npm bin)/protractor protractor-{js|dart2js}-conf.js --ng-help`
 
-Angular uses [clang-format](http://clang.llvm.org/docs/ClangFormat.html) to format the source code. If the source code
-is not properly formatted, the CI will fail and the PR can not be merged.
+## Project Information
 
-You can automatically format your code by running:
+### Folder structure
 
-``` shell
-$ gulp format
-```
+* `modules/*`: modules that will be loaded in the browser
+* `tools/*`: tools that are needed to build Angular
+* `dist/*`: build files are placed here.
 
-## Linting/verifying your source code
+### File suffixes
 
-You can check that your code is properly formatted and adheres to coding style by running:
+* `*.js`: javascript files that get transpiled to Dart and EcmaScript 5
+* `*.es6`: javascript files that get transpiled only to EcmaScript 5
+* `*.es5`: javascript files that don't get transpiled
+* `*.dart`: dart files that don't get transpiled
 
-``` shell
-$ gulp lint
-```
+## CI using Travis
 
-## Publishing snapshot builds
+For instructions on setting up Continuous Integration using Travis, see the instructions given
+[here](https://github.com/angular/angular.dart/blob/master/travis.md).
 
-When the `master` branch successfully builds on Travis, it automatically publishes build artifacts
-to repositories in the Angular org, eg. the `@angular/core` package is published to
-http://github.com/angular/core-builds.
-The ES2015 version of Angular is published to a different branch in these repos, for example
-http://github.com/angular/core-builds#master-es2015
+## Debugging
 
-You may find that your un-merged change needs some validation from external participants.
-Rather than requiring them to pull your Pull Request and build Angular locally, you can
-publish the `*-builds` snapshots just like our Travis build does.
+### Debug the transpiler
 
-First time, you need to create the github repositories:
+If you need to debug the transpiler:
 
-``` shell
-$ export TOKEN=[get one from https://github.com/settings/tokens]
-$ CREATE_REPOS=1 ./scripts/publish/publish-build-artifacts.sh [github username]
-```
+- add a `debugger;` statement in the transpiler code,
+- from the root folder, execute `node debug $(npm bin)/gulp build` to enter the node
+  debugger
+- press "c" to execute the program until you reach the `debugger;` statement,
+- you can then type "repl" to enter the REPL and inspect variables in the context.
 
-For subsequent snapshots, just run
+See the [Node.js manual](http://nodejs.org/api/debugger.html) for more information.
 
-``` shell
-$ ./scripts/publish/publish-build-artifacts.sh [github username]
-```
+Notes:
+- You can also execute `node $(npm bin)/karma start karma-dart.conf.js` depending on which
+  code you want to debug (the former will process the "modules" folder while the later processes
+  the transpiler specs).
+- You can also add `debugger;` statements in the specs (JavaScript). The execution will halt when
+  the developer tools are opened in the browser running Karma.
+
+### Debug the tests
+
+If you need to debug the tests:
+
+- add a `debugger;` statement to the test you want to debug (oe the source code),
+- execute karma `$(npm bin)/gulp test.js`,
+- press the top right "DEBUG" button,
+- open the dev tools and press F5,
+- the execution halt at the `debugger;` statement
+
+**Note (WebStorm users)**:
+You can create a Karma run config from WebStorm.
+Then in the "Run" menu, press "Debug 'karma-js.conf.js'", WebStorm will stop in the generated code
+on the `debugger;` statement.
+You can then step into the code and add watches.
+The `debugger;` statement is needed because WebStorm will stop in a transpiled file. Breakpoints in
+the original source files are not supported at the moment.
 
-The script will publish the build snapshot to a branch with the same name as your current branch,
-and create it if it doesn't exist.

LICENSE

@@ -1,21 +1,202 @@
-The MIT License
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
 
-Copyright (c) 2014-2017 Google, Inc. http://angular.io
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
 
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
+   1. Definitions.
 
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright {yyyy} {name of copyright owner}
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.

NAMING.md

@@ -1,32 +0,0 @@
-Naming Conventions in Angular
----
-
-In general Angular should follow TypeScript naming conventions.
-See: https://github.com/Microsoft/TypeScript/wiki/Coding-guidelines
-
-
-Classes:
-  - Example: `Compiler`, `ApplicationMetadata`
-  - Camel case with first letter upper-case
-  - In general prefer single words. (This is so that when appending `Proto` or `Factory` the class 
-    is still reasonable to work with.)
-  - Should not end with `Impl` or any other word which describes a specific implementation of an 
-    interface.
-  
-  
-Interfaces:
-  - Follow the same rules as Classes 
-  - Should not have `I` or `Interface` in the name or any other way of identifying it as an interface.
-
-  
-Methods and functions:
-  - Example: `bootstrap`, `someMethod`
-  - Should be camel case with first lower case
-
-
-Constants
-  - Example: `CORE_DIRECTIVES`
-  - Should be all uppercase with SNAKE_CASE
-
-
-

README.md

@@ -1,30 +1,52 @@
-[![Build Status](https://travis-ci.org/angular/angular.svg?branch=master)](https://travis-ci.org/angular/angular)
-[![CircleCI](https://circleci.com/gh/angular/angular/tree/master.svg?style=shield)](https://circleci.com/gh/angular/angular/tree/master)
-[![Join the chat at https://gitter.im/angular/angular](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/angular/angular?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
-[![Issue Stats](http://issuestats.com/github/angular/angular/badge/pr?style=flat)](http://issuestats.com/github/angular/angular)
-[![Issue Stats](http://issuestats.com/github/angular/angular/badge/issue?style=flat)](http://issuestats.com/github/angular/angular)
-[![npm version](https://badge.fury.io/js/%40angular%2Fcore.svg)](https://badge.fury.io/js/%40angular%2Fcore)
-
-[![Sauce Test Status](https://saucelabs.com/browser-matrix/angular2-ci.svg)](https://saucelabs.com/u/angular2-ci)
-*Safari (7+), iOS (7+), Edge (14) and IE mobile (11) are tested on [BrowserStack][browserstack].*
-
-Angular
+Angular [![Build Status](https://travis-ci.org/angular/angular.svg?branch=master)](https://travis-ci.org/angular/angular) [![Join the chat at https://gitter.im/angular/angular](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/angular/angular?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 =========
 
-Angular is a development platform for building mobile and desktop web applications using Typescript/JavaScript (JS) and other languages.
+Angular is a development platform for building mobile and desktop web applications. This is the
+repository for [Angular 2][ng2], both the JavaScript (JS) and [Dart][dart] versions.
+
+Angular 2 is currently in **Alpha Preview**. We recommend using Angular 1.X for production
+applications:
+
+* [AngularJS][ngJS]: [angular/angular.js](http://github.com/angular/angular.js).
+* [AngularDart][ngDart]: [angular/angular.dart](http://github.com/angular/angular.dart).
 
 
-## Quickstart
+## Setup & Install Angular 2
 
-[Get started in 5 minutes][quickstart].
+Follow the instructions given on the [Angular download page][download].
 
 
 ## Want to help?
 
-Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our
-guidelines for [contributing][contributing] and then check out one of our issues in the [hotlist: community-help](https://github.com/angular/angular/labels/hotlist%3A%20community-help).
+Want to file a bug, or contribute some code or improve documentation?  Excellent! Read up on our
+guidelines for [contributing][contributing].
+
+
+## Examples
+
+To see the examples, first build the project as described
+[here](http://github.com/angular/angular/blob/master/DEVELOPER.md).
+
+### Hello World Example
+
+This example consists of three basic pieces - a component, a decorator and a
+service.  They are all constructed via injection. For more information see the
+comments in the source `modules/examples/src/hello_world/index.js`.
+
+You can build this example as either JS or Dart app:
+
+* JS:
+  * `$(npm bin)/gulp serve.js.dev`, and
+  * open `localhost:8000/examples/src/hello_world/` in Chrome.
+* Dart:
+  * `$(npm bin)/gulp serve/examples.dart`, and
+  * open `localhost:8080/src/hello_world` in Chrome (for dart2js) or
+    [Dartium][dartium] (for Dart VM).
 
-[browserstack]: https://www.browserstack.com/
 [contributing]: http://github.com/angular/angular/blob/master/CONTRIBUTING.md
-[quickstart]: https://angular.io/docs/ts/latest/quickstart.html
-[ng]: http://angular.io
+[dart]: http://www.dartlang.org
+[dartium]: http://www.dartlang.org/tools/dartium
+[download]: http://angular.io/download
+[ng2]: http://angular.io
+[ngDart]: http://angulardart.org
+[ngJS]: http://angularjs.org

SAVED_REPLIES.md

@@ -1,62 +0,0 @@
-# Saved Responses for Angular's Issue Tracker
-
-The following are canned responses that the Angular team should use to close issues on our issue tracker that fall into the listed resolution categories.
-
-Since GitHub currently doesn't allow us to have a repository-wide or organization-wide list of [saved replies](https://help.github.com/articles/working-with-saved-replies/), these replies need to be maintained by individual team members. Since the responses can be modified in the future, all responses are versioned to simplify the process of keeping the responses up to date.
-
-
-## Angular: Already Fixed (v1)
-```
-Thanks for reporting this issue. Luckily it has already been fixed in one of the recent releases. Please update to the most recent version to resolve the problem.
-
-If after upgrade the problem still exists in your application please open a new issue and provide a plunker reproducing the problem and describing the difference between the expected and current behavior. You can use this plunker template: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5?p=catalogue
-```
-
-## Angular: Don't Understand (v1)
-```
-I'm sorry but we don't understand the problem you are reporting.
-
-If the problem still exists please open a new issue and provide a plunker reproducing the problem and describing the difference between the expected and current behavior. You can use this plunker template: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5?p=catalogue
-```
-
-
-## Angular: Duplicate (v1)
-```
-Thanks for reporting this issue. However this issue is a duplicate of an existing issue #<ISSUE_NUMBER>. Please subscribe to that issue for future updates.
-```
-
-
-## Angular: Insufficient Information Provided (v1)
-```
-Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out [our submission guidelines](https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-submitting-an-issue) to understand why we can't act on issues that are lacking important information.
-
-If the problem still persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.
-```
-
-## Angular: Issue Outside of Angular (v1)
-```
-I'm sorry but this issue is not caused by Angular. Please contact the author(s) of project <PROJECT NAME> or file issue on their issue tracker.
-```
-
-
-## Angular: Non-reproducible (v1)
-```
-I'm sorry but we can't reproduce the problem following the instructions you provided.
-
-If the problem still exists please open a new issue following [our submission guidelines](https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-submitting-an-issue).
-```
-
-## Angular: Obsolete (v1)
-```
-Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular version.
-
-If the problem still persists, please file a new issue and ensure you provide the version of Angular affected and include the steps to reproduce the problem when filling out the issue template.
-```
-
-
-## Angular: Support Request (v1)
-```
-Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on [StackOverflow](http://stackoverflow.com/) using tag `angular`.
-
-If you are wondering why we don't resolve support issues via the issue tracker, please [check out this explanation](https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-got-a-question-or-problem).
-```

TOOLS.md

@@ -1,140 +0,0 @@
-# Developer Tools for Angular
-
-Here you will find a collection of tools and tips for keeping your application
-perform well and contain fewer bugs.
-
-## Angular debug tools in the dev console
-
-Angular provides a set of debug tools that are accessible from any browser's
-developer console. In Chrome the dev console can be accessed by pressing
-Ctrl + Shift + j.
-
-### Enabling debug tools
-
-By default the debug tools are disabled. You can enable debug tools as follows:
-
-```typescript
-import {enableDebugTools} from '@angular/platform-browser';
-
-bootstrap(Application).then((appRef) => {
-  enableDebugTools(appRef);
-});
-```
-
-### Using debug tools
-
-In the browser open the developer console (Ctrl + Shift + j in Chrome). The
-top level object is called `ng` and contains more specific tools inside it.
-
-Example:
-
-```javascript
-ng.profiler.timeChangeDetection();
-```
-
-## Performance
-
-### Change detection profiler
-
-If your application is janky (it misses frames) or is slow according to other
-metrics it is important to find the root cause of the issue. Change detection
-is a phase in Angular's lifecycle that detects changes in values that are
-bound to UI, and if it finds a change it performs the corresponding UI update.
-However, sometimes it is hard to tell if the slowness is due to the act of
-computing the changes being slow, or due to the act of applying those changes
-to the UI. For your application to be performant it is important that the
-process of computing changes is very fast. For best results it should be under
-3 milliseconds in order to leave room for the application logic, the UI updates
-and browser's rendering pipeline to fit withing the 16 millisecond frame
-(assuming the 60 FPS target frame rate).
-
-Change detection profiler repeatedly performs change detection without invoking
-any user actions, such as clicking buttons or entering text in input fields. It
-then computes the average amount of time it took to perform a single cycle of
-change detection in milliseconds and prints it to the console. This number
-depends on the current state of the UI. You will likely see different numbers
-as you go from one screen in your application to another.
-
-#### Running the profiler
-
-Enable debug tools (see above), then in the dev console enter the following:
-
-```javascript
-ng.profiler.timeChangeDetection();
-```
-
-The results will be printed to the console.
-
-#### Recording CPU profile
-
-Pass `{record: true}` an argument:
-
-```javascript
-ng.profiler.timeChangeDetection({record: true});
-```
-
-Then open the "Profiles" tab. You will see the recorded profile titled
-"Change Detection". In Chrome, if you record the profile repeatedly, all the
-profiles will be nested under "Change Detection".
-
-#### Interpreting the numbers
-
-In a properly-designed application repeated attempts to detect changes without
-any user actions should result in no changes to be applied on the UI. It is
-also desirable to have the cost of a user action be proportional to the amount
-of UI changes required. For example, popping up a menu with 5 items should be
-vastly faster than rendering a table of 500 rows and 10 columns. Therefore,
-change detection with no UI updates should be as fast as possible. Ideally the
-number printed by the profiler should be well below the length of a single
-animation frame (16ms). A good rule of thumb is to keep it under 3ms.
-
-#### Investigating slow change detection
-
-So you found a screen in your application on which the profiler reports a very
-high number (i.e. >3ms). This is where a recorded CPU profile can help. Enable
-recording while profiling:
-
-```javascript
-ng.profiler.timeChangeDetection({record: true});
-```
-
-Then look for hot spots using
-[Chrome CPU profiler](https://developer.chrome.com/devtools/docs/cpu-profiling).
-
-#### Reducing change detection cost
-
-There are many reasons for slow change detection. To gain intuition about
-possible causes it would help to understand how change detection works. Such a
-discussion is outside the scope of this document (TODO link to docs), but here
-are some key concepts in brief.
-
-By default Angular uses "dirty checking" mechanism for finding model changes.
-This mechanism involves evaluating every bound expression that's active on the
-UI. These usually include text interpolation via `{{expression}}` and property
-bindings via `[prop]="expression"`. If any of the evaluated expressions are
-costly to compute they could contribute to slow change detection. A good way to
-speed things up is to use plain class fields in your expressions and avoid any
-kinds of computation. Example:
-
-```typescript
-@Component({
-  template: '<button [enabled]="isEnabled">{{title}}</button>'
-})
-class FancyButton {
-  // GOOD: no computation, just return the value
-  isEnabled: boolean;
-
-  // BAD: computes the final value upon request
-  _title: String;
-  get title(): String { return this._title.trim().toUpperCase(); }
-}
-```
-
-Most cases like these could be solved by precomputing the value and storing the
-final value in a field.
-
-Angular also supports a second type of change detection - the "push" model. In
-this model Angular does not poll your component for changes. Instead, the
-component "tells" Angular when it changes and only then does Angular perform
-the update. This model is suitable in situations when your data model uses
-observable or immutable objects (also a discussion for another time).

TRIAGE_AND_LABELS.md

@@ -1,158 +0,0 @@
-# Triage Process and Github Labels for Angular
-
-This document describes how the Angular team uses labels and milestones 
-to triage issues on github. The basic idea of the process is that
-caretaker only assigns a component and type (bug, feature) label. The 
-owner of the component than is in full control of how the issues should 
-be triaged further.
-
-Once this process is implemented and in use, we will revisit it to see 
-if further labeling is needed.
-
-## Components
-
-A caretaker should be able to determine which component the issue 
-belongs to. The components have a clear piece of source code associated
-with it.
-
-* `comp: animations`: `@matsko`
-* `comp: benchpress`: `@tbosch`
-* `comp: build & ci`: `@IgorMinar` -- All build and CI scripts 
-* `comp: common`: `@mhevery`  -- This includes core components / pipes.
-* `comp: core & compiler`: `@tbosch` -- Because core and compiler are very 
-  intertwined, we will be treating them as one.
-* `comp: forms`: `@kara`
-* `comp: http`: `@jeffbcross`
-* `comp: i18n`: `@vicb`
-* `comp: language service`: `@chuckjaz`
-* `comp: metadata-extractor`: `@chuckjaz`
-* `comp: router`: `@vicb`
-* `comp: testing`: `@juliemr`
-* `comp: upgrade`: `@mhevery`
-* `comp: web-worker`: `@vicb`
-* `comp: zones`: `@mhevery`
-
-There are few components which are cross-cutting. They don't have
-a clear location in the source tree. We will treat them as a component
-even thought no specific source tree is associated with them.
-
-* `comp: docs`: `@naomiblack`
-* `comp: packaging`: `@IgorMinar`
-* `comp: performance`: `@tbosch`
-* `comp: security`: `@IgorMinar`
-
-
-## Type
-What kind of problem is this?
-
-* `type: RFC / discussion / question`
-* `type: bug`
-* `type: chore`
-* `type: feature`
-* `type: performance`
-* `type: refactor`
-
-## Caretaker Triage Process
-
-It is the caretaker's responsibility to assign `comp:  *` to each new
-issue as they come in. The reason why we limit the responsibility of the
-caretaker to this one label is that it is likely that without domain
-knowledge the caretaker could mislabel issues or lack knowledge of
-duplicate issues.
-
-
-## Component's owner Triage Process
-
-At this point we are leaving each component owner to determine their own
-process for their component.
-
-It will be up to the component owner to determine the order in which the
-issues within the component will be resolved.
-
-Several owners have adopted the issue categorization based on
-[user pain](http://www.lostgarden.com/2008/05/improving-bug-triage-with-user-pain.html)
-used by AngularJS. In this system every issue is assigned frequency and
-severity based on which the total user pain score is calculated.
-
-Following is the definition of various frequency and severity levels:
-
-1. `freq(score): *` – How often does this issue come up? How many developers does this affect?
-    * low (1) - obscure issue affecting a handful of developers
-    * moderate (2) - impacts auxiliary usage patterns, only small number of applications are affected
-    * high (3) - impacts primary usage patterns, affecting most Angular apps
-    * critical (4) - impacts all Angular apps
-1. `severity(score): *` - How bad is the issue?
-    * inconvenience (1) - causes ugly/boilerplate code in apps
-    * confusing (2) - unexpected or inconsistent behavior; hard-to-debug
-    * broken expected use (3) - it's hard or impossible for a developer using Angular to accomplish something that Angular should be able to do
-    * memory leak (4)
-    * regression (5) - functionality that used to work no longer works in a new release due to an unintentional change
-    * security issue (6)
-
-
-These criteria are then used to calculate a "user pain" score as follows:
-
-`pain = severity × frequency`
-
-
-### Assigning Issues to Milestones
-
-Any issue that is being worked on must have:
-
-* An `Assignee`: The person doing the work.
-* A `Milestone`: When we expect to complete this work.
-
-We aim to only have at most three milestones open at a time:
-
-* Closing Milestone: A milestone with a very small number of issues, about to release. 
-* Current Milestone: Work that we plan to complete within one week.
-* Next Milestone: Work that is > 1 week but current for the team.
-
-The [backlog](https://github.com/angular/angular/issues?q=is%3Aopen+is%3Aissue+no%3Amilestone) 
-consists of all issues that have been triaged but do not have an assignee or milestone.  
-
-## Triaged vs Untrained PRs
-
-PRs should also be label with a `comp: *` so that it is clear which 
-primary area the PR effects.
-
-Because of the cumulative pain associated with rebasing PRs, we triage PRs daily, and 
-closing or reviewing PRs is a top priority ahead of other ongoing work. 
-
-Every triaged PR must have a `pr_action` label assigned to it and an assignee:
- 
-* `pr_action: review` -- work is complete and comment is needed from the assignee.
-* `pr_action: cleanup` -- more work is needed from the current assignee. 
-* `pr_action: discuss` -- discussion is needed, to be led by the current assignee.
-* `pr_action: merge` -- the PR should be merged. Add this to a PR when you would like to 
-  trigger automatic merging following a successful build. This is described in [COMMITTER.md](COMMITTER.md).
-
-In addition, PRs can have the following states:
-
-* `pr_state: LGTM` -- PR may have outstanding changes but does not require further review.
-* `pr_state: WIP` -- PR is experimental or rapidly changing. Not ready for review or triage.
-* `pr_state: blocked` -- PR is blocked on an issue or other PR. Not ready for review or triage.
-
-Note that an LGTM state does not mean a PR is ready to merge: for example, a reviewer might set the
-LGTM state but request a minor tweak that doesn't need further review, e.g., a rebase or small 
-uncontroversial change.
-
-PRs do not need to be assigned to milestones, unless a milestone release should be held for that 
-PR to land.
-
-
-## Special Labels
-
-### action:design
-More active discussion is needed before the issue can be worked on further. Typically used for 
-`type: feature` or `type: RFC/discussion/question`
-
-[See all issues that need discussion](https://github.com/angular/angular/labels/action:%20Design)
-
-### cla
-Managed by googlebot. Indicates whether a PR has a CLA on file for its author(s). Only issues with 
-`cla:yes` should be merged into master.
-
-### WORKS_AS_INTENDED
-
-Only used on closed issues, to indicate to the reporter why we closed it.

angular.io/.firebaserc

@@ -1,5 +0,0 @@
-{
-  "projects": {
-    "staging": "aio-staging"
-  }
-}

angular.io/README.md

@@ -1,31 +0,0 @@
-# Site
-
-This project was generated with [angular-cli](https://github.com/angular/angular-cli) version 1.0.0-beta.26.
-
-## Development server
-Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.
-
-## Code scaffolding
-
-Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive/pipe/service/class/module`.
-
-## Build
-
-Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory. Use the `--prod` flag for a production build.
-
-## Running unit tests
-
-Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.io).
-
-## Running end-to-end tests
-
-Run `ng e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).
-Before running the tests make sure you are serving the app via `ng serve`.
-
-## Deploying to GitHub Pages
-
-Run `ng github-pages:deploy` to deploy to GitHub Pages.
-
-## Further help
-
-To get more help on the `angular-cli` use `ng help` or go check out the [Angular-CLI README](https://github.com/angular/angular-cli/blob/master/README.md).

angular.io/angular-cli.json

@@ -1,59 +0,0 @@
-{
-  "project": {
-    "version": "1.0.0-beta.26",
-    "name": "site"
-  },
-  "apps": [
-    {
-      "root": "src",
-      "outDir": "dist",
-      "assets": [
-        "assets",
-        "favicon.ico"
-      ],
-      "index": "index.html",
-      "main": "main.ts",
-      "polyfills": "polyfills.ts",
-      "test": "test.ts",
-      "tsconfig": "tsconfig.json",
-      "prefix": "app",
-      "styles": [
-        "styles.scss"
-      ],
-      "scripts": [
-
-      ],
-      "environments": {
-        "source": "environments/environment.ts",
-        "dev": "environments/environment.ts",
-        "prod": "environments/environment.prod.ts"
-      }
-    }
-  ],
-  "e2e": {
-    "protractor": {
-      "config": "./protractor.conf.js"
-    }
-  },
-  "test": {
-    "karma": {
-      "config": "./karma.conf.js"
-    }
-  },
-  "defaults": {
-    "styleExt": "css",
-    "prefixInterfaces": false,
-    "inline": {
-      "style": false,
-      "template": false
-    },
-    "spec": {
-      "class": false,
-      "component": true,
-      "directive": true,
-      "module": false,
-      "pipe": true,
-      "service": true
-    }
-  }
-}

angular.io/database.rules.json

@@ -1,6 +0,0 @@
-{
-  "rules": {
-    ".read": "auth != null",
-    ".write": "auth != null"
-  }
-}

angular.io/e2e/app.e2e-spec.ts

@@ -1,14 +0,0 @@
-import { SitePage } from './app.po';
-
-describe('site App', function() {
-  let page: SitePage;
-
-  beforeEach(() => {
-    page = new SitePage();
-  });
-
-  it('should display message saying app works', () => {
-    page.navigateTo();
-    expect(page.getParagraphText()).toEqual('home-page works!');
-  });
-});

angular.io/e2e/app.po.ts

@@ -1,11 +0,0 @@
-import { browser, element, by } from 'protractor';
-
-export class SitePage {
-  navigateTo() {
-    return browser.get('/');
-  }
-
-  getParagraphText() {
-    return element(by.css('app-home-page p')).getText();
-  }
-}

angular.io/e2e/tsconfig.json

@@ -1,16 +0,0 @@
-{
-  "compileOnSave": false,
-  "compilerOptions": {
-    "declaration": false,
-    "emitDecoratorMetadata": true,
-    "experimentalDecorators": true,
-    "module": "commonjs",
-    "moduleResolution": "node",
-    "outDir": "../dist/out-tsc-e2e",
-    "sourceMap": true,
-    "target": "es5",
-    "typeRoots": [
-      "../node_modules/@types"
-    ]
-  }
-}

angular.io/firebase.json

@@ -1,14 +0,0 @@
-{
-  "database": {
-    "rules": "database.rules.json"
-  },
-  "hosting": {
-    "public": "dist",
-    "rewrites": [
-      {
-        "source": "**",
-        "destination": "/index.html"
-      }
-    ]
-  }
-}

angular.io/karma.conf.js

@@ -1,42 +0,0 @@
-// Karma configuration file, see link for more information
-// https://karma-runner.github.io/0.13/config/configuration-file.html
-module.exports = function (config) {
-  config.set({
-    basePath: '',
-    frameworks: ['jasmine', 'angular-cli'],
-    plugins: [
-      require('karma-jasmine'),
-      require('karma-chrome-launcher'),
-      require('karma-remap-istanbul'),
-      require('angular-cli/plugins/karma')
-    ],
-    files: [
-      { pattern: './src/test.ts', watched: false }
-    ],
-    preprocessors: {
-      './src/test.ts': ['angular-cli']
-    },
-    mime: {
-      'text/x-typescript': ['ts','tsx']
-    },
-    remapIstanbulReporter: {
-      reports: {
-        html: 'coverage',
-        lcovonly: './coverage/coverage.lcov'
-      }
-    },
-    angularCli: {
-      config: './angular-cli.json',
-      environment: 'dev'
-    },
-    reporters: config.angularCli && config.angularCli.codeCoverage
-              ? ['progress', 'karma-remap-istanbul']
-              : ['progress'],
-    port: 9876,
-    colors: true,
-    logLevel: config.LOG_INFO,
-    autoWatch: true,
-    browsers: ['Chrome'],
-    singleRun: false
-  });
-};

angular.io/package.json

@@ -1,56 +0,0 @@
-{
-  "name": "angular.io",
-  "version": "0.0.0",
-  "main": "index.js",
-  "repository": "git@github.com:angular/angular.git",
-  "author": "Angular",
-  "license": "MIT",
-  "angular-cli": {},
-  "scripts": {
-    "ng": "ng",
-    "start": "ng serve",
-    "build": "ng build",
-    "lint": "tslint \"src/**/*.ts\" --project src/tsconfig.json --type-check && tslint \"e2e/**/*.ts\" --project e2e/tsconfig.json --type-check",
-    "test": "ng test",
-    "pree2e": "webdriver-manager update --standalone false --gecko false",
-    "e2e": "protractor",
-    "deploy-staging": "firebase use staging --token \"$FIREBASE_TOKEN\" && yarn run ~~deploy",
-    "pre~~deploy": "ng build --prod",
-    "~~deploy": "firebase deploy --message \"Commit: $TRAVIS_COMMIT\" --non-interactive --token \"$FIREBASE_TOKEN\""
-  },
-  "private": true,
-  "dependencies": {
-    "@angular/common": "^2.3.1",
-    "@angular/compiler": "^2.3.1",
-    "@angular/core": "^2.3.1",
-    "@angular/forms": "^2.3.1",
-    "@angular/http": "^2.3.1",
-    "@angular/material": "^2.0.0-beta.1",
-    "@angular/platform-browser": "^2.3.1",
-    "@angular/platform-browser-dynamic": "^2.3.1",
-    "@angular/router": "^3.3.1",
-    "core-js": "^2.4.1",
-    "rxjs": "^5.0.1",
-    "ts-helpers": "^1.1.1",
-    "zone.js": "^0.7.2"
-  },
-  "devDependencies": {
-    "@angular/compiler-cli": "^2.3.1",
-    "@types/jasmine": "2.5.38",
-    "@types/node": "^6.0.42",
-    "angular-cli": "1.0.0-beta.26",
-    "codelyzer": "~2.0.0-beta.1",
-    "firebase-tools": "^3.2.1",
-    "jasmine-core": "2.5.2",
-    "jasmine-spec-reporter": "2.5.0",
-    "karma": "1.2.0",
-    "karma-chrome-launcher": "^2.0.0",
-    "karma-cli": "^1.0.1",
-    "karma-jasmine": "^1.0.2",
-    "karma-remap-istanbul": "^0.2.1",
-    "protractor": "~4.0.13",
-    "ts-node": "1.2.1",
-    "tslint": "^4.3.0",
-    "typescript": "2.0.10"
-  }
-}

angular.io/protractor.conf.js

@@ -1,39 +0,0 @@
-// Protractor configuration file, see link for more information
-// https://github.com/angular/protractor/blob/master/lib/config.ts
-
-/*global jasmine */
-var SpecReporter = require('jasmine-spec-reporter');
-
-exports.config = {
-  allScriptsTimeout: 11000,
-  getPageTimeout: 30000,
-  specs: [
-    './e2e/**/*.e2e-spec.ts'
-  ],
-  capabilities: {
-    'browserName': 'chrome'
-  },
-  directConnect: true,
-  baseUrl: 'http://localhost:4200/',
-  framework: 'jasmine2',
-  jasmineNodeOpts: {
-    showColors: true,
-    defaultTimeoutInterval: 30000,
-    print: function() {}
-  },
-  useAllAngular2AppRoots: true,
-  beforeLaunch: function() {
-    require('ts-node').register({
-      project: 'e2e'
-    });
-  },
-  onPrepare: function() {
-    jasmine.getEnv().addReporter(new SpecReporter());
-  }
-};
-
-if (process.env.TRAVIS) {
-  exports.config.capabilities.chromeOptions = {
-    binary: process.env.CHROME_BIN
-  };
-}

angular.io/src/app/app.component.html

@@ -1,7 +0,0 @@
-<md-toolbar color="primary" class="app-toolbar">
-  <span>Angular</span>
-
-</md-toolbar>
-<section class="app-content">
-  <router-outlet></router-outlet>
-</section>

angular.io/src/app/app.component.spec.ts

@@ -1,38 +0,0 @@
-// /* tslint:disable:no-unused-variable */
-
-// import { TestBed, async } from '@angular/core/testing';
-// import { AppComponent } from './app.component';
-
-describe('AppComponent', () => {
-  // beforeEach(() => {
-  //   TestBed.configureTestingModule({
-  //     declarations: [
-  //       AppComponent
-  //     ],
-  //   });
-  //   TestBed.compileComponents();
-  // });
-  it('should work', () => {
-    expect(true).toBe(true);
-  });
-});
-
-//   it('should create the app', async(() => {
-//     const fixture = TestBed.createComponent(AppComponent);
-//     const app = fixture.debugElement.componentInstance;
-//     expect(app).toBeTruthy();
-//   }));
-
-//   it(`should have as title 'app works!'`, async(() => {
-//     const fixture = TestBed.createComponent(AppComponent);
-//     const app = fixture.debugElement.componentInstance;
-//     expect(app.title).toEqual('app works!');
-//   }));
-
-//   it('should render title in a h1 tag', async(() => {
-//     const fixture = TestBed.createComponent(AppComponent);
-//     fixture.detectChanges();
-//     const compiled = fixture.debugElement.nativeElement;
-//     expect(compiled.querySelector('h1').textContent).toContain('app works!');
-//   }));
-// });

angular.io/src/app/app.component.ts

@@ -1,10 +0,0 @@
-import { Component } from '@angular/core';
-
-@Component({
-  selector: 'app-shell',
-  templateUrl: './app.component.html',
-  styleUrls: ['./app.component.scss']
-})
-export class AppComponent {
-  title = 'app works!';
-}

angular.io/src/app/app.module.ts

@@ -1,21 +0,0 @@
-import { BrowserModule } from '@angular/platform-browser';
-import { NgModule } from '@angular/core';
-import { RouterModule } from '@angular/router';
-import { AppComponent } from './app.component';
-import { MdToolbarModule } from '@angular/material/toolbar';
-
-@NgModule({
-  declarations: [
-    AppComponent
-  ],
-  imports: [
-    BrowserModule,
-    MdToolbarModule.forRoot(),
-    RouterModule.forRoot([
-      { path: '', loadChildren: './home-page/home-page.module#HomePageModule'}
-    ])
-  ],
-  providers: [],
-  bootstrap: [AppComponent]
-})
-export class AppModule { }

angular.io/src/app/docs-app/docs-app.component.html

@@ -1,3 +0,0 @@
-<p>
-  docs-app works!
-</p>

angular.io/src/app/docs-app/docs-app.component.spec.ts

@@ -1,28 +0,0 @@
-// /* tslint:disable:no-unused-variable */
-// import { async, ComponentFixture, TestBed } from '@angular/core/testing';
-// import { By } from '@angular/platform-browser';
-// import { DebugElement } from '@angular/core';
-
-// import { DocsAppComponent } from './docs-app.component';
-
-// describe('DocsAppComponent', () => {
-//   let component: DocsAppComponent;
-//   let fixture: ComponentFixture<DocsAppComponent>;
-
-//   beforeEach(async(() => {
-//     TestBed.configureTestingModule({
-//       declarations: [ DocsAppComponent ]
-//     })
-//     .compileComponents();
-//   }));
-
-//   beforeEach(() => {
-//     fixture = TestBed.createComponent(DocsAppComponent);
-//     component = fixture.componentInstance;
-//     fixture.detectChanges();
-//   });
-
-//   it('should create', () => {
-//     expect(component).toBeTruthy();
-//   });
-// });

angular.io/src/app/docs-app/docs-app.component.ts

@@ -1,15 +0,0 @@
-import { Component, OnInit } from '@angular/core';
-
-@Component({
-  selector: 'app-ngio-docs',
-  templateUrl: './docs-app.component.html',
-  styleUrls: ['./docs-app.component.css']
-})
-export class DocsAppComponent implements OnInit {
-
-  constructor() { }
-
-  ngOnInit() {
-  }
-
-}

angular.io/src/app/docs-app/docs-app.module.ts

@@ -1,19 +0,0 @@
-import { NgModule } from '@angular/core';
-import { CommonModule } from '@angular/common';
-import { DocsAppComponent } from './docs-app.component';
-import { RouterModule } from '@angular/router';
-
-@NgModule({
-  imports: [
-    CommonModule,
-    RouterModule.forChild([
-      { path: '', pathMatch: 'full', component: DocsAppComponent}
-    ])
-  ],
-  declarations: [
-    DocsAppComponent
-  ]
-})
-export class DocsAppModule {
-
-}

angular.io/src/app/home-page/home-page.component.html

@@ -1,3 +0,0 @@
-<p>
-  home-page works!
-</p>

angular.io/src/app/home-page/home-page.component.spec.ts

@@ -1,28 +0,0 @@
-// /* tslint:disable:no-unused-variable */
-// import { async, ComponentFixture, TestBed } from '@angular/core/testing';
-// import { By } from '@angular/platform-browser';
-// import { DebugElement } from '@angular/core';
-
-// import { HomePageComponent } from './home-page.component';
-
-// describe('HomePageComponent', () => {
-//   let component: HomePageComponent;
-//   let fixture: ComponentFixture<HomePageComponent>;
-
-//   beforeEach(async(() => {
-//     TestBed.configureTestingModule({
-//       declarations: [ HomePageComponent ]
-//     })
-//     .compileComponents();
-//   }));
-
-//   beforeEach(() => {
-//     fixture = TestBed.createComponent(HomePageComponent);
-//     component = fixture.componentInstance;
-//     fixture.detectChanges();
-//   });
-
-//   it('should create', () => {
-//     expect(component).toBeTruthy();
-//   });
-// });

angular.io/src/app/home-page/home-page.component.ts

@@ -1,15 +0,0 @@
-import { Component, OnInit } from '@angular/core';
-
-@Component({
-  selector: 'app-home-page',
-  templateUrl: './home-page.component.html',
-  styleUrls: ['./home-page.component.css']
-})
-export class HomePageComponent implements OnInit {
-
-  constructor() { }
-
-  ngOnInit() {
-  }
-
-}

angular.io/src/app/home-page/home-page.module.ts

@@ -1,15 +0,0 @@
-import { NgModule } from '@angular/core';
-import { CommonModule } from '@angular/common';
-import { HomePageComponent } from './home-page.component';
-import { RouterModule } from '@angular/router';
-
-@NgModule({
-  imports: [
-    CommonModule,
-    RouterModule.forChild([
-      { path: '', component: HomePageComponent }
-    ])
-  ],
-  declarations: [HomePageComponent]
-})
-export class HomePageModule { }

angular.io/src/assets/documents/docs/api/common/date-pipe.html

@@ -1,239 +0,0 @@
-<header class="hero background-sky"><h1 class="hero-title is-standard-case">DatePipe</h1><span
-    class="badge is-stable">Stable</span>
-  <div class="clear"></div>
-  <h2 class="hero-subtitle">Pipe</h2></header>
-<article class="l-content-small grid-fluid docs-content">
-  <div layout="row" layout-xs="column" class="row-margin">
-    <div flex="20" flex-xs="100"><h2 class="h2-api-docs">What it does</h2></div>
-    <div flex="80" flex-xs="100"><p>Formats a date according to locale rules.</p>
-    </div>
-  </div>
-  <div layout="row" layout-xs="column" class="row-margin">
-    <div flex="20" flex-xs="100"><h2 class="h2-api-docs">How to use</h2></div>
-    <div flex="80" flex-xs="100"><p><code>date_expression | date[:format]</code></p>
-    </div>
-  </div>
-  <div layout="row" layout-xs="column" class="row-margin">
-    <div flex="20" flex-xs="100"><h2 class="h2-api-docs">NgModule</h2></div>
-    <div flex="80" flex-xs="100" class="code-links">CommonModule
-
-    </div>
-  </div>
-  <div layout="row" layout-xs="column" class="row-margin">
-    <div flex="20" flex-xs="100"><h2 class="h2-api-docs">Description</h2></div>
-    <div flex="80" flex-xs="100" class="code-links"><p>Where:</p>
-      <ul>
-        <li><code>expression</code> is a date object or a number (milliseconds since UTC epoch) or
-          an ISO string
-          (<a href="https://www.w3.org/TR/NOTE-datetime">https://www.w3.org/TR/NOTE-datetime</a>).
-        </li>
-        <li><code>format</code> indicates which date/time components to include. The format can be
-          predifined as
-          shown below or custom as shown in the table.
-          <ul>
-            <li><code>&#39;medium&#39;</code>: equivalent to <code>&#39;yMMMdjms&#39;</code> (e.g.
-              <code>Sep 3, 2010, 12:05:08 PM</code> for <code>en-US</code>)
-            </li>
-            <li><code>&#39;short&#39;</code>: equivalent to <code>&#39;yMdjm&#39;</code> (e.g.
-              <code>9/3/2010, 12:05 PM</code> for <code>en-US</code>)
-            </li>
-            <li><code>&#39;fullDate&#39;</code>: equivalent to <code>&#39;yMMMMEEEEd&#39;</code>
-              (e.g. <code>Friday, September 3, 2010</code> for <code>en-US</code>)
-            </li>
-            <li><code>&#39;longDate&#39;</code>: equivalent to <code>&#39;yMMMMd&#39;</code> (e.g.
-              <code>September 3, 2010</code> for <code>en-US</code>)
-            </li>
-            <li><code>&#39;mediumDate&#39;</code>: equivalent to <code>&#39;yMMMd&#39;</code> (e.g.
-              <code>Sep 3, 2010</code> for <code>en-US</code>)
-            </li>
-            <li><code>&#39;shortDate&#39;</code>: equivalent to <code>&#39;yMd&#39;</code> (e.g.
-              <code>9/3/2010</code> for <code>en-US</code>)
-            </li>
-            <li><code>&#39;mediumTime&#39;</code>: equivalent to <code>&#39;jms&#39;</code> (e.g.
-              <code>12:05:08 PM</code> for <code>en-US</code>)
-            </li>
-            <li><code>&#39;shortTime&#39;</code>: equivalent to <code>&#39;jm&#39;</code> (e.g.
-              <code>12:05 PM</code> for <code>en-US</code>)
-            </li>
-          </ul>
-        </li>
-      </ul>
-      <table>
-        <thead>
-        <tr>
-          <th>Component</th>
-          <th style="text-align:center">Symbol</th>
-          <th>Narrow</th>
-          <th>Short Form</th>
-          <th>Long Form</th>
-          <th>Numeric</th>
-          <th>2-digit</th>
-        </tr>
-        </thead>
-        <tbody>
-        <tr>
-          <td>era</td>
-          <td style="text-align:center">G</td>
-          <td>G (A)</td>
-          <td>GGG (AD)</td>
-          <td>GGGG (Anno Domini)</td>
-          <td>-</td>
-          <td>-</td>
-        </tr>
-        <tr>
-          <td>year</td>
-          <td style="text-align:center">y</td>
-          <td>-</td>
-          <td>-</td>
-          <td>-</td>
-          <td>y (2015)</td>
-          <td>yy (15)</td>
-        </tr>
-        <tr>
-          <td>month</td>
-          <td style="text-align:center">M</td>
-          <td>L (S)</td>
-          <td>MMM (Sep)</td>
-          <td>MMMM (September)</td>
-          <td>M (9)</td>
-          <td>MM (09)</td>
-        </tr>
-        <tr>
-          <td>day</td>
-          <td style="text-align:center">d</td>
-          <td>-</td>
-          <td>-</td>
-          <td>-</td>
-          <td>d (3)</td>
-          <td>dd (03)</td>
-        </tr>
-        <tr>
-          <td>weekday</td>
-          <td style="text-align:center">E</td>
-          <td>E (S)</td>
-          <td>EEE (Sun)</td>
-          <td>EEEE (Sunday)</td>
-          <td>-</td>
-          <td>-</td>
-        </tr>
-        <tr>
-          <td>hour</td>
-          <td style="text-align:center">j</td>
-          <td>-</td>
-          <td>-</td>
-          <td>-</td>
-          <td>j (13)</td>
-          <td>jj (13)</td>
-        </tr>
-        <tr>
-          <td>hour12</td>
-          <td style="text-align:center">h</td>
-          <td>-</td>
-          <td>-</td>
-          <td>-</td>
-          <td>h (1 PM)</td>
-          <td>hh (01 PM)</td>
-        </tr>
-        <tr>
-          <td>hour24</td>
-          <td style="text-align:center">H</td>
-          <td>-</td>
-          <td>-</td>
-          <td>-</td>
-          <td>H (13)</td>
-          <td>HH (13)</td>
-        </tr>
-        <tr>
-          <td>minute</td>
-          <td style="text-align:center">m</td>
-          <td>-</td>
-          <td>-</td>
-          <td>-</td>
-          <td>m (5)</td>
-          <td>mm (05)</td>
-        </tr>
-        <tr>
-          <td>second</td>
-          <td style="text-align:center">s</td>
-          <td>-</td>
-          <td>-</td>
-          <td>-</td>
-          <td>s (9)</td>
-          <td>ss (09)</td>
-        </tr>
-        <tr>
-          <td>timezone</td>
-          <td style="text-align:center">z</td>
-          <td>-</td>
-          <td>-</td>
-          <td>z (Pacific Standard Time)</td>
-          <td>-</td>
-          <td>-</td>
-        </tr>
-        <tr>
-          <td>timezone</td>
-          <td style="text-align:center">Z</td>
-          <td>-</td>
-          <td>Z (GMT-8:00)</td>
-          <td>-</td>
-          <td>-</td>
-          <td>-</td>
-        </tr>
-        <tr>
-          <td>timezone</td>
-          <td style="text-align:center">a</td>
-          <td>-</td>
-          <td>a (PM)</td>
-          <td>-</td>
-          <td>-</td>
-          <td>-</td>
-        </tr>
-        </tbody>
-      </table>
-      <p>In javascript, only the components specified will be respected (not the ordering,
-        punctuations, ...) and details of the formatting will be dependent on the locale.</p>
-      <p>Timezone of the formatted text will be the local system timezone of the end-user&#39;s
-        machine.</p>
-      <p>WARNINGS:</p>
-      <ul>
-        <li>this pipe is marked as pure hence it will not be re-evaluated when the input is mutated.
-          Instead users should treat the date as an immutable object and change the reference when
-          the
-          pipe needs to re-run (this is to avoid reformatting the date on every change detection run
-          which would be an expensive operation).
-        </li>
-        <li>this pipe uses the Internationalization API. Therefore it is only reliable in Chrome and
-          Opera
-          browsers.
-        </li>
-      </ul>
-      <h3 id="examples">Examples</h3>
-      <p>Assuming <code>dateObj</code> is (year: 2015, month: 6, day: 15, hour: 21, minute: 43,
-        second: 11)
-        in the <em>local</em> time and locale is &#39;en-US&#39;:</p>
-      <code-example format="linenums" language="js">{{ dateObj | date }} // output is &#039;Jun 15,
-        2015&#039;
-        {{ dateObj | date:&#039;medium&#039; }} // output is &#039;Jun 15, 2015, 9:43:11 PM&#039;
-        {{ dateObj | date:&#039;shortTime&#039; }} // output is &#039;9:43 PM&#039;
-        {{ dateObj | date:&#039;mmss&#039; }} // output is &#039;43:11&#039;
-      </code-example>
-      <div class="code-example">
-        <code-example language="ts" format="linenums">@Component({
-          selector: &#39;date-pipe&#39;,
-          template: `&lt;div&gt;
-          &lt;p&gt;Today is {{today | date}}&lt;/p&gt;
-          &lt;p&gt;Or if you prefer, {{today | date:&#39;fullDate&#39;}}&lt;/p&gt;
-          &lt;p&gt;The time is {{today | date:&#39;jmZ&#39;}}&lt;/p&gt;
-          &lt;/div&gt;`
-          })
-          export class DatePipeComponent {
-          today: number = Date.now();
-          }
-        </code-example>
-      </div>
-    </div>
-  </div>
-  <p class="location-badge">exported from <a href="index.html">@angular/common/index</a>
-    defined in <a
-        href="https://github.com/angular/angular/tree/2.2.0-beta.1/modules/@angular/common/src/pipes/date_pipe.ts#L12-L116">@angular/common/src/pipes/date_pipe.ts</a>
-  </p></article>

angular.io/src/assets/documents/docs/api/index.html

@@ -1,7 +0,0 @@
-<br><br>
-TODO: api index doc
-<br><br>
-In the meantime visit our awesome <a href="docs/api/common/date-pipe">DatePipe API page</a>.
-<br><br>
-<br><br>
-<br><br>

angular.io/src/assets/documents/docs/guide/overview.html

@@ -1 +0,0 @@
-TODO: guide overview doc

angular.io/src/assets/documents/docs/index.html

@@ -1,7 +0,0 @@
-<br><br>
-TODO: docs index doc
-<br><br>
-<a href="docs/api/">API index page</a>
-<br><br>
-<br><br>
-<br><br>

angular.io/src/assets/documents/events.html

@@ -1,38 +0,0 @@
-<header class="hero background-sky"><h1 class="hero-title ">Events</h1>
-  <div class="clear"></div>
-  <h2 class="hero-subtitle">Where we'll be presenting</h2>
-</header>
-<article class="l-content ">
-  <table class="is-full-width">
-    <thead>
-    <tr>
-      <th>Event</th>
-      <th>Location</th>
-      <th>Date</th>
-    </tr>
-    </thead>
-    <tbody><!-- Devoxx Belgium -->
-    <tr>
-      <th><a target="_blank" href="https://www.devoxx.be/">Devoxx Belgium</a></th>
-      <td>Antwerp, Belgium</td>
-      <td>Nov. 7-11, 2016</td>
-    </tr><!-- DEVIntersection -->
-    <tr>
-      <th><a target="_blank" href="https://www.devintersectioneurope.com/">DEVintersection
-        Europe</a></th>
-      <td>Amsterdam, Netherlands</td>
-      <td>Nov 14-16, 2016</td>
-    </tr><!-- dotJS -->
-    <tr>
-      <th><a target="_blank" href="http://www.dotjs.io/">dotJS</a></th>
-      <td>Paris, France</td>
-      <td>Dec. 5, 2016</td>
-    </tr><!-- NG-BE -->
-    <tr>
-      <th><a target="_blank" href="https://ng-be.org/">NG-BE</a></th>
-      <td>Ghent, Belgium</td>
-      <td>Dec. 9, 2016</td>
-    </tr>
-    </tbody>
-  </table>
-</article>

angular.io/src/assets/documents/features.html

@@ -1,64 +0,0 @@
-<header class="hero background-sky"><h1 class="hero-title ">Features &amp; Benefits</h1>
-  <div class="clear"></div>
-</header>
-<article class="l-content ">
-  <div>
-    <div><h2 class="text-headline">Cross Platform</h2>
-      <div class="feature-row">
-        <div class="feature"><h3>Progressive web apps</h3>
-          <p class="text-body">Use modern web platform capabilities to deliver app-like experiences.
-            High performance, offline, and zero-step installation.</p></div>
-        <div class="feature"><h3>Native</h3>
-          <p class="text-body">Build native mobile apps with strategies from Ionic Framework,
-            NativeScript, and React Native.</p></div>
-        <div class="feature"><h3>Desktop</h3>
-          <p class="text-body">Create desktop-installed apps across Mac, Windows, and Linux using
-            the same Angular methods you've learned for the web plus the ability to access native OS
-            APIs.</p></div>
-      </div>
-      <h2 class="text-headline">Speed and Performance</h2>
-      <div class="feature-row">
-        <div class="feature"><h3>Code generation</h3>
-          <p class="text-body">Angular turns your templates into code that's highly optimized for
-            today's JavaScript virtual machines, giving you all the benefits of hand-written code
-            with the productivity of a framework.</p></div>
-        <div class="feature"><h3>Universal</h3>
-          <p class="text-body">Serve the first view of your application on node.js, .NET, PHP, and
-            other servers for near-instant rendering in just HTML and CSS. Also paves the way for
-            sites that optimize for SEO.</p></div>
-        <div class="feature"><h3>Code splitting</h3>
-          <p class="text-body">Angular apps load quickly with the new Component Router, which
-            delivers automatic code-splitting so users only load code required to render the view
-            they request.</p></div>
-      </div>
-      <h2 class="text-headline">Productivity</h2>
-      <div class="feature-row">
-        <div class="feature"><h3>Templates</h3>
-          <p class="text-body">Quickly create UI views with simple and powerful template syntax.</p>
-        </div>
-        <div class="feature"><h3>Angular CLI</h3>
-          <p class="text-body">Command line tools: start building fast, add components and tests,
-            then instantly deploy.</p></div>
-        <div class="feature"><h3>IDEs</h3>
-          <p class="text-body">Get intelligent code completion, instant errors, and other feedback
-            in popular editors and IDEs.</p></div>
-      </div>
-      <h2 class="text-headline">Full Development Story</h2>
-      <div class="feature-row">
-        <div class="feature"><h3>Testing</h3>
-          <p class="text-body">With Karma for unit tests, you can know if you've broken things every
-            time you save. And Protractor makes your scenario tests run faster and in a stable
-            manner.</p></div>
-        <div class="feature"><h3>Animation</h3>
-          <p class="text-body">Create high-performance, complex choreographies and animation
-            timelines with very little code through Angular's intuitive API.</p></div>
-        <div class="feature"><h3>Accessibility</h3>
-          <p class="text-body">Create accessible applications with ARIA-enabled components,
-            developer guides, and built-in a11y test infrastructure.</p></div>
-      </div>
-    </div>
-  </div>
-  <div class="cta-bar"><a href="/docs/ts/latest/quickstart.html" md-button="md-button"
-                          class="button button-large button-shield md-raised md-primary">Get
-    Started</a></div>
-</article>

angular.io/src/assets/documents/home.html

@@ -1,72 +0,0 @@
-<header class="background-sky l-relative">
-  <div class="hero background-superhero-paper is-large"><img
-      src="assets/images/logos/angular2/angular.svg" class="hero-logo"/>
-    <h1 class="text-headline">One framework.<br>Mobile &amp; desktop.</h1><a
-        href="/docs/ts/latest/quickstart.html" md-button="md-button"
-        class="hero-cta md-raised button button-large button-plain">Get Started</a></div>
-  <announcement-bar class="announcement-bar">
-    <div class="announcement-bar-slide cleafix is-visible"><img
-        src="assets/images/logos/anglebrackets/devintersection.png" width="64"/>
-      <p>Join us for <strong>DEVintersection Amsterdam</strong> Nov 14-16!</p><a
-          href="https://www.devintersectioneurope.com/#!/" target="_blank" class="button md-button">Register
-        now</a></div>
-  </announcement-bar>
-</header>
-<article class="l-content ">
-  <div class="home-rows"><!-- Group 1-->
-    <div layout="row" layout-xs="column" class="home-row">
-      <div class="promo-img-container promo-1">
-        <div><img src="assets/images/home/responsive-framework.svg"></div>
-      </div>
-      <div class="text-container">
-        <div class="text-block promo-1-desc l-pad-top-2"><h3 class="text-headline">Develop Across
-          All Platforms</h3>
-          <p class="text-body">Learn one way to build applications with Angular and reuse your code
-            and abilities to build apps for any deployment target. For web, mobile web, native
-            mobile and native desktop.
-          </p></div>
-      </div>
-    </div><!-- Group 2-->
-    <div layout="row" layout-xs="column" class="home-row">
-      <div class="text-container">
-        <div class="text-block"><h3 class="text-headline">Speed & Performance</h3>
-          <p class="text-body">Achieve the maximum speed possible on the Web Platform today, and
-            take it further, via Web Workers and server-side rendering.</p>
-          <p class="text-body">Angular puts you in control over scalability. Meet huge data
-            requirements by building data models on RxJS, Immutable.js or another push-model.</p>
-        </div>
-      </div>
-      <div class="promo-img-container promo-2">
-        <div><img src="assets/images/home/speed-performance.svg"></div>
-      </div>
-    </div><!-- Group 3-->
-    <div layout="row" layout-xs="column" class="home-row">
-      <div class="promo-img-container promo-3">
-        <div><img src="assets/images/home/joyful-development.png"></div>
-      </div>
-      <div class="text-container">
-        <div class="text-block promo-3-desc"><h3 class="text-headline">Incredible Tooling</h3>
-          <p class="text-body">Build features quickly with simple, declarative templates. Extend the
-            template language with your own components and use a wide array of existing components.
-            Get immediate Angular-specific help and feedback with nearly every IDE and editor. All
-            this comes together so you can focus on building amazing apps rather than trying to make
-            the code work.
-          </p></div>
-      </div>
-    </div><!-- Group 4-->
-    <div layout="row" layout-xs="column" class="home-row">
-      <div class="text-container">
-        <div class="text-block l-pad-top-2"><h3 class="text-headline">Loved by Millions</h3>
-          <p class="text-body">From prototype through global deployment, Angular delivers the
-            productivity and scalable infrastructure that supports Google's largest
-            applications.</p></div>
-      </div>
-      <div class="promo-img-container promo-4">
-        <div><img src="assets/images/home/loved-by-millions.png"></div>
-      </div>
-    </div>
-    <div class="cta-bar"><a href="/docs/ts/latest/quickstart.html" md-button="md-button"
-                            class="button button-large button-shield md-raised md-primary">Get
-      Started</a></div>
-  </div>
-</article>

angular.io/src/assets/documents/news.html

@@ -1,115 +0,0 @@
-<header class="hero background-sky"><h1 class="hero-title ">News</h1>
-  <div class="clear"></div>
-</header>
-<article class="l-content ">
-  <div class="grid-fluid l-space-bottom-2">
-    <div class="c12 text-center"><h3 class="text-headline text-uppercase"> Core Team</h3></div>
-    <div class="clear"></div>
-  </div>
-  <div class="grid-fluid">
-    <div class="c6">
-      <div class="article-card">
-        <div class="date">Oct 12, 2016</div>
-        <div class="title"><a target="_blank"
-                              href="http://angularjs.blogspot.com/2016/10/angular-210-now-available.html">Angular
-          2.1.0 Now Available</a></div>
-        <p>Angular version 2.1.0 - incremental-metamorphosis - is a minor release following our
-          announced adoption of Semantic Versioning...</p>
-        <div class="author"><img src="assets/images/bios/stephenfluin.jpg">
-          <div class="posted">Posted by <b>Stephen Fluin</b></div>
-        </div>
-      </div>
-    </div>
-    <div class="c6">
-      <div class="article-card">
-        <div class="date">Oct 7, 2016</div>
-        <div class="title"><a target="_blank"
-                              href="http://angularjs.blogspot.com/2016/10/versioning-and-releasing-angular.html">Versioning
-          and Releasing Angular</a></div>
-        <p>In order for the ecosystem around Angular to thrive, developers need stability from the
-          Angular framework so that reusable components and libraries, tools and learned practices
-          don’t go obsolete unexpectedly...</p>
-        <div class="author"><img src="assets/images/bios/igor-minar.jpg">
-          <div class="posted">Posted by <b>Igor Minar</b></div>
-        </div>
-      </div>
-    </div>
-  </div>
-  <div class="grid-fluid l-space-bottom-2 l-space-top-4">
-    <div class="c12 text-center"><h3 class="text-headline text-uppercase"> Developer Community</h3>
-    </div>
-    <div class="clear"></div>
-  </div>
-  <div class="grid-fluid">
-    <div class="c6">
-      <div class="article-card">
-        <div class="date">Oct 30, 2016</div>
-        <div class="title"><a target="_blank"
-                              href="https://www.thepolyglotdeveloper.com/2016/10/use-pre-populated-sqlite-database-nativescript-angular-2/">Use
-          A Pre-Populated SQLite Database With NativeScript And Angular 2</a></div>
-        <p>I figured it would be a good idea to demonstrate how to ship a NativeScript Angular 2
-          application with a pre-filled SQLite database rather than populating it on-the-fly....</p>
-        <div class="author"><img src="assets/images/bios/shield-bio-placeholder.png">
-          <div class="posted">Posted by <b>Nic Raboy</b></div>
-        </div>
-      </div>
-    </div>
-    <div class="c6">
-      <div class="article-card">
-        <div class="date">Oct 13, 2016</div>
-        <div class="title"><a target="_blank"
-                              href="http://blog.thoughtram.io/angular/2016/10/13/two-way-data-binding-in-angular-2.html">Two-way
-          Data Binding in Angular 2</a></div>
-        <p>If there was one feature in Angular that made us go “Wow”, then it was probably its
-          two-way data binding system. Changes in the application state have been automagically
-          reflected into the view...</p>
-        <div class="author"><img src="assets/images/bios/angular-gde-bio-placeholder.png">
-          <div class="posted">Posted by <b>Pascal Precht</b></div>
-        </div>
-      </div>
-    </div>
-  </div>
-  <div class="grid-fluid">
-    <div class="c6">
-      <div class="article-card">
-        <div class="date">Oct 10, 2016</div>
-        <div class="title"><a target="_blank"
-                              href="http://www.creativebloq.com/how-to/build-a-material-design-app-with-angular-2">Build
-          a Material Design app with Angular 2</a></div>
-        <p>This walkthrough reveals how to create a DialogComponent and to-do app with Angular
-          Material and the Angular CLI...</p>
-        <div class="author"><img src="assets/images/bios/shield-bio-placeholder.png">
-          <div class="posted">Posted by <b>Daniel Zen</b></div>
-        </div>
-      </div>
-    </div>
-    <div class="c6">
-      <div class="article-card">
-        <div class="date">Sept 30, 2016</div>
-        <div class="title"><a target="_blank"
-                              href="http://www.simb.co/angular-cli-using-docker/?platform=hootsuite">Using
-          Angular CLI to create Angular 2 applications in Docker</a></div>
-        <p>Angular CLI is a great tool for developing Angular 2 applications. I thought it would be
-          fun to do a quick demo...</p>
-        <div class="author"><img src="assets/images/bios/shield-bio-placeholder.png">
-          <div class="posted">Posted by <b>Simeon Bateman</b></div>
-        </div>
-      </div>
-    </div>
-  </div>
-  <div class="grid-fluid l-space-bottom-2 l-space-top-4">
-    <div class="c12 text-center"><h3 class="text-headline text-uppercase">Twitter</h3></div>
-    <div class="clear"></div>
-    <div class="grid-fluid">
-      <div class="c3"><p></p></div>
-      <div class="c6">
-        <div class="article-card">
-          <div class="title"><a href="http://twitter.com/angularjs" data-show-count="false"
-                                class="twitter-follow-button">Follow @angularjs</a></div>
-          <p><a class="twitter-timeline" data-chrome="nofooter noborders noheader"
-                href="http://twitter.com/angularjs" data-widget-id="700150278465523713"></a></p>
-        </div>
-      </div>
-    </div>
-  </div>
-</article>