duxianwei520/react: a React 18 admin starter with Vite, Redux Toolkit and Ant Design
An admin management framework built with React, Vite, Redux, Ant Design, Axios and Less.
At a glance
- What is it?
- The repository is a Chinese-language admin dashboard template that pairs React 18 with Vite 6, Redux Toolkit, Ant Design 6 and a bundled Mock.js server. It is a starting point for CRUD back offices, not a published component library, and its README is the only documentation.
- Who is it for?
- Adopt duxianwei520/react if you need a Chinese-market admin shell with login, role and module management already wired, and you are willing to read the source because the README is the only documentation. Do not adopt it if you need a published, versioned component library, TypeScript types, or a documented upgrade path; there are no releases and no changelog.
- 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 116 days ago.
- What is it written in?
- Mainly JavaScript, 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
- duxianwei520/react5,339 ★ · -4
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| duxianwei520/react | 5.3k | 5.3k |
-4 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What duxianwei520/react actually is, and who it is for
This is a scaffold, not a product. The package.json names it react-admin and marks it private, which prevents accidental publication through npm. What you get is a working admin shell: login with permission control, a Redux Toolkit store demonstrating the full pattern, Mock.js endpoints, axios cross-origin configuration, a DraftJS editor, ECharts integration and Socket.io. The README states that user management, role management and module management are already implemented, and that running npm start shows the complete feature set.
The intended reader is a developer who has to stand up a PC-side management system and does not want to assemble routing, state, UI kit and mock layer from scratch. The stack is opinionated and current: React 18.3.1, redux 5.0.1, @reduxjs/toolkit 2.2.0, react-router-dom 6.28.1, vite 6.0.5, axios 1.7.9, less 4.2.0, antd 6.3.2, echarts 5.6.0 and draft-js 0.11.7. That is a coherent 2025-era combination rather than a legacy webpack build.
It is not for you if you want a library to import into an existing app. There is no npm package, no API reference and no TypeScript. The README is in Simplified Chinese, which is fine for the target audience and a friction point for everyone else.
How the Vite dev server, Mock.js and the axios interceptor fit together
The architecture is visible in the scripts and in the repository layout. npm start does not run Vite alone; it runs concurrently with two child processes, npm run dev (which is vite) and npm run mock (which is nodemon --watch app/mocks/ app/mocks/http.js). So the browser talks to the Vite dev server, and the mock layer is a separate Node process that nodemon restarts whenever a file under app/mocks changes.
The data contract is fixed and documented in the README. Every asynchronous response is expected to look like this:
{
data: {
totalCount: 100,
currentPage: 1,
pageSize: 10,
'list': [
],
},
msg: '',
status: 1,
}The README says all async requests pass through ajax.js in the configs directory, where status 1 means success, 0 means a parameter or other error, and -1 means the session expired and the app redirects to login. Human-readable text rides in msg. That is a three-state convention rather than HTTP status codes, and it is the single most important thing to understand before swapping the mock server for a real backend: your API has to speak this envelope or you have to rewrite the interceptor.
The repository also keeps a babel.config.js and a postcss.config.js alongside vite.config.js, and the devDependencies still list Babel presets and plugins for decorators and class properties. Vite handles the build, but the Babel configuration remains, which suggests the project was migrated from an older webpack-era setup rather than written for Vite from the start.
Install and first run
The README gives a shallow clone, an install and a start. Use the depth-1 clone it recommends, since the history is not needed to run the template.
git clone --depth 1 https://github.com/duxianwei520/react.git
cd react
npm install
npm startnpm start is the important one. Per package.json it expands to concurrently "npm run dev" "npm run mock", so you should see both the Vite server output and the nodemon output from app/mocks/http.js in the same terminal. If only one of them appears, the mock layer is not running and the login and list screens will fail.
The README warns that most failed starts come from incomplete npm downloads, and it explicitly recommends against cnpm, suggesting a VPN instead if the registry is slow. That is a real constraint for users behind a slow connection to the npm registry, and it is the project's own diagnosis, not a guess.
For a production bundle the README gives one command:
npm run buildThat maps to vite build. The README calls it the packaging and deployment step for the production environment. There is also a preview script and a lint script in package.json, though the README does not describe them.
The status-code envelope is the sharpest edge
The three-value status convention is convenient inside the template and awkward the moment you leave it. A REST backend that returns 401 for an expired token, 400 for a bad parameter and 200 with a body for success will not trip the -1 branch, because that branch is looking at a JSON field, not at the HTTP status. You either wrap every response on the server or you edit the interceptor. The README says the parameters can be adjusted to fit the situation, but it does not document how, and it does not describe the interceptor's file contents beyond its location.
The second limitation is the absence of releases. The repository has no published GitHub releases and no changelog in its top-level entries. Upgrading means diffing master, and the package.json pins nothing beyond caret ranges, so a fresh npm install months from now can resolve different minor versions of antd, Vite or Redux Toolkit than the ones the template was written against. Ant Design 6 and Redux 5 are both major-version surfaces with breaking changes behind them.
Third, this is a front-end template with a mock server, not a backend. The README points to two companion repositories, an Express version and a plain Node version, and says the plain Node one implements three real endpoints for registration, login and fetching user information. Anything beyond those three is mock data. If your project needs real persistence, you are building that yourself.
How it differs from Ant Design Pro and from a plain Vite scaffold
The closest well-known alternative is Ant Design Pro. Ant Design Pro is a maintained framework with its own CLI, its own scaffolding conventions and a documentation site; this project is a single repository you clone and then own outright. The practical difference is governance. With Ant Design Pro you follow someone else's upgrade path and directory conventions. With duxianwei520/react you fork, and every future React or Ant Design major becomes your migration.
The other alternative is the plain Vite React template plus antd installed by hand. That gives you a smaller surface and no inherited assumptions about the response envelope, the mock process or the permission model. The cost is that login, role management and module management are exactly the parts you would then write. The value of this repository is concentrated in those three features plus the axios layer, not in the bundler configuration.
A third path, for teams already standardized on Next.js or on a component library with published types, is to skip this entirely. Nothing here is hard to reproduce, and the reproduction would match your conventions instead of the template's.
Maintenance, upgrades and the MIT licence
The repository is not archived, and the last push was on 2026-07-22. The template uses React 18 and Vite 6. Pin a Git commit for a reproducible checkout and review changes before updating. The .circleci directory and a .travis.yml are both present in the top-level entries, which is a sign of a long-lived repository that has changed CI providers over time rather than a curated release process.
Upgrade cost is dominated by the caret ranges. Redux 5 removed legacy APIs, Redux Toolkit 2 changed several defaults, and antd 6 is a major release; a future npm install can move all three. If you fork this, commit a lockfile and keep it, because package-lock.json is already in the repository and helps reproduce dependency installs.
The licence is MIT, per the LICENSE file and the README badge. MIT permits commercial use and modification with the copyright notice retained. That is a permissive position and the usual one for templates; check the LICENSE file itself for the exact wording rather than relying on the badge, and note that the licence covers this repository, not the dependencies it pulls in, each of which carries its own terms.
Editorial conclusion
Adopt duxianwei520/react if you need a Chinese-market admin shell with login, role and module management already wired, and you are willing to read the source because the README is the only documentation. Do not adopt it if you need a published, versioned component library, TypeScript types, or a documented upgrade path; there are no releases and no changelog. Before committing, run npm start and confirm the concurrently script brings up both Vite and the Mock.js server, then check that the axios interceptor in the configs directory matches your own status-code convention, since the template assumes status 1 for success, 0 for errors and -1 for an expired session.
Frequently asked questions
How do I install duxianwei520/react?
Clone the repository with git clone --depth 1 https://github.com/duxianwei520/react.git, then run npm install and npm start. The README notes that failed installs are usually incomplete npm downloads and recommends a VPN over cnpm.
Does duxianwei520/react need a backend to run?
No. npm start runs Vite and a Mock.js server together via concurrently, so the login, role and module management screens work against mock data. The README points to separate Express and plain Node repositories if you want real endpoints.
What response format does duxianwei520/react expect from an API?
A JSON envelope with data, msg and status fields, where status 1 means success, 0 means an error and -1 means the session expired and the app redirects to login. The README states all async requests pass through ajax.js in the configs directory.
Which versions of React, Vite and Ant Design does duxianwei520/react use?
The README lists React 18.3.1, vite 6.0.5, antd 6.3.2, redux 5.0.1, @reduxjs/toolkit 2.2.0, react-router-dom 6.28.1, axios 1.7.9 and less 4.2.0.
How do I build duxianwei520/react for production?
The README gives npm run build as the production packaging and deployment command, and package.json maps it to vite build. There is also a preview script, though the README does not describe it.
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/duxianwei520-react)Star history chart for your README
[](https://hysenlabs.com/projects/duxianwei520-react)Was this useful?