Consider adding languageServiceOptions to TSConfig

[mrazauskas]

🔍 Search Terms

"language", "service", "options", "tsconfig"

✅ Viability Checklist

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

This is just a design issue. Without reading the documentation it isn’t clear that compilerOptions.plugins are actually "language service plugins". The compiler does not load the plugins, hence it might make sense separating them to languageServiceOptions (similar to watchOptions).

This issue could be considered as a candidate for #54500

📃 Motivating Example

languageServiceOptions.plugins makes it clear that these plugins will not be loaded during compile time.

💻 Use Cases

Each time when the plugins option is used.