angular/packages/core/schematics
Kristiyan Kostadinov 9895e4492f fix(migrations): replace leftover modules with their exports during pruning (#57684)
Currently during the module pruning stage of the standalone migration we assume that any leftover modules which only have `imports` and `exports` can safely be removed. That can be incorrect for the cases where some parts of the app were converted to standalone outside of the migration.

These changes update the logic so that such modules are replaced with the `exports` which are used within the specific component.

Fixes #51420.

PR Close #57684
2024-09-06 14:15:50 +00:00
..
migrations refactor(migrations): ensure control flow analysis of signal input migration works with all TS versions (#57566) 2024-08-29 07:51:39 -07:00
ng-generate fix(migrations): replace leftover modules with their exports during pruning (#57684) 2024-09-06 14:15:50 +00:00
test fix(migrations): replace leftover modules with their exports during pruning (#57684) 2024-09-06 14:15:50 +00:00
utils refactor(migrations): allow tsurge migrations to run with just NgCompiler (#57562) 2024-08-28 08:47:46 -07:00
BUILD.bazel feat(migrations): add migration to convert standalone component routes to be lazy loaded (#56428) 2024-07-30 20:00:37 +00:00
collection.json feat(migrations): add migration to convert standalone component routes to be lazy loaded (#56428) 2024-07-30 20:00:37 +00:00
migrations.json feat(core): Add a schematic to migrate afterRender phase flag (#55648) 2024-06-10 13:53:39 -07:00
package.json refactor(migrations): ensure CommonJS migrations can be accessed (#43657) 2021-10-04 16:24:48 -07:00
tsconfig.json build: align schematics tsconfig with rest of the project (#51969) 2023-10-04 07:28:41 -07:00