Can't use decorator with @Component

[toxik]

Which @angular/* package(s) are the source of the bug?

Don't known / other

Is this a regression?

Yes

Description

Given

const RunMe = <T extends { new (...args: any[]): {} }>(ctr: T) => class Ran extends ctr {
  constructor(...args: any[]) {
      super(...args);
      debugger;
  }
}

@Component({ .. })
@RunMe
class SomeComponent { }

With the devtools open it should stop inside the Ran constructor.
Angular 16 works, Angular 17 doesn't

Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-bapqxf?file=src%2Fmain.ts

Please provide the exception or error you saw

No response

Please provide the environment you discovered this bug in (run ng version)

Angular CLI: 17.0.3
Node: 18.18.0
Package Manager: npm 9.8.1
OS: darwin arm64

Angular: 17.0.4
... animations, common, compiler, compiler-cli, core, forms
... localize, platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1700.3
@angular-devkit/build-angular   17.0.3
@angular-devkit/core            17.0.3
@angular-devkit/schematics      17.0.3
@angular/cli                    17.0.3
@schematics/angular             17.0.3
ng-packagr                      17.0.2
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.2

Anything else?

No response

[JoostK]

This is because of the change to the es2022 target, which enables native support for static blocks. Angular's factory function refers to SomeComponent from this static block, which is not the decorated SomeComponent but the original class.

This is only the behavior under experimentalDecorators: true. ECMAScript decorators do refer to the decorated type from within a static block.

Note that using decorators on Angular classes is not supported.

Duplicate of #45477.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}