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.

まず、allowJs、checkJs、noImplicitAny が有効な場合に JavaScript ファイルを処理する TypeScript compiler API の処理を追跡し、次に、示されている空の Set、Map、WeakMap、array、object のケースを noExplicitAny がどこで報告すべきかを特定します。完了条件は、noExplicitAny が有効なときにこれらの例が lint エラーを生成し、出力される JavaScript を変更しないことです。プロジェクトの既存のテストカバレッジから場所が特定できる場合は、関連する compiler テストを追加または更新してください。