ESLint quiz

Test your ESLint knowledge with a free interactive quiz — 30 questions with answers and explanations. No signup needed to play.

What makes a rule "type-aware" in @typescript-eslint, as opposed to a plain syntax rule?

1. What makes a rule "type-aware" in @typescript-eslint, as opposed to a plain syntax rule?
2. What is the recommended division of responsibility between ESLint and Prettier?
3. What is the narrowest way to suppress a single ESLint violation on one specific line?
4. A team wants fast linting on every keystroke in the editor but still wants type-aware checks. What is a common approach?
5. What is the effect of `/* eslint-disable no-console */` followed later by `/* eslint-enable no-console */`?
6. Given `'no-unused-vars': ['error', { argsIgnorePattern: '^_' }]`, what does the second array element configure?
7. What is the risk of hand-picking every single rule from zero instead of starting from a shareable recommended config?
8. What should a new project starting today generally use?
9. What must `languageOptions.parserOptions.project` be set to for type-aware TypeScript rules to work?
10. Why does linting `.ts`/`.tsx` files require a different parser than ESLint's default?
11. What does a "shareable config" like `js.configs.recommended` provide?
12. Why is it good practice to leave a reason alongside an inline `eslint-disable` comment (e.g. "-- legacy SDK has no types")?

More quizzes