Go to file
Paul Gschwendtner 391767fb8f build: fix size artifacts not measured by github robot (#27042)
Currently the Github robot is not able to measure the artifacts of the `hello_world` and `todo` bundling tests because those will be only built with the `ivy-only` rule tag. This means that the current CircleCI job that is supposed to upload the size artifacts, does not even build those bundles.

PR Close #27042
2018-11-20 10:44:12 -08:00
.circleci build: fix size artifacts not measured by github robot (#27042) 2018-11-20 10:44:12 -08:00
.github build: fix size artifacts not measured by github robot (#27042) 2018-11-20 10:44:12 -08:00
aio docs: The note had an indentation and was missing line breaks (#27183) 2018-11-20 10:43:31 -08:00
docs build: use bazel version from node modules (#26691) 2018-10-30 16:19:13 -04:00
integration build: update to latest Bazel rules_typescript (#27138) 2018-11-17 12:19:32 -08:00
modules build(bazel): upgrade benchmarks to protractor_web_test_suite for CI without local chrome (#26908) 2018-11-07 16:47:39 -08:00
packages fix(ivy): set `ng-version` attribute on root component (#27175) 2018-11-20 10:43:51 -08:00
scripts fix: missing semi-colon and empty line (#26945) 2018-11-05 11:37:55 -08:00
tools build: update to latest Bazel rules_typescript (#27138) 2018-11-17 12:19:32 -08:00
.bazelignore build: add aio/node_modules to the .bazelignore file (#26471) 2018-10-23 08:57:42 -07:00
.bazelrc build(bazel): turn on --nolegacy-external-runfiles (#26770) 2018-11-14 12:23:38 -08:00
.bowerrc
.clang-format
.editorconfig
.gitattributes
.gitignore feat(bazel): Bazel workspace schematics (#26971) 2018-11-16 12:18:06 -08:00
.mailmap
.nvmrc build: update .nvmrc file to correct node version (#25992) 2018-09-18 13:11:58 -07:00
.pullapprove.yml ci: exclude symbol golden files from build-and-ci pullapprove group (#27004) 2018-11-08 13:10:53 -08:00
.travis.yml ci(docs-infra): remove jobs from Travis config (#26377) 2018-10-23 14:35:38 -07:00
BUILD.bazel build: use bazel version from node modules (#26691) 2018-10-30 16:19:13 -04:00
CHANGELOG.md release: cut the v7.1.0-rc.0 release 2018-11-14 14:27:00 -08:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md docs: Indicate that PRs should have an associated issue (#25436) 2018-10-15 16:51:46 -07:00
LICENSE
README.md build: run CI (#26488) 2018-10-19 20:59:29 -07:00
WORKSPACE build: Move non-bazel deps to devDependencies (#26691) 2018-10-30 16:19:13 -04:00
bower.json
browser-providers.conf.js feat(elements): enable Shadow DOM v1 and slots (#24861) 2018-08-30 21:33:14 -07:00
build.sh feat(ivy): implement TestBed (#25369) 2018-08-14 11:58:47 -07:00
gulpfile.js style: update gulp task to format untracked and diff files separately (#24969) 2018-09-27 12:09:08 -07:00
index.bzl style: format .bzl files with buildifier (#23544) 2018-08-08 13:12:07 -07:00
karma-js.conf.js build(bazel): use fine-grained npm deps (#26111) (#26488) 2018-10-19 20:59:29 -07:00
package.json build: update to latest Bazel rules_typescript (#27138) 2018-11-17 12:19:32 -08:00
protractor-e2e.conf.js
protractor-examples-e2e.conf.js
protractor-perf.conf.js ci: configure chrome options for protractor (#26735) 2018-10-26 14:48:05 -04:00
shims_for_IE.js
test-events.js
test-main.js refactor(core): remove withBody from public testing API (#25171) 2018-07-31 15:09:32 -07:00
test.sh feat: typescript 2.9 support (#24652) 2018-07-03 13:32:06 -07:00
tslint.json style: tslint enforces no debugger statements left behind (#25532) 2018-08-16 16:00:22 -07:00
yarn.lock build: update to latest Bazel rules_typescript (#27138) 2018-11-17 12:19:32 -08:00
yarn.lock.readme.md docs: replace npm with yarn in lockfile readme (#25309) 2018-08-06 13:38:13 -07:00

README.md

Build Status CircleCI BrowserStack Status Join the chat at https://gitter.im/angular/angular npm version

Angular

Angular is a development platform for building mobile and desktop web applications using Typescript/JavaScript and other languages.

Quickstart

Get started in 5 minutes.

Changelog

Learn about the latest improvements.

Want to help?

Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues in the hotlist: community-help.