angular-cn/packages/localize/schematics/ng-add/README.md

# @angular/localize schematic for `ng add`

This schematic will be executed when an Angular CLI user runs `ng add @angular/localize`.

It will search their `angular.json` file, and find polyfills and main files for server builders.
Then it will add the `@angular/localize/init` polyfill that `@angular/localize` needs to work.

If the user specifies that they want to use `$localize` at runtime then the dependency will be
added to the `depdendencies` section of `package.json` rather than in the `devDependencies` which
is the default.
feat(ivy): support ng-add in localize package (#32791) PR Close #32791 2019-09-20 16:05:45 +01:00			# @angular/localize schematic for `ng add`

refactor(localize): use the new workspaces API for ng-add schematic (#36897) Updates the @angular/localize ng-add schematic to use the new workspaces API and removes dependency on private APIs. PR Close #36897 2020-05-05 12:47:12 +03:00			This schematic will be executed when an Angular CLI user runs `ng add @angular/localize`.
feat(ivy): support ng-add in localize package (#32791) PR Close #32791 2019-09-20 16:05:45 +01:00
			It will search their `angular.json` file, and find polyfills and main files for server builders.
fix(localize): install `@angular/localize` in `devDependencies` by default (#38680) Previously this package was installed in the default `dependencies` section of `package.json`, but this meant that its own dependencies are treated as dependencies of the main project: Babel, for example. Generally, $localize` is not used at runtime - it is compiled out by the translation tooling, so there is no need for it to be a full dependency. In fact, even if it is used at runtime, the package itself is only used at dev-time since the runtime bits will be bundled into a distributable. So putting this package in `devDependencies` would only prevent libraries from bringing the package into application projects that used them. This is probably good in itself, since it should be up to the downstream project to decide if it wants to include `@angular/localize` at runtime. This commit changes the default location of the package to be the `devDependencies` section, but gives an option `useAtRuntime` to choose otherwise. Fixes #38329 PR Close #38680 2020-09-02 16:16:10 +01:00			Then it will add the `@angular/localize/init` polyfill that `@angular/localize` needs to work.

			If the user specifies that they want to use `$localize` at runtime then the dependency will be
			added to the `depdendencies` section of `package.json` rather than in the `devDependencies` which
			`is the default.`