Using a mix of lowercase and uppercase causes pain on case-insensitive file systems like APFS by default on macOS.

Changing file case in Git commits is a bit weird already. My preference is to keep with existing conventions instead of injecting my own but if you’re starting a new project skip the (lower) camel case.

In the last week, I imported a TypeScript file with a different case than what was on disk by mistake. Some tools accepted it. The import-x/extensions ESLint rule failed because of the case mismatch. The error message there did not suggest anything about letter case.