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
19 lines
556 B
TypeScript
19 lines
556 B
TypeScript
import fs from 'fs'
|
|
import path from 'path'
|
|
import * as Log from '../build/output/log'
|
|
|
|
export function getProjectDir(dir?: string) {
|
|
const resolvedDir = path.resolve(dir || '.')
|
|
const realDir = fs.realpathSync.native(resolvedDir)
|
|
|
|
if (
|
|
resolvedDir !== realDir &&
|
|
resolvedDir.toLowerCase() === realDir.toLowerCase()
|
|
) {
|
|
Log.warn(
|
|
`Invalid casing detected for project dir, received ${resolvedDir} actual path ${realDir}, see more info here https://nextjs.org/docs/messages/invalid-project-dir-casing`
|
|
)
|
|
}
|
|
|
|
return realDir
|
|
}
|