Aral Balkan<p>Note: if you want to avoid above-mentioned case sensitivity issues with the rest of your team on Node.js projects if you’re on macOS (the extension quirk appears to be a Node quirk), add this to your jsconfig.json (or TypeScript configuration file if, for some reason, you love having a build process):</p><p>{<br> "compilerOptions": {<br> …<br> "forceConsistentCasingInFileNames": true,<br> …<br> }<br> …<br>}</p><p>More: <a href="https://www.typescriptlang.org/tsconfig/#forceConsistentCasingInFileNames" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">typescriptlang.org/tsconfig/#f</span><span class="invisible">orceConsistentCasingInFileNames</span></a></p><p><a href="https://mastodon.ar.al/tags/NodeJS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NodeJS</span></a> <a href="https://mastodon.ar.al/tags/macOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>macOS</span></a> <a href="https://mastodon.ar.al/tags/caseSensitivity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>caseSensitivity</span></a> <a href="https://mastodon.ar.al/tags/JavaScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>JavaScript</span></a> <a href="https://mastodon.ar.al/tags/TypeScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TypeScript</span></a></p>