Antd Admin's two templates come with a build stack you did not pick
AI-friendly enterprise front-end best practices
At a glance
- What is it?
- Antd Admin ships two Ant Design 6 admin templates and a scaffolding CLI, built on React 19, TanStack Router/Query, Zustand and Zod, with mock-first local development so no backend is needed. What a template hands you silently matters as much as what it gives you: a vite alias to a VoidZero build and a pnpm allowlist with two entries.
- Who is it for?
- Antd Admin suits a team that wants an Ant Design 6 admin shell with URL-synced tables, JWT login and Playwright coverage already wired, and that is willing to own the backend contract its mocks define. It does not suit a team needing a specific admin layout today, because two templates are offered and one of them is only a language variant.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 25 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 16, 2026, and from our analysis. They are not legal advice.
Star history
- zuiidea/antd-admin9,770 ★ · -3
| Repository | 2026-09-28 | 2026-11-16 |
|---|---|---|
| zuiidea/antd-admin | 9.8k | 9.8k |
-3 Stars in the last 49 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Two templates, and one of them is only a translation variant
The template list is short enough to state in full. `basic` is an English-only setup. `with-lingui` is a bilingual setup pairing `en` and `zh` with Lingui. Everything else the project calls a feature sits on top of one of those two.
That is worth weighing before you clone anything, because a template catalogue with two entries is not a menu of admin layouts. A team whose admin screen has an unusual shape will be writing that part, and the i18n option is the only axis the two entries differ on.
The scaffolding CLI is `init-antd-admin`, and it lives in `packages/create`, which is also where the detailed behaviour is documented rather than in the top-level README.
Every scaffold command pulls @latest, and no option pins a version
Four package runners are offered for the interactive path:
npx init-antd-admin@latest
pnpm dlx init-antd-admin@latest
yarn dlx init-antd-admin@latest
bunx init-antd-admin@latestAnd two for the scripted path, where the project directory and the template are named directly:
pnpm dlx init-antd-admin@latest my-app --example basic -m pnpm
pnpm dlx init-antd-admin@latest my-app --example with-lingui --skip-installThe options table carries `[project-directory]`, `-e, --example <name | url>`, `--example-path <path>` for a subpath inside a remote repository, `-m, --package-manager <pm>` taking npm, pnpm, yarn or bun, plus `--skip-install`, `--skip-transforms` and `--no-git`.
There is no version flag in that table, and every command shown ends in `@latest`. So the template you evaluate today and the template your team scaffolds next month are not the same commit, and the documented commands give you no way to say otherwise.
Your vite and vitest are VoidZero builds wearing the upstream names
The root package.json carries pnpm overrides that alias two packages to entirely different ones:
"vite": "npm:@voidzero-dev/vite-plus-core@latest",
"vitest": "npm:@voidzero-dev/vite-plus-test@latest"Under those overrides, `vite` in your dependency graph is `@voidzero-dev/vite-plus-core` and `vitest` is `@voidzero-dev/vite-plus-test`. The `latest` tag is floating, and pnpm-lock.yaml is what freezes the choice for anyone who commits it.
Two consequences. A lockfile you regenerate, or a CI job that installs without one, can resolve a different build tool than the one you tested, with no manifest change to show for it. And when a bug appears in the dev server or the test runner, the package you have to read is the VoidZero one, while your error messages and imports use the upstream name.
onlyBuiltDependencies holds exactly two entries, and that is deliberate
The pnpm config in the same file lists what is allowed to run install scripts:
"onlyBuiltDependencies": [
"esbuild",
"msw"
]This is the pnpm behaviour where dependencies with build steps stay unbuilt until they are named. Two names here mean esbuild gets to compile its binary and msw gets to do whatever it does on install, and nothing else in the tree does.
The consequence bites on day one of a template that is not the one you evaluated. Add a dependency with a postinstall build, and it installs successfully and then misbehaves at runtime, because its build step was skipped by policy rather than by failure. The fix is one entry in a list you have to know exists, which is a reasonable trade for reproducible installs and an unpleasant one to debug cold.
Mock-first development means your mocks define the API contract
Local development runs with no backend required, and that is the feature that makes the template quick to evaluate. The same feature moves a decision into your lap: the JWT login flow with access and refresh tokens, and the menu and permission guards described as backend-driven, have to be backed by something, and the mocks are that something on day one.
So the frontend team effectively specifies the response shapes the guards read. Later, when a real backend arrives with different key names or a different refresh rule, the work is not a one-line base URL swap. It is reconciling every mock with the actual contract, and every screen that trusted the mock's idea of a permission.
Mock-first is the right call for building the UI. It is a commitment about who owns the API contract, and this template makes that commitment for you rather than leaving it open.
Table pagination, sorting and search live in the URL
Table state is URL-synced, which covers pagination, sorting and search together. It pairs with TanStack Router and TanStack Query for data fetching and Zustand for the rest of the client state, on React 19 and Ant Design 6, with Zod at the typed API boundaries and reusable CRUD patterns built on top.
The reader-facing effect is good: a filtered table can be shared as a link. The developer-facing effect is that the URL stops being a navigation concern and becomes a schema. Every filter parameter is now part of a contract that bookmarks and screenshots depend on, and renaming one is a breaking change for anyone who saved the link.
Dark mode theme switching is bundled in the same layer. For a product with a user preference stored elsewhere, that preference now has two homes.
A pnpm-pinned turbo monorepo that hands you four package managers
The repository root is a pnpm workspace with `pnpm-workspace.yaml`, `turbo.json` and a committed `pnpm-lock.yaml`, and `packageManager` is pinned to [email protected]. Build, dev and lint all run through `turbo run`, there is an fmt script that also runs through turbo, and there is a `setup:git-hooks` script pointing core.hooksPath at a `.githooks` directory.
So the template accepts npm, pnpm, yarn or bun through `-m`, while the repo you are learning from is pnpm-only with a lockfile that assumes it. Those are different worlds and the template is the one you ship.
The manifest declares version 6.0.0 while published tags run 6.0.1 from 2026-05-26, 6.0.0 from 2026-03-14 and 5.5.0 from 2026-02-19. The repository is not archived and the last push was on 2026-10-22. Production documentation sits at a separate docs site, and the `.cursor/` directory at the root matches the project's description of itself as AI-friendly front-end practices.
Editorial conclusion
Antd Admin suits a team that wants an Ant Design 6 admin shell with URL-synced tables, JWT login and Playwright coverage already wired, and that is willing to own the backend contract its mocks define. It does not suit a team needing a specific admin layout today, because two templates are offered and one of them is only a language variant. Before scaffolding, check the @voidzero-dev/[email protected] override that replaces vite, and whether your tooling can live with a repo pinned to [email protected].
Frequently asked questions
What templates does Antd Admin provide?
Two. `basic` is an English-only setup, and `with-lingui` is a bilingual setup with `en` and `zh` using Lingui. Both are scaffolded through the `init-antd-admin` CLI, which lives in `packages/create`.
How do I scaffold an Antd Admin app without interactive prompts?
Name the project directory and the template directly, for example `pnpm dlx init-antd-admin@latest my-app --example basic -m pnpm`, or the bilingual variant with `--example with-lingui --skip-install`. Add `--skip-install`, `--skip-transforms` or `--no-git` to skip the matching step.
Does Antd Admin need a backend to run locally?
No. Mock-first local development means you can run the template with no backend required, while JWT login with an access/refresh flow and backend-driven menu and permission guards are already wired. The mocks you ship with become the contract you own until a real API replaces them.
Which build and test tools does Antd Admin use?
The root package.json overrides `vite@*` to `npm:@voidzero-dev/[email protected]`, and `turbo` runs build, dev and lint across the workspace. E2E coverage uses Playwright.
What does Antd Admin require of a package manager?
The scaffold CLI accepts npm, pnpm, yarn or bun through `-m, --package-manager <pm>`, and can be run with npx, pnpm dlx, yarn dlx or bunx. The repository itself pins `[email protected]` and keeps a pnpm-lock.yaml at the root.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/zuiidea-antd-admin)Star history chart for your README
[](https://hysenlabs.com/projects/zuiidea-antd-admin)Was this useful?