Next.js should enforce case sensitivity even if OS doesn't
See original GitHub issueBug 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.
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
NextJS case insensitive route for SSG pages - Stack Overflow
NextJS routes are case sensitive.You can use fallback property in getStaticPaths to catch the routes which aren't in the same case as the ......
Read more >How to Build Scalable Architecture for your Next.js Project
Let's create a new commit with the message ci: implement husky . If all has been setup properly your lint script should run...
Read more >Best way to manage URL case sensitivity | Community
We are building a site where we want all URLs to be case insensitive. On the code side, we are using NextJS with...
Read more >3 Configuring Authentication - Database - Oracle Help Center
To verify the user's password and enforce case sensitivity in password ... If not, then secure roles will remain unusable even after their...
Read more >Next.js Tutorial for Beginners (Getting Started) | Stack Diary
This tutorial does not use TypeScript, but if you want to use TypeScript, run npx create-next-app and append --typescript ; this will ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@utiq Thanks a lot for the code. I actually took out the
--globalflag and it worked perfectly.I solved my problem, in my case it was my git configuration, I run this:
git config --global core.ignorecase false