bug(material): imports "could not be determined statically" error with MatListModule, MatMenuModule, MatButton in standalone components

[BeckThomas2202]

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

21.2.5

Description

Description

Since upgrading to @angular/material@21.2.7, standalone components using Angular Material
imports produce the following compiler error:

'imports' must be an array of components, directives, pipes or NgModules.
Value could not be determined statically.

Affected imports that I tried

• MatListModule from @angular/material/list
• MatMenuModule from @angular/material/menu
• MatButton from @angular/material/button
• MatSlideToggle from @angular/material/slide-toggle

Workaround

Downgrading to @angular/material@21.2.5 resolves the issue.

Reproduction

import { MatSlideToggle } from '@angular/material/slide-toggle';

@Component({
  selector: 'my-component',
  imports: [ MatSlideToggle  ],
  templateUrl: './my-component.html',
})
export class MyComponent {}

Expected Behavior

No error. This worked correctly on 21.2.5.

Actual Behavior

Angular Language server error :
'imports' must be an array of components, directives, pipes or NgModules. Value could not be determined statically.

Environment

Environment

Package	Version
@angular/material	21.2.7
@angular/core	21.2.0
@angular/cli	21.2.5
Node	22.13.1

[ok7sai]

I was unable the reproduce the issue. Here's a demo with version 21.2.7 https://stackblitz.com/edit/stackblitz-starters-gcvi65od?file=src%2Fmain.ts
Would be nice if you can provide a reproducible demo.