Support for custom Automatic Type Acquisition scopes.

Search Terms

Automatic type acquisition scopes, custom type acquisition, acquire types from custom scope

Suggestion

The ability to specify in .tsconfig and/or IDE settings additional scopes to search beyond @types for type acquisition.

Use Cases

Private repositories with large amounts of JavaScript code and a small number of TypeScript developers who wish to produce accurate typings, and a high barrier to entry to modifying/adding declaration files to the JavaScript projects. This mirrors the public ecosystem with say, react and @types/react.

Examples

A new string array parameter of scopes to search for:

{
  "typeAcquisition": {
    "searchScopes": [
      "@companyname-types",
      "@types"
    ]
  }
}

This would also allow overriding the @types scope. The first scope with a matching declaration should win.

Checklist

My suggestion meets these guidelines:
[X] This wouldn't be a breaking change in existing TypeScript / JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. new expression-level syntax)

Inizia individuando l'implementazione dell'acquisizione automatica dei tipi e la gestione di typeAcquisition in tsconfig, quindi traccia il modo in cui vengono attualmente risolti gli scope dei pacchetti di dichiarazioni. Definisci il comportamento di configurazione per searchScopes, incluso l'ordine e le sovrascritture di @types, e aggiungi una copertura che dimostri che viene selezionato il primo scope di dichiarazione corrispondente.