* Fixes the stylelint deprecation warning
* Fixes that stylelint lints the compiled bundles from `dist/` folders of the `dashboard` or `screenshot` app
* Updates the package-lock with NPM@5.1
* At some point the `@types/rx` package has been added as a dependency on the project. The `@types/rx` are not for the RxJS implementation that Angular uses. Also RxJS provides typings on it's own since it's build using TypeScript.
Apparently developers that clone the Material repository to get their own version of Material are running the `npm run build` command and are expecting the CDK and Material release output to be inside of the `dist/` folder.
Currently only the Material package will be built and the CDK isn't built at all. This commit changes the npm build task so that it builds every release package of the publish task.
Closes#5372
* No longer includes the license comments from every source file in the different FESM and UMD bundles.
* Build packages are now emitted with explicit `LF` line endings instead of platform dependent line endings.
The dependency on `tsc-wrapped` should be added explicitly. Our tooling uses the `@angular/tsc-wrapped` package directly and it currently only works because the `@angular/compiler-cli` has a dependency on it.
If not specified explicitly, the `@angular/tsc-wrapped` dependency might be a local dependency of the compiler-cli and our tooling won't be able to access it anymore.
Recently Dgeni switch to a more recent version of TypeScript and now getters and setters are counting as individual members. This causes different properties to show up twice in the API docs.
Fixes this temporary by filtering duplicate member docs. Also removes the inhertied docs processor since it doesn't work and needs some more work in the `dgeni-packages` repository.
Fixes#4923
Fixes the Universal Prerendering task by using the same workaround as for the AOT job (building sources in the output directory already)
Building the sources in the output directory (similar as for the AOT task) is theonly known workaround for https://github.com/angular/angular/issues/12249
* In components inline styles there shouldn't be any Sourcemap reference. This adds bloat and also doesn't do anything right now.
* No longer builds sourcemaps for all compiled SCSS. The sourcemaps don't work for development either (styles are inlined too)
* Prebuilt themes no longer contain source-maps.
* build: upgrade dev dependencies
* Upgrades outdated development dependencies to the latest versions.
* Skipped upgrading Autoprefixer due to a breaking change with the Browserlist.
* Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3
* Skipped upgrading google-closure-compiler due to https://github.com/alexeagle/closure-compiler-angular-bundling/issues/30
* Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See https://github.com/angular/protractor/issues/4176)
* Lock jasmine types
* build: use shared logic to build packages
* No longer creates the whole set of gulp tasks just to build a single package.
* Makes the package building & releasing more consistent. No extra `build:release` just for the `lib` package.
References #4108
* Address feedback
* Fixes the Google Cloud Storage upload for the goldens.
The issue seems to happen because the `@google-cloud/storage` package has been installed manually and the `google-cloud` now uses a different storage version than before. Noticed this while debugging the `google-cloud` package.
* At some point in tslint the `no-unused-variable` rule has been deprecated in favor of `noUnusedLocals` and `noUnusedParameters`. Since we don't want to have compilation errors for unused variables we re-implemented the `no-unused-variable` rule ourself and used it as a custom rule.
* Recently we switched to a newer version of TSLint and TypeScript and the custom tslint rule won't ever work again. (tslint now requires a type-checker to be enabled). The custom rule fails currently and causes TSLint to not work with some editors (e.g Webstorm).
* build: run closure-compiler
* Adds a script that runs the closure-compiler against the devapp / demo-app.
* The script will run on the CI as a new mode. Ensuring that all our components are closure-compatible.
Fixes#1206.
* Address feedback
Set up firebase functions to copy valid data to firebase storage/database
Use JasonWebToken to validate data written to firebase
Github Status change will be done in another PR
Result at: https://material2-screenshots.firebaseapp.com/3628
* Bumps the required Angular version to 4 and TypeScript to 2.1.6.
* Fixes deprecation warnings for `<template>` usages.
* Fixes any unit and e2e test failures.
* Includes the new animations module and switches any components that use animations to it.
* Fixes issues with the various test apps.
Fixes#3357.
Fixes#3336.
FIxes#3301.
* build: ship esm bundle
* Now ships a Flat / ESM bundle (similar as for Angular 4+ releases)
* In future PRs we will remove the single ES-files and can just link to the ES bundle (as in angular/angular).
* Use template strings for diagnostic
* Since we had a lot of TSLint issues on our tooling scripts & tasks, we should run TSLint on those as well.
* Also updates Dgeni to latest version, because it now supports TypeScript typings.
* Add google cloud storage
* Add screenshots to e2e test
* Renamed functions. Add types. Remove firebase, use firebase-admin
* dependencies
* Save pull request sha to firebase db
* Save travis job id
* Add function to update github commit status
* remove update status code
* Add update status
* Address comments
* Add fs-extra
* try using ES6 Promise
* .
* Fix cannot find name promise
* Add back function to save filenames to firebase
* Update comments
* release: generated changes
* updating breaking changes
* minor changes
* add a fun inventive name that sets up apart from everyone else
* add note that forroot is deprecated
* add note about module
* fix select
* add new line for module example
* add ts styling
* add md input example
* indent input example
* Currently Angular Material supports Angular v2.2.0, but some components already use methods that are only available in `v2.3.0`.
This means that Material isn't really compatible with v2.2.0 anymore.
* Since Angular `v.2.3.0` includes a lot of good fixes (like proper metadata inheritance) we should upgrade to `v2.3.0`.
See https://github.com/angular/angular/commit/f5c8e0989d85bc064f689fc3595207dfb29413f4
Related to #2394
Jeremy Elbourn