Ufdjrw

I'm finding that we have dev's on windows that are checking in code that works even though it has file name casing errors like:

import speakers.js

instead of

import Speakers.js

Which is correct. On windows, it works, Mac it does not. What's the best way to insure that windows devs don't check in problem code like this?

Use a linter

Linters are programs that validates that your source code complies with some rules. A linter may forbid the use of the var keyword, or may enforce that a semicolon is present at the end of a line.

In javascript, the most common linter is eslint. It is reasonable easy to setup and most code editors play well with it.

There is a specific eslint plugin that checks that some rules are enforced in require and import calls: eslint plugin dependencies. It enforce that files exist or that file names are/are not case sensitive, so this plugin should do the trick for you. (However, I never configured it by myself. I believe most cli apps from javascript frameworks include it in their default configuration).

If you setup this properly, developers will see warnings in their editors when they try to use mayus within import or require sentences, and the command eslint will fail if run.

 Use javascript hooks to ensure no invalid commit is pushed to the repository

Using git hooks, you can enforce that eslint (or any other linter or command) must pass in order for a commit to be added to a repository.

This article explain how to do this with javascript (disclaimer, I'm the author), and provides some context on the matter.

Also there is the husky package that easily allows you to setup git hooks to prevent bad commits. The good thing about using husky is that the hooks can get pushed to the repository, so new developers on the project don't need to manually setup their .git/hooks/ files.

This is definitely an OS problem. Didnt try yet but you can activate the windows case sensitive option to avoid import errors. You have to execute the following command:

fsutil.exe file SetCaseSensitiveInfo C:folderpath enable

Be advice:

• Linux Subsystem should be enabled:
  Run the following command as Administrator in PowerShell to enable this optional feature:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

• It doesnt affect subfolders so a recursive script would be needed