TSServer should expose tsconfig

Search Terms

TSServer TSconfig ProjectInfo

Suggestion

export interface ProjectInfo {
  configFileName: string;
  fileNames?: string[];
  languageServiceDisabled?: boolean;
 }

TSServer should also include the project config (the final form of tsconfig.json with all the extends resolved) in the ProjectInfo response

Use Cases

Currently, the editor is expected to send compileOnSaveEmitFile command on each save if compileOnSave flag is set. To figure that out, the editor has to parse the tsconfig.json file and check if the flag is set. The initial version of extend was relatively easy to implement. But now with the support for package name, it's complex to implement correctly.

Why can't you use tsc --showConfig?

Currently we bundle the tsserver.js file along the plugin. So the only dependency is nodejs. This also makes it easier to use it in js projects which don't have typescript dependency. If we depend on tsc, we would also have to bundle tsc file etc.

see https://github.com/ananthakumaran/tide/issues/310

Es werden keine Dateien, Tests oder Einstiegspunkte genannt. Beginne damit, die TSServer ProjectInfo-Antwort und den Pfad zum Laden der Projektkonfiguration nachzuverfolgen, und überprüfe dann, dass die Antwort die endgültige tsconfig mit allen aufgelösten extends offenlegt und den Anwendungsfall compileOnSave unterstützt.