angular/packages/compiler-cli/private
Paul Gschwendtner 7f550ea0c8 refactor(compiler-cli): move JIT transforms into ngtsc (#56892)
This commit moves the JIT transforms into the ngtsc folder. They existed
outside of ngtsc mostly as an historic artifact— and now with compiler
relying on them even more deeply, it makes sense to move them into
`ngtsc/transform`.

PR Close #56892
2024-07-10 17:29:20 +02:00
..
babel.d.ts build: remove unneeded babel types postinstall patching (#53441) 2023-12-08 14:33:59 -08:00
bazel.ts refactor: switch packages away from deep cross-package imports (#43431) 2021-10-01 18:28:43 +00:00
BUILD.bazel refactor(compiler-cli): move JIT transforms into ngtsc (#56892) 2024-07-10 17:29:20 +02:00
localize.ts refactor: switch packages away from deep cross-package imports (#43431) 2021-10-01 18:28:43 +00:00
migrations.ts refactor: migrate compiler-cli to prettier formatting (#55485) 2024-04-29 10:25:43 -07:00
README.md refactor: switch packages away from deep cross-package imports (#43431) 2021-10-01 18:28:43 +00:00
tooling.ts refactor(compiler-cli): move JIT transforms into ngtsc (#56892) 2024-07-10 17:29:20 +02:00

This is a directory defining the @angular/compiler-cli/private entry-point. The entry-point can be used to expose code that is needed by other Angular framework packages, without having to expose code through the primary entry-point.

The primary entry-point has a couple of downsides when it comes to cross-package imports:

  • It exports various other things that will end up creating additional type dependencies. e.g. when the Angular localize package relies on it, it might end up accidentally relying on @types/node.
  • The primary entry-point has a larger build graph, slowing down local development as much more things can invalidate the dependent targets. A smaller subset leads to faster incremental builds.