TypeScript as a peerDependency

Are there any reasons this package has so old TypeScript peerDependency? It breaks the build:

 ERROR  @typescript-eslint/eslint-plugin > @typescript-eslint/experimental-utils > @typescript-eslint/typescript-estree: tsutils@3.21.0 requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none was installed.

[silverwind]

I too came here through a eslint plugin which through a chain of dependencies and with npm v7 now installing peerDependencies, ends up bloating my node_modules with an unused typescript compiler:

eslint-plugin-jest@24.3.6
┬ @typescript-eslint/experimental-utils@4.24.0
└─┬ @typescript-eslint/typescript-estree@4.24.0
  └─┬ tsutils@3.21.0
    └── typescript@4.2.4

[darekkay]

If you don’t have TypeScript installed, why would you install this package? Its sole purpose is to simplify using the TypeScript API.

@ajafff One use case: having an eslint-config package that supports different environments conditionally, like JavaScript projects (no TS required) and TypeScript projects at the same time (example). This currently leads to a warning because of tsutils being included in packages like @typescript-eslint/eslint-plugin:

warning "@typescript-eslint/eslint-plugin > tsutils@3.21.0" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >=
3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".

People keep having this issue because of tsutils, unfortunately:

• https://github.com/typescript-eslint/typescript-eslint/issues/1287
• https://github.com/jest-community/eslint-plugin-jest/issues/467

This is what peerDependenciesMeta was created for:

This allows you to integrate and interact with a variety of host packages without requiring all of them to be installed.

This would be the required change in package.json:

  "peerDependenciesMeta": {
    "typescript": {
      "optional": true
    }
  }

Are you open to such a change?