Suggestion: Config files authored in JS should automatically have intellisense support

Some libraries (e.g. Babel, Webpack, ESLint) use JS files for their config files.

We don't automatically provide IntelliSense support for these - however, the existing definitions (at least for Babel and Webpack) do provide types that describe the module shape of the files, so they can be manually set up today with a JSDoc comment.

It may be possible to provide a mechanism for associating these config files with their @types packages, and allowing those packages to specify that a given type expresses the module shape of the config file.

Courtesy of @uniqueiniquity

First suggested here: https://developercommunity.visualstudio.com/content/idea/385119/better-webpack-support.html

Überprüfe die im Issue beschriebene manuelle JSDoc-Einrichtung und wie die Babel- und Webpack-Definitionen in @types die Formen von Konfigurationsmodulen ausdrücken. Definiere und implementiere einen Zuordnungsmechanismus für JavaScript-Konfigurationsdateien und verifiziere anschließend, dass sie ohne einen JSDoc-Kommentar IntelliSense erhalten.