V3 Admin Vite: four commands to a dashboard, and what the template refuses to give up
An AI-friendly Vue3 admin template.
At a glance
- What is it?
- V3 Admin Vite is a Vue 3 admin template whose pitch is that it configures itself for AI coding tools, ships three build modes and fixes style on commit. The catch is that it is deliberately whole: TypeScript stays in, page routes come from your backend, and the 4.x line is frozen.
- Who is it for?
- Pick V3 Admin Vite if your team wants a Vue 3 admin shell that already speaks a backend-driven routing API and agrees with eslint --fix on commit style; the trade is that you inherit its opinions, TypeScript included. Verify three things before you commit: that your backend can serve the dynamic routes, that you can meet node 20.19+ or 22.12+ with pnpm 10, and what it will cost to remove modules you do not want.
- 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 127 days ago.
- What is it written in?
- Mainly Vue, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- un-pany/v3-admin-vite7,072 ★ · +10
| Repository | 2026-09-28 | 2026-11-15 |
|---|---|---|
| un-pany/v3-admin-vite | 7.1k | 7.1k |
10 Stars in the last 48 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
pnpm dev is four commands, and Node 22.12 is the real floor
The shortest documented path from a clean machine to a running dashboard is four commands, and every one of them assumes pnpm:
# Clone the project
git clone https://github.com/un-pany/v3-admin-vite.git
# Enter the project directory
cd v3-admin-vite
# Install dependencies
pnpm i
# Start the development server
pnpm dev`pnpm dev` maps to `vite` in package.json, so there is no wrapper script to read before you start it. The floor is not recent Node but two exact versions: node 20.19+ or 22.12+, with pnpm 10+. A pnpm-lock.yaml and a .npmrc sit in the root, so a different package manager will not reproduce the same tree. Editor setup is part of the documented flow as well, since the recommended plugins live in .vscode/extensions.json and the README tells you to install them.
Three .env files, three build modes, and vue-tsc runs before every bundle
Builds are split by mode rather than by flag. The root carries .env, .env.development, .env.production and .env.staging, and two build scripts exist:
# Build for the staging environment
pnpm build:staging
# Build for the production environment
pnpm buildIn package.json those expand to `vue-tsc && vite build --mode staging` and `vue-tsc && vite build`. The type check runs first in both, so a type error fails the build instead of surfacing later, and a production bundle cannot be produced without a passing vue-tsc run. Preview then serves whatever the build already wrote:
# Execute the build command first to generate the dist directory, then run the preview command
pnpm preview`pnpm preview` is `vite preview`, and the ordering is not optional: no dist directory, nothing to serve.
The AI claim is carried by four tool directories and a skills lock file
The template describes itself as an AI friendly admin dashboard and says it supports mainstream AI coding tools such as Claude Code, CodeX, Cursor, Trae and Antigravity. The repository makes that concrete in a way an ordinary Vue template would not: `.claude/`, `.cursor/`, `.agents/` and `.trae/` sit at the root, two agent instruction files (AGENTS.md and CLAUDE.md) are committed, and there is a skills-lock.json. Recommended skills go in with one command:
npx skills experimental_installWorth being precise about what that does and does not tell you. It shows where the tool-specific configuration lives, and it shows the author expects those tools to be running. It does not pin any AI tool version and states no compatibility range, so if your organisation standardises on one of these editors the exposure is configuration drift when the tools change shape, not a template that stops working.
Page permissions arrive from your backend through dynamic routing
Permission handling carries the biggest architectural consequence, and version 5.2 is where it moved: the notification block says 5.2 delivers a backend-controlled dynamic routing permission system. The built-in list spells out page-level permissions with dynamic routing controlled by backend APIs, button-level permissions handled by permission directives and functions, and route guards.
That design has a price. Login and logout are described as a demonstration.
pnpm lint rewrites files, and husky rewrites them again before commit
Quality gates are wired at two levels, and both mutate your working copy:
# Code linting and formatting
pnpm lint
# Unit tests
pnpm test`pnpm lint` is `eslint --fix`, not a check that reports and exits. It rewrites files in place. The commit path repeats the work, because package.json sets `prepare` to husky and lint-staged to `"*": "eslint --fix"`, so every staged file is rewritten on the way in. The config is @antfu/eslint-config with eslint-plugin-format behind it, backed by .editorconfig and the .husky/ directory in the root. The effect for a team is that style is enforced at commit time rather than in review, which holds up well until a contributor's editor disagrees with the format rules and the commit refuses to land.
vitest and happy-dom are wired in, but no coverage claim comes with them
There is a test runner and it is more than a token dependency. package.json sets `test` to vitest, and the dev dependencies add @vue/test-utils 2.4.11, happy-dom 20.10.6 and a tests/ directory at the root. Unit tests run with `pnpm test`.
None of that turns into evidence about the template itself. There is no coverage figure, no count of the tests that ship, and no claim that the built-in features are regression tested. The Features section makes a different kind of promise: no complex encapsulation, no complicated type gymnastics, as detailed comments as possible on every configuration item, third-party dependencies kept up to date, and one consistent style for code, naming and comments. Those are claims about readability. If you plan to fork this template, the things you can verify from the repository are the pinned versions and the scripts; the behaviour claims are yours to test.
Removing TypeScript yourself is the job the paid lazy package was built for
The template is deliberately opinionated about staying whole. Its own notification block says that if you do not want to remove TypeScript or other modules yourself, there is a paid lazy package for that, linked from issue 225.
Read plainly, that is a limitation with a price tag attached. The project treats TypeScript and the rest of the module set as load-bearing and hands the surgery to a paid service instead of documenting a supported way to drop them. The consequence is concrete: if your organisation has a rule against TypeScript, or you need a much smaller bundle, you are choosing between doing that removal work yourself and paying for it. No lighter build is described in the README.
4.x is frozen, and the upgrade path is a branch link rather than a guide
Version 4.x will no longer be maintained unless there are critical bugs, and the only instruction given for anyone still on it is to switch to the 4.x branch. The README gives no upgrade guide. That matters because the distance between the two lines is not cosmetic: 4.x predates the backend-controlled routing that 5.2 introduces, so moving up is a change to how your routes are produced, not a version bump.
The cadence on the current line is visible from the releases: v5.0.2 on 2025-07-14, v5.1.0 on 2026-01-19 and v5.2.0 on 2026-07-10, with the last push landing on 2026-07-11. The licence is MIT, copyright 2022 to the present, and separate projects cover the cases this one declines: a mobile web app template and an Electron desktop version.
Editorial conclusion
Pick V3 Admin Vite if your team wants a Vue 3 admin shell that already speaks a backend-driven routing API and agrees with eslint --fix on commit style; the trade is that you inherit its opinions, TypeScript included. Verify three things before you commit: that your backend can serve the dynamic routes, that you can meet node 20.19+ or 22.12+ with pnpm 10, and what it will cost to remove modules you do not want. The MIT licence lets you fork and edit freely.
Frequently asked questions
What does V3 Admin Vite include out of the box?
User management with a login and logout demonstration, permission management at page and button level plus route guards, development, staging and production environments, normal, dark and deep blue themes, left-side, top and hybrid layouts, per-user dashboard pages, 403 and 404 error pages, mobile-compatible layouts, and extras such as an SVG sprite sheet, dynamic sidebar and breadcrumbs, tab navigation, content zoom and fullscreen.
Which Node and package manager versions does V3 Admin Vite need?
The recommended environment is node 20.19+ or 22.12+ with pnpm 10+, and the repository ships a pnpm-lock.yaml. The recommended editor is the latest Visual Studio Code, or Cursor and Trae as AI IDEs, with the recommended plugins listed in .vscode/extensions.json.
How does V3 Admin Vite handle permissions and routes?
Page-level permissions come from dynamic routing controlled by backend APIs, which version 5.2 introduces as a backend-controlled dynamic routing permission system. Button-level permissions come from permission directives and functions, and route guards sit alongside them.
How do you build and preview V3 Admin Vite locally?
Run pnpm build:staging for the staging environment or pnpm build for production; both run vue-tsc before vite build. Then run pnpm preview, which is vite preview, after the build has generated the dist directory.
How does V3 Admin Vite lint and test its code?
pnpm lint runs eslint --fix, and pnpm test runs vitest. Husky is wired through the prepare script, and lint-staged applies eslint --fix to every staged file, so formatting is enforced at commit time. The ESLint config is @antfu/eslint-config with eslint-plugin-format.
What happens to the 4.x branch of V3 Admin Vite?
Version 4.x will no longer be maintained unless there are critical bugs, and the README points anyone still on it at the 4.x branch. Maintenance continues on the 5.x line, where v5.2.0 was released on 2026-07-10.
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/un-pany-v3-admin-vite)Star history chart for your README
[](https://hysenlabs.com/projects/un-pany-v3-admin-vite)Was this useful?