ead56eaab6
This fixes Next.js running into unexpected errors on Windows when invalid casing for a project directory is used. I was able to reproduce the issue on my local Windows machine and this resolved the issue there. <details> <summary>screenshot of error while reproducing</summary> <img width="838" alt="Screen Shot 2021-09-18 at 23 21 40" src="https://user-images.githubusercontent.com/22380829/133915825-ac4abdd2-fcf8-4309-9873-e6d88dfe485d.png"> </details> ## Bug - [x] Related issues linked using `fixes #number` - [ ] Integration tests added - [x] Errors have helpful link attached, see `contributing.md` Fixes: https://github.com/vercel/next.js/issues/27396 Fixes: https://github.com/vercel/next.js/issues/16535 Fixes: https://github.com/vercel/next.js/issues/17592
16 lines
768 B
Markdown
16 lines
768 B
Markdown
# Invalid Project Directory Casing
|
|
|
|
#### Why This Error Occurred
|
|
|
|
When starting Next.js, the current directory is a different casing than the actual directory on your filesystem. This can cause files to resolve inconsistently.
|
|
|
|
This can occur when using a case-insensitive filesystem. For example, opening PowerShell on Windows navigating to `cd path/to/myproject` instead of `cd path/to/MyProject`.
|
|
|
|
#### Possible Ways to Fix It
|
|
|
|
Ensure the casing for the current working directory matches the actual case of the real directory. Use a terminal that enforces case-sensitivity.
|
|
|
|
### Useful Links
|
|
|
|
- [Next.js CLI documentation](https://nextjs.org/docs/api-reference/cli)
|
|
- [Case sensitivity in filesystems](https://en.wikipedia.org/wiki/Case_sensitivity#In_filesystems)
|