Skip to main content

We now have a Recommended Tech Stack 🧰

· 2 min read
Gergely Sipos
Gergely Sipos
Frontend Architect

Remember when we said this was an experiment? Well, the experiment grew up. We just shipped a curated, 13-tool Recommended Tech Stack for Aliz frontend projects — a single reference for what we reach for when starting something new.

Every new project kicks off with the same tooling debate. React or Angular? Zustand or Redux? CSS Modules or Tailwind? These conversations have value, but they shouldn't happen from scratch every single time.

Our philosophy is sensible defaults, not mandates. Think of it as a paved path — similar to what Spotify and others call a "golden path." Teams can step off it when there's a good reason. The goal is straightforward: less time debating, more time shipping.

What's in the stack​

Thirteen tools, grouped by concern:

  • UI & Types: React, TypeScript
  • State: Zustand (client) + TanStack Query (server)
  • Styling: Tailwind CSS, shadcn/ui, MUI
  • Build & Test: Vite, Vitest, Playwright
  • Content sites: Astro
  • Charting: Recharts → ECharts (progressive complexity)

A few connections worth calling out:

  • Vite powers both the build and the test runner. Vitest runs on top of Vite's transform pipeline, so your dev and test environments share the same config.
  • shadcn/ui is Tailwind + Radix under the hood — you copy-paste components into your project rather than installing a package. Full ownership, no dependency lock-in.
  • Zustand for client state, TanStack Query for server state — a clean separation that keeps stores small and caches honest.

Each tool has its own doc page with rationale and official links. The overview is the best starting point.

These aren't contrarian picks​

We're not betting on anything exotic. The 2025–2026 ecosystem data tells a clear story:

  • Vite overtook webpack as the default bundler (State of JS 2024).
  • Tailwind CSS crossed 75% usage among surveyed developers (State of CSS 2024).
  • Vitest and Playwright both sit in the top satisfaction tier for their categories.
  • TypeScript is no longer optional — it's the baseline expectation for production frontend code.

We're recommending what the ecosystem already converged on. No surprises, just alignment.

What's next​

Each tool page is a short intro — enough to understand why it's there and where to go deeper. The stack will evolve as the ecosystem does, and contributions are welcome.

Start here: Recommended Tech Stack overview 🛠️