Repository navigation
[create-next-app] Add first-class support for Oxlint & Oxfmt (--oxlint / --oxfmt) #101684
aliaksandrsen
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Goals
create-next-appvia dedicated flags (e.g.,--oxlint,--oxfmtor--oxc).create-next-appprompt alongside ESLint, Biome, and None..oxlintrc.json(and.oxfmtrc.json) with the built-innextjsplugin enabled.Non-Goals
nextjsplugin in Oxlint covering@next/next/*rules.Background
create-next-apprecently introduced the--biomeflag as an alternative to ESLint, which received overwhelmingly positive feedback from developers looking for faster Rust-based tooling.create-vite) recently adopted Oxlint as the default linter for its React templates, while Oxfmt has emerged as a drop-in, ~30x–100x faster alternative to Prettier.nextjsplugin (covering App Router, Server Components, Image optimizations, Link components, and more).examples/with-oxlintexample. However, bootstrapping vianpx create-next-app --example with-oxlintbypasses the regular interactive setup (Tailwind CSS, Turbopack, App Router vs Pages,src/directory, alias configuration), which creates unnecessary friction for teams wanting to use Oxlint on a standard setup.Proposal
Add
--oxlint(and optionally--oxfmtor unified--oxc) tocreate-next-app:Expand the linter prompt in create-next-app:
• Generate .oxlintrc.json:
All reactions