Practical Problem: case-mismatch in package/file require statements

[martinheidegger]

I noticed recently that I can write require('myPackage') and require('mypackage') interchangeably on my OS because the OS is case-insensitive. This is problematic because when I try to use the same project, package on a OS that case-sensitive the imports don't seem to work. This seems to be an issue that could occur with any package and any file. Since its a systemic issue I think it would be good if node.js would try to check if the case of the file/folder actually matches the case entered and show an error message or deprecation warning that can be turned off via a flag.

[bnoordhuis]

That's been suggested more than once in the past, see e.g. #5143. There is a more recent issue I can't find anymore that proposes exactly what you are suggesting.

The canonical filename on case-insensitive file systems can only be found by walking the directory with fs.readdir(). Doing that for every require() statement would introduce massive performance degradation that no amount of clever caching could fix.

[martinheidegger]

Sorry for posting a duplicate then. Didn't find the other issues 😔
nodejs/node-v0.x-archive#8145 This seems to be the PR associated.

[XadillaX]

Is this feature still in need? If yes, I will take this issue and work on it. @bnoordhuis

[bnoordhuis]

Sorry, I should have closed this. I'll do that now. The feature request is understandable but there is no reasonable way to implement it.