angular-cn/packages/compiler-cli
Pete Bacon Darwin 4e1b5e43fa fix(compiler-cli): compute the correct target output for `$localize` messages (#36989)
In some versions of TypeScript, the transformation of synthetic
`$localize` tagged template literals is broken.
See https://github.com/microsoft/TypeScript/issues/38485

We now compute what the expected final output target of the
compilation will be so that we can generate ES5 compliant
`$localize` calls instead of relying upon TS to do the downleveling
for us.

This is a workaround for the TS compiler bug, which could be removed
when this is fixed. But since it only affects ES5 targeted compilations,
which is now not the norm, it has limited impact on the majority of
Angular projects. So this fix can probably be left in indefinitely.

PR Close #36989
2020-05-14 10:50:30 -07:00
..
integrationtest feat: remove @angular/http (#27038) 2020-05-05 17:42:01 -07:00
ngcc fix(ngcc): support `defineProperty()` re-exports in CommonJS and UMD (#36989) 2020-05-14 10:50:29 -07:00
src fix(compiler-cli): compute the correct target output for `$localize` messages (#36989) 2020-05-14 10:50:30 -07:00
test fix(compiler-cli): compute the correct target output for `$localize` messages (#36989) 2020-05-14 10:50:30 -07:00
BUILD.bazel perf(compiler-cli): split Ivy template type-checking into multiple files (#36211) 2020-05-05 18:40:42 -07:00
index.ts refactor(compiler-cli): Move diagnostics files to language service (#33809) 2019-11-14 09:29:07 -08:00
package.json build: prepare for TypeScript 3.9 (#36989) 2020-05-14 10:50:28 -07:00
tsconfig-build.json build: reference zone.js from source directly instead of npm. (#33046) 2019-11-06 00:48:34 +00:00
tsconfig.json perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525) 2019-07-09 09:40:46 -07:00