close
The Wayback Machine - https://web.archive.org/web/20200219073439/https://github.com/angular/components
Skip to content
Component infrastructure and Material Design components for Angular
TypeScript HTML CSS Starlark Other
Branch: master
Clone or download
devversion and jelbourn build: support for lazily loading examples in dev-app or docs
Adds support for lazily loading examples in the dev-app, e2e-app or
eventually in the docs. Since we already have modules per component
and use Ivy in the docs, we can lazily load the examples and also
get rid of the large bulk `ExampleModule`.
Latest commit a0aee92 Feb 17, 2020
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Image .circleci build: temporarily disable safari 10 browserstack tests (#18483) Feb 12, 2020
Image .github feat(cdk-experimental/table): experimental column resize (#16114) Feb 13, 2020
Image .vscode chore: disable vscode autoformat settings (#15406) Mar 7, 2019
Image guides refactor: rename `nav` schematic to `navigation` (#18364) Feb 4, 2020
Image scripts build: make built dev-app web package writable (#18481) Feb 12, 2020
Image src build: support for lazily loading examples in dev-app or docs Feb 18, 2020
Image test build: remove test blocklist (#18372) Feb 4, 2020
Image tools build: support for lazily loading examples in dev-app or docs Feb 18, 2020
Image .bazelignore build: update to Angular 7.0.1 http_archive & @angular/bazel package (#… Oct 29, 2018
Image .bazelrc build: update to bazel v2.1.0 (#18457) Feb 12, 2020
Image .bazelversion build: update to bazel v2.1.0 (#18457) Feb 12, 2020
Image .clang-format chore: add `yarn format` command and pre-commit hook to ensure code i… Feb 9, 2019
Image .editorconfig chore: remove `indent_size = 2` from editorconfig as it messes up the ( Jun 10, 2019
Image .firebaserc feat(table): support sticky headers, footers, and columns (#11483) Jun 7, 2018
Image .gitignore build: use genrule to generate example module (#17615) Nov 6, 2019
Image .stylelintrc.json refactor: enable Ivy and fix template type checking issues (#17392) Oct 22, 2019
Image BUILD.bazel build: enforce golden files and lint entry-point configuration (#18092) Jan 6, 2020
Image CHANGELOG.md chore: copy v9 changelog and version bump to master (#18418) Feb 6, 2020
Image CODE_REVIEWS.md build: restructure demo-app in favor of bazel (#13965) Nov 15, 2018
Image CODING_STANDARDS.md chore: remove noRxjsPatchImportsRule (#10765) Apr 10, 2018
Image CONTRIBUTING.md build: changelog should collect deprecations (#17740) Nov 18, 2019
Image DEV_ENVIRONMENT.md docs: update dev environment instructions (#18359) Feb 4, 2020
Image FAQ.md docs: fixed minor typos and table formatting (#18042) Dec 29, 2019
Image LICENSE chore: bump year (#18078) Jan 6, 2020
Image README.md docs: update readme for Q1 2020 (#18128) Jan 8, 2020
Image WORKSPACE build: update to bazel v2.1.0 (#18457) Feb 12, 2020
Image angular-tsconfig.json build: remove unused dependencies (#17988) Dec 17, 2019
Image build-config.js prototype(checkbox): create prototype checkbox based on MDC Web (#15782) Apr 16, 2019
Image firebase.json build: add script to deploy dev-app web package to firebase (#17989) Dec 17, 2019
Image gulpfile.js build: remove unused dependencies (#17988) Dec 17, 2019
Image package.json build: bump tslint and stylelint to latest major versions (#18527) Feb 18, 2020
Image packages.bzl build: remove hard-coded karma systemjs config (#18025) Jan 16, 2020
Image rollup-globals.bzl feat(material-experimental): initial prototype of mdc-form-fie… (#17903) Jan 7, 2020
Image scss-bundle.config.json build: update scss-bundle to avoid node-sass dependency (#17978) Dec 16, 2019
Image tsconfig.json build: support for lazily loading examples in dev-app or docs Feb 18, 2020
Image tslint.json build: disallow nested ternary expressions (#18243) Jan 22, 2020
Image yarn.lock build: bump tslint and stylelint to latest major versions (#18527) Feb 18, 2020

README.md

Official components for Angular

npm version Build status Gitter

The Angular team builds and maintains both common UI components and tools to help you build your own custom components. The team maintains several npm packages.

Package Description Docs
@angular/cdk Library that helps you author custom UI components with common interaction patterns Docs
@angular/material Material Design UI components for Angular applications Docs
@angular/google-maps Angular components built on top of the Google Maps JavaScript API Docs
@angular/youtube-player Angular component built on top of the YouTube Player API Docs

Quick links

Documentation, demos, and guides | Frequently Asked Questions | Community Google group | Contributing | StackBlitz Template

Getting started

See our Getting Started Guide if you're building your first project with Angular Material.

Contributing

If you'd like to contribute, please follow our contributing guidelines. Please see our help wanted label for a list of issues with good opportunities for contribution.

High level work planned for Q1 2020 (Jan - Mar):

  • Date-range picker
  • Finish remaining test harnesses for Angular Material components (four remaining as of January)
  • Continuing to create new, API-compatible versions of the Angular Material components backed by MDC Web (see @jelbourn's ng-conf talk). There are five remaining components to complete here as of January.
  • Add support for density configuration for the new components based on MDC Web.
  • Authoring benchmarks to collect performance metrics for Angular Material components. These benchmarks will live inside Google's internal code repository for the time being, but we should be able to publish the results.

About the team

The Angular Components team is part of the Angular team at Google. The team includes both Google employees and community contributors from around the globe.

Our team has two primary goals:

  • Build high-quality UI components that developers can drop into existing applications
  • Provide tools that help developers build their own custom components with common interaction patterns

What do we mean by "high-quality" components?

  • Internationalized and accessible so that all users can use them.
  • Straightforward APIs that don't confuse developers.
  • Behave as expected across a wide variety of use-cases without bugs.
  • Behavior is well-tested with both unit and integration tests.
  • Customizable within the bounds of the Material Design specification.
  • Performance cost is minimized.
  • Code is clean and well-documented to serve as an example for Angular developers.

Browser and screen reader support

The Angular Components team supports the most recent two versions of all major browsers: Chrome (including Android), Firefox, Safari (including iOS), and IE11 / Edge.

We aim for great user experience with the following screen readers:

  • Windows: NVDA and JAWS with IE11 / FF / Chrome.
  • macOS: VoiceOver with Safari / Chrome.
  • iOS: VoiceOver with Safari
  • Android: Android Accessibility Suite (formerly TalkBack) with Chrome.
  • Chrome OS: ChromeVox with Chrome.
You can’t perform that action at this time.