honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: convert Ivy opt-in doc to opt-out (#31858) 

PR Close #31858
This commit is contained in:
Filipe Silva 2019-07-26 14:21:13 +01:00 committed by atscott
parent 9bc9685911
commit 860b5d0efa
2 changed files with 19 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

47
aio/content/guide/ivy.md
View File

@ -1,38 +1,24 @@
# Opting into Angular Ivy # Opting out of Angular Ivy
Ivy is the code name for Angular's [next-generation compilation and rendering pipeline](https://blog.angular.io/a-plan-for-version-8-0-and-ivy-b3318dfc19f7). Starting with Angular version 8, you can choose to opt in to start using a preview version of Ivy and help in its continuing development and tuning. Ivy is the code name for Angular's [next-generation compilation and rendering pipeline](https://blog.angular.io/a-plan-for-version-8-0-and-ivy-b3318dfc19f7).
Starting with Angular version 9, Ivy compilation and rendering pipeline is enabled by default.
The previous compilation and rendering pipeline, View Engine, is deprecated in version 9, and will be removed at a later date.
You can choose to opt out of Ivy and continue using View Engine while making the transition.
<div class="alert is-helpful"> To opt out of Ivy and continue using View Engine for an existing project, set the `enableIvy` option in the `angularCompilerOptions` in your project's `tsconfig.json` to `false`.
To preview Ivy, use `@angular/core@next` version of Angular (8.1.x), rather than `@angular/core@latest` (8.0.x), as it contains all the latest bug fixes and improvements.
</div>
## Using Ivy in a new project
To start a new project with Ivy enabled, use the `--enable-ivy` flag with the [`ng new`](cli/new) command:
```sh
ng new shiny-ivy-app --enable-ivy
```
The new project is automatically configured for Ivy. Specifically, the enableIvy option is set to `true` in the project's `tsconfig.app.json` file.
## Using Ivy in an existing project
To update an existing project to use Ivy, set the `enableIvy` option in the `angularCompilerOptions` in your project's `tsconfig.app.json`.
```json ```json
{ {
"compilerOptions": { ... }, "compilerOptions": { ... },
"angularCompilerOptions": { "angularCompilerOptions": {
"enableIvy": true "enableIvy": false
} }
} }
``` ```
AOT compilation with Ivy is faster and should be used by default. In the `angular.json` workspace configuration file, set the default build options for your project to always use AOT compilation. AOT compilation with Ivy is faster than with View Engine, and can be used for development.
If you opt out of Ivy, AOT compilation will be slower, and should not be used for development in large projects.
When Ivy is disabled for a large project, make sure that the `aot` build option in that project configuration is
set to `false` and it's only set to `true` in the `production` configuration.
```json ```json
{ {
@ -42,7 +28,13 @@ AOT compilation with Ivy is faster and should be used by default. In the `angula
"build": { "build": {
"options": { "options": {
... ...
"aot": true, "aot": false,
},
"configurations": {
"production": {
...
"aot": true
}
} }
} }
} }
@ -50,6 +42,3 @@ AOT compilation with Ivy is faster and should be used by default. In the `angula
} }
} }
``` ```
To stop using the Ivy compiler, set `enableIvy` to `false` in `tsconfig.app.json`, or remove it completely. Also remove `"aot": true` from your default build options if you didn't have it there before.

2
aio/content/navigation.json
View File

@ -579,7 +579,7 @@
{ {
"url": "guide/ivy", "url": "guide/ivy",
"title": "Angular Ivy", "title": "Angular Ivy",
"tooltip": "Opting into Angular Ivy with Angular CLI." "tooltip": "Opting out of Angular Ivy with Angular CLI."
}, },
{ {
"url": "guide/web-worker", "url": "guide/web-worker",