Enable `noExplicitAny` in `./tsconfig.json`.

⭐ Suggestion & 📃 Motivating Example & 💻 Use Cases

The following .js code, in project with a ./tsconfig.json that has allowJs:true, checkJs:true,noImplicitAny:true, does not lint error:

const mySet = new Set;
const myMap = new Map;
const myWeakMap = new WeakMap;
const myArray = [];
const myObj = {};

It would be nice to lint error for those cases when noExplicitAny:true is used.

🔍 Search Terms

• noExplicitAny
• TypeScript compiler API
• ./tsconfig.json
• allowJs
• checkJs

✅ Viability Checklist

My suggestion meets these guidelines:

• 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 feature would agree with the rest of TypeScript's Design Goals.

Empieza siguiendo el manejo de la TypeScript compiler API para los archivos JavaScript cuando allowJs, checkJs y noImplicitAny están habilitados, y determina después dónde debería informar noExplicitAny de los casos mostrados de Set, Map, WeakMap, array y objeto vacíos. Se considera terminado cuando esos ejemplos producen errores de lint al habilitar noExplicitAny sin cambiar el JavaScript emitido; añade o actualiza las pruebas relevantes del compilador si la cobertura de pruebas existente del proyecto identifica un lugar adecuado.