[Bug] hint shouldn't warn about forceConsistentCasingInFileNames when TS version is >= 5.0.0

[hamirmahal]

🐞 Bug report

Description

hint shouldn't warn about forceConsistentCasingInFileNames when the TypeScript version is >= 5.0.0.

Details

forceConsistentCasingInFileNames defaults to true for TypeScript versions >= 5.0.0.

[hamirmahal]

--forceConsistentCasingInFileNames, which ensured that all references to the same file name in a project agreed in casing, now defaults to true. This can help catch differences issues with code written on case-insensitive file systems.

[hamirmahal]

Next.js removed forceConsistentCasingInFileNames from their create-next-app template for this reason.

[hamirmahal]

[vidorteg]

Hi @hamirmahal,

Thank you for the report, do you have a minimal repro or example on where are you observing this behavior and also how that differs to your expected output, it would be better if no images are provided as I cannot copy/paste from them. Where are you adding this compilerOptions option?

[hamirmahal]

Hello @vidorteg,

You're welcome. An otherwise empty repository with this tsconfig.json reproduces the error.

{
  "compilerOptions": { <- webhint says `forceConsistentCasingInFileNames` should be `true`
    "strict": true
  }
}

I'm adding the compilerOptions option to tsconfig.json.

webhint gives a

The compiler option "forceConsistentCasingInFileNames" should be enabled to reduce issues when working with different OSes.webhinttypescript-config/consistent-casing

warning, but it doesn't need to. forceConsistentCasingInFileNames defaults to true for TypeScript versions >= 5.0.0.

[vidorteg]

this is extremely helpful, thank you @hamirmahal, will take a look.