-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Next.js should enforce case sensitivity even if OS doesn't #11742
Comments
this PR won't fix this exact case, but it seems related. |
Switching this from a bug to feature request due to your PR landing @Janpot 🙏 |
I was having the same kind of error: Not sure what I actually did wrong here, even though I'm pretty sure I used correct casing for the component file. |
@CallmeHongmaybe Same issue, how did you solve it? |
I think this could be useful. isEnvDevelopment && new CaseSensitivePathsPlugin(), |
@utiq I actually haven't solved this yet. |
So I'm just gonna put the |
I solved my problem, in my case it was my git configuration, I run this: |
@utiq Thanks a lot for the code. I actually took out the |
Can I get an official recommendation whether we should keep My app build was successful on my local environment (Windows) but was failing in Vercel. I was getting:
Later I've found out that it was because I'd renamed that path from To fix it, I changed
So I had to change it to a brand new path name like: And only then I was able to build it successfully on Vercel. Later I was able to go back to my desired path name as Maybe my |
Had the same problem. |
Please verify that your issue can be recreated with Why was this issue marked with the
|
This issue has been automatically closed because it wasn't verified against next@canary. If you think it was closed by accident, please leave a comment. If you are running into a similar issue, please open a new issue with a reproduction. Thank you. |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Bug report
Describe the bug
User churn due to:
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.
The text was updated successfully, but these errors were encountered: