You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which @angular/* package(s) are the source of the bug?
forms
Is this a regression?
No
Description
The migration available in v13.2.0-next.1 fails to pick up forms in lazy-loaded modules in a CLI app.
The repo provided as reproduction is a simple CLI app, with a lazy-loaded module containing a component with a FormControl (added in the second commit).
steps:
git clone https://github.com/cexbrayat/typed-forms.git
npm i
ng update @angular/core --migrate-only migration-v14-typed-forms
Please provide a link to a minimal reproduction of the bug
❯ ng update @angular/core --migrate-only migration-v14-typed-forms
The installed Angular CLI version is outdated.
Installing a temporary Angular CLI versioned 13.1.2 to perform the update.
✔ Package successfully installed.
Using package manager: 'npm'
Collecting installed dependencies...
Found 23 dependencies.
** Executing 'migration-v14-typed-forms' of package '@angular/core' **
❯ Experimental migration that adds <any>s for Typed Forms.
Migration completed.
Please provide the environment you discovered this bug in (run ng version)
This happened in every application I tried to run the migration. I think it even sometimes doesn't find components in modules, but I struggled to reproduce in a bare application.
The text was updated successfully, but these errors were encountered:
Thank you for this great reproduction @cexbrayat, we really appreciate it! This only affected external migrations (not google3 migrations), so we might not have caught it in time. This will be fixed in #44881.
Which @angular/* package(s) are the source of the bug?
forms
Is this a regression?
No
Description
The migration available in v13.2.0-next.1 fails to pick up forms in lazy-loaded modules in a CLI app.
The repo provided as reproduction is a simple CLI app, with a lazy-loaded module containing a component with a FormControl (added in the second commit).
steps:
Please provide a link to a minimal reproduction of the bug
https://github.com/cexbrayat/typed-forms
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
This happened in every application I tried to run the migration. I think it even sometimes doesn't find components in modules, but I struggled to reproduce in a bare application.
The text was updated successfully, but these errors were encountered: