angular-cn/packages/core/schematics/migrations
Alex Rickabaugh 95c729f5d1 build: typescript 3.8 support (#35864)
This commit adds support in the Angular monorepo and in the Angular
compiler(s) for TypeScript 3.8. All packages can now compile with
TS 3.8.

For most of the repo, only a handful few typings adjustments were needed:

* TS 3.8 has a new `CustomElementConstructor` DOM type, which enforces a
  zero-argument constructor. The `NgElementConstructor` type previously
  declared a required `injector` argument despite the fact that its
  implementation allowed `injector` to be optional. The interface type was
  updated to reflect the optionality of the argument.
* Certain error messages were changed, and expectations in tests were
  updated as a result.
* tsserver (part of language server) now returns performance information in
  responses, so test expectations were changed to only assert on the actual
  body content of responses.

For compiler-cli and schematics (which use the TypeScript AST) a major
breaking change was the introduction of the export form:

```typescript
export * as foo from 'bar';
```

This is a `ts.NamespaceExport`, and the `exportClause` of a
`ts.ExportDeclaration` can now take this type as well as `ts.NamedExports`.
This broke a lot of places where `exportClause` was assumed to be
`ts.NamedExports`.

For the most part these breakages were in cases where it is not necessary
to handle the new `ts.NamedExports` anyway. ngtsc's design uses the
`ts.TypeChecker` APIs to understand syntax and so automatically supports the
new form of exports.

The View Engine compiler on the other hand extracts TS structures into
metadata.json files, and that format was not designed for namespaced
exports. As a result it will take a nontrivial amount of work if we want to
support such exports in View Engine. For now, these new exports are not
accounted for in metadata.json, and so using them in "folded" Angular
expressions will result in errors (probably claiming that the referenced
exported namespace doesn't exist).

Care was taken to only use TS APIs which are present in 3.7/3.6, as Angular
needs to remain compatible with these for the time being.

This commit does not update angular.io.

PR Close #35864
2020-03-10 17:51:20 -04:00
..
dynamic-queries refactor(core): update migrations descriptions (#33440) 2019-10-28 17:07:50 -07:00
google3 refactor(core): missing-injectable migration should respect providers of directives and components (#33011) 2019-10-14 20:24:01 +00:00
missing-injectable perf(ivy): reuse prior analysis work during incremental builds (#34288) 2019-12-12 13:11:45 -08:00
module-with-providers perf(ivy): reuse prior analysis work during incremental builds (#34288) 2019-12-12 13:11:45 -08:00
move-document refactor(core): add `createMigrationCompilerHost` (#32827) 2019-10-04 11:45:35 -07:00
renderer-to-renderer2 fix(core): renderer-to-renderer2 migration not migrating methods (#33571) 2019-11-05 22:05:17 +00:00
static-queries refactor(core): update migrations descriptions (#33440) 2019-10-28 17:07:50 -07:00
template-var-assignment refactor(core): update migrations descriptions (#33440) 2019-10-28 17:07:50 -07:00
undecorated-classes-with-decorated-fields refactor(core): update migrations descriptions (#33440) 2019-10-28 17:07:50 -07:00
undecorated-classes-with-di build: typescript 3.8 support (#35864) 2020-03-10 17:51:20 -04:00