Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
Yes
Description
I have a large Angular project split into libraries using NX.
When I use this migration script specifying:
when I specify the path of the directory I want to migrate, it works as expected.
However, when I use other migration scripts such as:
even though I try to use it by passing a specific directory path, it starts scanning the entire project and at some points it runs out of memory.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
The problem is that it tries to scan the entire project even when it's not needed because a path is specified.
Please note that this only affects SOME migration scripts (e.g. self-closing tag) while other (e.g. control-flow migration) do not have this issue.
Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 19.2.5
Node: 22.14.0
Package Manager: npm 10.9.2
OS: darwin arm64
Angular: 19.2.4
... animations, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, router
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1902.5
@angular-devkit/build-angular 19.2.5
@angular-devkit/core 19.2.5
@angular-devkit/schematics 19.2.5
@angular/cdk 19.2.7
@angular/cli 19.2.5
@schematics/angular 19.2.5
ng-packagr 19.2.0
rxjs 7.8.2
typescript 5.8.2
zone.js 0.15.0
Anything else?
No response
Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
Yes
Description
I have a large Angular project split into libraries using NX.
When I use this migration script specifying:
when I specify the path of the directory I want to migrate, it works as expected.
However, when I use other migration scripts such as:
even though I try to use it by passing a specific directory path, it starts scanning the entire project and at some points it runs out of memory.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version)Anything else?
No response