@angular-devkit/build-angular (12.2.0-next.2) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ silence Sass compiler warnings from 3rd party stylesheets | + +
+
+ [Closes #21235] + + + |
+
+
+
+ |
+
+ force linker `sourceMapping` option to false. | + +
+
+ [Closes #21271] + + + |
+
+
+
+ |
+
+ ensure `NG_PERSISTENT_BUILD_CACHE` always creates a cache in the specified cache directory | + ++ | +
+
+
+ |
+
+ fail browser build when index generation fails | + ++ | +
+
+
+ |
+
+ fix issue were `@media all` causing critical CSS inling to fail | + +
+
+ [Closes #20804] + + + |
+
+
+
+ |
+
+ `extractLicenses` didn't have an effect when using server builder | + ++ | +
+
+
+ |
+
+ display incompatibility errors | + +
+
+ [Closes #21322] + + + |
+
+
+
+ |
+
+ limit advanced terser passes to two | + ++ | +
+
+
+ |
+
+ exclude `outputPath` from persistent build cache key | + +
+
+ [Closes #21275] + + + |
+
+
+
+ |
+
+ use `esbuild` as a CSS optimizer for component styles | + ++ | +
@ngtools/webpack (12.2.0-next.2) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ only track file dependencies | + +
+
+ [Closes #21228] + + + |
+
+
+
+ |
+
+ allow generated assets of Angular component resources | + ++ | +
+
+
+ |
+
+ avoid non-actionable template type-checker syntax diagnostics | + ++ | +
@schematics/angular (12.2.0-next.2) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ destroy test module after every test | + +
+
+ [Closes #21280] + + + |
+
+
+
+ |
+
+ remove unsafe any usage in application spec file | + ++ | +
+
+
+ |
+
+ replace interactive `div` with `button` in application component template | + ++ | +
+
+
+ |
+
+ use stricter semver for `karma-jasmine-html-reporter` | + ++ | +
@angular-devkit/build-angular (12.1.2) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ silence Sass compiler warnings from 3rd party stylesheets | + +
+
+ [Closes #21235] + + + |
+
+
+
+ |
+
+ ensure `NG_PERSISTENT_BUILD_CACHE` always creates a cache in the specified cache directory | + ++ | +
+
+
+ |
+
+ force linker `sourceMapping` option to false. | + +
+
+ [Closes #21271] + + + |
+
+
+
+ |
+
+ fail browser build when index generation fails | + ++ | +
+
+
+ |
+
+ `extractLicenses` didn't have an effect when using server builder | + ++ | +
+
+
+ |
+
+ fix issue were `@media all` causing critical CSS inling to fail | + +
+
+ [Closes #20804] + + + |
+
+
+
+ |
+
+ display incompatibility errors | + +
+
+ [Closes #21322] + + + |
+
+
+
+ |
+
+ exclude `outputPath` from persistent build cache key | + +
+
+ [Closes #21275] + + + |
+
@ngtools/webpack (12.1.2) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ only track file dependencies | + +
+
+ [Closes #21228] + + + |
+
+
+
+ |
+
+ allow generated assets of Angular component resources | + ++ | +
+
+
+ |
+
+ avoid non-actionable template type-checker syntax diagnostics | + ++ | +
@schematics/angular (12.1.2) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ remove unsafe any usage in application spec file | + ++ | +
+
+
+ |
+
+ replace interactive `div` with `button` in application component template | + ++ | +
+
+
+ |
+
+ use stricter semver for `karma-jasmine-html-reporter` | + ++ | +
@angular-devkit/build-angular (12.1.1) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ handle `ENOENT` and `ENOTDIR` errors when deleting outputs | + +
+
+ [Closes #21202] + + + |
+
+
+
+ |
+
+ downlevel `for await...of` when targeting ES2018+ | + +
+
+ [Closes #21196] + + + |
+
+
+
+ |
+
+ configure webpack target in common configuration | + +
+
+ [Closes #21239] + + + |
+
+
+
+ |
+
+ update `mini-css-extract-plugin` to `1.6.2` | + ++ | +
+
+
+ |
+
+ update `webpack` to `5.41.1` | + ++ | +
@angular/cli (12.1.1) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ disable update notifier when retrieving package manager version during `ng version` | + +
+
+ [Closes #21172] + + + |
+
@ngtools/webpack (12.1.1) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ encode component style data | + +
+
+ [Closes #21236] + + + |
+
@angular-devkit/build-angular (12.2.0-next.1) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ add support to inline Adobe Fonts | + +
+
+ [Closes #21186] + + + |
+
+
+
+ |
+
+ handle `ENOENT` and `ENOTDIR` errors when deleting outputs | + +
+
+ [Closes #21202] + + + |
+
+
+
+ |
+
+ downlevel `for await...of` when targeting ES2018+ | + +
+
+ [Closes #21196] + + + |
+
+
+
+ |
+
+ configure webpack target in common configuration | + +
+
+ [Closes #21239] + + + |
+
+
+
+ |
+
+ use combination of `esbuild` and `terser` as a JavaScript optimizer | + ++ | +
+
+
+ |
+
+ cache JavaScriptOptimizerPlugin results | + ++ | +
@angular/cli (12.2.0-next.1) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ disable update notifier when retrieving package manager version during `ng version` | + +
+
+ [Closes #21172] + + + |
+
@ngtools/webpack (12.2.0-next.1) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ encode component style data | + +
+
+ [Closes #21236] + + + |
+
@angular-devkit/build-angular (12.1.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ handle ng-packagr errors more gracefully. | + ++ | +
+
+
+ |
+
+ control linker template sourcemapping via builder sourcemap options | + ++ | +
+
+
+ |
+
+ parse web-workers in tests when webWorkerTsConfig is defined | + ++ | +
@ngtools/webpack (12.1.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ remove no longer needed component styles workaround | + ++ | +
@schematics/angular (12.1.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ add 'none' value for the 'style' option of the component schematic | + ++ | +
+
+
+ |
+
+ display warning during migrations when using third-party builders | + ++ | +
+
+
+ |
+
+ add devtools to ng new | + ++ | +
@angular-devkit/build-angular (12.1.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ enable webpack Trusted Types support | + ++ | +
+
+
+ |
+
+ deprecate protractor builder | + ++ | +
+
+
+ |
+
+ support using TypeScript 4.3 | + ++ | +
+
+
+ |
+
+ revert open to 8.0.2 | + +
+
+ [Closes #20807] + + + |
+
+
+
+ |
+
+ correctly ignore inline styles during i18n extraction | + ++ | +
+
+
+ |
+
+ use the name as chunk filename instead of id | + ++ | +
|
+
+
+ |
+
+ handle ng-packagr errors more gracefully. | + ++ | +
|
+
+
+ |
+
+ control linker template sourcemapping via builder sourcemap options | + ++ | +
|
+
+
+ |
+
+ parse web-workers in tests when webWorkerTsConfig is defined | + ++ | +
+
+
+ |
+
+ use CSS optimization plugin that leverages workers | + ++ | +
+
+
+ |
+
+ enable opt-in usage of file system cache | + ++ | +
@angular/cli (12.1.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ show Node.js version support status in version command | + +
+
+ [Closes #20879] + + + |
+
+
+
+ |
+
+ handle unscoped authentication details in `.npmrc` files | + ++ | +
+
+
+ |
+
+ don't resolve `.npmrc` from parent directories | + ++ | +
@ngtools/webpack (12.1.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ support using TypeScript 4.3 | + ++ | +
+
+
+ |
+
+ remove redundant inline style cache | + ++ | +
+
+
+ |
+
+ ensure plugin provided Webpack instance is used | + ++ | +
+
+
+ |
+
+ disable caching for ngcc synchronous Webpack resolver | + ++ | +
|
+
+
+ |
+
+ remove no longer needed component styles workaround | + ++ | +
@schematics/angular (12.1.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ create new projects with TypeScript 4.3 | + ++ | +
+
+
+ |
+
+ add migration to replace deprecated `--prod` | + +
+
+ [Closes #21036] + + + |
+
|
+
+
+ |
+
+ add 'none' value for the 'style' option of the component schematic | + ++ | +
|
+
+
+ |
+
+ display warning during migrations when using third-party builders | + ++ | +
|
+
+
+ |
+
+ add devtools to ng new | + ++ | +
@angular-devkit/build-angular (12.1.0-next.6) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ don't parse `new Worker` syntax when `webWorkerTsConfig` is not defined in karma builder | + +
+
+ [Closes #21108] + + + |
+
+
+
+ |
+
+ explicitly set compilation target in test configuration | + +
+
+ [Closes #21111] + + + |
+
|
+
+
+ |
+
+ use the name as chunk filename instead of id | + ++ | +
|
+
+
+ |
+
+ enable opt-in usage of file system cache | + ++ | +
@angular/cli (12.1.0-next.6) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ handle unscoped authentication details in `.npmrc` files | + ++ | +
|
+
+
+ |
+
+ don't resolve `.npmrc` from parent directories | + ++ | +
@schematics/angular (12.1.0-next.6) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ add migration to replace deprecated `--prod` | + +
+
+ [Closes #21036] + + + |
+
@angular-devkit/build-angular (12.0.5) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ don't parse `new Worker` syntax when `webWorkerTsConfig` is not defined in karma builder | + +
+
+ [Closes #21108] + + + |
+
+
+
+ |
+
+ explicitly set compilation target in test configuration | + +
+
+ [Closes #21111] + + + |
+
@angular/cli (12.0.5) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ handle unscoped authentication details in .npmrc files | + ++ | +
@angular-devkit/build-angular (12.1.0-next.5) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ support using TypeScript 4.3 | + ++ | +
+
+
+ |
+
+ ensure all Webpack Stats assets are present on rebuilds | + +
+
+ [Closes #21038] + + + |
+
+
+
+ |
+
+ dispose Sass worker resources on Webpack shutdown | + +
+
+ [Closes #20985] + + + |
+
+
+
+ |
+
+ show progress during re-builds | + ++ | +
+
+
+ |
+
+ correctly mark async chunks as non initial in dev-server | + ++ | +
+
+
+ |
+
+ add web-workers in lazy chunks in stats output | + +
+
+ [Closes #21059] + + + |
+
+
+
+ |
+
+ styles CSS files not available in unit tests | + +
+
+ [Closes #21054] + + + |
+
+
+
+ |
+
+ reduce memory usage by cleaning output directory before emitting | + ++ | +
@angular-devkit/schematics (12.1.0-next.5) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ handle updating renamed files | + +
+
+ [Closes #14255] + + + + [Closes #21083] + + + |
+
@angular/cli (12.1.0-next.5) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ avoid shell exec when bootstrapping update command | + ++ | +
+
+
+ |
+
+ correctly redirect nested Angular schematic dependency requests | + +
+
+ [Closes #21075] + + + |
+
@ngtools/webpack (12.1.0-next.5) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ support using TypeScript 4.3 | + ++ | +
|
+
+
+ |
+
+ ensure plugin provided Webpack instance is used | + ++ | +
|
+
+
+ |
+
+ disable caching for ngcc synchronous Webpack resolver | + ++ | +
@schematics/angular (12.1.0-next.5) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ create new projects with TypeScript 4.3 | + ++ | +
+
+
+ |
+
+ added webWorkerTsConfig into test option | + ++ | +
+
+
+ |
+
+ working with formatting | + ++ | +
@angular-devkit/build-angular (12.0.4) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ ensure all Webpack Stats assets are present on rebuilds | + +
+
+ [Closes #21038] + + + |
+
+
+
+ |
+
+ dispose Sass worker resources on Webpack shutdown | + +
+
+ [Closes #20985] + + + |
+
+
+
+ |
+
+ show progress during re-builds | + ++ | +
+
+
+ |
+
+ correctly mark async chunks as non initial in dev-server | + ++ | +
+
+
+ |
+
+ add web-workers in lazy chunks in stats output | + +
+
+ [Closes #21059] + + + |
+
+
+
+ |
+
+ styles CSS files not available in unit tests | + +
+
+ [Closes #21054] + + + |
+
+
+
+ |
+
+ reduce memory usage by cleaning output directory before emitting | + ++ | +
@angular-devkit/schematics (12.0.4) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ handle updating renamed files | + +
+
+ [Closes #14255] + + + + [Closes #21083] + + + |
+
@angular/cli (12.0.4) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ avoid shell exec when bootstrapping update command | + ++ | +
+
+
+ |
+
+ correctly redirect nested Angular schematic dependency requests | + +
+
+ [Closes #21075] + + + |
+
@ngtools/webpack (12.0.4) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ ensure plugin provided Webpack instance is used | + ++ | +
@schematics/angular (12.0.4) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ added webWorkerTsConfig into test option | + ++ | +
+
+
+ |
+
+ working with formatting | + ++ | +
@angular-devkit/build-angular (12.0.3) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ do not resolve web-workers in server builds | + +
+
+ [Closes #20877] + + + |
+
+
+
+ |
+
+ provided earlier build feedback in console | + +
+
+ [Closes #20957] + + + |
+
+
+
+ |
+
+ correctly ignore inline styles during i18n extraction | + +
+
+ [Closes #20968] + + + |
+
+
+
+ |
+
+ update `license-webpack-plugin` to `2.3.19` | + ++ | +
@angular-devkit/build-webpack (0.1200.3) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ include only required stats in webpackStats | + ++ | +
@angular-devkit/core (12.0.3) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ show allowed enum values when validation on enum fails | + ++ | +
+
+
+ |
+
+ handle complex smart defaults in schemas | + ++ | +
+
+
+ |
+
+ handle async schema validations | + ++ | +
+
+
+ |
+
+ transform path using getSystemPath for NodeJsAsyncHost's `exists` method | + ++ | +
@angular/cli (12.0.3) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ update supported range of node versions to be less restrictive | + +
+
+ [Closes #20796] + + + |
+
@ngtools/webpack (12.0.3) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ normalize paths when adding file dependencies | + +
+
+ [Closes #20891] + + + |
+
+
+
+ |
+
+ remove redundant inline style cache | + ++ | +
@schematics/angular (12.0.3) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ make version 12 workspace config migration idempotent | + +
+
+ [Closes #20979] + + + |
+
+
+
+ |
+
+ show better error when non existing project is passed to the component schematic | + ++ | +
@angular-devkit/build-angular (12.1.0-next.4) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ do not resolve web-workers in server builds | + +
+
+ [Closes #20877] + + + |
+
+
+
+ |
+
+ provided earlier build feedback in console | + +
+
+ [Closes #20957] + + + |
+
|
+
+
+ |
+
+ correctly ignore inline styles during i18n extraction | + ++ | +
@angular-devkit/build-webpack (0.1201.0-next.4) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ include only required stats in webpackStats | + ++ | +
@angular-devkit/core (12.1.0-next.4) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ show allowed enum values when validation on enum fails | + ++ | +
+
+
+ |
+
+ handle complex smart defaults in schemas | + ++ | +
+
+
+ |
+
+ handle async schema validations | + ++ | +
+
+
+ |
+
+ transform path using getSystemPath for NodeJsAsyncHost's `exists` method | + ++ | +
@angular/cli (12.1.0-next.4) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ update supported range of node versions to be less restrictive | + +
+
+ [Closes #20796] + + + |
+
@ngtools/webpack (12.1.0-next.4) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ normalize paths when adding file dependencies | + +
+
+ [Closes #20891] + + + |
+
|
+
+
+ |
+
+ remove redundant inline style cache | + ++ | +
@schematics/angular (12.1.0-next.4) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ make version 12 workspace config migration idempotent | + +
+
+ [Closes #20979] + + + |
+
+
+
+ |
+
+ show better error when non existing project is passed to the component schematic | + ++ | +
@angular-devkit/build-angular (12.1.0-next.3) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ enable webpack Trusted Types support | + ++ | +
|
+
+
+ |
+
+ deprecate protractor builder | + ++ | +
+
+
+ |
+
+ ensure Sass worker implementation supports Node.js 12.14 | + ++ | +
+
+
+ |
+
+ don't add `.hot-update.js` script tags | + +
+
+ [Closes #20855] + + + |
+
+
+
+ |
+
+ correctly generate ServiceWorker config on Windows | + +
+
+ [Closes #20894] + + + |
+
+
+
+ |
+
+ ensure latest inline stylesheet data is used during rebuilds | + ++ | +
+
+
+ |
+
+ allow i18n extraction on application that uses web-workers | + +
+
+ [Closes #20930] + + + |
+
+
+
+ |
+
+ hide stacktraces from dart-sass errors | + ++ | +
+
+
+ |
+
+ resolve absolute outputPath properly | + +
+
+ [Closes #20935] + + + |
+
+
+
+ |
+
+ show `--disable-host-check` warning only when not using `disableHostCheck` | + +
+
+ [Closes #20951] + + + |
+
+
+
+ |
+
+ disable CSS optimization parallelism for components styles | + +
+
+ [Closes #20883] + + + |
+
+
+
+ |
+
+ load postcss-preset-env configuration once | + ++ | +
@angular/cli (12.1.0-next.3) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ show Node.js version support status in version command | + +
+
+ [Closes #20879] + + + |
+
+
+
+ |
+
+ ng update on windows to allow path | + ++ | +
@ngtools/webpack (12.1.0-next.3) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ re-emit component stylesheet assets | + +
+
+ [Closes #20882] + + + |
+
@angular-devkit/build-angular (12.0.2) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ ensure Sass worker implementation supports Node.js 12.14 | + ++ | +
+
+
+ |
+
+ don't add `.hot-update.js` script tags | + +
+
+ [Closes #20855] + + + |
+
+
+
+ |
+
+ correctly generate ServiceWorker config on Windows | + +
+
+ [Closes #20894] + + + |
+
+
+
+ |
+
+ ensure latest inline stylesheet data is used during rebuilds | + ++ | +
+
+
+ |
+
+ allow i18n extraction on application that uses web-workers | + +
+
+ [Closes #20930] + + + |
+
+
+
+ |
+
+ hide stacktraces from dart-sass errors | + ++ | +
+
+
+ |
+
+ resolve absolute outputPath properly | + +
+
+ [Closes #20935] + + + |
+
+
+
+ |
+
+ show `--disable-host-check` warning only when not using `disableHostCheck` | + +
+
+ [Closes #20951] + + + |
+
+
+
+ |
+
+ update PostCSS to 8.3 | + ++ | +
+
+
+ |
+
+ disable CSS optimization parallelism for components styles | + +
+
+ [Closes #20883] + + + |
+
+
+
+ |
+
+ load postcss-preset-env configuration once | + ++ | +
@angular/cli (12.0.2) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ ng update on windows to allow path | + ++ | +
@ngtools/webpack (12.0.2) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ re-emit component stylesheet assets | + +
+
+ [Closes #20882] + + + |
+
@angular-devkit/build-angular (12.0.1) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ add experimental web-assembly | + +
+
+ [Closes #20762] + + + |
+
+
+
+ |
+
+ fix error with inline styles when running extract-i18n | + ++ | +
+
+
+ |
+
+ add `NG_BUILD_MAX_WORKERS` settimgs to control maximum number of workers | + ++ | +
+
+
+ |
+
+ non injected styles should not count as initial | + +
+
+ [Closes #20781] + + + |
+
+
+
+ |
+
+ revert open to 8.0.2 | + +
+
+ [Closes #20807] + + + |
+
+
+
+ |
+
+ correctly resolve babel runtime helpers | + +
+
+ [Closes #20800] + + + |
+
+
+
+ |
+
+ compile schema in synchronously | + +
+
+ [Closes #20847] + + + |
+
+
+
+ |
+
+ execute dart-sass in a worker | + ++ | +
+
+
+ |
+
+ reduce JSON stats | + ++ | +
+
+
+ |
+
+ use CSS optimization plugin that leverages workers | + ++ | +
+
+
+ |
+
+ render Sass using a pool of workers | + ++ | +
+
+
+ |
+
+ clean no-longer used assets during builds | + ++ | +
@angular/cli (12.0.1) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ cannot locate bin for temporary package | + ++ | +
+
+
+ |
+
+ clean node modules directory prior to updating | + ++ | +
+
+
+ |
+
+ improve `--prod` deprecation warning | + +
+
+ [Closes #20806] + + + |
+
@ngtools/webpack (12.0.1) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ reduce non-watch mode TypeScript diagnostic analysis overhead | + ++ | +
@schematics/angular (12.0.1) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ remove --prod option from README template | + ++ | +
+
+
+ |
+
+ don't add `skipTest` option to module schematic options | + +
+
+ [Closes #20811] + + + |
+
+
+
+ |
+
+ add migration to remove `skipTests` from `@schematics/angular:module` | + +
+
+ [Closes #20848] + + + |
+
@angular-devkit/build-angular (12.1.0-next.2) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ add experimental web-assembly | + +
+
+ [Closes #20762] + + + |
+
+
+
+ |
+
+ add `NG_BUILD_MAX_WORKERS` settimgs to control maximum number of workers | + ++ | +
+
+
+ |
+
+ non injected styles should not count as initial | + +
+
+ [Closes #20781] + + + |
+
|
+
+
+ |
+
+ revert open to 8.0.2 | + +
+
+ [Closes #20807] + + + |
+
+
+
+ |
+
+ correctly resolve babel runtime helpers | + +
+
+ [Closes #20800] + + + |
+
+
+
+ |
+
+ compile schema in synchronously | + +
+
+ [Closes #20847] + + + |
+
+
+
+ |
+
+ execute dart-sass in a worker | + ++ | +
+
+
+ |
+
+ reduce JSON stats | + ++ | +
|
+
+
+ |
+
+ use CSS optimization plugin that leverages workers | + ++ | +
+
+
+ |
+
+ render Sass using a pool of workers | + ++ | +
+
+
+ |
+
+ clean no-longer used assets during builds | + ++ | +
@angular/cli (12.1.0-next.2) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ cannot locate bin for temporary package | + ++ | +
+
+
+ |
+
+ clean node modules directory prior to updating | + ++ | +
+
+
+ |
+
+ improve `--prod` deprecation warning | + +
+
+ [Closes #20806] + + + |
+
@ngtools/webpack (12.1.0-next.2) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ reduce non-watch mode TypeScript diagnostic analysis overhead | + ++ | +
@schematics/angular (12.1.0-next.2) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ remove --prod option from README template | + ++ | +
+
+
+ |
+
+ don't add `skipTest` option to module schematic options | + +
+
+ [Closes #20811] + + + |
+
+
+
+ |
+
+ add migration to remove `skipTests` from `@schematics/angular:module` | + +
+
+ [Closes #20848] + + + |
+
@angular-devkit/architect (0.1200.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ add implementation for defaultConfiguration | + ++ | +
@angular-devkit/build-angular (12.0.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ add `postcss-preset-env` with stage 3 features | + ++ | +
+
+
+ |
+
+ drop support for karma version 5.2 | + ++ | +
+
+
+ |
+
+ drop support for ng-packagr version 11 | + ++ | +
+
+
+ |
+
+ enable inlineCritical by default | + ++ | +
+
+
+ |
+
+ show warning during build when project requires IE 11 support | + ++ | +
+
+
+ |
+
+ expose legacy-migrate message format | + ++ | +
+
+
+ |
+
+ integrate JIT mode linker | + +
+
+ [Closes #20281] + + + |
+
+
+
+ |
+
+ upgrade to Webpack 5 throughout the build system | + ++ | +
+
+
+ |
+
+ support processing component inline CSS styles | + ++ | +
+
+
+ |
+
+ support specifying stylesheet language for inline component styles | + ++ | +
+
+
+ |
+
+ remove left-over `experimentalRollupPass` option | + ++ | +
+
+
+ |
+
+ support writing large Webpack stat outputs | + ++ | +
+
+
+ |
+
+ ensure output directory is present before writing stats JSON | + ++ | +
+
+
+ |
+
+ remove deprecated View Engine support for i18n extraction | + ++ | +
+
+
+ |
+
+ remove usage of deprecated View Engine compiler | + ++ | +
+
+
+ |
+
+ remove deprecated i18nLocale and i18nFormat options from i18n-extract | + ++ | +
+
+
+ |
+
+ update karma builder to use non-deprecated API | + ++ | +
+
+
+ |
+
+ disable webpack cache when using `NG_BUILD_CACHE` | + ++ | +
+
+
+ |
+
+ remove duplicate application bundle generation complete message | + ++ | +
+
+
+ |
+
+ mark programmatic builder execution functions as experimental | + ++ | +
+
+
+ |
+
+ avoid double build optimizer processing | + ++ | +
+
+
+ |
+
+ replace Webpack 4 `hashForChunk` hook usage | + ++ | +
+
+
+ |
+
+ use new Webpack watch API in karma webpack plugin | + ++ | +
+
+
+ |
+
+ recover from CSS optimization errors | + ++ | +
+
+
+ |
+
+ disable Webpack 5 automatic public path support | + ++ | +
+
+
+ |
+
+ always inject live reload client when using live reload | + ++ | +
+
+
+ |
+
+ change several builder options defaults | + ++ | +
+
+
+ |
+
+ show warning when using stylus | + ++ | +
+
+
+ |
+
+ avoid triggering file change after file build | + ++ | +
+
+
+ |
+
+ remove left-over `forkTypeChecker` option | + ++ | +
+
+
+ |
+
+ disable CSS declaration sorting optimizations | + +
+
+ [Closes #20693] + + + |
+
+
+
+ |
+
+ disable `showCircularDependencies` by default | + ++ | +
+
+
+ |
+
+ use Webpack's GC memory caching in watch mode | + ++ | +
+
+
+ |
+
+ improve incremental time during Karma tests | + ++ | +
+
+
+ |
+
+ avoid async downlevel for known ES2015 code | + ++ | +
@angular-devkit/build-optimizer (0.1200.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ support Webpack 5 | + ++ | +
@angular-devkit/build-webpack (0.1200.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ provide output path in builder results | + ++ | +
+
+
+ |
+
+ support Webpack 5 | + ++ | +
@angular-devkit/core (12.0.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ add handling for `defaultConfiguration` target definition property | + ++ | +
+
+
+ |
+
+ update schema validator | + ++ | +
+
+
+ |
+
+ ensure job input values are processed in order | + ++ | +
+
+
+ |
+
+ improve handling of set schema values | + +
+
+ [Closes #20594] + + + |
+
@angular/cli (12.0.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ add `defaultConfiguration` property to architect schema | + ++ | +
+
+
+ |
+
+ deprecate `--prod` command line argument | + ++ | +
+
+
+ |
+
+ confirm ng add action before installation | + ++ | +
+
+
+ |
+
+ support TypeScript 4.2 | + ++ | +
+
+
+ |
+
+ ensure odd number Node.js version message is a warning | + ++ | +
+
+
+ |
+
+ remove npm 7 incompatibility notification | + ++ | +
+
+
+ |
+
+ avoid exceptions for expected errors in architect commands | + ++ | +
+
+
+ |
+
+ ensure update migrations are fully executed | + ++ | +
+
+
+ |
+
+ exclude deprecated packages with removal migrations from update | + ++ | +
+
+
+ |
+
+ add message update updating from non LTS versions of the CLI | + ++ | +
+
+
+ |
+
+ ignore `tsickle` during updates | + ++ | +
+
+
+ |
+
+ run all migrations when updating from or between prereleases | + ++ | +
+
+
+ |
+
+ add package manager name and version in `ng version` output | + ++ | +
+
+
+ |
+
+ Support XDG Base Directory Specification | + ++ | +
+
+
+ |
+
+ don't display options multiple times in schematics help output | + ++ | +
+
+
+ |
+
+ change package installation to async | + ++ | +
+
+
+ |
+
+ infer schematic defaults correctly when using `--project` | + +
+
+ [Closes #20666] + + + |
+
+
+
+ |
+
+ propagate update's force option to package managers | + ++ | +
+
+
+ |
+
+ allow unsetting config when value is `undefined` | + ++ | +
+
+
+ |
+
+ allow config object to be of JSON. | + ++ | +
+
+
+ |
+
+ disallow additional properties in builders sections | + ++ | +
@ngtools/webpack (12.0.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ support Webpack 5 | + ++ | +
+
+
+ |
+
+ drop support for string based lazy loading | + ++ | +
+
+
+ |
+
+ support multiple plugin instances per compilation | + ++ | +
+
+
+ |
+
+ support generating data URIs for inline component styles in JIT | + ++ | +
+
+
+ |
+
+ support processing inline component styles in AOT | + ++ | +
+
+
+ |
+
+ remove Webpack 5 deprecation warning in resource loader | + ++ | +
+
+
+ |
+
+ use correct Webpack asset stage in resource loader | + ++ | +
+
+
+ |
+
+ remove Webpack plugin for deprecated ViewEngine compiler | + ++ | +
+
+
+ |
+
+ only track actual resource file dependencies | + ++ | +
+
+
+ |
+
+ avoid adding transitive dependencies to Webpack's dependency graph | + ++ | +
+
+
+ |
+
+ use precalculated dependencies in unused file check | + ++ | +
+
+
+ |
+
+ only check affected files for Angular semantic diagnostics | + ++ | +
+
+
+ |
+
+ cache results of processed inline resources | + ++ | +
+
+
+ |
+
+ rebuild Angular required files asynchronously | + ++ | +
+
+
+ |
+
+ reduce source file and Webpack module iteration | + ++ | +
@schematics/angular (12.0.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ add migration to remove deprecated options from 'angular.json' | + ++ | +
+
+
+ |
+
+ strict mode by default | + ++ | +
+
+
+ |
+
+ use new zone.js entry-points | + ++ | +
+
+
+ |
+
+ add migration to use new zone.js entry-points | + ++ | +
+
+
+ |
+
+ add migration to remove emitDecoratorMetadata | + ++ | +
+
+
+ |
+
+ augment `universal` schematics to import `platform-server` shims | + +
+
+ [Closes #40559] + + + |
+
+
+
+ |
+
+ update new project dependencies version | + +
+
+ [Closes #20106] + + + |
+
+
+
+ |
+
+ production builds by default | + ++ | +
+
+
+ |
+
+ deprecate `legacyBrowsers` application and ng-new option | + ++ | +
+
+
+ |
+
+ add migration to remove `lazyModules` configuration option | + ++ | +
+
+
+ |
+
+ add migration to update lazy loading string syntax to use dynamic imports | + ++ | +
+
+
+ |
+
+ update several TypeScript compilation target (Syntax) | + ++ | +
+
+
+ |
+
+ remove tslint and codelyzer from new projects | + +
+
+ [Closes #20105] + + + + [Closes #18465] + + + |
+
+
+
+ |
+
+ add production by default optional migration | + ++ | +
+
+
+ |
+
+ update new workspaces to use Karma 6.3 | + ++ | +
+
+
+ |
+
+ remove `entryComponent` from `component` schematic | + ++ | +
+
+
+ |
+
+ configure new libraries to be published in Ivy partial mode | + ++ | +
+
+
+ |
+
+ update `jasmine-spec-reporter` to version 7 | + ++ | +
+
+
+ |
+
+ migrate web workers to support Webpack 5 | + ++ | +
+
+
+ |
+
+ only update removed v12 options in migration | + ++ | +
+
+
+ |
+
+ add `additionalProperties` to all schemas | + ++ | +
+
+
+ |
+
+ remove references to the prod flag | + ++ | +
+
+
+ |
+
+ only show legacy browsers deprecation warning when option is used | + ++ | +
+
+
+ |
+
+ remove leftover workspace tslint config | + ++ | +
+
+
+ |
+
+ correctly handle adding multi-line strings to `@NgModule` metadata | + ++ | +
+
+
+ |
+
+ run update-i18n migration for server builder | + ++ | +
+
+
+ |
+
+ update web-worker to support Webpack 5 | + ++ | +
+
+
+ |
+
+ set `inlineStyleLanguage` when application `style` option is used | + ++ | +
+
+
+ |
+
+ set `inlineStyleLanguage` for universal if present in build options | + ++ | +
+
+
+ |
+
+ remove jasmine-spec-reporter and ts-node from default workspace | + ++ | +
+
+
+ |
+
+ remove Protractor from home page | + ++ | +
+
+
+ |
+
+ remove lint command from package.json | + +
+
+ [Closes #20618] + + + |
+
+
+
+ |
+
+ fix migration for namedChunks and option | + ++ | +
+
+
+ |
+
+ add "type" option in enum schematic | + ++ | +
+
+
+ |
+
+ only run `emitDecoratorMetadata` removal migration in safe workspaces | + ++ | +
+
+
+ |
+
+ replace `clientProject` with `project` | + ++ | +
+ @schematics/angular: remove `stylus` from `style` options (fd729ac) +
+`styl` (Stylus) is no longer a supported value as `style` in `application`, `component`, `ng-new` schematics. Stylus is not actively maintained and only 0.3% of the Angular CLI users use it. + +(cherry picked from commit 0272fc55b67d1a3f986b996c8eb21aea31eedf51) + ++ @angular-devkit/build-angular: change several builder options defaults (656f8d7) +
+A number of browser and server builder options have had their default values changed. The aim of these changes is to reduce the configuration complexity and support the new "production builds by default" initiative. + +**Browser builder** +| Option | Previous default value | New default value | +|----------------------------------------|---------------------------|-------------------| +| optimization | false | true | +| aot | false | true | +| buildOptimizer | false | true | +| sourceMap | true | false | +| extractLicenses | false | true | +| namedChunks | true | false | +| vendorChunk | true | false | + +**Server builder** +| Option | Previous default value | New default value | +|---------------|------------------------|-------------------| +| optimization | false | true | +| sourceMap | true | false | + +(cherry picked from commit 0a74d0d28daf68510459ed73ef048c91bfcabbbc) + ++ @angular-devkit/core: update schema validator (0875313) +
+support for JSON Schema draft-04 and draft-06 is removed. If you have schemas using the `id` keyword replace them with `$id`. For an interim period we will auto rename any top level `id` keyword to `$id`. + +**NB**: This change only effects schematics and builders authors. + ++ @angular-devkit/build-angular: upgrade to Webpack 5 throughout the build system (d883ce5) +
+Webpack 5 lazy loaded file name changes +Webpack 5 generates similar but differently named files for lazy loaded JavaScript files in development configurations (when the `namedChunks` option is enabled). +For the majority of users this change should have no effect on the application and/or build process. Production builds should also not be affected as the `namedChunks` option is disabled by default in production configurations. +However, if a project's post-build process makes assumptions as to the file names then adjustments may need to be made to account for the new naming paradigm. +Such post-build processes could include custom file transformations after the build, integration into service-side frameworks, or deployment procedures. +Example development file name change: `lazy-lazy-module.js` --> `src_app_lazy_lazy_module_ts.js` + +Webpack 5 now includes web worker support. However, the structure of the URL within the `Worker` constructor must be in a specific format that differs from the current requirement. +Web worker usage should be updated as shown below (where `./app.worker` should be replaced with the actual worker name): +Before: `new Worker('./app.worker', ...)` +After: `new Worker(new URL('./app.worker', import.meta.url), ...)` + ++ @ngtools/webpack: remove Webpack plugin for deprecated ViewEngine compiler (160102a) +
+Removal of View Engine support from application builds +With the removal of the deprecated View Engine compiler in Angular version 12 for applications, the View Engine Webpack plugin has been removed. +The Ivy-based Webpack plugin is the default used within the Angular CLI. +If using a custom standalone Webpack configuration, the removed `AngularCompilerPlugin` should be replaced with the Ivy-based `AngularWebpackPlugin`. + ++ @angular-devkit/build-angular: remove deprecated i18n options from server and browser builder (5cf9a08) +
+Removal of deprecated browser and server command options. +- `i18nFile`, use `locales` object in the project metadata instead. +- `i18nFormat`, No longer needed as the format will be determined automatically. +- `i18nLocale`, use `localize` option instead. + ++ @angular-devkit/build-angular: remove deprecated i18nLocale and i18nFormat options from i18n-extract (eca5a01) +
+Removal of deprecated `extract-i18n` command options +The deprecated `i18nLocale` option has been removed and the `i18n.sourceLocale` within a project's configuration should be used instead. +The deprecated `i18nFormat` option has been removed and the `format` option should be used instead. + ++ @angular-devkit/build-angular: remove usage of deprecated View Engine compiler (677913f) +
+Removal of View Engine support from application builds +With the removal of the deprecated View Engine compiler in Angular version 12 for applications, Ivy-based compilation will always be used when building an application. +The default behavior for applications is to use the Ivy compiler when building and no changes are required for these applications. +For applications that have opted-out of Ivy, a warning will be shown and an Ivy-based build will be attempted. If the build fails, +the application may need to be updated to become Ivy compatible. + ++ @schematics/angular: remove `entryComponent` from `component` schematic (8582ddc) +
+`entryComponent` option has been removed from the `component` schematic as this was intended to be used with the now no longer supported ViewEngine rendering engine. + ++ @angular-devkit/build-angular: remove view engine app-shell generation (1c2aeeb) +
+App-shell builder now only supports generation using Ivy + ++ @angular-devkit/build-angular: remove deprecated View Engine support for i18n extraction (012700a) +
+Removal of View Engine support from i18n extraction +With the removal of the deprecated View Engine compiler in Angular version 12 for applications, the `ng extract-i18n` command will now always use the Ivy compiler. +The `--ivy` option has also been removed as Ivy-based extraction is always enabled. +The default behavior for applications is to use the Ivy compiler for building/extraction and no changes are required for these applications. +For applications that have opted-out of Ivy, a warning will be shown and Ivy-based extraction will be attempted. If the extraction fails, +the application may need to be updated to become Ivy compatible. + ++ @angular/cli: confirm ng add action before installation (985dc1a) +
+The `ng add` command will now ask the user to confirm the package and version prior to installing and executing an uninstalled package. +This new behavior allows a user to abort the action if the version selected is not appropriate or if a typo occurred on the command line and an incorrect package would be installed. +A `--skip-confirmation` option has been added to skip the prompt and directly install and execute the package. This option is useful in CI and non-TTY scenarios such as automated scripts. + ++ @angular-devkit/build-angular: remove deprecated `lazyModules` option (8d66912) +
+Server and Browser builder `lazyModules` option has been removed without replacement. + ++ @ngtools/webpack: drop support for string based lazy loading (0dc7327) +
+With this change we drop support for string based lazy loading `./lazy.module#LazyModule` use dynamic imports instead. + +The following options which were used to support the above syntax were removed without replacement. + +- discoverLazyRoutes +- additionalLazyModules +- additionalLazyModuleResources +- contextElementDependencyConstructor + ++ @angular-devkit/build-angular: enable inlineCritical by default (aa3ea88) +
+Critical CSS inlining is now enabled by default. If you wish to turn this off set `inlineCritical` to `false`. + +See: https://angular.dev/reference/configs/workspace-config#optimization-configuration + ++ @angular-devkit/build-angular: drop support for zone.js 0.10 (f309516) +
+Minimum supported `zone.js` version is `0.11.4` + ++ @angular-devkit/build-angular: drop support for ng-packagr version 11 (44e75be) +
+Minimum supported `ng-packagr` version is `12.0.0-next` + ++ @angular-devkit/build-angular: drop support for karma version 5.2 (fa5cf53) +
+Minimum supported `karma` version is `6.0.0` + ++ set minimum Node.js version to 12.13 (d1f6169) +
+Node.js version 10 will become EOL on 2021-04-30. +Angular CLI 12 will require Node.js 12.13+ or 14.15+. Node.js 12.13 and 14.15 are the first LTS releases for their respective majors. + ++ @angular-devkit/build-angular: remove file-loader dependency (6732294) +
+The unsupported/undocumented, Webpack specific functionality to `import`/`require()` a non-module file has been removed. + +Before + +```js +import img from './images/asset.png'; +``` + +After + +```html +
+```
+
+---
+
+# Special Thanks
+
+Alan Agius, Charles Lyding, Keen Yee Liau, Joey Perrott, Doug Parker, Cédric Exbrayat, Douglas Parker, George Kalpakas, Sam Bulatov, Joshua Chapman, Santosh Yadav, David Shevitz, Kristiyan Kostadinov
+
+
+
+
+
+# v12.0.0-rc.3 (2021-05-10)
+
+# Commits
+
+@angular/cli (12.0.0-rc.3) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ propagate update's force option to package managers | + ++ | +
|
+
+
+ |
+
+ allow unsetting config when value is `undefined` | + ++ | +
|
+
+
+ |
+
+ allow config object to be of JSON. | + ++ | +
|
+
+
+ |
+
+ disallow additional properties in builders sections | + ++ | +
@angular-devkit/build-angular (12.0.0-rc.2) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ disable CSS declaration sorting optimizations | + +
+
+ [Closes #20693] + + + |
+
@angular/cli (12.0.0-rc.2) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ don't display options multiple times in schematics help output | + ++ | +
|
+
+
+ |
+
+ change package installation to async | + ++ | +
|
+
+
+ |
+
+ infer schematic defaults correctly when using `--project` | + +
+
+ [Closes #20666] + + + |
+
@ngtools/webpack (12.0.0-rc.2) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ rebuild Angular required files asynchronously | + ++ | +
|
+
+
+ |
+
+ reduce source file and Webpack module iteration | + ++ | +
@schematics/angular (12.0.0-rc.2) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ add "type" option in enum schematic | + ++ | +
|
+
+
+ |
+
+ only run `emitDecoratorMetadata` removal migration in safe workspaces | + ++ | +
|
+
+
+ |
+
+ replace `clientProject` with `project` | + ++ | +
@angular-devkit/build-angular (12.0.0-rc.1) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ remove left-over `forkTypeChecker` option | + ++ | +
+
+
+ |
+
+ output webpack-dev-server and webpack-dev-middleware errors | + ++ | +
|
+
+
+ |
+
+ improve incremental time during Karma tests | + ++ | +
|
+
+
+ |
+
+ avoid async downlevel for known ES2015 code | + ++ | +
@angular-devkit/core (12.0.0-rc.1) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ improve handling of set schema values | + +
+
+ [Closes #20594] + + + |
+
@angular/cli (12.0.0-rc.1) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ add package manager name and version in `ng version` output | + ++ | +
|
+
+
+ |
+
+ Support XDG Base Directory Specification | + ++ | +
@schematics/angular (12.0.0-rc.1) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ remove jasmine-spec-reporter and ts-node from default workspace | + ++ | +
|
+
+
+ |
+
+ remove Protractor from home page | + ++ | +
|
+
+
+ |
+
+ remove lint command from package.json | + +
+
+ [Closes #20618] + + + |
+
+
+
+ |
+
+ avoid unuse imports for canLoad guard generation | + ++ | +
|
+
+
+ |
+
+ fix migration for namedChunks and option | + ++ | +
@angular-devkit/schematics-cli (12.0.0-rc.1) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ accept windows like paths for schematics | + ++ | +
@angular-devkit/build-angular (12.0.0-rc.0) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ avoid double build optimizer processing | + ++ | +
|
+
+
+ |
+
+ replace Webpack 4 `hashForChunk` hook usage | + ++ | +
|
+
+
+ |
+
+ use new Webpack watch API in karma webpack plugin | + ++ | +
|
+
+
+ |
+
+ recover from CSS optimization errors | + ++ | +
|
+
+
+ |
+
+ disable Webpack 5 automatic public path support | + ++ | +
|
+
+
+ |
+
+ always inject live reload client when using live reload | + ++ | +
|
+
+
+ |
+
+ change several builder options defaults | + ++ | +
|
+
+
+ |
+
+ show warning when using stylus | + ++ | +
+
+
+ |
+
+ set Tailwind CSS mode when using Tailwind | + ++ | +
|
+
+
+ |
+
+ avoid triggering file change after file build | + ++ | +
|
+
+
+ |
+
+ use Webpack's GC memory caching in watch mode | + ++ | +
@angular/cli (12.0.0-rc.0) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ ignore `tsickle` during updates | + ++ | +
|
+
+
+ |
+
+ run all migrations when updating from or between prereleases | + ++ | +
@ngtools/webpack (12.0.0-rc.0) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ only track actual resource file dependencies | + ++ | +
|
+
+
+ |
+
+ cache results of processed inline resources | + ++ | +
@schematics/angular (12.0.0-rc.0) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ set `inlineStyleLanguage` when application `style` option is used | + ++ | +
|
+
+
+ |
+
+ set `inlineStyleLanguage` for universal if present in build options | + ++ | +
+ @schematics/angular: remove `stylus` from `style` options (fd729ac) +
+`styl` (Stylus) is no longer a supported value as `style` in `application`, `component`, `ng-new` schematics. Stylus is not actively maintained and only 0.3% of the Angular CLI users use it. + +(cherry picked from commit 0272fc55b67d1a3f986b996c8eb21aea31eedf51) + ++ @angular-devkit/build-angular: change several builder options defaults (656f8d7) +
+A number of browser and server builder options have had their default values changed. The aim of these changes is to reduce the configuration complexity and support the new "production builds by default" initiative. + +**Browser builder** +| Option | Previous default value | New default value | +|----------------------------------------|---------------------------|-------------------| +| optimization | false | true | +| aot | false | true | +| buildOptimizer | false | true | +| sourceMap | true | false | +| extractLicenses | false | true | +| namedChunks | true | false | +| vendorChunk | true | false | + +**Server builder** +| Option | Previous default value | New default value | +|---------------|------------------------|-------------------| +| optimization | false | true | +| sourceMap | true | false | + +(cherry picked from commit 0a74d0d28daf68510459ed73ef048c91bfcabbbc) + +--- + +# Special Thanks + +Alan Agius, Charles Lyding, Keen Yee Liau, Joey Perrott, David Shevitz + + + + + +# v12.0.0-next.9 (2021-04-14) + +# Commits + +@angular-devkit/build-angular (12.0.0-next.9) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ upgrade to Webpack 5 throughout the build system | + ++ | +
|
+
+
+ |
+
+ support processing component inline CSS styles | + ++ | +
|
+
+
+ |
+
+ support specifying stylesheet language for inline component styles | + ++ | +
|
+
+
+ |
+
+ update karma builder to use non-deprecated API | + ++ | +
|
+
+
+ |
+
+ disable webpack cache when using `NG_BUILD_CACHE` | + ++ | +
|
+
+
+ |
+
+ remove duplicate application bundle generation complete message | + ++ | +
|
+
+
+ |
+
+ mark programmatic builder execution functions as experimental | + ++ | +
@angular-devkit/build-webpack (0.1200.0-next.9) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ support Webpack 5 | + ++ | +
@angular-devkit/core (12.0.0-next.9) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ update schema validator | + ++ | +
@angular/cli (12.0.0-next.9) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ add message update updating from non LTS versions of the CLI | + ++ | +
@ngtools/webpack (12.0.0-next.9) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ support multiple plugin instances per compilation | + ++ | +
|
+
+
+ |
+
+ support generating data URIs for inline component styles in JIT | + ++ | +
|
+
+
+ |
+
+ support processing inline component styles in AOT | + ++ | +
@schematics/angular (12.0.0-next.9) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ configure new libraries to be published in Ivy partial mode | + ++ | +
|
+
+
+ |
+
+ update `jasmine-spec-reporter` to version 7 | + ++ | +
|
+
+
+ |
+
+ migrate web workers to support Webpack 5 | + ++ | +
|
+
+
+ |
+
+ update web-worker to support Webpack 5 | + ++ | +
+ @angular-devkit/core: update schema validator (0875313) +
+support for JSON Schema draft-04 and draft-06 is removed. If you have schemas using the `id` keyword replace them with `$id`. For an interim period we will auto rename any top level `id` keyword to `$id`. + +**NB**: This change only effects schematics and builders authors. + ++ @angular-devkit/build-angular: upgrade to Webpack 5 throughout the build system (d883ce5) +
+Webpack 5 generates similar but differently named files for lazy loaded JavaScript files in development configurations (when the `namedChunks` option is enabled). +For the majority of users this change should have no effect on the application and/or build process. Production builds should also not be affected as the `namedChunks` option is disabled by default in production configurations. +However, if a project's post-build process makes assumptions as to the file names then adjustments may need to be made to account for the new naming paradigm. +Such post-build processes could include custom file transformations after the build, integration into service-side frameworks, or deployment procedures. +Example development file name change: `lazy-lazy-module.js` --> `src_app_lazy_lazy_module_ts.js` + ++ @angular-devkit/build-angular: upgrade to Webpack 5 throughout the build system (d883ce5) +
+Webpack 5 now includes web worker support. However, the structure of the URL within the `Worker` constructor must be in a specific format that differs from the current requirement. +Web worker usage should be updated as shown below (where `./app.worker` should be replaced with the actual worker name): + +Before: + +``` +new Worker('./app.worker', ...) +``` + +After: + +``` +new Worker(new URL('./app.worker', import.meta.url), ...) +``` + +--- + +# Special Thanks + +Alan Agius, Charles Lyding, Keen Yee Liau, Doug Parker, Douglas Parker + + + + + +# v12.0.0-next.8 (2021-04-07) + +# Commits + +@angular-devkit/build-angular (0.1200.0-next.8) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ remove deprecated i18nLocale and i18nFormat options from i18n-extract | + ++ | +
@ngtools/webpack (12.0.0-next.8) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ remove Webpack plugin for deprecated ViewEngine compiler | + ++ | +
@schematics/angular (12.0.0-next.8) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ run update-i18n migration for server builder | + ++ | +
+ @ngtools/webpack: remove Webpack plugin for deprecated ViewEngine compiler (160102a) +
+Removal of View Engine support from application builds +With the removal of the deprecated View Engine compiler in Angular version 12 for applications, the View Engine Webpack plugin has been removed. +The Ivy-based Webpack plugin is the default used within the Angular CLI. +If using a custom standalone Webpack configuration, the removed `AngularCompilerPlugin` should be replaced with the Ivy-based `AngularWebpackPlugin`. + ++ @angular-devkit/build-angular: remove deprecated i18n options from server and browser builder (5cf9a08) +
+Removal of deprecated browser and server command options. +- `i18nFile`, use `locales` object in the project metadata instead. +- `i18nFormat`, No longer needed as the format will be determined automatically. +- `i18nLocale`, use `localize` option instead. + ++ @angular-devkit/build-angular: remove deprecated i18nLocale and i18nFormat options from i18n-extract (eca5a01) +
+Removal of deprecated `extract-i18n` command options +The deprecated `i18nLocale` option has been removed and the `i18n.sourceLocale` within a project's configuration should be used instead. +The deprecated `i18nFormat` option has been removed and the `format` option should be used instead. + +--- + +# Special Thanks + +Charles Lyding, Renovate Bot, Alan Agius, Doug Parker, Joey Perrott + + + + + +# v12.0.0-next.7 (2021-04-02) + +# Commits + +@angular-devkit/build-angular (0.1200.0-next.7) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ validate scripts and styles bundleName | + +
+
+ [Closes #20360] + + + |
+
|
+
+
+ |
+
+ remove deprecated View Engine support for i18n extraction | + ++ | +
|
+
+
+ |
+
+ remove usage of deprecated View Engine compiler | + ++ | +
@angular/cli (12.0.0-next.7) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ ensure update migrations are fully executed | + ++ | +
|
+
+
+ |
+
+ exclude deprecated packages with removal migrations from update | + ++ | +
@ngtools/webpack (12.0.0-next.7) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ use correct Webpack asset stage in resource loader | + ++ | +
|
+
+
+ |
+
+ only check affected files for Angular semantic diagnostics | + ++ | +
@schematics/angular (12.0.0-next.7) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ remove `entryComponent` from `component` schematic | + ++ | +
|
+
+
+ |
+
+ correctly handle adding multi-line strings to `@NgModule` metadata | + ++ | +
+
+
+ |
+
+ explicitly specify ServiceWorker registration strategy | + ++ | +
+ @angular-devkit/build-angular: remove usage of deprecated View Engine compiler (677913f) +
+Removal of View Engine support from application builds +With the removal of the deprecated View Engine compiler in Angular version 12 for applications, Ivy-based compilation will always be used when building an application. +The default behavior for applications is to use the Ivy compiler when building and no changes are required for these applications. +For applications that have opted-out of Ivy, a warning will be shown and an Ivy-based build will be attempted. If the build fails, +the application may need to be updated to become Ivy compatible. + ++ @schematics/angular: remove `entryComponent` from `component` schematic (8582ddc) +
+`entryComponent` option has been removed from the `component` schematic as this was intended to be used with the now no longer supported ViewEngine rendering engine. + ++ @angular-devkit/build-angular: remove view engine app-shell generation (1c2aeeb) +
+App-shell builder now only supports generation using Ivy + ++ @angular-devkit/build-angular: remove deprecated View Engine support for i18n extraction (012700a) +
+Removal of View Engine support from i18n extraction +With the removal of the deprecated View Engine compiler in Angular version 12 for applications, the `ng extract-i18n` command will now always use the Ivy compiler. +The `--ivy` option has also been removed as Ivy-based extraction is always enabled. +The default behavior for applications is to use the Ivy compiler for building/extraction and no changes are required for these applications. +For applications that have opted-out of Ivy, a warning will be shown and Ivy-based extraction will be attempted. If the extraction fails, +the application may need to be updated to become Ivy compatible. + +--- + +# Special Thanks + +Charles Lyding, Alan Agius, Renovate Bot, George Kalpakas, Joey Perrott, Keen Yee Liau + + + + + +# v12.0.0-next.6 (2021-03-24) + +# Commits + +@angular-devkit/build-angular (0.1200.0-next.6) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ ensure output directory is present before writing stats JSON | + ++ | +
@schematics/angular (12.0.0-next.6) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ add production by default optional migration | + ++ | +
|
+
+
+ |
+
+ update new workspaces to use Karma 6.3 | + ++ | +
|
+
+
+ |
+
+ remove leftover workspace tslint config | + ++ | +
@angular-devkit/build-angular (0.1200.0-next.5) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ expose legacy-migrate message format | + ++ | +
|
+
+
+ |
+
+ integrate JIT mode linker | + +
+
+ [Closes #20281] + + + |
+
+
+
+ |
+
+ display correct filename for bundles that are ES2016+ | + ++ | +
+
+
+ |
+
+ don't load an input sourcemap from file when using Babel | + ++ | +
|
+
+
+ |
+
+ support writing large Webpack stat outputs | + ++ | +
+
+
+ |
+
+ skip FESM2015 from `async` transformation | + ++ | +
+
+
+ |
+
+ remove Webpack Stats.toJson usage in analytics plugin | + ++ | +
+
+
+ |
+
+ remove Webpack Stats.toJson usage in karma plugin | + ++ | +
+
+
+ |
+
+ enforce Babel not to load sourcemaps from file | + ++ | +
|
+
+
+ |
+
+ disable `showCircularDependencies` by default | + ++ | +
@angular-devkit/build-webpack (0.1200.0-next.5) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ provide output path in builder results | + ++ | +
@angular/cli (12.0.0-next.5) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ confirm ng add action before installation | + ++ | +
|
+
+
+ |
+
+ support TypeScript 4.2 | + ++ | +
+
+
+ |
+
+ remove `project` from required properties in ng-packagr schema | + ++ | +
@ngtools/webpack (12.0.0-next.5) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ remove Webpack 5 deprecation warning in resource loader | + ++ | +
|
+
+
+ |
+
+ avoid adding transitive dependencies to Webpack's dependency graph | + ++ | +
|
+
+
+ |
+
+ use precalculated dependencies in unused file check | + ++ | +
@schematics/angular (12.0.0-next.5) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ update several TypeScript compilation target (Syntax) | + ++ | +
|
+
+
+ |
+
+ remove tslint and codelyzer from new projects | + +
+
+ [Closes #20105] + + + + [Closes #18465] + + + |
+
|
+
+
+ |
+
+ remove references to the prod flag | + ++ | +
+
+
+ |
+
+ fix youtube icon margin | + ++ | +
|
+
+
+ |
+
+ only show legacy browsers deprecation warning when option is used | + ++ | +
+
+
+ |
+
+ remove Native value from viewEncapsulation option | + ++ | +
+
+
+ |
+
+ use title for svg on home page | + ++ | +
+ @angular/cli: confirm ng add action before installation (985dc1a) +
+The `ng add` command will now ask the user to confirm the package and version prior to installing and executing an uninstalled package. +This new behavior allows a user to abort the action if the version selected is not appropriate or if a typo occurred on the command line and an incorrect package would be installed. +A `--skip-confirmation` option has been added to skip the prompt and directly install and execute the package. This option is useful in CI and non-TTY scenarios such as automated scripts. + +--- + +# Special Thanks + +Alan Agius, Charles Lyding, Renovate Bot, Doug Parker, Cédric Exbrayat, Kristiyan Kostadinov, Mouad Ennaciri, Omar Hasan + + + + + +# v12.0.0-next.4 (2021-03-10) + +# Commits + +@angular-devkit/architect (0.1200.0-next.4) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ add implementation for defaultConfiguration | + ++ | +
@angular-devkit/build-angular (0.1200.0-next.4) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ show warning during build when project requires IE 11 support | + ++ | +
+
+
+ |
+
+ only remove nomodule and defer attributes empty values | + +
+
+
+ [Closes #20207] + + + |
+
@angular-devkit/core (12.0.0-next.4) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ add handling for `defaultConfiguration` target definition property | + ++ | +
@angular/cli (12.0.0-next.4) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ deprecate `--prod` command line argument | + ++ | +
|
+
+
+ |
+
+ add `defaultConfiguration` property to architect schema | + ++ | +
|
+
+
+ |
+
+ avoid exceptions for expected errors in architect commands | + ++ | +
+
+
+ |
+
+ add ng-packagr builder schema in IDE schema | + ++ | +
@ngtools/webpack (12.0.0-next.4) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ drop support for string based lazy loading | + ++ | +
@schematics/angular (12.0.0-next.4) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ add migration to update lazy loading string syntax to use dynamic imports | + ++ | +
|
+
+
+ |
+
+ add migration to remove `lazyModules` configuration option | + ++ | +
|
+
+
+ |
+
+ deprecate `legacyBrowsers` application and ng-new option | + ++ | +
|
+
+
+ |
+
+ production builds by default | + ++ | +
|
+
+
+ |
+
+ add `additionalProperties` to all schemas | + ++ | +
+ @angular-devkit/build-angular: remove deprecated `lazyModules` option (8d66912) +
+Server and Browser builder `lazyModules` option has been removed without replacement. + ++ @ngtools/webpack: drop support for string based lazy loading (0dc7327) +
+With this change we drop support for string based lazy loading `./lazy.module#LazyModule` use dynamic imports instead. + +The following options which were used to support the above syntax were removed without replacement. + +- discoverLazyRoutes +- additionalLazyModules +- additionalLazyModuleResources +- contextElementDependencyConstructor + +--- + +# Special Thanks + +Alan Agius, Charles Lyding, Renovate Bot, Joey Perrott + + + + + +# v12.0.0-next.3 (2021-03-03) + +# Commits + +@angular-devkit/build-angular (0.1200.0-next.3) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ enable inlineCritical by default | + ++ | +
|
+
+
+ |
+
+ remove left-over `experimentalRollupPass` option | + ++ | +
+
+
+ |
+
+ inline critical font-face rules when using crittical css inlining | + ++ | +
@schematics/angular (12.0.0-next.3) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ update ng new links | + ++ | +
+ @angular-devkit/build-angular: enable inlineCritical by default (aa3ea88) +
+Critical CSS inlining is now enabled by default. If you wish to turn this off set `inlineCritical` to `false`. + +See: https://angular.dev/reference/configs/workspace-config#optimization-configuration + +--- + +# Special Thanks + +Renovate Bot, Charles Lyding, Alan Agius, Keen Yee Liau, Douglas Parker, twerske + + + + + +# v12.0.0-next.2 (2021-02-24) + +# Commits + +@angular-devkit/build-angular (0.1200.0-next.2) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ only show index and service worker status once | + ++ | +
+
+
+ |
+
+ disable declaration and declarationMap | + +
+
+
+ [Closes #20103] + + + |
+
@angular/cli (12.0.0-next.2) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ remove npm 7 incompatibility notification | + ++ | +
@schematics/angular (12.0.0-next.2) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ update new project dependencies version | + +
+
+ [Closes #20106] + + + |
+
|
+
+
+ |
+
+ augment `universal` schematics to import `platform-server` shims | + +
+
+ [Closes #40559] + + + |
+
|
+
+
+ |
+
+ add migration to remove emitDecoratorMetadata | + ++ | +
@angular-devkit/build-angular (0.1200.0-next.1) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ drop support for ng-packagr version 11 | + ++ | +
|
+
+
+ |
+
+ drop support for karma version 5.2 | + ++ | +
@angular-devkit/build-optimizer (0.1200.0-next.1) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ support Webpack 5 | + ++ | +
@angular/cli (12.0.0-next.1) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ support update migration packages with no entry points | + +
+
+
+ [Closes #20032] + + + |
+
|
+
+
+ |
+
+ ensure odd number Node.js version message is a warning | + ++ | +
+
+
+ |
+
+ improve error logging when resolving update migrations | + ++ | +
@ngtools/webpack (12.0.0-next.1) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ support Webpack 5 | + ++ | +
+
+
+ |
+
+ normalize paths when pruning AOT rebuild requests | + ++ | +
@schematics/angular (12.0.0-next.1) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ add migration to use new zone.js entry-points | + ++ | +
|
+
+
+ |
+
+ use new zone.js entry-points | + ++ | +
+ @angular-devkit/build-angular: drop support for zone.js 0.10 (f309516) +
+Minimum supported `zone.js` version is `0.11.4` + ++ @angular-devkit/build-angular: drop support for ng-packagr version 11 (44e75be) +
+Minimum supported `ng-packagr` version is `12.0.0-next` + ++ @angular-devkit/build-angular: drop support for karma version 5.2 (fa5cf53) +
+Minimum supported `karma` version is `6.0.0` + +--- + +# Special Thanks + +Renovate Bot, Alan Agius, Charles Lyding, Keen Yee Liau, Aravind V Nair + + + + + +# v12.0.0-next.0 (2021-02-11) + +# Commits + +@angular-devkit/build-angular (0.1200.0-next.0) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ add `postcss-preset-env` with stage 3 features | + ++ | +
+
+
+ |
+
+ ensure i18n extraction sourcemaps are fully configured | + ++ | +
+
+
+ |
+
+ the root Tailwind configuration file is always picked | + ++ | +
+
+
+ |
+
+ fixed ignoring of karma plugins config | + +
+
+
+ [Closes #19993] + + + |
+
@angular-devkit/core (12.0.0-next.0) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ ensure job input values are processed in order | + ++ | +
@angular/cli (12.0.0-next.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ update NPM 7 guidance | + ++ | +
@ngtools/webpack (12.0.0-next.0) | ||
| Commit + | Description + | Notes + |
+
+
+ |
+
+ reduce overhead of Angular compiler rebuild requests | + ++ | +
@schematics/angular (12.0.0-next.0) | ||
| Commit + | Description + | Notes + |
|
+
+
+ |
+
+ strict mode by default | + ++ | +
|
+
+
+ |
+
+ add migration to remove deprecated options from 'angular.json' | + ++ | +
|
+
+
+ |
+
+ only update removed v12 options in migration | + ++ | +
+ set minimum Node.js version to 12.13 (d1f6169) +
+Node.js version 10 will become EOL on 2021-04-30. +Angular CLI 12 will require Node.js 12.13+ or 14.15+. Node.js 12.13 and 14.15 are the first LTS releases for their respective majors. + ++ @angular-devkit/build-angular: remove file-loader dependency (6732294) +
+The unsupported/undocumented, Webpack specific functionality to `import`/`require()` a non-module file has been removed. + +Before + +```js +import img from './images/asset.png'; +``` + +After + +```html +
+```
+
+---
+
+# Special Thanks
+
+Renovate Bot, Charles Lyding, Alan Agius, Doug Parker, Bruno Baia, Amadou Sall, S. Iftekhar Hossain
+
+---
+
+**Note: For release notes prior to this CHANGELOG see [release notes](https://github.com/angular/angular-cli/releases).**
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 000000000000..501598396449
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,79 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering a safe and welcoming environment, we as
+the Angular team pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity, gender expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Use welcoming and inclusive language
+* Respect each other
+* Provide and gracefully accept constructive criticism
+* Show empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* The use of sexualized language or imagery
+* Unwelcome sexual attention or advances
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Angular team are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Angular team have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, and to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies to all Angular communication channels - online or in person,
+and it also applies when an individual is representing the project or its community in
+public spaces. Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the Angular team at conduct@angular.io. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The Angular team
+will maintain confidentiality with regard to the reporter of an incident.
+Enforcement may result in an indefinite ban from all official Angular communication
+channels, or other actions as deemed appropriate by the Angular team.
+
+Angular maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+### Appeal
+
+If you are banned you may contest the decision. To do so email conduct@angular.io with the subject line "Repeal Ban for {{your name here}}" and body with the responses to the following:
+
+* Why do you believe you did not violate the Code of Conduct?
+* Were other factors involved in this situation the leadership team may have been unaware of?
+* Why do you wish to be a part of the Angular community?
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index eb9d2a2d7c66..06db9756c89d 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -26,8 +26,8 @@ should be tagged with tag `angular-cli` or `angular-devkit`.
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
+- 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
@@ -60,7 +60,7 @@ Before you submit an issue, please search the issue tracker, maybe an issue for
We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. Having a reproducible scenario gives us wealth of important information without going back & forth to you with additional questions like:
- version of Angular CLI used
-- `.angular-cli.json` or `angular.json` configuration
+- `angular.json` configuration
- version of Angular DevKit used
- 3rd-party libraries and their versions
- and most importantly - a use-case that fails
@@ -71,7 +71,7 @@ We will be insisting on a minimal reproduce scenario in order to save maintainer
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-cli/issues/new).
+You can file new issues by selecting from our [new issue templates](https://github.com/angular/angular-cli/issues/new/choose) and filling out the issue template.
### Submitting a Pull Request (PR)
@@ -84,7 +84,7 @@ Before you submit your Pull Request (PR) consider the following guidelines:
* Make your changes in a new git branch:
```shell
- git checkout -b my-fix-branch master
+ git checkout -b my-fix-branch main
```
* Create your patch, **including appropriate test cases**.
@@ -106,18 +106,25 @@ Before you submit your Pull Request (PR) consider the following guidelines:
git push origin my-fix-branch
```
-* In GitHub, send a pull request to `devkit:master`.
+* In GitHub, send a pull request to `angular/angular-cli:main`.
* If we suggest changes then:
* Make the required updates.
* Re-run the Angular DevKit test suites to ensure tests are still passing.
- * Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
+* Once your PR is approved and you are done with any follow up changes:
+ * Rebase to the current main to pre-emptively address any merge conflicts.
```shell
- git rebase master -i
+ git rebase upstream/main -i
git push -f
```
+ * Add the `action: merge` label and the correct
+[target label](https://github.com/angular/angular/blob/main/docs/TRIAGE_AND_LABELS.md#pr-target)
+ (if PR author has the project collaborator status, or else the last reviewer
+ should do this).
+ * The current caretaker will merge the PR to the target branch(es) within 1-2
+ business days.
-That's it! Thank you for your contribution!
+That's it! 🎉 Thank you for your contribution!
#### After your pull request is merged
@@ -130,10 +137,10 @@ from the main (upstream) repository:
git push origin --delete my-fix-branch
```
-* Check out the master branch:
+* Check out the main branch:
```shell
- git checkout master -f
+ git checkout main -f
```
* Delete the local branch:
@@ -142,10 +149,10 @@ from the main (upstream) repository:
git branch -D my-fix-branch
```
-* Update your master with the latest upstream version:
+* Update your local `main` with the latest upstream version:
```shell
- git pull --ff upstream master
+ git pull --ff upstream main
```
## Coding Rules
@@ -185,16 +192,15 @@ If the commit reverts a previous commit, it should begin with `revert: `, follow
### Type
Must be one of the following:
-* **build**: Changes that affect the build system or external dependencies. [2]
-* **ci**: Changes to our CI configuration files and scripts. [2]
-* **docs**: Documentation only changes.
-* **feat**: A new feature. [1]
-* **fix**: A bug fix. [1]
-* **refactor**: A code change that neither fixes a bug nor adds a feature
-* **release**: A release commit. Must only include version changes. [2]
-* **revert**: A git commit revert. The description must include the original commit message. [2]
-* **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.
+* **build**: Changes to local repository build system and tooling
+* **ci**: Changes to CI configuration and CI specific tooling [2]
+* **docs**: Changes which exclusively affects documentation.
+* **feat**: Creates a new feature [1]
+* **fix**: Fixes a previously discovered failure/bug [1]
+* **perf**: Improves performance without any change in functionality or API [1]
+* **refactor**: Refactor without any change in functionality or API (includes style changes)
+* **release**: A release point in the repository [2]
+* **test**: Improvements or corrections made to the project's test suite
[1] This type MUST have a scope. See the next section for more information.@@ -205,21 +211,20 @@ The scope should be the name of the npm package affected as perceived by the per The following is the list of supported scopes: +* **@angular/build** * **@angular/cli** +* **@angular/create** * **@angular/pwa** +* **@angular/ssr** * **@angular-devkit/architect** * **@angular-devkit/architect-cli** * **@angular-devkit/build-angular** -* **@angular-devkit/build-ng-packagr** -* **@angular-devkit/build-optimizer** * **@angular-devkit/build-webpack** * **@angular-devkit/core** * **@angular-devkit/schematics** * **@angular-devkit/schematics-cli** * **@ngtools/webpack** * **@schematics/angular** -* **@schematics/schematics** -* **@schematics/update** ### Subject @@ -249,12 +254,32 @@ Just as in the **subject**, use the imperative, present tense: "change" not "cha The body should include the motivation for the change and contrast this with previous behavior. ### Footer -The footer should contain any information about **Breaking Changes** and is also the place to -reference GitHub issues that this commit **Closes**. +The footer can contain information about breaking changes and deprecations. It is also the place to reference GitHub issues, Jira tickets, and other PRs that are related to this commit or that this commit will close. +For example: -**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. +``` +BREAKING CHANGE:
Angular CLI - The CLI tool for Angular.
-This is the home of the DevKit and the Angular CLI code. You can find the Angular CLI specific README -[here](/packages/angular/cli/README.md). +
+
+ 
+
+ The Angular CLI is a command-line interface tool that you use to initialize, develop, scaffold,
+
and maintain Angular applications directly from a command shell.
+
+
+ angular.dev/tools/cli
+
+
+ Contributing Guidelines
+ ·
+ Submit an Issue
+ ·
+ Blog
+
+
+
-[](https://github.com/angular/angular-cli/fork) [](https://github.com/angular/angular-cli) +## Documentation +Get started with Angular CLI, learn the fundamentals and explore advanced topics on our documentation website. +- [Getting started][quickstart] +- [CLI][cli] +- [Workspace and project file structure][filestructure] +- [Workspace configuration][workspaceconfig] +- [Schematics][schematics] -### Quick Links -[Gitter](https://gitter.im/angular/angular-cli) | [Contributing](/CONTRIBUTING.md) | [Angular CLI](http://github.com/angular/angular-cli) | -|---|---|---| +## Development Setup ----- -## The Goal of Angular CLI +### Prerequisites -The Angular CLI creates, manages, builds and test your Angular projects. It's built on top of the -Angular DevKit. +- Install [Node.js] which includes [Node Package Manager][npm] -## The Goal of DevKit +### Setting Up a Project -DevKit's goal is to provide a large set of libraries that can be used to manage, develop, deploy and -analyze your code. +Install the Angular CLI globally: -# Getting Started - Local Development +``` +npm install -g @angular/cli +``` -## Installation -To get started locally, follow these instructions: +Create workspace: -1. If you haven't done it already, [make a fork of this repo](https://github.com/angular/angular-cli/fork). -1. Clone to your local computer using `git`. -1. Make sure that you have Node 10.9 or later installed. See instructions [here](https://nodejs.org/en/download/). The Angular CLI requires Node 8, but development requires Node 10. -1. Make sure that you have `yarn` installed; see instructions [here](https://yarnpkg.com/lang/en/docs/install/). -1. Run `yarn` (no arguments) from the root of your clone of this project. -1. Run `yarn link` to add all custom scripts we use to your global install. +``` +ng new [PROJECT NAME] +``` -## Creating New Packages -Adding a package to this repository means running two separate commands: +Run the application: -1. `schematics devkit:package PACKAGE_NAME`. This will update the `.monorepo` file, and create the - base files for the new package (package.json, src/index, etc). -1. `devkit-admin templates`. This will update the README and all other template files that might - have changed when adding a new package. +``` +cd [PROJECT NAME] +ng serve +``` -For private packages, you will need to add a `"private": true` key to your package.json manually. -This will require re-running the template admin script. +Angular is cross-platform, fast, scalable, has incredible tooling, and is loved by millions. -# Packages +## Quickstart + +[Get started in 5 minutes][quickstart]. + +## Ecosystem + +
+ 
+
-
-
-aot
-
- --aot default value: false
-
- Build using Ahead of Time compilation. -
-
-
-
-app
-
- --app (aliases: -a)
-
- Specifies app name or index to use. -
-
-
-
-base-href
-
- --base-href (aliases: -bh)
-
- Base url for the application being built. -
-
-
-
-deploy-url
-
- --deploy-url (aliases: -d)
-
- URL where files will be deployed. -
-
-
-
-environment
-
- --environment (aliases: -e)
-
- Defines the build environment. -
-
-
-
-extract-css
-
- --extract-css (aliases: -ec)
-
- Extract css from global styles onto css files instead of js ones. -
-
-
-
-i18n-file
-
- --i18n-file
-
- Localization file to use for i18n. -
-
-
-
-i18n-format
-
- --i18n-format
-
- Format of the localization file specified with --i18n-file. -
-
-
-
-locale
-
- --locale
-
- Locale to use for i18n. -
-
-
-
-missing-translation
-
- --missing-translation
-
- How to handle missing translations for i18n. -
-
- Values: error, warning, ignore
-
-
-
-output-hashing
-
- --output-hashing (aliases: -oh)
-
- Define the output filename cache-busting hashing mode. -
-
- Values: none, all, media, bundles
-
-
-
-output-path
-
- --output-path (aliases: -op)
-
- Path where output will be placed. -
-
-
-
-delete-output-path
-
- --delete-output-path (aliases: -dop) default value: true
-
- Delete the output-path directory. -
-
-
-
-poll
-
- --poll
-
- Enable and define the file watching poll time period (milliseconds). -
-
-
-
-progress
-
- --progress (aliases: -pr) default value: true inside TTY, false otherwise
-
- Log progress to the console while building. -
-
-
-
-sourcemap
-
- --sourcemap (aliases: -sm, sourcemaps)
-
- Output sourcemaps. -
-
-
-
-stats-json
-
- --stats-json
-
- Generates a stats.json file which can be analyzed using tools such as: webpack-bundle-analyzer or https://webpack.github.io/analyse/.
-
-
-
-target
-
- --target (aliases: -t, -dev, -prod) default value: development
-
- Defines the build target. -
-
-
-
-vendor-chunk
-
- --vendor-chunk (aliases: -vc) default value: true
-
- Use a separate bundle containing only vendor libraries. -
-
-
-
-common-chunk
-
- --common-chunk (aliases: -cc) default value: true
-
- Use a separate bundle containing code used across multiple bundles. -
-
-
-
-verbose
-
- --verbose (aliases: -v) default value: false
-
- Adds more details to output logging. -
-
-
-
-watch
-
- --watch (aliases: -w)
-
- Run build when files change. -
-
-
-
-show-circular-dependencies
-
- --show-circular-dependencies (aliases: -scd)
-
- Show circular dependency warnings on builds. -
-
-
-
-build-optimizer
-
- --build-optimizer
-
- Enables @angular-devkit/build-optimizer optimizations when using `--aot`. -
-
-
-
-named-chunks
-
- --named-chunks (aliases: -nc)
-
- Use file name for lazy loaded chunks. -
-
-
-
-
-bundle-dependencies
-
- --bundle-dependencies
-
- In a server build, state whether `all` or `none` dependencies should be bundles in the output. -
-
-
diff --git a/docs/documentation/1-x/config.md b/docs/documentation/1-x/config.md
deleted file mode 100644
index b114b60c0d7d..000000000000
--- a/docs/documentation/1-x/config.md
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-# ng config
-
-## Overview
-`ng config [key] [value]` Get/set configuration values.
-`[key]` should be in JSON path format. Example: `a[3].foo.bar[2]`.
-If only the `[key]` is provided it will get the value.
-If both the `[key]` and `[value]` are provided it will set the value.
-
-## Options
-extract-licenses
-
- --extract-licenses default value: true
-
- Extract all licenses in a separate file, in the case of production builds only. -
-
-
diff --git a/docs/documentation/1-x/doc.md b/docs/documentation/1-x/doc.md
deleted file mode 100644
index f6ea8b2d8d33..000000000000
--- a/docs/documentation/1-x/doc.md
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-# ng doc
-
-## Overview
-`ng doc [search term]` Opens the official Angular API documentation for a given keyword on [angular.io](https://angular.io).
-
-## Options
-
-global
-
- --global default value: false
-
- Get/set the value in the global configuration (in your home directory). -
-
-
diff --git a/docs/documentation/1-x/e2e.md b/docs/documentation/1-x/e2e.md
deleted file mode 100644
index 6e638298b67d..000000000000
--- a/docs/documentation/1-x/e2e.md
+++ /dev/null
@@ -1,81 +0,0 @@
-
-
-# ng e2e
-
-## Overview
-`ng e2e` serves the application and runs end-to-end tests
-
-### Running end-to-end tests
-
-```bash
-ng e2e
-```
-
-End-to-end tests are run via [Protractor](http://www.protractortest.org/).
-
-## Options
-
-Please note that options that are supported by `ng serve` are also supported by `ng e2e`
-
-search
-
- --search (alias: -s) default value: false
-
- Search for the keyword in the whole [angular.io](https://angular.io) documentation instead of just the API. -
-
-
-
-config
-
- --config (aliases: -c)
-
- Use a specific config file. Defaults to the protractor config file in .angular-cli.json.
-
-
-
-element-explorer
-
- --element-explorer (aliases: -ee) default value: false
-
- Start Protractor's Element Explorer for debugging. -
-
-
-
-serve
-
- --serve (aliases: -s) default value: true
-
- Compile and Serve the app. All serve options are also available. The live-reload option defaults to false, and the default port will be random. -
-- NOTE: Build failure will not launch the e2e task. You must first fix error(s) and run e2e again. -
-
-
-
-specs
-
- --specs (aliases: -sp) default value: []
-
- Override specs in the protractor config. Can send in multiple specs by repeating flag (ng e2e --specs=spec1.ts --specs=spec2.ts).
-
-
-
-suite
-
- --suite (aliases: -su)
-
- Override suite in the protractor config. Can send in multiple suite by comma separated values (ng e2e --suite=suiteA,suiteB).
-
-
diff --git a/docs/documentation/1-x/eject.md b/docs/documentation/1-x/eject.md
deleted file mode 100644
index d1c55e34a6a0..000000000000
--- a/docs/documentation/1-x/eject.md
+++ /dev/null
@@ -1,233 +0,0 @@
-
-
-# ng eject
-
-## Overview
-`ng eject` ejects your app and output the proper webpack configuration and scripts.
-
-This command uses the same flags as `ng build`, generating webpack configuration to match those
-flags.
-
-You can use `--force` to overwrite existing configurations.
-You can eject multiple times, to have a dev and prod config for instance, by renaming the ejected
-configuration and using the `--force` flag.
-
-### Ejecting the CLI
-
-```bash
-ng eject
-```
-
-## Options
-webdriver-update
-
- --webdriver-update (aliases: -wu) default value: true
-
- Try to update webdriver. -
-
-
-
-aot
-
- --aot
-
- Build using Ahead of Time compilation. -
-
-
-
-app
-
- --app (aliases: -a) default value: 1st app
-
- Specifies app name to use. -
-
-
-
-base-href
-
- --base-href (aliases: -bh)
-
- Base url for the application being built. -
-
-
-
-deploy-url
-
- --deploy-url (aliases: -d)
-
- URL where files will be deployed. -
-
-
-
-environment
-
- --environment (aliases: -e)
-
- Defines the build environment. -
-
-
-
-extract-css
-
- --extract-css (aliases: -ec)
-
- Extract css from global styles onto css files instead of js ones. -
-
-
-
-force
-
- --force default value: false
-
- Overwrite any webpack.config.js and npm scripts already existing. -
-
-
-
-i18n-file
-
- --i18n-file
-
- Localization file to use for i18n. -
-
-
-
-i18n-format
-
- --i18n-format
-
- Format of the localization file specified with --i18n-file. -
-
-
-
-locale
-
- --locale
-
- Locale to use for i18n. -
-
-
-
-missing-translation
-
- --missing-translation
-
- How to handle missing translations for i18n. -
-
- Values: error, warning, ignore
-
-
-
-output-hashing
-
- --output-hashing (aliases: -oh) default value:
-
- Define the output filename cache-busting hashing mode. Possible values: none, all, media, bundles
-
-
-
-output-path
-
- --output-path (aliases: -op) default value:
-
- Path where output will be placed. -
-
-
-
-poll
-
- --poll
-
- Enable and define the file watching poll time period (milliseconds) . -
-
-
-
-progress
-
- --progress (aliases: -pr) default value: true inside TTY, false otherwise
-
- Log progress to the console while building. -
-
-
-
-sourcemap
-
- --sourcemap (aliases: -sm, sourcemaps)
-
- Output sourcemaps. -
-
-
-
-target
-
- --target (aliases: -t, -dev, -prod) default value: development
-
- Defines the build target. -
-
-
-
-vendor-chunk
-
- --vendor-chunk (aliases: -vc) default value: true
-
- Use a separate bundle containing only vendor libraries. -
-
-
-
-common-chunk
-
- --common-chunk (aliases: -cc) default value: true
-
- Use a separate bundle containing code used across multiple bundles. -
-
-
-
-verbose
-
- --verbose (aliases: -v) default value: false
-
- Adds more details to output logging. -
-
-
diff --git a/docs/documentation/1-x/generate.md b/docs/documentation/1-x/generate.md
deleted file mode 100644
index 74bae41b3a65..000000000000
--- a/docs/documentation/1-x/generate.md
+++ /dev/null
@@ -1,48 +0,0 @@
-
-
-# ng generate
-
-## Overview
-`ng generate [name]` generates the specified blueprint
-
-## Available blueprints:
- - [class](1-x/generate/class)
- - [component](1-x/generate/component)
- - [directive](1-x/generate/directive)
- - [enum](1-x/generate/enum)
- - [guard](1-x/generate/guard)
- - [interface](1-x/generate/interface)
- - [module](1-x/generate/module)
- - [pipe](1-x/generate/pipe)
- - [service](1-x/generate/service)
-
-## Options
-watch
-
- --watch (aliases: -w)
-
- Run build when files change. -
-
-
-
-dry-run
-
- --dry-run (aliases: -d) default value: false
-
- Run through without making any changes. -
-
-
-
-force
-
- --force (aliases: -f) default value: false
-
- Forces overwriting of files. -
-
-
diff --git a/docs/documentation/1-x/generate/class.md b/docs/documentation/1-x/generate/class.md
deleted file mode 100644
index e1ccd6f5c1b0..000000000000
--- a/docs/documentation/1-x/generate/class.md
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-# ng generate class
-
-## Overview
-`ng generate class [name]` generates a class
-
-## Options
-app
-
- --app
-
- Specifies app name to use. -
-
-
-
-app
-
- --app (aliases: -a) default value: 1st app
-
- Specifies app name to use. -
-
-
diff --git a/docs/documentation/1-x/generate/component.md b/docs/documentation/1-x/generate/component.md
deleted file mode 100644
index 37b31a077b67..000000000000
--- a/docs/documentation/1-x/generate/component.md
+++ /dev/null
@@ -1,117 +0,0 @@
-
-
-# ng generate component
-
-## Overview
-`ng generate component [name]` generates a component
-
-## Options
-spec
-
- --spec
-
- Specifies if a spec file is generated. -
-
-
-
-app
-
- --app (aliases: -a) default value: 1st app
-
- Specifies app name to use. -
-
-
-
-change-detection
-
- --change-detection (aliases: -c)
-
- Specifies the change detection strategy. -
-
-
-
-flat
-
- --flat default value: false
-
- Flag to indicate if a dir is created. -
-
-
-
-export
-
- --export default value: false
-
- Specifies if declaring module exports the component. -
-
-
-
-inline-style
-
- --inline-style (aliases: -s) default value: false
-
- Specifies if the style will be in the ts file. -
-
-
-
-inline-template
-
- --inline-template (aliases: -t) default value: false
-
- Specifies if the template will be in the ts file. -
-
-
-
-module
-
- --module (aliases: -m)
-
- Allows specification of the declaring module's file name (e.g `app.module.ts`). -
-
-
-
-prefix
-
- --prefix
-
- Specifies whether to use the prefix. -
-
-
-
-skip-import
-
- --skip-import default value: false
-
- Allows for skipping the module import. -
-
-
-
-spec
-
- --spec
-
- Specifies if a spec file is generated. -
-
-
diff --git a/docs/documentation/1-x/generate/directive.md b/docs/documentation/1-x/generate/directive.md
deleted file mode 100644
index 9ed8f37046c7..000000000000
--- a/docs/documentation/1-x/generate/directive.md
+++ /dev/null
@@ -1,77 +0,0 @@
-
-
-# ng generate directive
-
-## Overview
-`ng generate directive [name]` generates a directive
-
-## Options
-view-encapsulation
-
- --view-encapsulation (aliases: -v)
-
- Specifies the view encapsulation strategy. -
-
-
-
-app
-
- --app (aliases: -a) default value: 1st app
-
- Specifies app name to use. -
-
-
-
-export
-
- --export default value: false
-
- Specifies if declaring module exports the component. -
-
-
-
-flat
-
- --flat
-
- Flag to indicate if a dir is created. -
-
-
-
-module
-
- --module (aliases: -m)
-
- Allows specification of the declaring module. -
-
-
-
-prefix
-
- --prefix
-
- Specifies whether to use the prefix. -
-
-
-
-skip-import
-
- --skip-import
-
- Allows for skipping the module import. -
-
-
diff --git a/docs/documentation/1-x/generate/enum.md b/docs/documentation/1-x/generate/enum.md
deleted file mode 100644
index c7b4b66ff19f..000000000000
--- a/docs/documentation/1-x/generate/enum.md
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-# ng generate enum
-
-## Overview
-`ng generate enum [name]` generates an enumeration
-
-## Options
-spec
-
- --spec
-
- Specifies if a spec file is generated. -
-
-
diff --git a/docs/documentation/1-x/generate/guard.md b/docs/documentation/1-x/generate/guard.md
deleted file mode 100644
index 3435dd172f66..000000000000
--- a/docs/documentation/1-x/generate/guard.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# ng generate guard
-
-## Overview
-`ng generate guard [name]` generates a guard
-
-## Options
-app
-
- --app (aliases: -a) default value: 1st app
-
- Specifies app name to use. -
-
-
-
-app
-
- --app (aliases: -a) default value: 1st app
-
- Specifies app name to use. -
-
-
-
-flat
-
- --flat
-
- Indicate if a dir is created. -
-
-
-
-module
-
- --module (aliases: -m)
-
- Specifies where the guard should be provided. -
-
-
diff --git a/docs/documentation/1-x/generate/interface.md b/docs/documentation/1-x/generate/interface.md
deleted file mode 100644
index 8aa09de4ca76..000000000000
--- a/docs/documentation/1-x/generate/interface.md
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-# ng generate interface
-
-## Overview
-`ng generate interface [name] spec
-
- --spec
-
- Specifies if a spec file is generated. -
-
-
-
-app
-
- --app (aliases: -a) default value: 1st app
-
- Specifies app name to use. -
-
-
diff --git a/docs/documentation/1-x/generate/module.md b/docs/documentation/1-x/generate/module.md
deleted file mode 100644
index 55559f122406..000000000000
--- a/docs/documentation/1-x/generate/module.md
+++ /dev/null
@@ -1,59 +0,0 @@
-
-
-# ng generate module
-
-## Overview
-`ng generate module [name]` generates an NgModule
-
-## Options
-type
-- Optional String to specify the type of interface. -
-
-
-
-app
-
- --app (aliases: -a) default value: 1st app
-
- Specifies app name to use. -
-
-
-
-flat
-
- --flat
-
- Flag to indicate if a dir is created. -
-
-
-
-module
-
- --module (aliases: -m)
-
- Specifies where the module should be imported. -
-
-
-
-spec
-
- --spec
-
- Specifies if a spec file is generated. -
-
-
-
-
diff --git a/docs/documentation/1-x/generate/pipe.md b/docs/documentation/1-x/generate/pipe.md
deleted file mode 100644
index b8ee09497f3a..000000000000
--- a/docs/documentation/1-x/generate/pipe.md
+++ /dev/null
@@ -1,67 +0,0 @@
-
-
-# ng generate pipe
-
-## Overview
-`ng generate pipe [name]` generates a pipe
-
-## Options
-routing
-
- --routing
-
- Specifies if a routing module file should be generated. -
-
-
-
-app
-
- --app (aliases: -a) default value: 1st app
-
- Specifies app name to use. -
-
-
-
-export
-
- --export
-
- Specifies if declaring module exports the pipe. -
-
-
-
-flat
-
- --flat
-
- Flag to indicate if a dir is created. -
-
-
-
-module
-
- --module (aliases: -m)
-
- Allows specification of the declaring module. -
-
-
-
-skip-import
-
- --skip-import
-
- Allows for skipping the module import. -
-
-
diff --git a/docs/documentation/1-x/generate/service.md b/docs/documentation/1-x/generate/service.md
deleted file mode 100644
index eb94f5c5b9bc..000000000000
--- a/docs/documentation/1-x/generate/service.md
+++ /dev/null
@@ -1,47 +0,0 @@
-
-
-# ng generate service
-
-## Overview
-`ng generate service [name]` generates a service
-
-## Options
-spec
-
- --spec
-
- Specifies if a spec file is generated. -
-
-
-
-app
-
- --app (aliases: -a) default value: 1st app
-
- Specifies app name to use. -
-
-
-
-flat
-
- --flat
-
- Flag to indicate if a dir is created. -
-
-
-
-module
-
- --module (aliases: -m)
-
- Specifies where the service should be provided. -
-
-
diff --git a/docs/documentation/1-x/home.md b/docs/documentation/1-x/home.md
deleted file mode 100644
index a03e9c185ecb..000000000000
--- a/docs/documentation/1-x/home.md
+++ /dev/null
@@ -1,66 +0,0 @@
-
-
-# Angular CLI
-
-NOTE: this documentation is for Angular CLI 1.x. For Angular CLI 6 go [here](home) instead.
-
-### Overview
-The Angular CLI is a tool to initialize, develop, scaffold and maintain [Angular](https://angular.io) applications
-
-### Getting Started
-To install the Angular CLI:
-```
-npm install -g @angular/cli
-```
-
-Generating and serving an Angular project via a development server
-[Create](1-x/new) and [run](1-x/serve) a new project:
-```
-ng new my-project
-cd my-project
-ng serve
-```
-Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.
-
-### Bundling
-
-All builds make use of bundling, and using the `--prod` flag in `ng build --prod`
-or `ng serve --prod` will also make use of uglifying and tree-shaking functionality.
-
-### Running unit tests
-
-```bash
-ng test
-```
-
-Tests will execute after a build is executed via [Karma](http://karma-runner.github.io/0.13/index.html), and it will automatically watch your files for changes. You can run tests a single time via `--watch=false` or `--single-run`.
-
-### Running end-to-end tests
-
-```bash
-ng e2e
-```
-
-Before running the tests make sure you are serving the app via `ng serve`.
-End-to-end tests are run via [Protractor](http://www.protractortest.org/).
-
-### Additional Commands
-* [ng new](1-x/new)
-* [ng serve](1-x/serve)
-* [ng generate](1-x/generate)
-* [ng lint](1-x/lint)
-* [ng test](1-x/test)
-* [ng e2e](1-x/e2e)
-* [ng build](1-x/build)
-* [ng get/ng set](1-x/config)
-* [ng doc](1-x/doc)
-* [ng eject](1-x/eject)
-* [ng xi18n](1-x/xi18n)
-* [ng update](1-x/update)
-
-## Angular CLI Config Schema
-* [Config Schema](1-x/angular-cli)
-
-### Additional Information
-There are several [stories](1-x/stories) which will walk you through setting up
-additional aspects of Angular applications.
diff --git a/docs/documentation/1-x/lint.md b/docs/documentation/1-x/lint.md
deleted file mode 100644
index 46a005c8741e..000000000000
--- a/docs/documentation/1-x/lint.md
+++ /dev/null
@@ -1,47 +0,0 @@
-
-
-# ng lint
-
-## Overview
-`ng lint` will lint you app code using tslint.
-
-## Options
-spec
-
- --spec
-
- Specifies if a spec file is generated. -
-
-
-
-fix
-
- --fix default value: false
-
- Fixes linting errors (may overwrite linted files). -
-
-
-
-force
-
- --force default value: false
-
- Succeeds even if there was linting errors. -
-
-
-
-type-check
-
- --type-check default value: false
-
- Controls the type check for linting. -
-
-
diff --git a/docs/documentation/1-x/new.md b/docs/documentation/1-x/new.md
deleted file mode 100644
index 2dedb230af07..000000000000
--- a/docs/documentation/1-x/new.md
+++ /dev/null
@@ -1,168 +0,0 @@
-
-
-# ng new
-
-## Overview
-`ng new [name]` creates a new angular application.
-
-Default applications are created in a directory of the same name, with an initialized Angular application.
-
-## Options
-format
-
- --format (aliases: -t) default value: prose
-
- Output format (prose, json, stylish, verbose, pmd, msbuild, checkstyle, vso, fileslist, codeFrame). -
-
-
-
-directory
-
- --directory (alias: -d) default value: dir
-
- The directory name to create the app in. -
-
-
-
-dry-run
-
- --dry-run (alias: -d) default value: false
-
- Run through without making any changes. Will list all files that would have been created when running ng new.
-
-
-
-inline-style
-
- --inline-style (alias: -s) default value: false
-
- Should have an inline style. -
-
-
-
-inline-template
-
- --inline-template (alias: -t) default value: false
-
- Should have an inline template. -
-
-
-
-minimal
-
- --minimal default value: false
-
- Should create a minimal app. -
-
-
-
-prefix
-
- --prefix (alias: -p) default value: app
-
- The prefix to use for all component selectors. -
-
- You can later change the value in .angular-cli.json (apps[0].prefix).
-
-
-
-routing
-
- --routing default value: false
-
- Generate a routing module. -
-
-
-
-skip-commit
-
- --skip-commit (alias: -sc) default value: false
-
- Skip committing the first commit to git. -
-
-
-
-skip-git
-
- --skip-git (alias: -g) default value: false
-
- Skip initializing a git repository. -
-
-
-
-skip-install
-
- --skip-install (alias: -si) default value: false
-
- Skip installing packages. -
-
-
-
-skip-tests
-
- --skip-tests (aliases: -S) default value: false
-
- Skip creating spec files. -
-- Skip including e2e functionality. -
-
-
-
-source-dir
-
- --source-dir (alias: -D) default value: src
-
- The name of the source directory. -
-
- You can later change the value in .angular-cli.json (apps[0].root).
-
-
-
-style
-
- --style default value: css
-
- The style file default extension. Possible values:
-
- -
-
- css -
- scss -
- less -
- sass -
- styl (
stylus) - -
- You can later change the value in .angular-cli.json (defaults.styleExt).
-
-
diff --git a/docs/documentation/1-x/serve.md b/docs/documentation/1-x/serve.md
deleted file mode 100644
index 2a441a2dc59c..000000000000
--- a/docs/documentation/1-x/serve.md
+++ /dev/null
@@ -1,316 +0,0 @@
-
-
-# ng serve
-
-## Overview
-`ng serve` builds the application and starts a web server.
-
-All the build Options are available in serve, below are the additional options.
-
-## Options
-verbose
-
- --verbose (alias: -v) default value: false
-
- Adds more details to output logging. -
-
-
-
-host
-
- --host (aliases: -H) default value: localhost
-
- Listens only on localhost by default. -
-
-
-
-hmr
-
- --hmr default value: false
-
- Enable hot module replacement. -
-
-
-
-live-reload
-
- --live-reload (aliases: -lr) default value: true
-
- Whether to reload the page on change, using live-reload. -
-
-
-
-public-host
-
- --public-host (aliases: --live-reload-client)
-
- Specify the URL that the browser client will use. -
-
-
-
-disable-host-check
-
- --disable-host-check default value: false
-
- Don't verify connected clients are part of allowed hosts. -
-
-
-
-open
-
- --open (aliases: -o) default value: false
-
- Opens the url in default browser. -
-
-
-
-port
-
- --port (aliases: -p) default value: 4200
-
- Port to listen to for serving. --port 0 will get a free port
-
-
-
-ssl
-
- --ssl
-
- Serve using HTTPS. -
-
-
-
-ssl-cert
-
- --ssl-cert (aliases: -) default value:
-
- SSL certificate to use for serving HTTPS. -
-
-
-
-ssl-key
-
- --ssl-key
-
- SSL key to use for serving HTTPS. -
-
-
-
-aot
-
- --aot
-
- Build using Ahead of Time compilation. -
-
-
-
-base-href
-
- --base-href (aliases: -bh)
-
- Base url for the application being built. -
-
-
-
-deploy-url
-
- --deploy-url (aliases: -d)
-
- URL where files will be deployed. -
-
-
-
-environment
-
- --environment (aliases: -e)
-
- Defines the build environment. -
-
-
-
-extract-css
-
- --extract-css (aliases: -ec)
-
- Extract css from global styles onto css files instead of js ones. -
-
-
-
-i18n-file
-
- --i18n-file
-
- Localization file to use for i18n. -
-
-
-
-i18n-format
-
- --i18n-format
-
- Format of the localization file specified with --i18n-file. -
-
-
-
-locale
-
- --locale
-
- Locale to use for i18n. -
-
-
-
-missing-translation
-
- --missing-translation
-
- How to handle missing translations for i18n. -
-
- Values: error, warning, ignore
-
-
-
-output-hashing
-
- --output-hashing (aliases: -oh) default value:
-
- Define the output filename cache-busting hashing mode. Possible values: none, all, media, bundles
-
-
-
-output-path
-
- --output-path (aliases: -op) default value:
-
- Path where output will be placed. -
-
-
-
-poll
-
- --poll
-
- Enable and define the file watching poll time period (milliseconds) . -
-
-
-
-progress
-
- --progress (aliases: -pr) default value: true inside TTY, false otherwise
-
- Log progress to the console while building. -
-
-
-
-proxy-config
-
- --proxy-config (aliases: -pc)
-
- Use a proxy configuration file to send some requests to a backend server rather than the webpack dev server. -
-
-
-
-sourcemap
-
- --sourcemap (aliases: -sm, sourcemaps)
-
- Output sourcemaps. -
-
-
-
-target
-
- --target (aliases: -t, -dev, -prod) default value: development
-
- Defines the build target. -
-
-
-
-vendor-chunk
-
- --vendor-chunk (aliases: -vc) default value: true
-
- Use a separate bundle containing only vendor libraries. -
-
-
-
-common-chunk
-
- --common-chunk (aliases: -cc) default value: true
-
- Use a separate bundle containing code used across multiple bundles. -
-
-
-
-verbose
-
- --verbose (aliases: -v) default value: false
-
- Adds more details to output logging. -
-
-
-
-
-## Note
-When running `ng serve`, the compiled output is served from memory, not from disk. This means that the application being served is not located on disk in the `dist` folder.
diff --git a/docs/documentation/1-x/stories.md b/docs/documentation/1-x/stories.md
deleted file mode 100644
index d602d59e328c..000000000000
--- a/docs/documentation/1-x/stories.md
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-# Stories describing how to do more with the CLI
-
- - [1.0 Update](1-x/stories/1.0-update)
- - [Asset Configuration](1-x/stories/asset-configuration)
- - [Autocompletion](1-x/stories/autocompletion)
- - [Configure Hot Module Replacement](1-x/stories/configure-hmr)
- - [CSS Preprocessors](1-x/stories/css-preprocessors)
- - [Global Lib](1-x/stories/global-lib)
- - [Global Scripts](1-x/stories/global-scripts)
- - [Global Styles](1-x/stories/global-styles)
- - [Angular Flex Layout](1-x/stories/include-angular-flex)
- - [Angular Material](1-x/stories/include-angular-material)
- - [AngularFire](1-x/stories/include-angularfire)
- - [Bootstrap](1-x/stories/include-bootstrap)
- - [Budgets](1-x/stories/budgets)
- - [Font Awesome](1-x/stories/include-font-awesome)
- - [Moving Into the CLI](1-x/stories/moving-into-the-cli)
- - [Moving Out of the CLI](1-x/stories/moving-out-of-the-cli)
- - [Proxy](1-x/stories/proxy)
- - [Routing](1-x/stories/routing)
- - [3rd Party Lib](1-x/stories/third-party-lib)
- - [Corporate Proxy](1-x/stories/using-corporate-proxy)
- - [Internationalization (i18n)](1-x/stories/internationalization)
- - [Serve from Disk](1-x/stories/disk-serve)
- - [Code Coverage](1-x/stories/code-coverage)
- - [Application Environments](1-x/stories/application-environments)
- - [Autoprefixer Configuration](1-x/stories/autoprefixer)
- - [Deploy to GitHub Pages](1-x/stories/github-pages)
- - [Linked Library](1-x/stories/linked-library)
- - [Multiple apps](1-x/stories/multiple-apps)
- - [Continuous Integration](1-x/stories/continuous-integration)
- - [Universal Rendering](1-x/stories/universal-rendering)
diff --git a/docs/documentation/1-x/stories/1.0-update.md b/docs/documentation/1-x/stories/1.0-update.md
deleted file mode 100644
index 9a32e4555ab9..000000000000
--- a/docs/documentation/1-x/stories/1.0-update.md
+++ /dev/null
@@ -1,503 +0,0 @@
-# Angular CLI migration guide
-
-In this migration guide we'll be looking at some of the major changes to CLI projects in the
-last two months.
-
-Most of these changes were not breaking changes and your project should work fine without them.
-
-But if you've been waiting for the perfect time to update, this is it!
-Along with major rebuild speed increases, we've been busy adding a lot of features.
-
-Documentation has also completely moved to [the wiki](https://github.com/angular/angular-cli/wiki).
-The new [Stories](https://github.com/angular/angular-cli/wiki/stories) section covers common usage
-scenarios, so be sure to have a look!
-
-Below are the changes between a project generated two months ago, with `1.0.0-beta.24` and
-a `1.0.0` project.
-If you kept your project up to date you might have a lot of these already.
-
-You can find more details about changes between versions in [the releases tab on GitHub](https://github.com/angular/angular-cli/releases).
-
-If you prefer, you can also generate a new project in a separate folder using
- `ng new upgrade-project --skip-install` and compare the differences.
-
-## @angular/cli
-
-Angular CLI can now be found on NPM under `@angular/cli` instead of `angular-cli`, and upgrading is a simple 3 step process:
-
-1. Uninstall old version
-2. Update node/npm if necessary
-3. Install new version
-
-### 1. Uninstall old version
-
-If you're using Angular CLI `beta.28` or less, you need to uninstall the `angular-cli` packages:
-```bash
-npm uninstall -g angular-cli # Remove global package
-npm uninstall --save-dev angular-cli # Remove from package.json
-```
-
-Otherwise, uninstall the `@angular/cli` packages:
-```bash
-npm uninstall -g @angular/cli # Remove global package
-npm uninstall --save-dev @angular/cli # Remove from package.json
-```
-
-Also purge the cache and local packages:
-```
-rm -rf node_modules dist # Use rmdir on Windows
-npm cache clean
-```
-
-At this point, you should not have Angular CLI on your system anymore. If invoking Angular CLI at the commandline reveals that it still exists on your system, you will have to manually remove it. See _Manually removing residual Angular CLI_.
-
-### 2. Update node/npm if necessary
-
-Angular CLI now has a minimum requirement of Node 6.9.0 or higher, together with NPM 3 or higher.
-
-If your Node or NPM versions do not meet these requirements, please refer to [the documentation](https://docs.npmjs.com/getting-started/installing-node) on how to upgrade.
-
-### 3. Install the new version
-
-To update Angular CLI to a new version, you must update both the global package and your project's local package:
-
-```bash
-npm install -g @angular/cli@latest # Global package
-npm install --save-dev @angular/cli@latest # Local package
-npm install # Restore removed dependencies
-```
-
-### Manually removing residual Angular CLI
-
-If you accidentally updated NPM before removing the old Angular CLI, you may find that uninstalling the package using `npm uninstall` is proving fruitless. This _could_ be because the global install (and uninstall) path changed between versions of npm from `/usr/local/lib` to `/usr/lib`, and hence, no longer searches through the old directory. In this case you'll have to remove it manually:
-
-`rm -rf /usr/local/lib/node_modules/@angular/cli`
-
-If the old Angular CLI package _still_ persists, you'll need to research how to remove it before proceeding with the upgrade.
-
-## .angular-cli.json
-
-`angular-cli.json` is now `.angular-cli.json`, but we still accept the old config file name.
-
-A few new properties have changed in it:
-
-### Schema
-
-Add the `$schema` property above project for handy IDE support on your config file:
-
-```
-"$schema": "./node_modules/@angular/cli/lib/config/schema.json",
-```
-
-### Polyfills
-
-There is now a dedicated entry for polyfills ([#3812](https://github.com/angular/angular-cli/pull/3812))
-inside `apps[0].polyfills`, between `main` and `test`:
-
-```
-"main": "main.ts",
-"polyfills": "polyfills.ts",
-"test": "test.ts",
-```
-
-Add it and remove `import './polyfills.ts';` from `src/main.ts` and `src/test.ts`.
-
-We also added a lot of descriptive comments to the existing `src/polyfills.ts` file, explaining
-which polyfills are needed for what browsers.
-Be sure to check it out in a new project!
-
-### Environments
-
-A new `environmentSource` entry ([#4705](https://github.com/angular/angular-cli/pull/4705))
-replaces the previous source entry inside environments.
-
-To migrate angular-cli.json follow the example below:
-
-Before:
-```
-"environments": {
- "source": "environments/environment.ts",
- "dev": "environments/environment.ts",
- "prod": "environments/environment.prod.ts"
-}
-```
-
-After:
-
-```
-"environmentSource": "environments/environment.ts",
-"environments": {
- "dev": "environments/environment.ts",
- "prod": "environments/environment.prod.ts"
-}
-```
-
-### Linting
-
-The CLI now uses the TSLint API ([#4248](https://github.com/angular/angular-cli/pull/4248))
-to lint several TS projects at once.
-
-There is a new `lint` entry in `.angular-cli.json` between `e2e` and `test` where all linting
-targets are listed:
-
-```
-"e2e": {
- "protractor": {
- "config": "./protractor.conf.js"
- }
-},
-"lint": [
- {
- "project": "src/tsconfig.app.json"
- },
- {
- "project": "src/tsconfig.spec.json"
- },
- {
- "project": "e2e/tsconfig.e2e.json"
- }
-],
-"test": {
- "karma": {
- "config": "./karma.conf.js"
- }
-},
-```
-
-### Generator defaults
-
-Now you can list generator defaults per generator ([#4389](https://github.com/angular/angular-cli/pull/4389))
-in `defaults`.
-
-Instead of:
-```
-"defaults": {
- "styleExt": "css",
- "prefixInterfaces": false,
- "inline": {
- "style": false,
- "template": false
- },
- "spec": {
- "class": false,
- "component": true,
- "directive": true,
- "module": false,
- "pipe": true,
- "service": true
- }
-}
-```
-
-You can instead list the flags as they appear on [the generator command](https://github.com/angular/angular-cli/wiki/generate-component):
-```
-"defaults": {
- "styleExt": "css",
- "component": {
- "inlineTemplate": false,
- "spec": true
- }
-}
-```
-
-## One tsconfig per app
-
-CLI projects now use one tsconfig per app ([#4924](https://github.com/angular/angular-cli/pull/4924)).
-
-- `src/tsconfig.app.json`: configuration for the Angular app.
-```
-{
- "compilerOptions": {
- "sourceMap": true,
- "declaration": false,
- "moduleResolution": "node",
- "emitDecoratorMetadata": true,
- "experimentalDecorators": true,
- "target": "es5",
- "lib": [
- "es2017",
- "dom"
- ],
- "outDir": "../out-tsc/app",
- "module": "es2015",
- "baseUrl": "",
- "types": []
- },
- "exclude": [
- "test.ts",
- "**/*.spec.ts"
- ]
-}
-```
-- `src/tsconfig.spec.json`: configuration for the unit tests.
-```
-{
- "compilerOptions": {
- "sourceMap": true,
- "declaration": false,
- "moduleResolution": "node",
- "emitDecoratorMetadata": true,
- "experimentalDecorators": true,
- "lib": [
- "es2017",
- "dom"
- ],
- "outDir": "../out-tsc/spec",
- "module": "commonjs",
- "target": "es5",
- "baseUrl": "",
- "types": [
- "jasmine",
- "node"
- ]
- },
- "files": [
- "test.ts"
- ],
- "include": [
- "**/*.spec.ts",
- "**/*.d.ts"
- ]
-}
-
-```
-- `e2e/tsconfig.e2e.json`: configuration for the e2e tests.
-```
-{
- "compilerOptions": {
- "sourceMap": true,
- "declaration": false,
- "moduleResolution": "node",
- "emitDecoratorMetadata": true,
- "experimentalDecorators": true,
- "lib": [
- "es2017"
- ],
- "outDir": "../out-tsc/e2e",
- "module": "commonjs",
- "target": "es5",
- "types":[
- "jasmine",
- "node"
- ]
- }
-}
-
-```
-
-There is an additional root-level `tsconfig.json` that is used for IDE integration.
-```
-{
- "compileOnSave": false,
- "compilerOptions": {
- "outDir": "./dist/out-tsc",
- "baseUrl": "src",
- "sourceMap": true,
- "declaration": false,
- "moduleResolution": "node",
- "emitDecoratorMetadata": true,
- "experimentalDecorators": true,
- "target": "es5",
- "typeRoots": [
- "node_modules/@types"
- ],
- "lib": [
- "es2017",
- "dom"
- ]
- }
-}
-```
-
-You can delete `e2e/tsconfig.json` and `src/tsconfig.json` after adding these.
-
-Also update `.angular-cli.json` to use them inside `apps[0]`:
-
-```
-"tsconfig": "tsconfig.app.json",
-"testTsconfig": "tsconfig.spec.json",
-```
-
-Then update `protractor.conf.js` to use the e2e config as well:
-```
-beforeLaunch: function() {
- require('ts-node').register({
- project: 'e2e/tsconfig.e2e.json'
- });
-},
-```
-
-These configs have an `types` array where you should add any package you install via `@types/*`.
-This array helps keep typings isolated to the apps that really need them and avoid problems with
-duplicate typings.
-
-For instance, the unit test `tsconfig` has `jasmine` and `node`, which correspond to
-`@types/jasmine` and `@types/node`.
-Add any typings you've installed to the appropriate `tsconfig` as well.
-
-## typings.d.ts
-
-There's a new `src/typings.d.ts` file that serves two purposes:
-- provides a centralized place for users to add their own custom typings
-- makes it easy to use components that use `module.id`, present in the documentation and in snippets
-
-```
-/* SystemJS module definition */
-declare var module: NodeModule;
-interface NodeModule {
- id: string;
-}
-```
-
-## package.json
-
-We've updated a lot of packages over the last months in order to keep projects up to date.
-
-Additions or removals are found in bold below.
-
-Packages in `dependencies`:
-- `@angular/*` packages now have a `^4.0.0` minimum
-- `core-js` remains unchanged at `^2.4.1`
-- `rxjs` was updated to `^5.1.0`
-- `ts-helpers` was **removed**
-- `zone.js` was updated to `^0.8.4`
-
-Packages in `devDependencies`:
-- `@angular/cli` at `1.0.0` replaces `angular-cli`
-- `@angular/compiler-cli` is also at `^4.0.0`
-- `@types/jasmine` remains unchanged and pinned at `2.5.38`
-- `@types/node` was updated to `~6.0.60`
-- `codelyzer` was updated to `~2.0.0`
-- `jasmine-core` was updated to `~2.5.2`
-- `jasmine-spec-reporter` was updated to `~3.2.0`
-- `karma` was updated to `~1.4.1`
-- `karma-chrome-launcher` was updated to `~2.0.0`
-- `karma-cli` was updated to `~1.0.1`
-- `karma-jasmine` was updated to `~1.1.0`
-- `karma-jasmine-html-reporter` was **added** at `^0.2.2`
-- `karma-coverage-istanbul-reporter` was **added** at `^0.2.0`, replacing `karma-remap-istanbul`
-- `karma-remap-istanbul` was **removed**
-- `protractor` was updated to `~5.1.0`
-- `ts-node` was updated to `~2.0.0`
-- `tslint` was updated to `~4.5.0`
-- `typescript` was updated to `~2.1.0`
-
-See the [karma](1-x/#karma.conf.js) and [protractor](1-x/#protractor.conf.js) sections below for more
-information on changed packages.
-
-The [Linting rules](1-x/#Linting rules) section contains a list of rules that changed due to updates.
-
-We also updated the scripts section to make it more simple:
-
-```
-"scripts": {
- "ng": "ng",
- "start": "ng serve",
- "build": "ng build",
- "test": "ng test",
- "lint": "ng lint",
- "e2e": "ng e2e"
-},
-```
-
-## karma.conf.js
-
-Karma configuration suffered some changes to improve the code-coverage functionality,
-use the new `@angular/cli` package, and the new HTML reporter.
-
-In the `frameworks` array update the CLI package to `@angular/cli`.
-
-In the `plugins` array:
-- add `require('karma-jasmine-html-reporter')` and `require('karma-coverage-istanbul-reporter')`
-- remove `require('karma-remap-istanbul')`
-- update the CLI plugin to `require('@angular/cli/plugins/karma')`
-
-Add a new `client` option just above `patterns`:
-```
-client:{
- clearContext: false // leave Jasmine Spec Runner output visible in browser
-},
-files: [
-```
-
-Change the preprocessor to use the new CLI package:
-```
-preprocessors: {
- './src/test.ts': ['@angular/cli']
-},
-```
-
-Replace `remapIstanbulReporter` with `coverageIstanbulReporter`:
-```
-coverageIstanbulReporter: {
- reports: [ 'html', 'lcovonly' ],
- fixWebpackSourcePaths: true
-},
-```
-
-Remove the config entry from `angularCli`:
-```
-angularCli: {
- environment: 'dev'
-},
-```
-
-Update the reporters to use `coverage-istanbul` instead of `karma-remap-istanbul`, and
-add `kjhtml` (short for karma-jasmine-html-reporter):
-```
-reporters: config.angularCli && config.angularCli.codeCoverage
- ? ['progress', 'coverage-istanbul']
- : ['progress', 'kjhtml'],
-```
-
-## protractor.conf.js
-
-Protractor was updated to the new 5.x major version, but you shouldn't need to change much
-to take advantage of all its new features.
-
-Replace the spec reporter import from:
-```
-var SpecReporter = require('jasmine-spec-reporter');
-```
-to
-```
-const { SpecReporter } = require('jasmine-spec-reporter');
-```
-
-Remove `useAllAngular2AppRoots: true`.
-
-Update `beforeLaunch` as described in [One tsconfig per app](1-x/#one-tsconfig-per-app):
-```
-beforeLaunch: function() {
- require('ts-node').register({
- project: 'e2e/tsconfig.e2e.json'
- });
-},
-```
-
-Update `onPrepare`:
-```
-onPrepare: function() {
- jasmine.getEnv().addReporter(new SpecReporter({ spec: { displayStacktrace: true } }));
-}
-```
-
-## Linting rules
-
-The updated versions of `tslint` and `codelyzer` contain a few rule changes that you should
-apply to your `tslint.json`:
-
-Add these new rules:
-```
-"callable-types": true,
-"import-blacklist": [true, "rxjs"],
-"import-spacing": true,
-"interface-over-type-literal": true,
-"no-empty-interface": true,
-"no-string-throw": true,
-"prefer-const": true,
-"typeof-compare": true,
-"unified-signatures": true,
-```
-
-Update `no-inferrable-types` to `"no-inferrable-types": [true, "ignore-params"]`.
diff --git a/docs/documentation/1-x/stories/application-environments.md b/docs/documentation/1-x/stories/application-environments.md
deleted file mode 100644
index d3c4b18d054c..000000000000
--- a/docs/documentation/1-x/stories/application-environments.md
+++ /dev/null
@@ -1,122 +0,0 @@
-# Application Environments
-
-## Configuring available environments
-
-`.angular-cli.json` contains an **environments** section. By default, this looks like:
-
-``` json
-"environments": {
- "dev": "environments/environment.ts",
- "prod": "environments/environment.prod.ts"
-}
-```
-
-You can add additional environments as required. To add a **staging** environment, your configuration would look like:
-
-``` json
-"environments": {
- "dev": "environments/environment.ts",
- "staging": "environments/environment.staging.ts",
- "prod": "environments/environment.prod.ts"
-}
-```
-
-## Adding environment-specific files
-
-The environment-specific files are set out as shown below:
-
-```
-└── src
- └── environments
- ├── environment.prod.ts
- └── environment.ts
-```
-
-If you wanted to add another environment for **staging**, your file structure would become:
-
-```
-└── src
- └── environments
- ├── environment.prod.ts
- ├── environment.staging.ts
- └── environment.ts
-```
-
-## Amending environment-specific files
-
-`environment.ts` contains the default settings. If you take a look at this file, it should look like:
-
-``` TypeScript
-export const environment = {
- production: false
-};
-```
-
-If you compare this to `environment.prod.ts`, which looks like:
-
-``` TypeScript
-export const environment = {
- production: true
-};
-```
-
-You can add further variables, either as additional properties on the `environment` object, or as separate objects, for example:
-
-``` TypeScript
-export const environment = {
- production: false,
- apiUrl: 'http://my-api-url'
-};
-```
-
-## Using environment-specific variables in your application
-
-Given the following application structure:
-
-```
-└── src
- └── app
- ├── app.component.html
- └── app.component.ts
- └── environments
- ├── environment.prod.ts
- ├── environment.staging.ts
- └── environment.ts
-```
-
-Using environment variables inside of `app.component.ts` might look something like this:
-
-``` TypeScript
-import { Component } from '@angular/core';
-import { environment } from './../environments/environment';
-
-@Component({
- selector: 'app-root',
- templateUrl: './app.component.html',
- styleUrls: ['./app.component.css']
-})
-export class AppComponent {
- constructor() {
- console.log(environment.production); // Logs false for default environment
- }
- title = 'app works!';
-}
-```
-
-## Environment-specific builds
-
-Running:
-
-```
-ng build
-```
-
-Will use the defaults found in `environment.ts`
-
-Running:
-
-```
-ng build --env=staging
-```
-
-Will use the values from `environment.staging.ts`
diff --git a/docs/documentation/1-x/stories/asset-configuration.md b/docs/documentation/1-x/stories/asset-configuration.md
deleted file mode 100644
index ef910b1d8561..000000000000
--- a/docs/documentation/1-x/stories/asset-configuration.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# Project assets
-
-You use the `assets` array in `.angular-cli.json` to list files or folders you want to copy as-is
-when building your project.
-
-By default, the `src/assets/` folder and `src/favicon.ico` are copied over.
-
-```json
-"assets": [
- "assets",
- "favicon.ico"
-]
-```
-
-You can also further configure assets to be copied by using objects as configuration.
-
-The array below does the same as the default one:
-
-```json
-"assets": [
- { "glob": "**/*", "input": "./assets/", "output": "./assets/" },
- { "glob": "favicon.ico", "input": "./", "output": "./" },
-]
-```
-
-`glob` is the a [node-glob](https://github.com/isaacs/node-glob) using `input` as base directory.
-`input` is relative to the project root (`src/` default), while `output` is
- relative to `outDir` (`dist` default).
-
- You can use this extended configuration to copy assets from outside your project.
- For instance, you can copy assets from a node package:
-
- ```json
-"assets": [
- { "glob": "**/*", "input": "../node_modules/some-package/images", "output": "./some-package/" },
-]
-```
-
-The contents of `node_modules/some-package/images/` will be available in `dist/some-package/`.
-
-## Writing assets outside of `dist/`
-
-Because of the security implications, the CLI will always refuse to read or write files outside of
-the project itself (scoped by `.angular-cli.json`). It is however possible to write assets outside
-the `dist/` build output folder during build.
-
-Because writing files in your project isn't an expected effect of `ng build`, it is disabled by
-default on every assets. In order to allow this behaviour, you need to set `allowOutsideOutDir`
-to `true` on your asset definition, like so:
-
-```json
-"assets": [
- {
- "glob": "**/*",
- "input": "./assets/",
- "output": "../not-dist/some/folder/",
- "allowOutsideOutDir": true
- },
-]
-```
-
-This needs to be set for every assets you want to write outside of your build output directory.
diff --git a/docs/documentation/1-x/stories/autocompletion.md b/docs/documentation/1-x/stories/autocompletion.md
deleted file mode 100644
index 324d6a2faa58..000000000000
--- a/docs/documentation/1-x/stories/autocompletion.md
+++ /dev/null
@@ -1,21 +0,0 @@
-# Autocompletion
-
-To turn on auto completion use the following commands:
-
-For bash:
-```bash
-ng completion --bash >> ~/.bashrc
-source ~/.bashrc
-```
-
-For zsh:
-```bash
-ng completion --zsh >> ~/.zshrc
-source ~/.zshrc
-```
-
-Windows users using gitbash:
-```bash
-ng completion --bash >> ~/.bash_profile
-source ~/.bash_profile
-```
\ No newline at end of file
diff --git a/docs/documentation/1-x/stories/autoprefixer.md b/docs/documentation/1-x/stories/autoprefixer.md
deleted file mode 100644
index c6902fccaf3b..000000000000
--- a/docs/documentation/1-x/stories/autoprefixer.md
+++ /dev/null
@@ -1,43 +0,0 @@
-# Change target browsers for Autoprefixer
-
-Currently, the CLI uses [Autoprefixer](https://github.com/postcss/autoprefixer) to ensure compatibility
-with different browser and browser versions. You may find it necessary to target specific browsers
-or exclude certain browser versions from your build.
-
-Internally, Autoprefixer relies on a library called [Browserslist](https://github.com/browserslist/browserslist)
-to figure out which browsers to support with prefixing.
-
-There are a few ways to tell Autoprefixer what browsers to target:
-
-### Add a browserslist property to the `package.json` file
-```
-"browserslist": [
- "> 1%",
- "last 2 versions"
-]
-```
-
-### Add a new file to the project directory called `.browserslistrc`
-```
-### Supported Browsers
-
-> 1%
-last 2 versions
-```
-
-Autoprefixer will look for the configuration file/property to use when it prefixes your css.
-Check out the [browserslist repo](https://github.com/browserslist/browserslist) for more examples of how to target
-specific browsers and versions.
-
-_Side note:_
-Those who are seeking to produce a [progressive web app](https://developers.google.com/web/progressive-web-apps/) and are using [Lighthouse](https://developers.google.com/web/tools/lighthouse/) to grade the project will
-need to add the following browserslist config to their package.json file to eliminate the [old flexbox](https://developers.google.com/web/tools/lighthouse/audits/old-flexbox) prefixes:
-
-`package.json` config:
-```
-"browserslist": [
- "last 2 versions",
- "not ie <= 10",
- "not ie_mob <= 10"
-]
-```
diff --git a/docs/documentation/1-x/stories/budgets.md b/docs/documentation/1-x/stories/budgets.md
deleted file mode 100644
index e01364f9ce09..000000000000
--- a/docs/documentation/1-x/stories/budgets.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# Budgets
-
-As applications grow in functionality, they also grow in size. Budgets is a feature in the
-Angular CLI which allows you to set budget thresholds in your configuration to ensure parts
-of your application stay within boundries which you set.
-
-**.angular-cli.json**
-```
-{
- ...
- apps: [
- {
- ...
- budgets: []
- }
- ]
-}
-```
-
-## Budget Definition
-
-- type
- - The type of budget.
- - Possible values:
- - bundle - The size of a specific bundle.
- - initial - The initial size of the app.
- - allScript - The size of all scripts.
- - all - The size of the entire app.
- - anyScript - The size of any one script.
- - any - The size of any file.
-- name
- - The name of the bundle.
- - Required only for type of "bundle"
-- baseline
- - The baseline size for comparison.
-- maximumWarning
- - The maximum threshold for warning relative to the baseline.
-- maximumError
- - The maximum threshold for error relative to the baseline.
-- minimumWarning
- - The minimum threshold for warning relative to the baseline.
-- minimumError
- - The minimum threshold for error relative to the baseline.
-- warning
- - The threshold for warning relative to the baseline (min & max).
-- error
- - The threshold for error relative to the baseline (min & max).
-
-## Specifying sizes
-
-Available formats:
-
-- `123` - size in bytes
-- `123b` - size in bytes
-- `123kb` - size in kilobytes
-- `123mb` - size in megabytes
-- `12%` - percentage
-
-## NOTES
-
-All sizes are relative to baseline.
-Percentages are not valid for baseline values.
diff --git a/docs/documentation/1-x/stories/code-coverage.md b/docs/documentation/1-x/stories/code-coverage.md
deleted file mode 100644
index 354063cc1242..000000000000
--- a/docs/documentation/1-x/stories/code-coverage.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# Code Coverage
-
-With the Angular CLI we can run unit tests as well as create code coverage reports. Code coverage reports allow us to see any parts of our code base that may not be properly tested by our unit tests.
-
-To generate a coverage report run the following command in the root of your project
-
-```bash
-ng test --watch=false --code-coverage
-```
-
-Once the tests complete a new `/coverage` folder will appear in the project. In your Finder or Windows Explorer open the `index.html` file. You should see a report with your source code and code coverage values.
-
-Using the code coverage percentages we can estimate how much of our code is tested. It is up to your team to determine how much code should be unit tested.
-
-## Code Coverage Enforcement
-
-If your team decides on a set minimum amount to be unit tested you can enforce this minimum with the Angular CLI. For example our team would like the code base to have a minimum of 80% code coverage. To enable this open the `karma.conf.js` and add the following in the `coverageIstanbulReporter:` key
-
-```javascript
-coverageIstanbulReporter: {
- reports: [ 'html', 'lcovonly' ],
- fixWebpackSourcePaths: true,
- thresholds: {
- statements: 80,
- lines: 80,
- branches: 80,
- functions: 80
- }
-}
-```
-
-The `thresholds` property will enforce a minimum of 80% code coverage when the unit tests are run in the project.
\ No newline at end of file
diff --git a/docs/documentation/1-x/stories/configure-hmr.md b/docs/documentation/1-x/stories/configure-hmr.md
deleted file mode 100644
index 1823e8f1ba79..000000000000
--- a/docs/documentation/1-x/stories/configure-hmr.md
+++ /dev/null
@@ -1,150 +0,0 @@
-# Configure Hot Module Replacement
-
-Hot Module Replacement (HMR) is a WebPack feature to update code in a running app without rebuilding it.
-This results in faster updates and less full page-reloads.
-
-You can read more about HMR by visiting [this page](https://webpack.js.org/guides/hot-module-replacement/).
-
-In order to get HMR working with Angular CLI we first need to add a new environment and enable it.
-
-Next we need to update the bootstrap process of our app to enable the
-[@angularclass/hmr](https://github.com/gdi2290/angular-hmr) module.
-
-### Add environment for HMR
-
-Create a file called `src/environments/environment.hmr.ts` with the following contents:
-
-```typescript
-
-export const environment = {
- production: false,
- hmr: true
-};
-```
-
-Update `src/environments/environment.prod.ts` and add the `hmr: false` flag to the environment:
-
-```typescript
-export const environment = {
- production: true,
- hmr: false
-};
-```
-
-Update `src/environments/environment.ts` and add the `hmr: false` flag to the environment:
-
-```typescript
-export const environment = {
- production: false,
- hmr: false
-};
-```
-
-
-Update `.angular-cli.json` by adding the new environment the existing environments object:
-
-```json
-"environmentSource": "environments/environment.ts",
-"environments": {
- "dev": "environments/environment.ts",
- "hmr": "environments/environment.hmr.ts",
- "prod": "environments/environment.prod.ts"
-},
-```
-
-Run `ng serve` with the flag `--hmr -e=hmr` to enable hmr and select the new environment:
-
-```bash
-ng serve --hmr -e=hmr
-```
-
-Create a shortcut for this by updating `package.json` and adding an entry to the script object:
-
-```json
-"scripts": {
- ...
- "hmr": "ng serve --hmr -e=hmr"
-}
-```
-
-
-### Add dependency for @angularclass/hmr and configure app
-
-In order to get HMR working we need to install the dependency and configure our app to use it.
-
-
-Install the `@angularclass/hmr` module as a dev-dependency
-
-```bash
-$ npm install --save-dev @angularclass/hmr
-```
-
-
-Create a file called `src/hmr.ts` with the following content:
-
-```typescript
-import { NgModuleRef, ApplicationRef } from '@angular/core';
-import { createNewHosts } from '@angularclass/hmr';
-
-export const hmrBootstrap = (module: any, bootstrap: () => Promisewatch
-
- --watch (aliases: -w)
-
- Run build when files change. -
-