Paul Gschwendtner fe2a8de1b5 refactor(compiler-cli): expose tooling code through private entry-point (#43431) ... Similar to the other private entry-points we have added for localize, bazel or the migrations, we should expose the tooling code through a dedicated private export. This will make the compiler-cli exports more consistent and it will become easier for the CLI to export necessary code. PR Close #43431		2021-10-01 18:28:46 +00:00
..
integrationtest	test(compiler-cli): fix integration test failing on windows due to missing runfile symlinking (#43431)	2021-10-01 18:28:46 +00:00
linker	refactor(compiler-cli): no longer use deep imports into @angular/compiler (#43431)	2021-10-01 18:28:46 +00:00
ngcc	refactor(compiler-cli): fix ngcc cluster workers incorrectly being marked as busy with ESM (#43431)	2021-10-01 18:28:46 +00:00
private	refactor(compiler-cli): expose tooling code through private entry-point (#43431)	2021-10-01 18:28:46 +00:00
src	refactor(compiler-cli): expose tooling code through private entry-point (#43431)	2021-10-01 18:28:46 +00:00
test	refactor(compiler-cli): expose tooling code through private entry-point (#43431)	2021-10-01 18:28:46 +00:00
BUILD.bazel	refactor(compiler-cli): expose tooling code through private entry-point (#43431)	2021-10-01 18:28:46 +00:00
esbuild.config.js	refactor: setup bundling for @angular/compiler-cli package (#43431)	2021-10-01 18:28:42 +00:00
import_meta_url.d.ts	refactor(compiler-cli): do not use __filename or __dirname global for ESM compatibility (#43431)	2021-10-01 18:28:45 +00:00
index.ts	refactor(compiler-cli): expose tooling code through private entry-point (#43431)	2021-10-01 18:28:46 +00:00
package.json	refactor(compiler-cli): expose tooling code through private entry-point (#43431)	2021-10-01 18:28:46 +00:00
tsconfig-build.json	build: update tsconfigs to use ES2020 as target and module (#43431)	2021-10-01 18:28:42 +00:00
tsconfig.json	build: update tsconfigs to use ES2020 as target and module (#43431)	2021-10-01 18:28:42 +00:00