mirror of
https://github.com/vercel/next.js.git
synced 2026-09-20 02:25:18 +08:00
Delba de Oliveira
1e6d2044b4
Closes: https://linear.app/vercel/issue/DOC-3249/cli-reference-pages Updates the `next` and `create-next-app` CLI pages to follow the reference page template. Moves these pages under "CLI" to match new IA. Redirects: https://github.com/vercel/next.js/pull/68899
19 lines
769 B
Plaintext
19 lines
769 B
Plaintext
---
|
|
title: 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](/docs/pages/api-reference/cli/next)
|
|
- [Case sensitivity in filesystems](https://en.wikipedia.org/wiki/Case_sensitivity#In_filesystems)
|