Tech debt: Inconsistent tsconfig between Dashboard and UI Extension

[houhoucoop]

Is your feature request related to a problem? Please describe.

The target in the dashboard's tsconfig.json is set to es2018, while in the extension, it is set to esnext. This difference causes successful compilation in the dashboard but errors when the extension consumes its components.

For example: https://github.com/rancher/dashboard/blob/master/shell/models/steve-schema.ts#L50-L53 In the dashboard, useDefineForClassFields: false is the default for es2018, which compile without issues. In the extension, useDefineForClassFields: true is the default for esnext, which causes the error.

Describe the solution you'd like

The target in the dashboard's tsconfig.json should be updated to esnext

Describe alternatives you've considered

N/A

Additional context

https://github.com/harvester/harvester/issues/7007

[aalves08]

@houhoucoop is this issue still relevant? Doing backlog grooming on extensions... How crucial is this?

[houhoucoop]

@aalves08 We already have a workaround in Harvester, so the criticality is low. Just not sure if other extensions are affected as well, though I’d guess not.