Next.js: Next.js should enforce case sensitivity even if OS doesn't

[Timer]

Bug report

Describe the bug

User churn due to:

Module not found: Can't resolve 'next/Head' in '/zeit/628124c9/pages'

To Reproduce

Import next/Head on a case insensitive filesystem and it will work.
Deploy to a sensitive one, it'll fail to build.

Expected behavior

Next.js should never of allowed the build in the first place and suggested the user fix the case sensitivity issue.

[Janpot]

this PR won't fix this exact case, but it seems related.
🤔 This may be solvable with with a linter as well. Or with case-sensitive-paths-webpack-plugin

[Timer]

Switching this from a bug to feature request due to your PR landing @Janpot 🙏

[CallmeHongmaybe]

I was having the same kind of error:
Module not found: Can't resolve '../../../components/Trends' in '/vercel/3e42d29f/pages/country/[category]'

Not sure what I actually did wrong here, even though I'm pretty sure I used correct casing for the component file.

[utiq]

@CallmeHongmaybe Same issue, how did you solve it?

[sphilee]

I think this could be useful.

isEnvDevelopment && new CaseSensitivePathsPlugin(),

https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/config/webpack.config.js#L660

[CallmeHongmaybe]

@utiq I actually haven't solved this yet.

[CallmeHongmaybe]

So I'm just gonna put the CaseSensitivePathsPlugin somewhere in next.config.js amirite

[utiq]

I solved my problem, in my case it was my git configuration, I run this:
git config --global core.ignorecase false

[CallmeHongmaybe]

@utiq Thanks a lot for the code. I actually took out the --global flag and it worked perfectly.