-
Notifications
You must be signed in to change notification settings - Fork 27.1k
ng g @angular/core:standalone does not migrate spec files #48944
Copy link
Copy link
Closed
Labels
P1Impacts a large percentage of users; if a workaround exists it is partial or overly painfulImpacts a large percentage of users; if a workaround exists it is partial or overly painfularea: migrationsIssues related to `ng update`/`ng generate` migrationsIssues related to `ng update`/`ng generate` migrationsbugcross-cutting: standaloneIssues related to the NgModule-less worldIssues related to the NgModule-less worldstate: has PR
Milestone
Description
Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
No
Description
ng new standalone-migration --defaults
cd standalone-migration
ng update @angular/core@next @angular/cli@next --force
ng g c hello
ng g @angular/core:standalone --defaults --mode standalone-bootstrap
neither app.component.spec.ts nor hello.component.spec.ts is migrated, so ng test fails.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Unexpected "AppComponent" found in the "declarations" array of the "TestBed.configureTestingModule" call, "AppComponent" is marked as standalone and can't be declared in any NgModule - did you intend to import it instead (by adding it to the "imports" array)?
Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 15.2.0-next.3
Node: 16.17.0
Package Manager: npm 8.19.3
OS: darwin arm64
Angular: 15.2.0-next.3
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1502.0-next.3
@angular-devkit/build-angular 15.2.0-next.3
@angular-devkit/core 15.2.0-next.3
@angular-devkit/schematics 15.2.0-next.3
@schematics/angular 15.2.0-next.3
rxjs 7.8.0
typescript 4.9.5
Anything else?
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P1Impacts a large percentage of users; if a workaround exists it is partial or overly painfulImpacts a large percentage of users; if a workaround exists it is partial or overly painfularea: migrationsIssues related to `ng update`/`ng generate` migrationsIssues related to `ng update`/`ng generate` migrationsbugcross-cutting: standaloneIssues related to the NgModule-less worldIssues related to the NgModule-less worldstate: has PR