angular

History

Alex Rickabaugh 345bdd3db0 fix(ivy): generate empty ngfactory files if needed (#27470 )

Previously the ngfactory shim generator in ngtsc would always write two
imports in the factory file shims:

1) an import to @angular/core
2) an import to the base file

If the base file has no exports, import #2 would be empty. This turns out
to cause issues downstream.

This commit changes the generated shim so if there are no exports in the
base file, the generated shim is empty too.

PR Close #27470

2018-12-05 10:46:51 -08:00

src

fix(ivy): generate empty ngfactory files if needed (#27470 )

2018-12-05 10:46:51 -08:00

BUILD.bazel

Revert "fix(ivy): correct ngtsc path handling in Windows (#26703 )"

2018-11-05 11:18:52 -08:00

index.ts

feat(ivy): generate .ngsummary.js shims (#26495 )

2018-10-19 13:30:02 -07:00

README.md

refactor(ivy): rename ngtsc/factories to ngtsc/shims (#26495 )

2018-10-19 13:30:01 -07:00

README.md

Deals with the creation of generated factory files.

Generated factory files create a catch-22 in ngtsc. Their contents depends on static analysis of the current program, yet they're also importable from the current program. This importability gives rise to the requirement that the contents of the generated file must be known before program creation, so that imports of it are valid. However, until the program is created, the analysis to determine the contents of the generated file cannot take place.

ngc used to get away with this because the analysis phase did not depend on program creation but on the metadata collection / global analysis process.

ngtsc is forced to take a different approach. A lightweight analysis pipeline which does not rely on the ts.TypeChecker (and thus can run before the program is created) is used to estimate the contents of a generated file, in a way that allows the program to be created. A transformer then operates on this estimated file during emit and replaces the estimated contents with accurate information.

It is important that this estimate be an overestimate, as type-checking will always be run against the estimated file, and must succeed in every case where it would have succeeded with accurate info.

This directory contains the utilities for generating, updating, and incorporating these factory files into a ts.Program.