Paul Gschwendtner 4f52678560 refactor(migrations): avoid flow node traversal limit by optimizing traversal (#57719) ... Instead of traversing the same paths multiple times, we should avoid this extra work and optimize. This solves some issues in super large files with extremely complex flow graphs. E.g. large `ngOnChanges` functions in Pantheon. For an example of a flow graph where it doesn't make sense to re-visit nodes that have multiple incoming edges, see this internal screenshot: https://screenshot.googleplex.com/6ub4e5e5gbzJAvH PR Close #57719		2024-09-08 17:11:51 +00:00
..
migrations	refactor(migrations): avoid flow node traversal limit by optimizing traversal (#57719)	2024-09-08 17:11:51 +00:00
ng-generate	fix(migrations): replace leftover modules with their exports during pruning (#57684)	2024-09-06 14:15:50 +00:00
test	feat(core): Add a schematics to migrate to standalone: false. (#57643)	2024-09-06 15:08:51 +00:00
utils	refactor(migrations): ensure project paths respect root directories (#57677)	2024-09-06 19:44:07 +00:00
BUILD.bazel	feat(core): Add a schematics to migrate to standalone: false. (#57643)	2024-09-06 15:08:51 +00:00
collection.json	refactor(migrations): switch from esbuild to Rollup for schematics bundling (#57602)	2024-09-03 09:07:03 -07:00
migrations.json	feat(core): Add a schematics to migrate to standalone: false. (#57643)	2024-09-06 15:08:51 +00:00
package.json	refactor(migrations): ensure CommonJS migrations can be accessed (#43657)	2021-10-04 16:24:48 -07:00
rollup.config.js	refactor(migrations): switch from esbuild to Rollup for schematics bundling (#57602)	2024-09-03 09:07:03 -07:00
tsconfig.json	refactor(migrations): avoid relative imports in schematic code (#57214)	2024-08-29 07:50:41 -07:00