Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Description
Before You File a Proposal Please Confirm You Have Done The Following...
- I havesearched for related issues and found none that match my proposal.
- I have searched thecurrent rule list and found no rules that match my proposal.
- I haveread 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:
| exportconstCORE_COMPILER_OPTIONS={ | |
| // Required to avoid parse from causing emit to occur | |
| noEmit:true, | |
| // Flags required to make no-unused-vars work | |
| noUnusedLocals:true, | |
| noUnusedParameters:true, | |
| }satisfiests.CompilerOptions; |
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 whenforceConsistentCasingInFileNames: true.
in the repo I was using, hacking this intoCORE_COMPILER_OPTIONS asfalse made the test runspeed up from 1m20s to 1m. i ran it a few times, and the times did vary but always had a significant improvement.
sosuggestion number 1: forceforceConsistentCasingInFileNames: 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