Andrew Kushnir aaf8145c48 fix(ivy): support module.id as @NgModule's "id" field value (#30040) ... Prior to this commit, the check that verifies correct "id" field type was too strict and didn't allow `module.id` as @NgModule's "id" field value. This change adds a special handling for `module.id` and uses it as id of @NgModule if specified. PR Close #30040		2019-04-23 14:50:58 -07:00
..
integrationtest	fix(bazel): use //:tsconfig.json as the default for ng_module (#29670)	2019-04-02 15:57:11 -07:00
ngcc	fix(ivy): ngcc - insert new imports after existing ones (#30029)	2019-04-22 16:29:30 -07:00
src	fix(ivy): support module.id as @NgModule's "id" field value (#30040)	2019-04-23 14:50:58 -07:00
test	fix(ivy): support module.id as @NgModule's "id" field value (#30040)	2019-04-23 14:50:58 -07:00
BUILD.bazel	refactor(ivy): move metadata registration to its own package (#29698)	2019-04-19 11:15:25 -07:00
index.ts	feat(compiler-cli): export tooling definitions (#29929)	2019-04-17 17:23:01 -07:00
ngtools2.ts	refactor(compiler-cli): expose ngtools api separately (#18978)	2017-08-31 14:37:13 -07:00
package.json	build: update to TypeScript 3.4 (#29372)	2019-04-10 12:12:16 -07:00
tsconfig-build.json	build(compiler-cli): enable full TypeScript strictness (#29436)	2019-03-21 12:14:39 -04:00
tsconfig.json	build(compiler-cli): enable full TypeScript strictness (#29436)	2019-03-21 12:14:39 -04:00