@aral I had to try because I’ve never noticed this. The entire filename still appears case insensitive to me.
@dmnelson Hmm, I wonder if Node.js has some funky import handling on macOS… I just ran into it in my Kitten project where imports success for main.layout.js Main.layout.js and MAIN.layout.js but not for main.Layout.js, main.layout.JS, etc.
Odd.
@aral Interesting. Maybe they have some of their own file comparison logic on top of whatever the OS does and it has a… different… outcome in case-insensitive filesystems.
@dmnelson @aral There is APFS case insensitive and case sensitive. I don’t remember what file system comes by default but in one of the thousand times I nuked my old Mac I came across that option.
More info / traces: https://apple.stackexchange.com/questions/415613/what-is-the-default-partition-type-case-sensitive-or-insensitive-in-macbook-pr#415615
@gabriel @aral Indeed, you could even choose case-sensitive on HFS+. Though it’s generally recommended to stick to case-insensitive since that’s what Mac software is developed on. In rare situations you may run into software that references file paths with the “wrong” case, and it breaks because the files it’s looking for are not found.