angular/packages/compiler-cli/private
Paul Gschwendtner b2066d4922 refactor(compiler-cli): detect input functions without partial evaluation (#53872)
This allows us to ensure signal inputs and a potential JIT transform
remain single file compilation compatible. The consequences are that
options need to be statically analyzable more strictly, compared to
loosened restrictions with static interpretation where e.g. `alias`
can be defined through a shared variable.

PR Close #53872
2024-01-10 12:33:31 -08: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): add transform to support signal input in JIT (#53808) 2024-01-10 12:21:05 +00:00
localize.ts refactor: switch packages away from deep cross-package imports (#43431) 2021-10-01 18:28:43 +00:00
migrations.ts refactor(compiler): rework and expose APIs to be used in schematics (#48730) 2023-01-13 12:24:32 -08: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): detect input functions without partial evaluation (#53872) 2024-01-10 12:33:31 -08: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.