Performance: forcefully disable some compiler flags #11241
Description
Before You File a Proposal Please Confirm You Have Done The Following...
- I have searched for related issues and found none that match my proposal.
- I have searched the current rule list and found no rules that match my proposal.
- I have read the FAQ and my problem is not listed.
Relevant Package
tsconfig-utils
My proposal is suitable for this project
- I believe my proposal would be useful to the broader TypeScript community (meaning it is not a niche proposal).
Description
We already have a default set of core compiler options here:
typescript-eslint/packages/tsconfig-utils/src/compilerOptions.ts
Lines 6 to 13 in 4ad8a07
afaict, these override the user's project compiler options.
while doing some reading through a CPU profile of a lint run, i noticed a significant amount of time is spent ensuring file names are correct when forceConsistentCasingInFileNames: true.
in the repo I was using, hacking this into CORE_COMPILER_OPTIONS as false made the test run speed up from 1m20s to 1m. i ran it a few times, and the times did vary but always had a significant improvement.
so suggestion number 1: force forceConsistentCasingInFileNames: false since we don't really care when linting.
suggestion/idea number 2: maybe this isn't the only setting? maybe there are others doing unnecessary checks we don't really care for in lint runs (typescript's own lint/strict checking, etc)
Additional Info
No response