Is your feature request related to a problem? Please describe.
Currently, the create-t3-app scaffolding process is experiencing "configuration drift" where various tool combinations (Biome, Prisma, Tailwind v4, and Oxc) are clashing on initial project generation. This creates immediate git diff churn and CI failures in what should be a "clean" repository state.
Describe the solution you'd like to see
Describe alternate solutions
Any thoughts?
Additional information
No response
Is your feature request related to a problem? Please describe.
Currently, the
create-t3-appscaffolding process is experiencing "configuration drift" where various tool combinations (Biome, Prisma, Tailwind v4, and Oxc) are clashing on initial project generation. This creates immediategit diffchurn and CI failures in what should be a "clean" repository state.Describe the solution you'd like to see
generated/prisma) are being caught in the Prettier/Biome formatting loop, causing persistent git diffs immediately after scaffolding (bug: Prisma generated files under generated/prisma are reformatted by Prettier, causing persistent git diff churn in fresh T3 scaffold #2217).useSortedClassesand Tailwind v4 resolution (biomeuseSortedClassesrule is counter intuitive #2126, bug: Tailwind CSS v4.x + Next.js ESM Module Resolution Issue #2127) are leading to linting errors on fresh installs.--import-aliasflag is triggeringTypeErrorcrashes in CI environments, indicating a regression in the CLI's argument parsing logic (bug: --import-alias flag crashes with TypeError when used in CI mode #2215).Describe alternate solutions
Any thoughts?
Additional information
No response