rsnext/test/integration/tsconfig-verifier
stefanprobst 42227559c6
fix: don't add forceConsistentCasingInFileNames to tsconfig when ts version >= 5.0 (#51564)
Currently, Next.js enforces that `forceConsistentCasingInFileNames: true` is added to a user's `tsconfig.json`.

This PR removes that behavior for CNA templates, and when the typescript version is >= 5.0.0, because since ts 5.0 `forceConsistentCasingInFileNames` is `true` by default. See https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/

related: https://github.com/vercel/next.js/issues/45617
2023-08-15 19:12:40 +00:00
..
app Enable App Router for all applications (#49088) 2023-05-04 17:47:10 +02:00
pages Stop overriding the user's TS config with defaults during next build (#45670) 2023-02-15 18:11:00 +01:00
test fix: don't add forceConsistentCasingInFileNames to tsconfig when ts version >= 5.0 (#51564) 2023-08-15 19:12:40 +00:00
value.ts Drop module: esnext requirement in tsconfig.json (#15276) 2020-07-18 19:37:13 +00:00