Should This Config Include TypeScript Rules?

This config includes TypeScript rules, but we use the config in every project, even those that don't use TypeScript. This sometimes causes problems, like rules intended for TS being applied to vanilla JS for the browser. Is there a better way to handle this? Can we scope the TS rules to files with TS extensions? What about Vue components with ``?

If it's not possible to scope based on TS usage, should we consider dropping the TS rules? We don't always use TS in new projects, and many of our older projects will never switch. Maybe this config should split into two? The outcome of this issue should be to thoroughly investigate our options and make a recommendation about if and how to change this config.

Start by inspecting the shared ESLint config and the TypeScript rules it currently enables. Reproduce the behavior in vanilla JavaScript, TypeScript, and Vue components with , then compare the available scoping or split-config options. Done means documenting the trade-offs and making a clear recommendation about whether and how to change the config.

Written by the indexing model from the issue text.