Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

docs: removed outdated migration documentation (#46257)

Browse source 
Fixes #46236

PR Close #46257
This commit is contained in:
Phalgun Vaddepalli 2022-06-04 16:50:29 +05:30 committed by Alex Rickabaugh
parent aa2e8acd0e
commit 385b5ec92c
2 changed files with 0 additions and 43 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
.pullapprove.yml
View file

@ -997,7 +997,6 @@ groups:
'aio/content/guide/web-worker.md',
'aio/content/guide/workspace-config.md',
'aio/content/guide/migration-solution-style-tsconfig.md',
'aio/content/guide/migration-update-module-and-target-compiler-options.md',
'aio/content/guide/migration-update-libraries-tslib.md',
])
reviewers:

42
aio/content/guide/migration-update-module-and-target-compiler-options.md
View file

@ -1,42 +0,0 @@
# Update `module` and `target` compiler options migration
## What does this migration do?
This migration adjusts the [`target`](https://www.typescriptlang.org/tsconfig#target) and [`module`](https://www.typescriptlang.org/tsconfig#module) settings within the [TypeScript configuration files](guide/typescript-configuration) for the workspace.
The changes to each option vary based on the builder or command that uses the TypeScript configuration file.
Unless otherwise commented, changes are only made if the existing value was not changed since the project was created.
This process helps ensure that intentional changes to the options are kept in place.
| TypeScript configuration files | Changed property | Existing value | New value |
|:--- |:--- |:--- |:--- |
| `<workspace base>/tsconfig.json` | `"module"` | `"esnext"` | `"es2020"` |
| Used in `browser` builder options \(`ng build` for applications\) | `"module"` | `"esnext"` | `"es2020"` |
| Used in `ng-packagr` builder options \(`ng build` for libraries\) | `"module"` | `"esnext"` | `"es2020"` |
| Used in `karma` builder options \(`ng test` for applications\) | `"module"` | `"esnext"` | `"es2020"` |
| Used in `server` builder options \(universal\) | `"module"` | `"commonjs"` | *removed* |
| Used in `server` builder options \(universal\) | `"target"` | *any* | `"es2016"` |
| Used in `protractor` builder options \(`ng e2e` for applications\) | `"target"` | `"es5"` | `"es2018"` |
## Why is this migration necessary?
This migration provides improvements to the long-term supportability of projects by updating the projects to use recommended best practice compilation options.
For the functionality that executes on Node.js, such as Universal and Protractor, the new settings provide performance and troubleshooting benefits as well.
The minimum Node.js version for the Angular CLI \(v10.13\) supports features in ES2018 and earlier.
By targeting later ES versions, the compiler transforms less code and can use newer features directly.
Since zone.js does not support native `async` and `await`, the universal builds still target ES2016.
## Why `"es2020"` instead of `"esnext"`?
In TypeScript 3.9, the behavior of the TypeScript compiler controlled by `module` is the same with both `"esnext"` and `"es2020"` values.
This behavior can change in the future, because the `"esnext"` option could evolve in a backwards incompatible ways, resulting in build-time or run-time errors during a TypeScript update.
As a result, code can become unstable.
Using the `"es2020"` option mitigates this risk.
<!-- links -->
<!-- external links -->
<!-- end links -->
@reviewed 2022-02-28