CodeVetter · Repo Unpack · Feature catalog
typescript-eslint/typescript-eslint
The primary user surface is ESLint configuration and diagnostics, supported by reusable parser and rule-author APIs. Presets distinguish correctness, strictness, style, and type-information requirements. The browser playground adds editable configurations, diagnostic markers, structural inspection, and shareable examples. The following catalog groups features found in inspected files rather than claiming exhaustive coverage of every rule.
- Users can select recommended, strict, and stylistic presets, their type-checked and type-checked-only variants, all, base, eslintRecommended, or disableTypeChecked.
- The deprecated config() helper flattens nested arrays and expands object-based extends; it rejects string extensions, nested extends, and basePath inside extensions.
- The parser exposes parse and parseForESLint alongside createProgram, clearCaches, and helpers for removing project-related parser options.
- Typed linting accepts project-service configuration, supplied Programs, or legacy project resolution; projectService and project together normally produce a configuration error.
- no-floating-promises detects unhandled Promise-like expressions, supports safe-call/type allowances and thenable/IIFE/void options, and offers await or void suggestions under applicable report branches.
- The recommended-type-checked preset enables promise, unsafe-value, assertion, unused-code, and other correctness rules while disabling corresponding core rules where replacements are configured.
- Rule authors receive RuleCreator with default-option merging and documentation URLs, plus a RuleTester that normalizes filenames and runs rules through a flat-config Linter.
- The playground exposes code, ESLint, and TypeScript configuration editing, error displays, ESTree/scope/TypeScript/type views, ESQuery filtering, and a Ctrl/Cmd-S lint-fix action.