rsnext/packages/create-next-app/templates
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 fix: don't add forceConsistentCasingInFileNames to tsconfig when ts version >= 5.0 (#51564) 2023-08-15 19:12:40 +00:00
app-tw fix: don't add forceConsistentCasingInFileNames to tsconfig when ts version >= 5.0 (#51564) 2023-08-15 19:12:40 +00:00
default fix: don't add forceConsistentCasingInFileNames to tsconfig when ts version >= 5.0 (#51564) 2023-08-15 19:12:40 +00:00
default-tw fix: don't add forceConsistentCasingInFileNames to tsconfig when ts version >= 5.0 (#51564) 2023-08-15 19:12:40 +00:00
index.ts chore(create-next-app): use tailwind.config.ts for typescript templates (#47795) 2023-08-01 20:05:57 +00:00
types.ts feat(cli): introduce --tailwind flag (#46927) 2023-03-16 16:06:27 +01:00