fix: added syntactic and semantic diagnostics

[gcaaa31928]

No description provided.

[qmhc]

What's the motivation for this change?

In buildStart hook, the plugin uses program.getDeclarationDiagnostics() to get all diagnostics info.

[gcaaa31928]

Apologies for the lack of explanation.

If we encounter the incorrect statement export const msg: string = 'hello' as number; in the TypeScript file, it can lead to unexpected results in the generated bundle. For instance, we might observe the declaration in the generated .d.ts file as export declare const msg: string;, which might not align with our intended outcome.

[qmhc]

Emm, I don't understand is that why you need them to use although program.getDeclarationDiagnostics() is run.

Doesn't program.getDeclarationDiagnostics() catch the error if export const msg: string = 'hello' as number; threw?

[gcaaa31928]

Yes, getDeclarationDiagnostics won't catch this error, you can test it on example

[qmhc]

Well, I think you can change const diagnostics = program.getDeclarationDiagnostics() (line 368) to the following instead of current:

const diagnostics = [
  ...program.getDeclarationDiagnostics(),
  ...program.getSemanticDiagnostics(),
  ...program.getSyntacticDiagnostics()
]

[gcaaa31928]

Well, I think you can change const diagnostics = program.getDeclarationDiagnostics() (line 368) to the following instead of current:

const diagnostics = [
  ...program.getDeclarationDiagnostics(),
  ...program.getSemanticDiagnostics(),
  ...program.getSyntacticDiagnostics()
]

Sure! already push and changed it, please review it