vxe-table's parallel Vue 2 and Vue 3 branches, and the six features locked behind the paid edition
A table solution, vxe-table, supporting both Vue 2 and Vue 3.
At a glance
- What is it?
- The MIT licensed Vue grid from x-extends publishes its v3 and v4 lines within two minutes of each other, has rebuilt the virtual renderer five times (v2 to v6), and lists cell copy/paste, region selection, find and replace, aggregate functions, data summary and chart integration as commercial features.
- Who is it for?
- Teams building a desktop Vue admin screen that needs editing, virtual scrolling and import or export in one component should trial vxe-table on the v4 branch, and should price the commercial edition before promising spreadsheet paste, because cell copy/paste and cell region selection are listed as paid items. Teams that need IE11, one build for both Vue majors, or a grid they can restyle without a vendor skin will not get it here.
- 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 1 day 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 21, 2026, and from our analysis. They are not legal advice.
Star history
- x-extends/vxe-table8,634 ★ · +7
| Repository | 2026-09-22 | 2026-11-21 |
|---|---|---|
| x-extends/vxe-table | 8.6k | 8.6k |
7 Stars in the last 60 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The v3 and v4 branches publish within a minute of each other
The two release lines land together. v4.23.14 shipped on 2026-11-03 at 05:36 UTC and v3.25.14 about a minute and a half earlier, after v4.23.13 on 2026-11-02. The v3 branch targets vue 2.6 through 2.7 and became the long term support line at v3.9; v4 targets vue 3.x and reached that status at v4.7, after an internal refactor that split the Table library from the Vxe UI library. Changelog entries mirror each other because the project states that features and APIs are kept in sync across both branches. The cost is packaging rather than parity. package.json on the main branch reports version 4.23.14, and the vue 2 build lives on a different branch entirely, so an estate running both Vue majors pins one tag and tracks the other separately.
The virtual renderer has been rebuilt six times and the seventh rewrite is still unchecked
Virtual rendering is the part of this grid that has been rewritten most often. v4.12 introduced virtual rendering v2 with support for million level data rendering, v4.13 brought v3 for smoother scrolling and better compatibility in Chrome, Safari and Firefox, v4.14 brought v4 for smoother rendering and dragging, and v4.15 brought v5 to cut memory usage. v4.11 separately reworked expand rows so they coexist with virtual rendering and frozen columns. v4.23 brought v6 for running a native scrollbar and a virtual scrollbar at the same time. Two further rewrites sit unchecked in the version list: v7 for tuning million level rendering, and v8 for pushing data volume into the tens of millions. Read those boxes as a plan, not a feature. Scrolling is still being tuned rather than settled: v4.19 improved trackpad smoothness on Windows and Mac, and v4.21 fixed a scroll misalignment case.
npm install vxe-table resolves one build, and npm run update needs the legacy peer flag
The install section targets vue 3.x and gives one command:
npm install vxe-tableRegistering the plugin and its stylesheet takes three statements. The CSS comes from the package itself rather than a separate CDN file, so a bundler build carries the theme along with the code:
// ...
import VxeUITable from 'vxe-table'
import 'vxe-table/lib/style.css'
// ...
createApp(App).use(VxeUITable).mount('#app')The README example mounts a vxe-table bound to tableData, with vxe-column children and a vxe-colgroup wrapping two further columns. Nothing else stands between you and rendered rows. One command deserves attention before you type it, because the repository does not use a plain install:
npm run updateThat script is npm install --legacy-peer-deps in package.json, so npm's default strict peer resolver does not accept this dependency graph unaided. If peer resolution blocks your own install, that flag is the project's own answer rather than something you have to guess at.
Entry points hand you source and types alongside the compiled bundles
The published fields tell you what form you receive. main resolves to lib/index.common.js, module to es/index.esm.js, unpkg and jsdelivr both to lib/index.umd.js, style to lib/style.css, and typings to types/index.d.ts. The files list ships dist, lib, es, src, helper, types, styles and packages, so an npm install brings the TypeScript sources and the helper directory down as well as the builds. Producing those directories runs lib:new, which is node scripts/build-modules.js; the older two-stage lib:old path built a bundle from index.ts and then ran gulp:
npm run libThe output is the es and lib pair those entry points expect. The local demo loop is the vue-cli-service:
npm run serveTwo consequences follow for contributors. The demos live in examples/ with router, style and views subdirectories, driven by vue.config.js and the vue-cli-service 5 toolchain, so a demo contribution is coupled to that build. And package.json defines no test script at all, which leaves the repository with no documented command that exercises the grid's own behaviour. When the correctness of sorting, filtering or editing matters to you, that verification has to come from tests you write.
Cell copy/paste and find/replace are checklist items marked as enterprise edition
Six entries in the feature checklist are labelled enterprise edition and point at store.vxeui.com: data summary, aggregate functions, cell region selection, cell copy and paste, cell find and replace, and integrated charts. That list sits next to a package description advertising a table "supporting copy-paste, data pivot table, and high-performance virtual list table solution", with no qualification attached. Read the two together and clipboard range paste looks like a free capability until you hit the paywall list. Pivot tables are stranger. They appear in the description and have no line in the checklist at all, so nothing in the repository tells you whether they ship inside the npm package or sit behind the same store. For a team whose users live in Excel, that is the first question to settle, because the free list already includes import, export and print, which covers file transfer but not cell level clipboard ranges.
IE11 support was withdrawn in December 2024 and no replacement line exists
Browser support was cut rather than widened. The v3.0 line kept IE11 compatibility, and both v3.0 and v4.0 are marked as stopped maintenance across 2020-03-01 to 2024-12-01. v3.9 and v4.7 then rebuilt on vue2.6 to 2.7 and vue3.2 plus, targeting modern browsers with IE dropped. Older lines are closed too: v2.0 ran from 2019-03-01 to 2021-12-01 and v1.0 from 2018-02-01 to 2020-04-01. The support matrix publishes five columns with minimum versions 80, 80, 90, 75 and 10, but the column headings do not survive in the text of the file, so confirm the browser mapping on the rendered page before relying on a specific minimum. The consequence for a reader is plain. An intranet that must open in IE11 has no supported line to sit on, and the branches that once handled it are closed to fixes.
Renderers mutate data in place, which widens the debugging surface
Configuration does the work. Columns declare their editor and display behaviour, and v4.22 is the release that lets an editing cell combine edit-render with other renderers rather than pick one. The checklist covers a data proxy for server side work, data validation, keyboard navigation, renderers, virtual scroll, virtual merging and theming through CSS variables, alongside a toolbar, a context menu and import, export and print. The stated design principle is two way data flow, where a renderer or a custom extension operates data values directly. That is convenient and it enlarges the debugging surface, because values change from inside renderers instead of from one visible place, and the repository carries no note on tracing which renderer wrote a given value. There is also no migration guide between the v3 and v4 branches, even though both are still taking releases, so any API gap between the two lines surfaces when you compile rather than when you read.
The Table and UI library split is where vxe-table parts ways with a headless table
The v4.7 split explains why a CDN page for this grid loads two stylesheets, vxe-pc-ui@4/lib/style.css and vxe-table@4/lib/style.css, and why xe-utils appears as its own script next to vue@3. Compare that with TanStack Table, the headless option. TanStack supplies state, sorting, filtering and pagination logic and leaves markup and styling to the application, while vxe-table ships the DOM, a CSS variable theme, keyboard navigation, a toolbar and a context menu as part of the component. Headless is the better fit when a design system forbids a vendor table skin, or when a screen shows four columns and nothing else. vxe-table is the shorter path when users need to paste ranges out of a spreadsheet on day one, and the price is owning the component's markup plus the six paid features.
Editorial conclusion
Teams building a desktop Vue admin screen that needs editing, virtual scrolling and import or export in one component should trial vxe-table on the v4 branch, and should price the commercial edition before promising spreadsheet paste, because cell copy/paste and cell region selection are listed as paid items. Teams that need IE11, one build for both Vue majors, or a grid they can restyle without a vendor skin will not get it here. Verify first by running npm run update, which is npm install --legacy-peer-deps, then checking which of the six enterprise features your own screens actually touch.
Frequently asked questions
Does vxe-table work with Vue 2 and Vue 3 from the same package?
No. The project keeps a v3 branch for vue 2.6 through 2.7, long term support from v3.9, and a v4 branch for vue 3.x, long term support from v4.7, and the two lines publish separate releases such as v3.25.14 and v4.23.14 on 2026-11-03. Both branches keep features and APIs in sync, but they ship as two builds.
Is Excel copy and paste included in the free vxe-table package?
The feature checklist marks cell copy/paste as an enterprise edition item, alongside cell region selection, find and replace, aggregate functions, data summary and integrated charts, all linked to store.vxeui.com. The package description still advertises copy-paste support without that qualification.
How do I run the vxe-table examples locally?
npm run update installs dependencies, npm run serve starts the dev server through vue-cli-service serve, and npm run lib compiles the es and lib directories. Note that npm run update is defined as npm install --legacy-peer-deps rather than a plain install.
Can vxe-table still run in Internet Explorer?
The v3.0 line kept IE11 compatibility, and both v3.0 and v4.0 are marked as stopped maintenance from 2020-03-01 to 2024-12-01. From v3.9 and v4.7 the project targets modern browsers only, and the design notes state that IE is not supported.
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/x-extends-vxe-table)Star history chart for your README
[](https://hysenlabs.com/projects/x-extends-vxe-table)Was this useful?