Bug: (Stackblitz provided) When keeping standalone=true dependency, get error

[johnwest80]

Description of the bug

Receive error below when .keep(DependencyComponent) is a standalone component.

Error: Unexpected "DependencyComponent" found in the "declarations" array of the "MockOfDependencyModule" NgModule, "DependencyComponent" 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)?

An example of the bug

Here is a stackblitz... toggling standalone on line 18 shows you success and the error above.

https://stackblitz.com/edit/github-qzwn2vfb-hzvpaoj3?file=src%2Ftest.spec.ts

Link:

Expect a way to have a kept component as an import rather than a declaration if it's standalone.

[GipHub123]

@johnwest80
When you change a standalone flag from false to true, the module becomes invalid.
Standalone components should not be added to the declarations section. Use imports instead.

@NgModule({
  imports: [DependencyComponent],
  exports: [DependencyComponent]
})
class DependencyModule {}

https://angular.dev/reference/migrations/standalone

[GipHub123]

@johnwest80 Is this still an issue? If not, could you please close it?

[satanTime]

Hi @GipHub123, could you please stop asking people to close issues?
because closing it doesn't solve it.

If you want to close issues, you can verify them yourself, and fix if needed. Or explain how to do what people ask.

[GipHub123]

@satanTime
I’ve commented on a couple of issues where I’ve been quite sure they are not bugs and don’t require any resolving or fixing.
The number of open issues is constantly increasing, and removing these “not-a-bug” issues helps the community focus on the real ones.

I haven’t asked anyone to close the issues — I asked if they still feel the issue needs resolving. If they feel that issue is not resolved / needs investigation, issue stays open.
So I’m not sure what's the problem here?