Feature: Relative tsconfig.json Projects

In typescript-eslint v5, in order to enable typed linting, your ESLint configuration must include a parserOptions.project property indicating which TSConfig(s) to use:

module.exports = {
  // ...
  parserOptions: {
    project: ['./tsconfig.json'],
  },
  // ...
};

This works well for repositories that have a single TSConfig for all files, such as small repositories using a single tsconfig.json or larger monorepos that have a tsconfig.eslint.json specifically used for linting.
But what if your project uses different TSConfig options for different TypeScript files in nested subdirectories?
Specifying the right array of relative TSConfig paths to try for each file in order can be cumbersome or downright impossible.

We recently added the option to specify parserOptions.project as just true in ESLint configurations.
This indicates to typescript-eslint that each file should be linted with the closest tsconfig.json file on disk.

module.exports = {
  // ...
  parserOptions: {
    project: true,
  },
  // ...
};

We hope using project = true simplifies configurations for repositories with nontrivial ESLint configuration setups.
We intend to add additional options around automatic TSConfig lookups to allow additional file names or other convenient behaviors.