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.

Start by tracing the TypeScript compiler API handling for JavaScript files when allowJs, checkJs, and noImplicitAny are enabled, then determine where noExplicitAny should report the shown empty Set, Map, WeakMap, array, and object cases. Done means those examples produce lint errors when noExplicitAny is enabled without changing emitted JavaScript; add or update relevant compiler tests if the project’s existing test coverage identifies a location.