# Ant Design Vue: an Ant Design component library for Vue 2 and Vue 3 > Ant Design Vue ports the Ant Design component set to Vue, shipping one package that targets both Vue 2 and Vue 3. It is a strong fit for data-heavy admin interfaces and a poor fit if you want small bundle sizes or a project with frequent releases. **vueComponent/ant-design-vue** โ€” ๐ŸŒˆ An enterprise-class UI components based on Ant Design and Vue. ๐Ÿœ - Repository: https://github.com/vueComponent/ant-design-vue - Website: https://antdv.com/ - Stars: 21,672 ยท Forks: 3,891 - Language: Vue - License: NOASSERTION - Published: 2026-09-21 ยท Updated: 2026-09-21 ยท Language: en - Canonical page: https://hysenlabs.com/projects/vuecomponent-ant-design-vue ## What Ant Design Vue is for, and who ends up using it Ant Design Vue describes itself as "an enterprise-class UI components based on Ant Design and Vue". The phrase that matters is enterprise-class, and the README is explicit that the target is desktop applications. This is a library for internal tools, dashboards, configuration consoles and back-office systems: screens with dense forms, sortable tables, filters and modals, where the visual language is already decided and the work is wiring data to controls. The intended user is a Vue team that wants Ant Design's look and component inventory without switching to React. The README lists shared Ant Design of React design resources as a feature, which is the honest way to describe the relationship: the design specification and the component semantics come from the React project, and this repository supplies the Vue implementation. If your organisation already uses Ant Design on a React product, the Vue port keeps the two interfaces visually consistent. It is not aimed at marketing pages, content sites or mobile-first products. Nothing in the README claims responsive or touch-oriented components, and the environment table lists desktop browsers plus Electron. Choosing it for a phone-first product means fighting the design system rather than using it. ## How the package is put together: component directories, a build pipeline and three entry points The repository layout shows a conventional component library: a components/ directory holding the individual components, a site/ directory for documentation, tests/ for the test suite, and antd-tools/ plus scripts/ for build and release automation. The package.json exposes several entry points rather than one. main points at lib/index.js, module at es/index.js, unpkg at dist/antd.min.js, and typings at es/index.d.ts. Those names tell you the release ships CommonJS, ES modules, a prebuilt browser bundle and TypeScript declarations as separate artefacts. At the top level there are also index.js, index.esm.js, index-with-locales.js and index-style-only.js. That split exists because locale data and styles can be pulled in separately from the components themselves, which matters when you want to control what ends up in the bundle. The build scripts confirm the same shape. compile runs antd-tools/cli/run.js compile, pub runs the same CLI with pub, and prebuild chains version generation, route generation, token statistics and token metadata before the build itself. Design tokens are generated into the repository rather than fetched at runtime, so theme values are baked in at build time. The dev script runs npm run routes and then vite serve site, which is how the documentation site is run locally. ## Installing ant-design-vue and rendering a first component The README recommends npm or yarn, on the grounds that it makes development easier and gives access to the wider JavaScript tooling ecosystem. The npm form is: ```bash npm install ant-design-vue --save ``` The yarn equivalent is a single command as well: ```bash yarn add ant-design-vue ``` The README also notes that in a poor network environment you can use other registries and tools such as cnpm. That is the entire installation guidance the README gives; it does not walk through registering the plugin, importing styles or configuring a bundler, and it does not show a component example. For those steps the README points at the home page, https://www.antdv.com/, and the getting-started page linked from the compatibility note. What the README does document clearly is the environment. Modern browsers are supported, with the last two versions of Edge, Firefox, Chrome, Safari and Opera, plus Electron. Version 1.x supported Internet Explorer 9 and above with polyfills, but that is a statement about the 1.x line, not about the current 4.x package. Server-side rendering is listed as supported. Vue 2 and Vue 3 are both listed as supported, which is unusual and is the first thing to check against your own project: the two Vue majors have different APIs, and the README does not explain how a single package serves both. ## The release cadence is the weakest part of the story The repository is not archived, and the last push was on 2026-09-19, so the codebase is still receiving commits. The published releases tell a different story. The most recent release listed is 4.2.6, tagged on 2024-11-11. Before that, 4.2.5 on 2024-09-19 and 4.2.3 on 2024-06-10. Three releases across roughly five months in 2024, and then nothing in the release list after November 2024. That gap between repository activity and published versions is the thing to understand before adopting. Commits landing on main do not reach you until they are published to the registry, and the release list gives no evidence of a version after 4.2.6. If your team plans upgrades around a predictable cadence, this is a real constraint rather than a cosmetic one. It also means a bug fixed on main may sit unreleased for a long time. The README does not document a release process, a support window for older majors, or a rollback procedure for a bad upgrade. The CHANGELOG.en-US.md and CHANGELOG.zh-CN.md files at the repository root are where release notes live, and the repository does not describe what they contain beyond their names. ## Where Ant Design Vue is the wrong tool The clearest limitation is scope. The README frames the library around desktop applications, and the environment table is a list of desktop browsers and Electron. There is no mobile framework, no touch gesture layer and no native shell in the picture. If your product is a mobile web app or a hybrid app, the component set will not match the interaction model you need. The second limitation is the version story. Supporting Vue 2 and Vue 3 in one package is a compatibility promise, not a guarantee that every component behaves identically across both. The README states the support without qualification or caveats, and it does not describe migration between the two or which major is recommended for new work. Treat the dual support as something to verify per component rather than as a settled fact. The third is bundle size. The package ships a dist/antd.min.js browser build alongside lib/, es/ and locale entry points, and the README's feature list advertises "a set of high-quality Vue components out of the box" rather than a minimal or tree-shakeable core. If your priority is the smallest possible client bundle for a few controls, a lighter headless or utility-first approach will serve you better, at the cost of building the visual layer yourself. ## Ant Design of React is the sibling, not the substitute The obvious alternative is Ant Design of React, which the README links to and names as the source of the shared design resources. The difference is not cosmetic. Ant Design of React is the original implementation of the design language, and this project is a Vue port of it. Component names, props and visual output are meant to line up, but the runtime, the ecosystem and the release schedule are separate. A fix or a new component in the React project does not automatically appear here. The practical consequence is a choice about which side of the port you want to be on. If your team is already a React shop, using Ant Design of React removes the porting layer entirely and keeps you on the reference implementation. If your team writes Vue, Ant Design Vue gives you the same visual language without a rewrite. What you should not assume is that the two projects move together: the release history here shows 4.2.6 as the latest version, and there is no statement in the README tying this project's schedule to the React project's. Within the Vue ecosystem, the repository's own Ecosystem table points at adjacent pieces rather than competitors: a VSCode extension, a vue-cli plugin, a Nuxt module, and @formily/antdv for form-heavy work. ## Licence and the cost of keeping up The README states that ant-design-vue is an MIT-licensed open source project. The repository's licence field is not a recognised SPDX identifier, so the README is the clearer statement of intent, but the LICENSE file at the repository root is the document that actually governs use. Read it rather than the badge. Nothing here is legal advice, and the MIT claim in the README is worth confirming against that file before you ship. The README also describes the funding model: the project asks for backers through Patreon, Open Collective and PayPal, and lists sponsors whose logos appear in the README. That is a signal about how maintenance is resourced. A project supported by donations and sponsor placements does not carry the same release guarantees as one with a commercial vendor behind it, and the release history above is consistent with that. Upgrade cost is dominated by the version gap. If you adopt 4.2.6 today, the next published version may include changes accumulated since 2024-11-11, and the CHANGELOG files are where those will be described. Budget time to read them rather than assuming a patch-level bump is inert. The repository also carries a SECURITY.md, so there is a stated channel for reporting vulnerabilities, though the README does not describe the response process. ## Conclusion Adopt Ant Design Vue when you are building a desktop, data-heavy admin application in Vue and want Ant Design's form, table and select components without writing them yourself. Do not adopt it if you need a small dependency footprint, first-class mobile layouts, or a release cadence you can plan around: the newest release listed is 4.2.6 from 2024-11-11. Before committing, verify in your own project how the components you depend on behave under your Vue version, since the README states support for both Vue 2 and Vue 3 and the two are not interchangeable. ## FAQ ### What is Ant Design Vue used for? It is a Vue component library built on the Ant Design specification, aimed at enterprise desktop applications. The README describes it as an enterprise-class UI design system for desktop applications with a set of high-quality Vue components out of the box. ### How do I install ant-design-vue? The README recommends npm or yarn and gives npm install ant-design-vue --save, or yarn add ant-design-vue. It notes that in a poor network environment you can use other registries and tools such as cnpm. ### What is ant design vue? It is a Vue implementation of Ant Design, published as the ant-design-vue package, that shares design resources with Ant Design of React. The README lists support for Vue 2 and Vue 3, server-side rendering, Electron and modern desktop browsers. ### Does Ant Design Vue support drag and drop? The README does not document drag and drop behaviour for any component, and the feature list covers the design system, the component set and shared Ant Design resources only. The repository's Ecosystem table lists related projects, but none of them is described as a drag and drop add-on. ## Sources - [Issues](https://github.com/vueComponent/ant-design-vue/issues) - [Project website](https://antdv.com/) - [README](https://github.com/vueComponent/ant-design-vue/blob/main/README.md) - [Releases](https://github.com/vueComponent/ant-design-vue/releases) - [vueComponent/ant-design-vue on GitHub](https://github.com/vueComponent/ant-design-vue) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/vuecomponent-ant-design-vue