George Kalpakas 1a34fbce25 fix(ngcc): rename the executable from ivy-ngcc to ngcc (#33140) ... Previously, the executable for the Angular Compatibility Compiler (`ngcc`) was called `ivy-ngcc`. This would be confusing for users not familiar with our internal terminology, especially given that we call it `ngcc` in all our docs and presentations. This commit renames the executable to `ngcc` and replaces `ivy-ngcc` with a script that errors with an informative message (prompting the user to use `ngcc` instead). Jira issue: [FW-1624](https://angular-team.atlassian.net/browse/FW-1624) PR Close #33140		2019-10-14 16:29:14 +00:00
..
integrationtest	build: update to nodejs rules 0.37.1 (#32151)	2019-09-25 11:29:12 -07:00
ngcc	fix(ngcc): rename the executable from ivy-ngcc to ngcc (#33140)	2019-10-14 16:29:14 +00:00
src	refactor(core): rename ngDirectiveDef to ɵdir (#33110)	2019-10-14 16:20:11 +00:00
test	refactor(core): rename ngDirectiveDef to ɵdir (#33110)	2019-10-14 16:20:11 +00:00
BUILD.bazel	build: fix build failures with worker mode cache and @types/events (#31325)	2019-07-01 14:16:43 -07:00
index.ts	refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921)	2019-06-25 16:25:24 -07:00
ngtools2.ts	refactor(compiler-cli): expose ngtools api separately (#18978)	2017-08-31 14:37:13 -07:00
package.json	fix(ngcc): rename the executable from ivy-ngcc to ngcc (#33140)	2019-10-14 16:29:14 +00:00
tsconfig-build.json	perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525)	2019-07-09 09:40:46 -07:00
tsconfig.json	perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525)	2019-07-09 09:40:46 -07:00