Paul Gschwendtner 1e5a818719 fix(ivy): ngtsc is unable to detect flat module entry-point on windows (#29453) ... Currently when building an Angular project with `ngtsc` and `flatModuleOutFile` enabled, the Ngtsc build will fail if there are multiple source files as root file names. Ngtsc and NGC currently determine the entry-point for multiple root file names by looking for files ending with `/index.ts`. This functionality is technically deprecated, but still supported and currently breaks on Windows as the root file names are not guaranteed to be normalized POSIX-like paths. In order to make this logic more reliable in the future, this commit also switches the shim generators and entry-point logic to the branded path types. This ensures that we don't break this in the future. PR Close #29453		2019-03-27 13:46:37 -07:00
..
fake_core	style: enforce buildifier lint on CI (#28186)	2019-02-26 16:57:41 -08:00
BUILD.bazel	build(bazel): back out of @bazel/jasmine 0.27.7 with shard count (#29444)	2019-03-21 09:59:13 -07:00
env.ts	fix(ivy): avoid missing imports for types that can be represented as values (#28941)	2019-02-27 15:13:40 -08:00
ngtsc_spec.ts	fix(ivy): ngtsc is unable to detect flat module entry-point on windows (#29453)	2019-03-27 13:46:37 -07:00
scope_spec.ts	fix(ivy): produce ts.Diagnostics for NgModule scope errors (#29191)	2019-03-08 14:21:48 -08:00
sourcemap_utils.ts	feat(ivy): add source mappings to compiled Angular templates (#28055)	2019-02-12 20:58:28 -08:00
template_mapping_spec.ts	test(ivy): add template source mapping tests (#28055)	2019-02-12 20:58:28 -08:00
template_typecheck_spec.ts	build: remove unused "test.sh" leftover code in compiler-cli (#28352)	2019-02-05 14:31:10 -05:00