How should Biome, Ultracite, and Oxlint coexist in a better-t-stack project? #474
armelhbobdad
started this conversation in
General
Replies: 1 comment
-
Ideally, you should use either Biome (or Ultracite) or Oxlint to keep things simple. I have given you the freedom to choose both in Better T Stack if you want. For example:
If you use both, turn off duplicate rules in one tool and run them separately in CI to avoid messy outputs. |
Beta Was this translation helpful? Give feedback.
0 replies
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.
-
Hi everyone 👋,
I just generated a new project using better-t-stack (awesome stack by the way!),
pnpm create better-t-stack@latest local-first-starter --frontend tanstack-start native-nativewind --backend elysia --runtime bun --database postgres --orm drizzle --api trpc --auth --addons turborepo fumadocs biome ultracite oxlint husky --examples todo --db-setup docker --web-deploy none --git --package-manager pnpm --install
and during setup, I selected all three lint/formatting addons: Biome, Ultracite and Oxlint.
Since Ultracite extends Biome and Oxlint overlaps with both, I'm wondering:
❓ My Main Questions:
Is there any benefit or conflict in keeping all three tools together in a monorepo or is that overkill?
How should I configure them to avoid rule conflicts or duplicated linting outputs?
Does anyone here have practical experience comparing Oxlint vs Biome (via Ultracite) in real-world CI workflows?
What would be a recommended strategy if I want to:
🧠 Thoughts?
Would love to hear how others are approaching this. If you're using a similar stack or have thoughts about tool layering, CI setup, or even rule overrides, I’m all ears!
Thanks in advance 🙏
Armel
Beta Was this translation helpful? Give feedback.
All reactions