@svgrid/mcp 3.0.44 → 3.0.45

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/data.js CHANGED
@@ -5311,7 +5311,7 @@ export const docs = [
5311
5311
  "path": "docs/help/benchmarks.md",
5312
5312
  "title": "Performance benchmarks",
5313
5313
  "section": "Help",
5314
- "markdown": "# Performance benchmarks\n\nEvery number on this page is produced by a checked-in script:\n\n| Table | Command | Where it runs |\n| -------------------------- | --------------- | ------------- |\n| Bundle size | `pnpm size` | Node |\n| Sort / filter / group, memory | `pnpm bench` | Node |\n| First paint, scroll | `pnpm bench:dom` | Chromium |\n\nAn earlier version of this page published a table of timings that no\nscript produced, and told readers to reproduce them with a `pnpm bench`\ncommand that did not exist. Where a figure has since been re-measured and\ncame out worse than the old claim, the section says so rather than\nquietly restating it.\n\nThe one number worth trusting on any grid's benchmark page is the one you\nmeasured yourself, on your data shape, on your hardware. The\n[benchmark harness recipe](../recipes/benchmark-harness.md) is a\ncopy-paste `<SvGrid>` probe that measures time-to-first-paint across any\n(rows x columns) matrix.\n\nLive load - 100k rows x 100 columns with row + column virtualization:\n\n<div data-docs-demo=\"06-large-dataset\" data-height=\"500\"></div>\n\n## Test rig\n\nThe engine table below was measured on this configuration. Your absolute\nnumbers will differ; the ratios between rows are the transferable part.\n\n| Component | Spec |\n| --------- | ------------------------------------------------ |\n| Machine | Developer workstation, win32 x64. Not a dedicated bench rig |\n| Engine | Node v24.18.0, median of 9 runs after a warm-up |\n| Browser | Chromium via Playwright, best of 2 runs |\n| Dataset | 100,000 rows x 9 columns, seeded so runs compare |\n| Target | The built `@svgrid/grid/core`, not `src/` |\n\nMedian rather than mean, so one GC pause cannot move a number. The\n`min`/`max` columns the harness prints are worth reading: the spread on a\nsort run is around 10%, which is why **elapsed time is reported but never\ngated in CI**. What CI gates instead is described under\n[What CI enforces](#what-ci-enforces).\n\n## Bundle size\n\nProduction build, gzipped, Svelte excluded as a peer. The table is\ngenerated from `docs/_data/svgrid-size.json` by `node tools/sync-guide-facts.mjs`\n(the file `pnpm size:json` writes), and the method and the lazy-chunk\nbreakdown are on the [bundle size reference](./bundle-size.md). An earlier\nversion of this page typed these and sat a month behind the measurement.\n\n<!-- size:start -->\nRe-measured **10 Nov 2026** at `@svgrid/grid` 3.0.33 with the script that ships in the repo (`pnpm size:json`):\n\n| Target | Base JS (gzip) | CSS (gzip) | Loaded on demand |\n| --- | ---: | ---: | ---: |\n| Headless core (`createSvGrid`) | **3.2 KB** | - | - |\n| Headless subpath (`@svgrid/grid/core`) | **10.1 KB** | - | - |\n| Full render component (`<SvGrid>`) | **99.9 KB** | **11.3 KB** | **198.9 KB** |\n| Standalone chart (`<SvChart>`) | **71.9 KB** | - | **15.0 KB** |\n<!-- size:end -->\n\nThe \"loaded on demand\" column is the code reachable only through\n`import()`: charts, the date-time editor, the menus, export. Outside the\ngrid package, and not in the ledger: the `@svgrid/enterprise` core is a few\nkilobytes of export, print and import shells; `jszip` loads on the first\nxlsx export or import and `pdfmake` with its fonts on the first PDF export,\nboth as optional peers, neither in your synchronous bundle.\n\nThe AI helpers are no longer in this table: they moved into the free\n`@svgrid/grid` and tree-shake out unless you import them.\n\nTree-shaking is friendly: importing `{ SvGrid, tableFeatures }`\nwithout `rowSortingFeature` doesn't pull the sort module.\n\n## First paint\n\n**Measured.** Run `pnpm bench:dom`. Driven against demo\n`06-large-dataset` in Chromium: click a dataset size, stop the clock on\nthe first painted frame that shows the new rows.\n\n| Scenario | Total | Building the data | Grid |\n| ------------------- | -------- | ----------------- | ------- |\n| 1,000 x 29 cols | 180 ms | 3 ms | 177 ms |\n| 10,000 x 53 cols | 315 ms | 31 ms | 284 ms |\n| 50,000 x 77 cols | 652 ms | 220 ms | 432 ms |\n| 100,000 x 100 cols | 1,205 ms | 633 ms | 572 ms |\n\n\"Building the data\" is the demo generating synthetic rows - at the top\nsize that is 9.5 million cells of test data, which a real app with data\nalready in hand does not pay. \"Grid\" is the remainder.\n\n**\"Grid\" overstates the grid's own cost, and by a lot.** A CPU profile of\nthe 100k x 100 mount attributes 28% of the window to the demo's data\ngenerator and another 14% to garbage collection, most of it cleaning up\nafter that generator. The demo's self-reported build time counts only the\ngenerator's own execution, not the GC pressure it creates, so subtracting\nit leaves a good deal of the demo's cost inside the \"Grid\" column. Roughly\nhalf the total is the harness rather than the component.\n\nTwo further caveats:\n\n- These come from a developer machine, not a dedicated bench rig, and\n run-to-run variance is roughly 2x. Treat the column ratios as the\n signal and the absolute values as a ceiling.\n- **The row-pipeline optimisations above did not move these numbers**, and\n should not be read as having done so. Mounting a grid with no sort and no\n filter never enters those code paths; both row models return early.\n\nAn earlier version of this page claimed 110 ms for the 100k x 100 case,\nwhich was never measured. Getting a trustworthy figure needs a mount\nharness that feeds pre-built data, so the number is not dominated by the\ncost of inventing it.\n\n## Scroll performance\n\n**Measured.** Run `pnpm bench:dom`. Sustained vertical scroll at 60\npx/frame over 240 frames, sampling the interval between animation frames:\n\n| Scenario | p50 | p95 | max | Dropped frames |\n| ---------------------- | ------- | ------- | ------- | -------------- |\n| 100k rows x 100 cols | 16.7 ms | 17.7 ms | 18.8 ms | 0 of 240 |\n| 1,000,000 rows x 9 cols | 16.7 ms | 18.1 ms | 19.1 ms | 0 of 240 |\n\nThis is the part of the grid that holds up well: a million rows scrolls\nwithout dropping a frame, and the 100-column case is indistinguishable\nfrom it because row and column virtualization are the same machinery.\n\nRead the numbers correctly, though. The harness drives scrolling from\n`requestAnimationFrame`, so an interval can never come in below the\ndisplay refresh - 16.7 ms on a 60 Hz panel is the floor, not a\nmeasurement of how cheap a frame is. What the table shows is that the\ngrid **holds** the frame budget, with zero frames over 1.5x the median.\nIt cannot show headroom above 60 fps.\n\nAn earlier version of this page claimed a p95 of 8 ms and \"~120 fps\".\nNo harness in the repository could have produced that figure, and this\none structurally cannot.\n\n> Video: One million rows in SvGrid\n\nTranscript: This SvGrid holds one million rows, generated in the browser, with sorting, filtering and inline editing switched on. Rows are virtualized, so only the ones in view are drawn. Scroll, and the frame rate stays flat. Jump anywhere in the set. The row numbers show the scale, and the grid keeps every row reachable. Row and column virtualization are the same machinery, so wide grids get the same treatment. Nothing to configure.\n\n## Sort, filter, group\n\n**Measured.** Run `pnpm bench` to reproduce. In-memory row-pipeline\noperations on 100,000 rows x 9 columns:\n\n| Operation | Median | Was | Change |\n| --------------------------------------------- | ------- | ------- | ------ |\n| Sort by one column | 27 ms | 351 ms | 13x |\n| Sort by three columns (multi-sort) | 48 ms | 569 ms | 12x |\n| Sort by a date column | 40 ms | 773 ms | 19x |\n| Sort by a text column (collated) | 59 ms | - | new |\n| Filter, one operator | 5 ms | 19 ms | 4x |\n| Filter, five operators ANDed | 7 ms | 24 ms | 3.5x |\n| Filter via the compiled Excel filter | 3 ms | - | new |\n| ... the same, on fully accented text | 22 ms | - | new |\n| Group by two columns + three aggregators | 50 ms | 229 ms | 4.6x |\n| Toggle one row's checkbox (filtered + sorted) | 0 ms | 103 ms | gone |\n| Export CSV, 10k rows x 9 cols | 10 ms | 8 ms | - |\n\nThe last two rows are the path `<SvGrid>` actually takes. The plain \"filter,\none operator\" rows drive the headless row model, whose default match is a\nsubstring compare - but the menu and filter-row surfaces compile through\n`compileExcelFilter`, which folds every value (decompose, strip diacritics,\nlowercase) so that \"cafe\" matches \"CAFÉ\". This suite had no case touching\nthat fold until a browser profile showed it was the most expensive single\nfunction in a filter. It now takes a fast path for pure-ASCII values, where\ndecomposition and diacritic-stripping are provably no-ops: 3 ms rather than\n21 ms for the same 100,000 rows. Accented data still pays the full fold,\nwhich is the 21 ms row, and gets the same answer it always did.\n\nEach case runs in a **fresh process**. They used to share one, which made\nevery figure depend on the order cases ran in: a case running eighth\ncarried seven predecessors' heap, and grouping measured 169 ms in a full\nrun against 51 ms on its own. An earlier version of this table published\nthe contaminated 106 ms for grouping. Forcing a garbage collection between\ncases did not fix it - the cost is a warmed, fragmented heap rather than\nuncollected garbage - so the harness now pays a few seconds of process\nstartup per case and reports numbers that mean the same thing whether you\nrun one case or all of them.\n\nText sorting has no \"was\", because this suite did not measure it until a\nbrowser comparison showed it was the slowest operation for every grid\ntested. Collation is what makes it expensive, and two things help:\n\n- **Columns whose distinct values are far fewer than their rows** - a\n status, a region, an owner - collate the distinct values once and sort\n rows by rank. That is what took the three-column case to 48 ms. A stride\n sample decides whether to try, because collecting distinct values costs\n about 9 ms on a column where nearly all of them are unique and saves\n about 19 ms where they repeat, so guessing wrong either way is\n measurable.\n- **`localeCompare` rather than a hoisted `Intl.Collator`.** The\n specification defines the former as constructing a collator per call, so\n caching one looks like the obvious win - and it is measurably slower,\n because V8 fast-paths `localeCompare` and going through a collator object\n misses that path. 33 ms against 83 ms sorting 100k ASCII strings, with\n byte-identical ordering. This page briefly published the slower version;\n re-measure before \"optimising\" it again.\n\nA third thing helps every sort: **the single-clause case gets its own\ncomparator.** Most sorts are one column, and the comparator runs O(n log n)\ntimes - 1.66 million calls for 100,000 rows - so the general loop's clause\nlookup, property loads and indirect call are paid 1.66 million times for\nvalues that never change. Hoisting them into a closure, and inlining the\nsubtraction for numeric columns, is worth about 15% on a single-column sort.\n\nGrouping got faster for a different reason: a group row shows the value\nits children agree on, and finding that used to mean scanning every child\neven for a column an outer level had already grouped by, where the answer\nis fixed by construction.\n\nMedians hold steady across runs; the min/max the harness also prints do\nnot, because this is a working developer machine rather than a quiet bench\nrig. A single sample can land 3x the median when something else on the box\nwakes up. That noise is the whole reason CI gates counters instead.\n\nThe \"Was\" column is the first measurement this harness took, before any of\nit was optimised. Building the harness is what exposed the defects; each\none is now closed and has a counter that fails the build if it returns:\n\n- **Sorting resolved the clause's column inside the comparator.** A\n single-clause sort of 100k rows called `getAllColumns()` 1,528,947\n times, scanning the column array on each. It now resolves once, and the\n comparator reads a precomputed key array instead of walking the row.\n- **The date comparator allocated two `Date` objects per comparison.**\n Timestamps are now computed once per row, which is most of why sorting a\n date column went from the slowest case to a fast one.\n- **Filtering materialised every row's full `Cell[]`** to read one field,\n defeating the lazy per-row cell cache: 100,000 cell arrays built and\n thrown away for a one-operator filter. Now zero.\n- **Toggling a checkbox re-ran the whole pipeline.** `rowSelection` sat in\n the row-model cache key, so selecting a row re-filtered and re-sorted the\n entire dataset even though nothing in the pipeline reads it. Selection is\n now free.\n- **Group aggregation allocated three arrays per aggregated column per\n group**, then finished with `Math.min(...values)`. It is a single pass\n now. The spread also crashed outright on a large enough group, which is\n fixed as a side effect.\n- **Text sorting collated on every comparison.** Distinct values are now\n ranked once where a column has few enough of them.\n\nNumbers here will move; the command that produces them will not.\n\n## Streaming updates\n\n**Measured.** Run `pnpm bench --case=tick-1k-of-100k-sorted` to reproduce.\nA tick is a new data array in which K row objects were replaced with new\nprices, handed to a grid sorted by that column, so the order has to stay\ncurrent. 100,000 rows x 9 columns, same rig as above:\n\n| Operation | Median | The same tick through a full sort |\n| ---------------------------------------------------- | ------ | --------------------------------- |\n| Tick: 100 rows replaced, sorted by the ticking column | 6 ms | 31 ms |\n| Tick: 1,000 rows replaced, sorted by the ticking column | 9 ms | 31 ms |\n\nThe right-hand column is the \"Sort by one column\" row above: before this\nround, any new data array re-sorted every row, so a 100-row tick cost\nexactly what a header click did. The sorted stage now keeps its previous\noutput with each row's sort key, drops the rows that were replaced, sorts\nthe K replacements among themselves and merges them back in one linear\npass: O(n + K log K) instead of O(n log n) key builds and comparisons. The\nfiltered stage does the same for a replacement whose membership did not\nchange. The result is byte-identical to a full sort, which a test pins by\ncomparing the two on every kind of key the sort specialises\n(`core.tick-repair.test.ts`).\n\nThree conditions, all checked, none assumed: the array has the same length\n(an add or a remove is structural and takes the full path), at least one\nobject was replaced and no more than a quarter of them (a new array with\nevery object the same is the documented \"I mutated rows in place, re-read\nthem\" refresh and runs the full pipeline), and the sorting state, filters\nand columns are the same objects as last time. The rows that were kept are\nassumed unchanged in value as well as identity, which is what an immutable\nupdate guarantees and an in-place mutation does not: a feed that mutates\nrows in place must pass a new array with no replacements to refresh.\n\nThe counter CI gates for this is cell reads on the kept rows during a tick,\nbudgeted at zero: a repaired sort never re-reads a row it kept, a full sort\nreads all of them.\n\nWhat the component adds on top of the engine per tick is a rebuild of the\nbase rows (2 ms at 100k, reusing every row object that did not change) and\nthe render of the visible window. Three things on that path used to be\nO(rows) per data change and are not now: the header checkbox state walked\nevery row to conclude \"none selected\" (30 ms at 100k), the expanded-rows\nstage copied all rows into a new array with nothing expanded, and the\ndev-time config check filtered every row to pick ten samples. The browser\nharness in the [comparison](./comparison.md) measures the whole thing,\nrender included, against the other grids on the same tick; that column\nlands with its next recorded run.\n\n## Spreadsheet engine\n\n**Measured.** Run `pnpm bench` with `@svgrid/enterprise` built\n(`pnpm --filter @svgrid/enterprise build:lib`) to reproduce; the cases live\nin `tools/bench/sheet-cases.mjs`. These were taken on a CI-class Linux\ncontainer with Node v22, not the workstation the table above used, so\ncompare the rows with each other rather than with the grid's.\n\nTwo different questions, because a spreadsheet is asked both: what does\nopening a workbook full of formulas cost once, and what does one keystroke\ncost all day.\n\n| Case | Median | Cells evaluated | Retained |\n| -------------------------------------------------------- | ------- | --------------- | -------- |\n| Open 1,000 rows, one `SUM` per row | 8 ms | 1,000 | 1.6 MB |\n| Open 10,000 rows, one `SUM` per row | 91 ms | 10,000 | 16.5 MB |\n| Open 50,000 rows, one `SUM` per row | 547 ms | 50,000 | 84.2 MB |\n| Type in one cell of a 10,000-row sheet | 0 ms | 1 | - |\n| Type in a column a single `SUM` of 10,000 cells reads | 14 ms | 1 | - |\n| Type at the top of a 10,000-row dependency chain | 71 ms | 10,000 | - |\n\nRead the third column first: it is the one CI gates, and the one that says\nwhat the engine is doing. A keystroke costs **one evaluation**, not a\nsheet's worth, because the dependency graph recomputes what read the cell\nand nothing else. The column-`SUM` row is the interesting pair: one\nevaluation, 14 ms, because that single `SUM` re-reads its 10,000 cells. The\nchain row is the worst case a sheet can have, a running balance where every\nrow reads the row above it: 10,000 evaluations for one keystroke, which is\nthe true cost of that shape and not a bug.\n\nSo the practical ceiling, on this container: **a sheet of tens of thousands\nof formula rows opens in well under a second and edits instantly**, and the\nthing that changes that is not the sheet's size but how much of it one cell\nfeeds. 50,000 formula rows retain about 84 MB, roughly 1.7 KB per row for\nthe text, the cached value and the graph edges.\n\nA chain longer than about a thousand rows used to overflow the JavaScript\nstack on the first keystroke and land `#NUM!` in the cell. The workbook now\nprimes a deep chain from its far end instead of recursing through it, so\nthe only limit left is the sheet's own size.\n\n## What CI enforces\n\nElapsed time is too noisy on a shared runner to fail a build on, and a\nflaky performance gate gets switched off within a month. So `pnpm\nbench:check` gates **work counters** instead - counts of algorithmic work,\nidentical on every machine:\n\n| Counter | Budget | Actual |\n| --------------------------------------------- | ------ | ------ |\n| `getAllColumns` calls inside a 1-clause sort | 8 | 1 |\n| `getAllColumns` calls inside a 3-clause sort | 24 | 1 |\n| `getAllCells` materialisations while filtering | 0 | 0 |\n| Filter re-runs caused by a selection change | 0 | 0 |\n| Sort re-runs caused by a selection change | 0 | 0 |\n| Cells evaluated opening a 10,000-row sheet | 10,004 | 10,000 |\n| Cells evaluated by one keystroke in that sheet | 4 | 1 |\n| Cells evaluated when a 10,000-cell `SUM` reads the edit | 3 | 1 |\n\nA count is a claim about the algorithm; a millisecond is a claim about the\nhardware. Only the first belongs in CI. Budgets live beside each case in\n`tools/bench/cases.mjs`, and the spreadsheet's in\n`tools/bench/sheet-cases.mjs`.\n\nEach case also declares which counters must be *present*, not just within\nbudget. Without that, a stage that stopped running altogether would satisfy\nevery budget by doing no work, which is the failure mode a gate like this\nis most likely to develop.\n\n## Memory\n\n**Measured** (`pnpm bench`, Node heap): building the row model for\n100,000 rows x 9 columns with no sort, filter or grouping retains\n**0.8 MB**, with no renderer attached. A row object is made the first time\nsomething reads it, so a grid showing twenty rows makes a screenful of\nthem, not 100,000.\n\nThe first sort, filter or grouping reads every row and makes them all. The\nbrowser harness measures that as the \"after sorting and filtering\" row in\nthe [comparison](./comparison.md#measured-performance): 17.8 MB at\n100,000 rows, and 128 MB at 1,000,000 (27 Oct 2026,\n`BENCH_ROWS=1000000 BENCH_GRIDS=svgrid pnpm bench:compare`), so about 130\nbytes a row: the row object, its id, and the sort key it keeps so a live\nupdate can be merged in without re-reading the rows. The 1,000,000-row\nfigure was 196 MB the day before. Reading one column used to build an\narray of every column's value on every row and keep it there, which only\nthe rows on screen use; a plain `field` column is now read from the data,\nand only a computed (`fieldFn`) column still builds the array.\n\nThe fully built row model was 16.0 MB at 100,000 rows before rows became\nlazy, and 64.9 MB before that. Each row was an object literal whose seven\nmethods were closures, so a 100k-row grid allocated 700k closures and a\nclosure scope per row before painting anything. The methods are now\ndefined once and shared, reading their row through `this`: 4x less memory\nand about 7x faster to build. They are still assigned as own properties\nrather than put on a prototype, because `Row` is public and several row\nmodels legitimately do `{ ...row, depth }` - a spread copies own\nproperties but not a prototype, so a class would silently strip the\nmethods off a cloned row.\n\nAn earlier version of this page said \"~22 MB\". That figure was not\nmeasured. Node's heap accounting is not the same as a browser's, so read\nthis as the engine's own cost rather than what a tab will show.\n\nTwo claims here are structural rather than measured, and both hold:\n\n- Virtualization keeps the rendered DOM to the visible window regardless\n of dataset size, so `<td>` count does not scale with row count.\n- No retained references when the grid unmounts - the cleanup path is\n exercised by the unmount test in `svgrid.behavior.test.ts`.\n\n## Server-side / chunked loading\n\nDemo [33. Server-side infinite scroll](https://svgrid.com/demos/33-server-infinite/) covers the chunked-load path. Numbers from that demo:\n\n| Scenario | Result |\n| ------------------------------------------------ | --------------------------------------- |\n| Initial paint, sparse 100k-row dataset | 110 ms to first chunk visible |\n| Scroll 50,000 rows in 1.5 s (fast wheel-flick) | 16 chunk requests cancelled mid-flight |\n| Sort 100k server-side rows | round-trip dominated by the mock latency (50-140 ms) |\n\n### The Server-Side Row Model over one million rows\n\nDemo [467](https://svgrid.com/demos/467-server-row-model-1m/) runs the\nEnterprise row model over a columnar in-memory warehouse of a million rows,\ngrouped Region > Country. `tests/perf/server-row-model.spec.ts` drives it in\nheadless Chromium (a developer workstation, 17 September 2026; a release\nritual, not a gate):\n\n| Scenario | Result |\n| ------------------------------------------------------------- | --------------------------------------------- |\n| First paint, navigation to the first group row (includes building the warehouse in the page) | 2.4 s |\n| Scroll 60,000 px through an open country of 62,000 leaves | 17 leaf requests, 0.28 per 1,000 px (one block of 100 rows is 3,400 px) |\n| Worst frame while blocks streamed in | 83 ms (layout of the changed rows; the grid keeps the row objects a block did not touch) |\n| Heap before / after streaming 700,000 px with `maxBlocksInCache: 24` | 225 MB / 225 MB - evicted blocks are collected |\n| Warehouse: a million rows as typed arrays | 22 MB; a cold sort on a new column 0.8 to 1.1 s, cached after; a grouped level 140 ms; a pivot with a grand total 330 ms |\n\n## AI helpers\n\nEnd-to-end timings against the bundled `mockAIProvider`:\n\n| Helper | Median time (ms) |\n| --------------- | ---------------- |\n| `aiFilter` | 350-750 (mock latency dominated) |\n| `aiSmartFill` (50 rows) | 400-900 |\n| `aiSummarize` | 350-750 |\n| `aiClassify` (20 rows) | 400-750 |\n\nAgainst a real model the latency is provider-side. The grid's own\nprompt-build + result-parse work stays under ~6 ms even for 1000-row\nclassify jobs.\n\n## Import / export\n\n| Operation | Time |\n| ------------------------------------ | ------ |\n| Parse CSV, 10k rows × 9 cols | 28 ms |\n| Parse xlsx, 10k rows × 9 cols | 140 ms (jszip unzip-dominated) |\n| Export CSV, 10k rows × 9 cols | 18 ms |\n| Export xlsx, 10k rows × 9 cols | 220 ms |\n| Export PDF, 1k rows × 9 cols (pdfmake) | 700 ms |\n\n## Reproducing locally\n\n```bash\ngit clone https://github.com/sv-grid/sv-grid\ncd sv-grid\npnpm install\npnpm --filter @svgrid/grid build # the bench runs the BUILT engine\npnpm bench # engine + memory tables\npnpm size # bundle table\npnpm bench:dom # first paint + scroll, in Chromium\n```\n\nThe bench takes a few options:\n\n```bash\npnpm bench --json # machine-readable, for trend tracking\npnpm bench --baseline=tools/bench/baseline.json # adds a delta column\npnpm bench --case=sort-1col # one case\npnpm bench:check # the work-counter gate CI runs\n```\n\n`pnpm bench` runs against the built `@svgrid/grid/core` rather than\n`src/`, so it also smoke-tests the entry a consumer actually imports.\n\n`pnpm bench:dom` drives Chromium through Playwright against the examples\ngallery, which lives in this repository, so it needs no private\nsubmodule. It is a Playwright project rather than part of `pnpm test:e2e`,\nand it is deliberately not in CI - see below.\n\nFor your own workload, the [benchmark harness\nrecipe](../recipes/benchmark-harness.md) and the [FPS HUD\nrecipe](../recipes/profiling-with-fps-hud.md) are copy-paste probes you\ncan drop into your app.\n\n## What we *don't* claim\n\n- That we are faster than any other grid. Nothing on *this* page is a\n head-to-head measurement. Everything here is sv-grid measured against\n sv-grid, which supports \"this got 10x faster\" and not \"this is faster\n than X\". For a real comparison there is a separate grid-agnostic\n harness - `pnpm bench:compare`, results and caveats in\n [Comparison](./comparison.md) - and it does not say we win everything.\n- That first paint is good. The grid half of the 100k x 100 case is still\n the worst number on this page, and this round did not touch it.\n- Any scroll figure above 60 fps. The harness is rAF-driven and cannot\n observe headroom past the display refresh. \"Zero dropped frames\" is the\n claim; \"120 fps\" is not.\n- Lab-grade first-paint numbers. Those come from a developer machine with\n roughly 2x run-to-run variance, not a dedicated rig.\n- \"Smoothest grid on the market\" - that depends entirely on what your\n cells render. A sparkline + currency formatter in every cell costs\n more than a number, and we don't pretend otherwise.\n- \"Zero allocations during scroll\" - the virtualizer recycles DOM\n nodes but cell snippets still allocate. The numbers above include\n real-world snippets (status pills, mini-bars).\n- Single-thread performance > 1M rows. For >1M, do the heavy lifting\n on the server and feed chunks through the [server-side infinite\n scroll pattern](https://svgrid.com/demos/33-server-infinite/).\n\n## Frequently asked questions\n\n### How fast is SvGrid?\n\nIt virtualizes both rows and columns, so only the visible window is in the DOM,\nand a million rows scrolls without dropping a frame. On the data side, a\nsingle-column sort of 100,000 rows takes about 27 ms and a one-operator filter\nabout 5 ms. Every table on this page comes from a checked-in script you can run\nyourself, and the numbers moved because the harness exposed real defects rather\nthan because the prose was rewritten.\n\n### How many rows can SvGrid handle?\n\nClient-side, 100k+ rows scroll smoothly thanks to virtualization. For millions\nof rows, page or chunk from the server (see Server-side data). The DOM only ever\nholds the visible window regardless of total row count.\n\n### How fast is SvGrid, and how big is it?\n\nIt ships a small bundle (the measured figures for the full render component\nand for the headless core alone are in the table above) and virtualizes by\ndefault. Raw scroll\nperformance is comparable for typical workloads; the bigger practical win is\nbundle size and a Svelte-native runtime with no framework bridge.\n\n## See also\n\n- [Browser support](./browser-support.md) - the matrix the benchmarks\n ran against.\n- [Testing and quality](./testing-and-quality.md) - the coverage\n thresholds that gate every release.\n"
5314
+ "markdown": "# Performance benchmarks\n\nEvery number on this page is produced by a checked-in script:\n\n| Table | Command | Where it runs |\n| -------------------------- | --------------- | ------------- |\n| Bundle size | `pnpm size` | Node |\n| Sort / filter / group, memory | `pnpm bench` | Node |\n| First paint, scroll | `pnpm bench:dom` | Chromium |\n\nAn earlier version of this page published a table of timings that no\nscript produced, and told readers to reproduce them with a `pnpm bench`\ncommand that did not exist. Where a figure has since been re-measured and\ncame out worse than the old claim, the section says so rather than\nquietly restating it.\n\nThe one number worth trusting on any grid's benchmark page is the one you\nmeasured yourself, on your data shape, on your hardware. The\n[benchmark harness recipe](../recipes/benchmark-harness.md) is a\ncopy-paste `<SvGrid>` probe that measures time-to-first-paint across any\n(rows x columns) matrix.\n\nLive load - 100k rows x 100 columns with row + column virtualization:\n\n<div data-docs-demo=\"06-large-dataset\" data-height=\"500\"></div>\n\n## Test rig\n\nThe engine table below was measured on this configuration. Your absolute\nnumbers will differ; the ratios between rows are the transferable part.\n\n| Component | Spec |\n| --------- | ------------------------------------------------ |\n| Machine | Developer workstation, win32 x64. Not a dedicated bench rig |\n| Engine | Node v24.18.0, median of 9 runs after a warm-up |\n| Browser | Chromium via Playwright, best of 2 runs |\n| Dataset | 100,000 rows x 9 columns, seeded so runs compare |\n| Target | The built `@svgrid/grid/core`, not `src/` |\n\nMedian rather than mean, so one GC pause cannot move a number. The\n`min`/`max` columns the harness prints are worth reading: the spread on a\nsort run is around 10%, which is why **elapsed time is reported but never\ngated in CI**. What CI gates instead is described under\n[What CI enforces](#what-ci-enforces).\n\n## Bundle size\n\nProduction build, gzipped, Svelte excluded as a peer. The table is\ngenerated from `docs/_data/svgrid-size.json` by `node tools/sync-guide-facts.mjs`\n(the file `pnpm size:json` writes), and the method and the lazy-chunk\nbreakdown are on the [bundle size reference](./bundle-size.md). An earlier\nversion of this page typed these and sat a month behind the measurement.\n\n<!-- size:start -->\nRe-measured **10 Nov 2026** at `@svgrid/grid` 3.0.34 with the script that ships in the repo (`pnpm size:json`):\n\n| Target | Base JS (gzip) | CSS (gzip) | Loaded on demand |\n| --- | ---: | ---: | ---: |\n| Headless core (`createSvGrid`) | **3.2 KB** | - | - |\n| Headless subpath (`@svgrid/grid/core`) | **10.2 KB** | - | - |\n| Full render component (`<SvGrid>`) | **99.6 KB** | **11.4 KB** | **206.3 KB** |\n| Standalone chart (`<SvChart>`) | **71.9 KB** | - | **16.0 KB** |\n<!-- size:end -->\n\nThe \"loaded on demand\" column is the code reachable only through\n`import()`: charts, the date-time editor, the menus, export. Outside the\ngrid package, and not in the ledger: the `@svgrid/enterprise` core is a few\nkilobytes of export, print and import shells; `jszip` loads on the first\nxlsx export or import and `pdfmake` with its fonts on the first PDF export,\nboth as optional peers, neither in your synchronous bundle.\n\nThe AI helpers are no longer in this table: they moved into the free\n`@svgrid/grid` and tree-shake out unless you import them.\n\nTree-shaking is friendly: importing `{ SvGrid, tableFeatures }`\nwithout `rowSortingFeature` doesn't pull the sort module.\n\n## First paint\n\n**Measured.** Run `pnpm bench:dom`. Driven against demo\n`06-large-dataset` in Chromium: click a dataset size, stop the clock on\nthe first painted frame that shows the new rows.\n\n| Scenario | Total | Building the data | Grid |\n| ------------------- | -------- | ----------------- | ------- |\n| 1,000 x 29 cols | 180 ms | 3 ms | 177 ms |\n| 10,000 x 53 cols | 315 ms | 31 ms | 284 ms |\n| 50,000 x 77 cols | 652 ms | 220 ms | 432 ms |\n| 100,000 x 100 cols | 1,205 ms | 633 ms | 572 ms |\n\n\"Building the data\" is the demo generating synthetic rows - at the top\nsize that is 9.5 million cells of test data, which a real app with data\nalready in hand does not pay. \"Grid\" is the remainder.\n\n**\"Grid\" overstates the grid's own cost, and by a lot.** A CPU profile of\nthe 100k x 100 mount attributes 28% of the window to the demo's data\ngenerator and another 14% to garbage collection, most of it cleaning up\nafter that generator. The demo's self-reported build time counts only the\ngenerator's own execution, not the GC pressure it creates, so subtracting\nit leaves a good deal of the demo's cost inside the \"Grid\" column. Roughly\nhalf the total is the harness rather than the component.\n\nTwo further caveats:\n\n- These come from a developer machine, not a dedicated bench rig, and\n run-to-run variance is roughly 2x. Treat the column ratios as the\n signal and the absolute values as a ceiling.\n- **The row-pipeline optimisations above did not move these numbers**, and\n should not be read as having done so. Mounting a grid with no sort and no\n filter never enters those code paths; both row models return early.\n\nAn earlier version of this page claimed 110 ms for the 100k x 100 case,\nwhich was never measured. Getting a trustworthy figure needs a mount\nharness that feeds pre-built data, so the number is not dominated by the\ncost of inventing it.\n\n## Scroll performance\n\n**Measured.** Run `pnpm bench:dom`. Sustained vertical scroll at 60\npx/frame over 240 frames, sampling the interval between animation frames:\n\n| Scenario | p50 | p95 | max | Dropped frames |\n| ---------------------- | ------- | ------- | ------- | -------------- |\n| 100k rows x 100 cols | 16.7 ms | 17.7 ms | 18.8 ms | 0 of 240 |\n| 1,000,000 rows x 9 cols | 16.7 ms | 18.1 ms | 19.1 ms | 0 of 240 |\n\nThis is the part of the grid that holds up well: a million rows scrolls\nwithout dropping a frame, and the 100-column case is indistinguishable\nfrom it because row and column virtualization are the same machinery.\n\nRead the numbers correctly, though. The harness drives scrolling from\n`requestAnimationFrame`, so an interval can never come in below the\ndisplay refresh - 16.7 ms on a 60 Hz panel is the floor, not a\nmeasurement of how cheap a frame is. What the table shows is that the\ngrid **holds** the frame budget, with zero frames over 1.5x the median.\nIt cannot show headroom above 60 fps.\n\nAn earlier version of this page claimed a p95 of 8 ms and \"~120 fps\".\nNo harness in the repository could have produced that figure, and this\none structurally cannot.\n\n> Video: One million rows in SvGrid\n\nTranscript: This SvGrid holds one million rows, generated in the browser, with sorting, filtering and inline editing switched on. Rows are virtualized, so only the ones in view are drawn. Scroll, and the frame rate stays flat. Jump anywhere in the set. The row numbers show the scale, and the grid keeps every row reachable. Row and column virtualization are the same machinery, so wide grids get the same treatment. Nothing to configure.\n\n## Sort, filter, group\n\n**Measured.** Run `pnpm bench` to reproduce. In-memory row-pipeline\noperations on 100,000 rows x 9 columns:\n\n| Operation | Median | Was | Change |\n| --------------------------------------------- | ------- | ------- | ------ |\n| Sort by one column | 27 ms | 351 ms | 13x |\n| Sort by three columns (multi-sort) | 48 ms | 569 ms | 12x |\n| Sort by a date column | 40 ms | 773 ms | 19x |\n| Sort by a text column (collated) | 59 ms | - | new |\n| Filter, one operator | 5 ms | 19 ms | 4x |\n| Filter, five operators ANDed | 7 ms | 24 ms | 3.5x |\n| Filter via the compiled Excel filter | 3 ms | - | new |\n| ... the same, on fully accented text | 22 ms | - | new |\n| Group by two columns + three aggregators | 50 ms | 229 ms | 4.6x |\n| Toggle one row's checkbox (filtered + sorted) | 0 ms | 103 ms | gone |\n| Export CSV, 10k rows x 9 cols | 10 ms | 8 ms | - |\n\nThe last two rows are the path `<SvGrid>` actually takes. The plain \"filter,\none operator\" rows drive the headless row model, whose default match is a\nsubstring compare - but the menu and filter-row surfaces compile through\n`compileExcelFilter`, which folds every value (decompose, strip diacritics,\nlowercase) so that \"cafe\" matches \"CAFÉ\". This suite had no case touching\nthat fold until a browser profile showed it was the most expensive single\nfunction in a filter. It now takes a fast path for pure-ASCII values, where\ndecomposition and diacritic-stripping are provably no-ops: 3 ms rather than\n21 ms for the same 100,000 rows. Accented data still pays the full fold,\nwhich is the 21 ms row, and gets the same answer it always did.\n\nEach case runs in a **fresh process**. They used to share one, which made\nevery figure depend on the order cases ran in: a case running eighth\ncarried seven predecessors' heap, and grouping measured 169 ms in a full\nrun against 51 ms on its own. An earlier version of this table published\nthe contaminated 106 ms for grouping. Forcing a garbage collection between\ncases did not fix it - the cost is a warmed, fragmented heap rather than\nuncollected garbage - so the harness now pays a few seconds of process\nstartup per case and reports numbers that mean the same thing whether you\nrun one case or all of them.\n\nText sorting has no \"was\", because this suite did not measure it until a\nbrowser comparison showed it was the slowest operation for every grid\ntested. Collation is what makes it expensive, and two things help:\n\n- **Columns whose distinct values are far fewer than their rows** - a\n status, a region, an owner - collate the distinct values once and sort\n rows by rank. That is what took the three-column case to 48 ms. A stride\n sample decides whether to try, because collecting distinct values costs\n about 9 ms on a column where nearly all of them are unique and saves\n about 19 ms where they repeat, so guessing wrong either way is\n measurable.\n- **`localeCompare` rather than a hoisted `Intl.Collator`.** The\n specification defines the former as constructing a collator per call, so\n caching one looks like the obvious win - and it is measurably slower,\n because V8 fast-paths `localeCompare` and going through a collator object\n misses that path. 33 ms against 83 ms sorting 100k ASCII strings, with\n byte-identical ordering. This page briefly published the slower version;\n re-measure before \"optimising\" it again.\n\nA third thing helps every sort: **the single-clause case gets its own\ncomparator.** Most sorts are one column, and the comparator runs O(n log n)\ntimes - 1.66 million calls for 100,000 rows - so the general loop's clause\nlookup, property loads and indirect call are paid 1.66 million times for\nvalues that never change. Hoisting them into a closure, and inlining the\nsubtraction for numeric columns, is worth about 15% on a single-column sort.\n\nGrouping got faster for a different reason: a group row shows the value\nits children agree on, and finding that used to mean scanning every child\neven for a column an outer level had already grouped by, where the answer\nis fixed by construction.\n\nMedians hold steady across runs; the min/max the harness also prints do\nnot, because this is a working developer machine rather than a quiet bench\nrig. A single sample can land 3x the median when something else on the box\nwakes up. That noise is the whole reason CI gates counters instead.\n\nThe \"Was\" column is the first measurement this harness took, before any of\nit was optimised. Building the harness is what exposed the defects; each\none is now closed and has a counter that fails the build if it returns:\n\n- **Sorting resolved the clause's column inside the comparator.** A\n single-clause sort of 100k rows called `getAllColumns()` 1,528,947\n times, scanning the column array on each. It now resolves once, and the\n comparator reads a precomputed key array instead of walking the row.\n- **The date comparator allocated two `Date` objects per comparison.**\n Timestamps are now computed once per row, which is most of why sorting a\n date column went from the slowest case to a fast one.\n- **Filtering materialised every row's full `Cell[]`** to read one field,\n defeating the lazy per-row cell cache: 100,000 cell arrays built and\n thrown away for a one-operator filter. Now zero.\n- **Toggling a checkbox re-ran the whole pipeline.** `rowSelection` sat in\n the row-model cache key, so selecting a row re-filtered and re-sorted the\n entire dataset even though nothing in the pipeline reads it. Selection is\n now free.\n- **Group aggregation allocated three arrays per aggregated column per\n group**, then finished with `Math.min(...values)`. It is a single pass\n now. The spread also crashed outright on a large enough group, which is\n fixed as a side effect.\n- **Text sorting collated on every comparison.** Distinct values are now\n ranked once where a column has few enough of them.\n\nNumbers here will move; the command that produces them will not.\n\n## Streaming updates\n\n**Measured.** Run `pnpm bench --case=tick-1k-of-100k-sorted` to reproduce.\nA tick is a new data array in which K row objects were replaced with new\nprices, handed to a grid sorted by that column, so the order has to stay\ncurrent. 100,000 rows x 9 columns, same rig as above:\n\n| Operation | Median | The same tick through a full sort |\n| ---------------------------------------------------- | ------ | --------------------------------- |\n| Tick: 100 rows replaced, sorted by the ticking column | 6 ms | 31 ms |\n| Tick: 1,000 rows replaced, sorted by the ticking column | 9 ms | 31 ms |\n\nThe right-hand column is the \"Sort by one column\" row above: before this\nround, any new data array re-sorted every row, so a 100-row tick cost\nexactly what a header click did. The sorted stage now keeps its previous\noutput with each row's sort key, drops the rows that were replaced, sorts\nthe K replacements among themselves and merges them back in one linear\npass: O(n + K log K) instead of O(n log n) key builds and comparisons. The\nfiltered stage does the same for a replacement whose membership did not\nchange. The result is byte-identical to a full sort, which a test pins by\ncomparing the two on every kind of key the sort specialises\n(`core.tick-repair.test.ts`).\n\nThree conditions, all checked, none assumed: the array has the same length\n(an add or a remove is structural and takes the full path), at least one\nobject was replaced and no more than a quarter of them (a new array with\nevery object the same is the documented \"I mutated rows in place, re-read\nthem\" refresh and runs the full pipeline), and the sorting state, filters\nand columns are the same objects as last time. The rows that were kept are\nassumed unchanged in value as well as identity, which is what an immutable\nupdate guarantees and an in-place mutation does not: a feed that mutates\nrows in place must pass a new array with no replacements to refresh.\n\nThe counter CI gates for this is cell reads on the kept rows during a tick,\nbudgeted at zero: a repaired sort never re-reads a row it kept, a full sort\nreads all of them.\n\nWhat the component adds on top of the engine per tick is a rebuild of the\nbase rows (2 ms at 100k, reusing every row object that did not change) and\nthe render of the visible window. Three things on that path used to be\nO(rows) per data change and are not now: the header checkbox state walked\nevery row to conclude \"none selected\" (30 ms at 100k), the expanded-rows\nstage copied all rows into a new array with nothing expanded, and the\ndev-time config check filtered every row to pick ten samples. The browser\nharness in the [comparison](./comparison.md) measures the whole thing,\nrender included, against the other grids on the same tick; that column\nlands with its next recorded run.\n\n## Spreadsheet engine\n\n**Measured.** Run `pnpm bench` with `@svgrid/enterprise` built\n(`pnpm --filter @svgrid/enterprise build:lib`) to reproduce; the cases live\nin `tools/bench/sheet-cases.mjs`. These were taken on a CI-class Linux\ncontainer with Node v22, not the workstation the table above used, so\ncompare the rows with each other rather than with the grid's.\n\nTwo different questions, because a spreadsheet is asked both: what does\nopening a workbook full of formulas cost once, and what does one keystroke\ncost all day.\n\n| Case | Median | Cells evaluated | Retained |\n| -------------------------------------------------------- | ------- | --------------- | -------- |\n| Open 1,000 rows, one `SUM` per row | 8 ms | 1,000 | 1.6 MB |\n| Open 10,000 rows, one `SUM` per row | 91 ms | 10,000 | 16.5 MB |\n| Open 50,000 rows, one `SUM` per row | 547 ms | 50,000 | 84.2 MB |\n| Type in one cell of a 10,000-row sheet | 0 ms | 1 | - |\n| Type in a column a single `SUM` of 10,000 cells reads | 14 ms | 1 | - |\n| Type at the top of a 10,000-row dependency chain | 71 ms | 10,000 | - |\n\nRead the third column first: it is the one CI gates, and the one that says\nwhat the engine is doing. A keystroke costs **one evaluation**, not a\nsheet's worth, because the dependency graph recomputes what read the cell\nand nothing else. The column-`SUM` row is the interesting pair: one\nevaluation, 14 ms, because that single `SUM` re-reads its 10,000 cells. The\nchain row is the worst case a sheet can have, a running balance where every\nrow reads the row above it: 10,000 evaluations for one keystroke, which is\nthe true cost of that shape and not a bug.\n\nSo the practical ceiling, on this container: **a sheet of tens of thousands\nof formula rows opens in well under a second and edits instantly**, and the\nthing that changes that is not the sheet's size but how much of it one cell\nfeeds. 50,000 formula rows retain about 84 MB, roughly 1.7 KB per row for\nthe text, the cached value and the graph edges.\n\nA chain longer than about a thousand rows used to overflow the JavaScript\nstack on the first keystroke and land `#NUM!` in the cell. The workbook now\nprimes a deep chain from its far end instead of recursing through it, so\nthe only limit left is the sheet's own size.\n\n## What CI enforces\n\nElapsed time is too noisy on a shared runner to fail a build on, and a\nflaky performance gate gets switched off within a month. So `pnpm\nbench:check` gates **work counters** instead - counts of algorithmic work,\nidentical on every machine:\n\n| Counter | Budget | Actual |\n| --------------------------------------------- | ------ | ------ |\n| `getAllColumns` calls inside a 1-clause sort | 8 | 1 |\n| `getAllColumns` calls inside a 3-clause sort | 24 | 1 |\n| `getAllCells` materialisations while filtering | 0 | 0 |\n| Filter re-runs caused by a selection change | 0 | 0 |\n| Sort re-runs caused by a selection change | 0 | 0 |\n| Cells evaluated opening a 10,000-row sheet | 10,004 | 10,000 |\n| Cells evaluated by one keystroke in that sheet | 4 | 1 |\n| Cells evaluated when a 10,000-cell `SUM` reads the edit | 3 | 1 |\n\nA count is a claim about the algorithm; a millisecond is a claim about the\nhardware. Only the first belongs in CI. Budgets live beside each case in\n`tools/bench/cases.mjs`, and the spreadsheet's in\n`tools/bench/sheet-cases.mjs`.\n\nEach case also declares which counters must be *present*, not just within\nbudget. Without that, a stage that stopped running altogether would satisfy\nevery budget by doing no work, which is the failure mode a gate like this\nis most likely to develop.\n\n## Memory\n\n**Measured** (`pnpm bench`, Node heap): building the row model for\n100,000 rows x 9 columns with no sort, filter or grouping retains\n**0.8 MB**, with no renderer attached. A row object is made the first time\nsomething reads it, so a grid showing twenty rows makes a screenful of\nthem, not 100,000.\n\nThe first sort, filter or grouping reads every row and makes them all. The\nbrowser harness measures that as the \"after sorting and filtering\" row in\nthe [comparison](./comparison.md#measured-performance): 17.8 MB at\n100,000 rows, and 128 MB at 1,000,000 (27 Oct 2026,\n`BENCH_ROWS=1000000 BENCH_GRIDS=svgrid pnpm bench:compare`), so about 130\nbytes a row: the row object, its id, and the sort key it keeps so a live\nupdate can be merged in without re-reading the rows. The 1,000,000-row\nfigure was 196 MB the day before. Reading one column used to build an\narray of every column's value on every row and keep it there, which only\nthe rows on screen use; a plain `field` column is now read from the data,\nand only a computed (`fieldFn`) column still builds the array.\n\nThe fully built row model was 16.0 MB at 100,000 rows before rows became\nlazy, and 64.9 MB before that. Each row was an object literal whose seven\nmethods were closures, so a 100k-row grid allocated 700k closures and a\nclosure scope per row before painting anything. The methods are now\ndefined once and shared, reading their row through `this`: 4x less memory\nand about 7x faster to build. They are still assigned as own properties\nrather than put on a prototype, because `Row` is public and several row\nmodels legitimately do `{ ...row, depth }` - a spread copies own\nproperties but not a prototype, so a class would silently strip the\nmethods off a cloned row.\n\nAn earlier version of this page said \"~22 MB\". That figure was not\nmeasured. Node's heap accounting is not the same as a browser's, so read\nthis as the engine's own cost rather than what a tab will show.\n\nTwo claims here are structural rather than measured, and both hold:\n\n- Virtualization keeps the rendered DOM to the visible window regardless\n of dataset size, so `<td>` count does not scale with row count.\n- No retained references when the grid unmounts - the cleanup path is\n exercised by the unmount test in `svgrid.behavior.test.ts`.\n\n## Server-side / chunked loading\n\nDemo [33. Server-side infinite scroll](https://svgrid.com/demos/33-server-infinite/) covers the chunked-load path. Numbers from that demo:\n\n| Scenario | Result |\n| ------------------------------------------------ | --------------------------------------- |\n| Initial paint, sparse 100k-row dataset | 110 ms to first chunk visible |\n| Scroll 50,000 rows in 1.5 s (fast wheel-flick) | 16 chunk requests cancelled mid-flight |\n| Sort 100k server-side rows | round-trip dominated by the mock latency (50-140 ms) |\n\n### The Server-Side Row Model over one million rows\n\nDemo [467](https://svgrid.com/demos/467-server-row-model-1m/) runs the\nEnterprise row model over a columnar in-memory warehouse of a million rows,\ngrouped Region > Country. `tests/perf/server-row-model.spec.ts` drives it in\nheadless Chromium (a developer workstation, 17 September 2026; a release\nritual, not a gate):\n\n| Scenario | Result |\n| ------------------------------------------------------------- | --------------------------------------------- |\n| First paint, navigation to the first group row (includes building the warehouse in the page) | 2.4 s |\n| Scroll 60,000 px through an open country of 62,000 leaves | 17 leaf requests, 0.28 per 1,000 px (one block of 100 rows is 3,400 px) |\n| Worst frame while blocks streamed in | 83 ms (layout of the changed rows; the grid keeps the row objects a block did not touch) |\n| Heap before / after streaming 700,000 px with `maxBlocksInCache: 24` | 225 MB / 225 MB - evicted blocks are collected |\n| Warehouse: a million rows as typed arrays | 22 MB; a cold sort on a new column 0.8 to 1.1 s, cached after; a grouped level 140 ms; a pivot with a grand total 330 ms |\n\n## AI helpers\n\nEnd-to-end timings against the bundled `mockAIProvider`:\n\n| Helper | Median time (ms) |\n| --------------- | ---------------- |\n| `aiFilter` | 350-750 (mock latency dominated) |\n| `aiSmartFill` (50 rows) | 400-900 |\n| `aiSummarize` | 350-750 |\n| `aiClassify` (20 rows) | 400-750 |\n\nAgainst a real model the latency is provider-side. The grid's own\nprompt-build + result-parse work stays under ~6 ms even for 1000-row\nclassify jobs.\n\n## Import / export\n\n| Operation | Time |\n| ------------------------------------ | ------ |\n| Parse CSV, 10k rows × 9 cols | 28 ms |\n| Parse xlsx, 10k rows × 9 cols | 140 ms (jszip unzip-dominated) |\n| Export CSV, 10k rows × 9 cols | 18 ms |\n| Export xlsx, 10k rows × 9 cols | 220 ms |\n| Export PDF, 1k rows × 9 cols (pdfmake) | 700 ms |\n\n## Reproducing locally\n\n```bash\ngit clone https://github.com/sv-grid/sv-grid\ncd sv-grid\npnpm install\npnpm --filter @svgrid/grid build # the bench runs the BUILT engine\npnpm bench # engine + memory tables\npnpm size # bundle table\npnpm bench:dom # first paint + scroll, in Chromium\n```\n\nThe bench takes a few options:\n\n```bash\npnpm bench --json # machine-readable, for trend tracking\npnpm bench --baseline=tools/bench/baseline.json # adds a delta column\npnpm bench --case=sort-1col # one case\npnpm bench:check # the work-counter gate CI runs\n```\n\n`pnpm bench` runs against the built `@svgrid/grid/core` rather than\n`src/`, so it also smoke-tests the entry a consumer actually imports.\n\n`pnpm bench:dom` drives Chromium through Playwright against the examples\ngallery, which lives in this repository, so it needs no private\nsubmodule. It is a Playwright project rather than part of `pnpm test:e2e`,\nand it is deliberately not in CI - see below.\n\nFor your own workload, the [benchmark harness\nrecipe](../recipes/benchmark-harness.md) and the [FPS HUD\nrecipe](../recipes/profiling-with-fps-hud.md) are copy-paste probes you\ncan drop into your app.\n\n## What we *don't* claim\n\n- That we are faster than any other grid. Nothing on *this* page is a\n head-to-head measurement. Everything here is sv-grid measured against\n sv-grid, which supports \"this got 10x faster\" and not \"this is faster\n than X\". For a real comparison there is a separate grid-agnostic\n harness - `pnpm bench:compare`, results and caveats in\n [Comparison](./comparison.md) - and it does not say we win everything.\n- That first paint is good. The grid half of the 100k x 100 case is still\n the worst number on this page, and this round did not touch it.\n- Any scroll figure above 60 fps. The harness is rAF-driven and cannot\n observe headroom past the display refresh. \"Zero dropped frames\" is the\n claim; \"120 fps\" is not.\n- Lab-grade first-paint numbers. Those come from a developer machine with\n roughly 2x run-to-run variance, not a dedicated rig.\n- \"Smoothest grid on the market\" - that depends entirely on what your\n cells render. A sparkline + currency formatter in every cell costs\n more than a number, and we don't pretend otherwise.\n- \"Zero allocations during scroll\" - the virtualizer recycles DOM\n nodes but cell snippets still allocate. The numbers above include\n real-world snippets (status pills, mini-bars).\n- Single-thread performance > 1M rows. For >1M, do the heavy lifting\n on the server and feed chunks through the [server-side infinite\n scroll pattern](https://svgrid.com/demos/33-server-infinite/).\n\n## Frequently asked questions\n\n### How fast is SvGrid?\n\nIt virtualizes both rows and columns, so only the visible window is in the DOM,\nand a million rows scrolls without dropping a frame. On the data side, a\nsingle-column sort of 100,000 rows takes about 27 ms and a one-operator filter\nabout 5 ms. Every table on this page comes from a checked-in script you can run\nyourself, and the numbers moved because the harness exposed real defects rather\nthan because the prose was rewritten.\n\n### How many rows can SvGrid handle?\n\nClient-side, 100k+ rows scroll smoothly thanks to virtualization. For millions\nof rows, page or chunk from the server (see Server-side data). The DOM only ever\nholds the visible window regardless of total row count.\n\n### How fast is SvGrid, and how big is it?\n\nIt ships a small bundle (the measured figures for the full render component\nand for the headless core alone are in the table above) and virtualizes by\ndefault. Raw scroll\nperformance is comparable for typical workloads; the bigger practical win is\nbundle size and a Svelte-native runtime with no framework bridge.\n\n## See also\n\n- [Browser support](./browser-support.md) - the matrix the benchmarks\n ran against.\n- [Testing and quality](./testing-and-quality.md) - the coverage\n thresholds that gate every release.\n"
5315
5315
  },
5316
5316
  {
5317
5317
  "slug": "help/bolt-new",
@@ -5332,7 +5332,7 @@ export const docs = [
5332
5332
  "path": "docs/help/bundle-size.md",
5333
5333
  "title": "Bundle size",
5334
5334
  "section": "Help",
5335
- "markdown": "# Bundle size\n\nWhat SvGrid costs in your bundle, how to reproduce the number on your\nbranch, and what to do if size matters.\n\n## Measured\n\nThe table below is generated from `docs/_data/svgrid-size.json`, the file\n`pnpm size:json` writes; `node tools/sync-guide-facts.mjs` rewrites it and\n`tools/competitor-facts.test.ts` fails when it is stale or when a size is\ntyped anywhere else on this page. An earlier version of this page typed its\nnumbers and sat a month behind the measurement.\n\n<!-- size:start -->\nRe-measured **10 Nov 2026** at `@svgrid/grid` 3.0.33 with the script that ships in the repo (`pnpm size:json`):\n\n| Target | Base JS (gzip) | CSS (gzip) | Loaded on demand |\n| --- | ---: | ---: | ---: |\n| Headless core (`createSvGrid`) | **3.2 KB** | - | - |\n| Headless subpath (`@svgrid/grid/core`) | **10.1 KB** | - | - |\n| Full render component (`<SvGrid>`) | **99.9 KB** | **11.3 KB** | **198.9 KB** |\n| Standalone chart (`<SvChart>`) | **71.9 KB** | - | **15.0 KB** |\n<!-- size:end -->\n\nThe two headless rows measure different things on purpose. `createSvGrid` is\nthe engine plus the row model it needs, which is what you pay when you import\njust that symbol. The subpath row is every export on `@svgrid/grid/core`\npulled in at once with nothing tree-shaken, so it is the ceiling rather than\nthe typical cost - a real consumer importing `createSvGrid` and two row models\nsits near the lower number.\n\nSvelte is a peer dependency and is excluded from every figure. Builds are\nminified and gzipped at level 9.\n\nThe \"loaded on demand\" column is code that is reachable only through\n`import()`, so it never lands in your initial bundle. The script prints the\nper-chunk breakdown; the chunks and what triggers each of them:\n\n| Chunk | Loads when |\n| --- | --- |\n| `SvDateTimePicker` | a date / datetime / time cell editor opens |\n| `chart` (engine) | charting is enabled |\n| `SvGridChart`, `SvGridChartPanel`, `SvGridChartView` | a chart renders, the chart panel opens, the grid switches to chart view |\n| `GridMenus` | a header or context menu opens |\n| `SvGridCellEditor` | editing is enabled (loads at mount, before the first edit) |\n| `SvGridDropdown` | a list / chips cell editor or the page-size picker opens |\n| `dismissable`, `popover`, `focus-trap` | any popover, menu or dropdown layer opens |\n| `export-format` | CSV / TSV / JSON export or clipboard copy runs |\n| `date-format` | a date column formats a value |\n| `column-resize`, `row-resize`, `row-drag-touch` | the first resize drag or touch row drag |\n\nThe Kanban board and the scheduler / calendar view are not in either\nfigure: their renderers live in `@svgrid/enterprise` and register into the\nfree grid through the board and scheduler view seams.\n\n## Reproduce on your branch\n\n`measure-size.mjs` runs one isolated Vite library build per target above,\nwith Svelte marked external, then gzips each emitted chunk and classifies\nit as `base` (statically reachable from the entry) or `lazy` (reachable\nonly via `import()`).\n\n```bash\nnode packages/grid/scripts/measure-size.mjs\n# or, from the repo root:\npnpm size\n```\n\nTo see where the weight sits inside the base bundle:\n\n```bash\ncorepack pnpm --filter @svgrid/grid build\nnpx source-map-explorer packages/grid/dist/index.js\n```\n\nA treemap opens in your browser. Each block is a source file scaled by its\nbyte cost in the final bundle.\n\n## @svgrid/enterprise\n\nThe Enterprise pack is a separate install and a separate bundle. `xlsx`\nexport pulls JSZip and PDF export pulls pdfmake as optional peer\ndependencies, imported on the first `api.exportData(...)` call rather than\nat module load, so neither is in your synchronous bundle.\n\n## What to do if size matters\n\n1. **Use the headless engine for read-only views.** When you only need to\n display server-side data with no interaction, `createGrid` plus a short\n `<table>` renderer costs the headless-core row of the table above rather\n than the full-component row. See the\n [headless engine reference](../reference/headless-engine.md).\n2. **Register only the features you use.** The grid is feature-gated:\n sorting, filtering, grouping, pagination, expansion, and selection are\n each opt-in and tree-shake out when not imported. See the\n [features reference](../reference/features.md).\n3. **Let the lazy chunks stay lazy.** Charts, date/time editors, menus,\n and export already split themselves. Importing their modules directly\n at the top level pulls them back into your base bundle.\n4. **Code-split the Enterprise pack.** `installEnterprise(api)` is\n async-safe, so import it in the route that needs export rather than at\n module load:\n `const { installEnterprise } = await import('@svgrid/enterprise')`.\n\n## See also\n\n- [Features reference](../reference/features.md) - what each feature does\n- [Headless engine reference](../reference/headless-engine.md) - skip the renderer entirely\n- [Going to production guide](../getting-started/6-going-to-production.md)\n"
5335
+ "markdown": "# Bundle size\n\nWhat SvGrid costs in your bundle, how to reproduce the number on your\nbranch, and what to do if size matters.\n\n## Measured\n\nThe table below is generated from `docs/_data/svgrid-size.json`, the file\n`pnpm size:json` writes; `node tools/sync-guide-facts.mjs` rewrites it and\n`tools/competitor-facts.test.ts` fails when it is stale or when a size is\ntyped anywhere else on this page. An earlier version of this page typed its\nnumbers and sat a month behind the measurement.\n\n<!-- size:start -->\nRe-measured **10 Nov 2026** at `@svgrid/grid` 3.0.34 with the script that ships in the repo (`pnpm size:json`):\n\n| Target | Base JS (gzip) | CSS (gzip) | Loaded on demand |\n| --- | ---: | ---: | ---: |\n| Headless core (`createSvGrid`) | **3.2 KB** | - | - |\n| Headless subpath (`@svgrid/grid/core`) | **10.2 KB** | - | - |\n| Full render component (`<SvGrid>`) | **99.6 KB** | **11.4 KB** | **206.3 KB** |\n| Standalone chart (`<SvChart>`) | **71.9 KB** | - | **16.0 KB** |\n<!-- size:end -->\n\nThe two headless rows measure different things on purpose. `createSvGrid` is\nthe engine plus the row model it needs, which is what you pay when you import\njust that symbol. The subpath row is every export on `@svgrid/grid/core`\npulled in at once with nothing tree-shaken, so it is the ceiling rather than\nthe typical cost - a real consumer importing `createSvGrid` and two row models\nsits near the lower number.\n\nSvelte is a peer dependency and is excluded from every figure. Builds are\nminified and gzipped at level 9.\n\nThe \"loaded on demand\" column is code that is reachable only through\n`import()`, so it never lands in your initial bundle. The script prints the\nper-chunk breakdown; the chunks and what triggers each of them:\n\n| Chunk | Loads when |\n| --- | --- |\n| `SvDateTimePicker` | a date / datetime / time cell editor opens |\n| `chart` (engine) | charting is enabled |\n| `SvGridChart`, `SvGridChartPanel`, `SvGridChartView` | a chart renders, the chart panel opens, the grid switches to chart view |\n| `GridMenus` | a header or context menu opens |\n| `SvGridCellEditor` | editing is enabled (loads at mount, before the first edit) |\n| `SvGridDropdown` | a list / chips cell editor or the page-size picker opens |\n| `dismissable`, `popover`, `focus-trap` | any popover, menu or dropdown layer opens |\n| `export-format` | CSV / TSV / JSON export or clipboard copy runs |\n| `date-format` | a date column formats a value |\n| `column-resize`, `row-resize`, `row-drag-touch` | the first resize drag or touch row drag |\n\nThe Kanban board and the scheduler / calendar view are not in either\nfigure: their renderers live in `@svgrid/enterprise` and register into the\nfree grid through the board and scheduler view seams.\n\n## Reproduce on your branch\n\n`measure-size.mjs` runs one isolated Vite library build per target above,\nwith Svelte marked external, then gzips each emitted chunk and classifies\nit as `base` (statically reachable from the entry) or `lazy` (reachable\nonly via `import()`).\n\n```bash\nnode packages/grid/scripts/measure-size.mjs\n# or, from the repo root:\npnpm size\n```\n\nTo see where the weight sits inside the base bundle:\n\n```bash\ncorepack pnpm --filter @svgrid/grid build\nnpx source-map-explorer packages/grid/dist/index.js\n```\n\nA treemap opens in your browser. Each block is a source file scaled by its\nbyte cost in the final bundle.\n\n## @svgrid/enterprise\n\nThe Enterprise pack is a separate install and a separate bundle. `xlsx`\nexport pulls JSZip and PDF export pulls pdfmake as optional peer\ndependencies, imported on the first `api.exportData(...)` call rather than\nat module load, so neither is in your synchronous bundle.\n\n## What to do if size matters\n\n1. **Use the headless engine for read-only views.** When you only need to\n display server-side data with no interaction, `createGrid` plus a short\n `<table>` renderer costs the headless-core row of the table above rather\n than the full-component row. See the\n [headless engine reference](../reference/headless-engine.md).\n2. **Register only the features you use.** The grid is feature-gated:\n sorting, filtering, grouping, pagination, expansion, and selection are\n each opt-in and tree-shake out when not imported. See the\n [features reference](../reference/features.md).\n3. **Let the lazy chunks stay lazy.** Charts, date/time editors, menus,\n and export already split themselves. Importing their modules directly\n at the top level pulls them back into your base bundle.\n4. **Code-split the Enterprise pack.** `installEnterprise(api)` is\n async-safe, so import it in the route that needs export rather than at\n module load:\n `const { installEnterprise } = await import('@svgrid/enterprise')`.\n\n## See also\n\n- [Features reference](../reference/features.md) - what each feature does\n- [Headless engine reference](../reference/headless-engine.md) - skip the renderer entirely\n- [Going to production guide](../getting-started/6-going-to-production.md)\n"
5336
5336
  },
5337
5337
  {
5338
5338
  "slug": "help/cells/cell-components",
@@ -5647,7 +5647,7 @@ export const docs = [
5647
5647
  "path": "docs/help/comparison.md",
5648
5648
  "title": "Comparison: SvGrid vs AG Grid vs TanStack Table",
5649
5649
  "section": "Help",
5650
- "markdown": "\n# Comparison: SvGrid vs AG Grid vs TanStack Table\n\nThe three projects solve overlapping problems, and the right choice\ndepends on the framework you ship on, how much of the grid you want to\nbuild yourself, and your budget. Every number on this page is read from\nnpm or measured by a script in this repository on the date shown; the\nblock below is regenerated by `node tools/sync-guide-facts.mjs` and the\nper-competitor pages under [/compare/](https://svgrid.com/compare/) list\nthe sources for every feature claim.\n\n<!-- facts:start ag-grid,tanstack-table -->\n> **Facts, checked 9 Nov 2026.** `ag-grid-community` 36.3.0, MIT, last published 4 Nov 2026, 16,400,000 npm downloads in the 30 days to 8 Nov 2026. `@tanstack/svelte-table` 9.3.1, MIT, last published 12 Oct 2026, 539,000 npm downloads in the same window. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026); `ag-grid-community` 36.3.0 346.4 KB JS, no separate stylesheet (measured 9 Nov 2026); `@tanstack/svelte-table` 9.3.1 36.5 KB JS, no separate stylesheet, svelte external (measured 9 Nov 2026). AG Grid pricing, as its site states it: AG Grid Community is free under MIT. AG Grid Enterprise is listed at $999 USD per developer with one year of updates and Zendesk support; the Enterprise Bundle with AG Charts Enterprise is $1,498 USD per developer (https://www.ag-grid.com/license-pricing/, read 12 Sep 2026). TanStack Table pricing, as its site states it: TanStack Table is MIT and free; tanstack.com is sponsor-supported and offers Enterprise Support as private consulting and expert support, with no licence sold for the table (https://tanstack.com/table/latest, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs AG Grid (community + enterprise)](https://svgrid.com/compare/ag-grid/), [SvGrid vs TanStack Table (Svelte)](https://svgrid.com/compare/tanstack-table/).\n<!-- facts:end -->\n\n## TL;DR\n\n| Project | Lives in | Ships | Licence |\n| --------------------- | ---------------------------------------- | ---------------------------------------------------------- | ----------------------------------------- |\n| **SvGrid** | Svelte 5 | Headless core + Svelte render component + Enterprise pack | MIT (Community) / commercial (Enterprise) |\n| **AG Grid Community** | React, Angular, Vue, plain JS | Full grid + renderer; Svelte through community integrations | MIT |\n| **AG Grid Enterprise**| same | Adds the set filter, range selection, master/detail, tree, grouping, pivot, charts, Excel export, server-side row model | Commercial, per developer |\n| **TanStack Table** | React, Vue, Svelte, Solid, Qwik, Lit, JS | Headless engine **only**; the Svelte adapter is Svelte 5 | MIT |\n\nThe bundle sizes and prices are in the facts block above, with the date\nthey were read and the method behind the sizes.\n\n## When SvGrid is the right choice\n\n- You're on **Svelte 5** and want a grid that uses the runtime's idioms\n (snippets for cells, `$state` for data, `$derived` for aggregates) -\n not a React-port pretending to be Svelte.\n- You want a **headless core you can render yourself** AND a\n default-styled component for the 80% case. Most \"headless\" libraries\n make you write the markup; most \"monolith\" libraries make you fight\n the markup. SvGrid does both in one package.\n- You need **clean theming via CSS custom properties** and a documented\n `--sg-*` token surface, not a hard-coded class soup.\n- You ship under **strict CSP** (no `eval`, no `new Function`, no\n inline scripts). SvGrid runs clean; AG Grid Community does too.\n TanStack Table is engine-only so the question doesn't apply.\n- You want **SSR markup that is meaningful before hydration** (good\n first paint, SEO, SvelteKit `+page.server` integration). SvGrid +\n TanStack Table both qualify. AG Grid renders client-side.\n- You want the features AG Grid sells as Enterprise - the set filter,\n range selection, master/detail, tree data, grouping with aggregation,\n integrated charts, flat server-side infinite scroll - **in the MIT\n core**. (Server-side grouping, tree, pivot and transactions are\n Enterprise in both.)\n\n## When AG Grid is the right choice\n\n- You're on **React, Angular, or Vue**, not Svelte. SvGrid is\n Svelte-only, and ag-grid.com points Svelte users to community-built\n integrations rather than an official package.\n- You need a push-based **viewport row model** for a real-time trading\n blotter, where the server streams the visible window over a socket.\n SvGrid's server-side row model covers sort, filter, grouping, tree,\n pivot, transactions and select-all across unloaded rows, and its\n real-time page merges deltas into loaded rows, but it does not have the\n viewport model.\n- You need **custom tool panels**. SvGrid's tool panel is a fixed\n Columns + Filters pair. Custom filter components are covered by a\n column's `customFilter`.\n- You need **AG Charts** for maps, network graphs, 3D or a canvas renderer.\n SvGrid's chart is SVG with decimation, and it ships 29 types, a configurable\n axis model, synchronized charts, a financial toolkit with indicator panes\n and drawing tools, a builder and PDF export in the MIT core; it does not\n draw maps.\n- You want a vendor with **a decade of enterprise procurement paperwork**\n already on file.\n\n## When TanStack Table is the right choice\n\n- You want a **rendering-framework-agnostic engine** so the same\n business logic powers React + Svelte + Solid surfaces in your\n monorepo.\n- You're already in the TanStack ecosystem (Query, Router, Form,\n Virtual) and want one mental model.\n- You're happy writing **all the markup yourself** - the row recycling,\n the keyboard map, the ARIA roles, the focus management, the\n drag-to-resize. That's the cost of \"engine only\".\n\n## Feature parity at a glance\n\nYes: shipped in that edition. Partial: needs extra work or a companion\npackage. No: not available. The AG Grid columns follow ag-grid.com's\nCommunity vs Enterprise page and its Set Filter, Tree Data and CSV export\npages; the dated list of those sources is on the\n[SvGrid vs AG Grid](https://svgrid.com/compare/ag-grid/) page, and the\nTanStack sources on [SvGrid vs TanStack Table](https://svgrid.com/compare/tanstack-table/).\n\n| | SvGrid Community | SvGrid Enterprise | AG Grid Community | AG Grid Enterprise | TanStack Table |\n| ------------------------------- | ---------------- | ----------------- | ----------------- | ------------------ | -------------- |\n| Headless core (engine only) | Yes | Yes | No | No | Yes |\n| Default render component | Yes (Svelte 5) | Yes | Yes (each framework) | Yes | No |\n| Sort (multi-column) | Yes | Yes | Yes | Yes | Yes (engine) |\n| Filter menu (operator + facet) | Yes | Yes | Partial (text and number filters; the set filter is Enterprise) | Yes | No |\n| Filter row | Yes | Yes | Yes | Yes | No |\n| Pagination | Yes | Yes | Yes | Yes | Yes (engine) |\n| Grouping + aggregation | Yes | Yes | No (Enterprise) | Yes | Yes (engine) |\n| Tree / expand-collapse rows | Yes | Yes | No (Enterprise) | Yes | Yes (engine) |\n| Master/detail | Yes | Yes | No (Enterprise) | Yes | No |\n| Cell range selection + copy/paste | Yes | Yes | No (Enterprise) | Yes | No |\n| Fill handle | Yes | Yes | No (Enterprise) | Yes | No |\n| Inline editing (typed editors) | Yes | Yes | Yes | Yes | No |\n| Column virtualization | Yes | Yes | Yes | Yes | No |\n| Row virtualization | Yes | Yes | Yes | Yes | Partial (pair with TanStack Virtual) |\n| Column pinning (left/right) | Yes | Yes | Yes | Yes | No |\n| Column tool panel | Yes | Yes | No (Enterprise) | Yes | No |\n| Context menu | Yes | Yes | No (Enterprise) | Yes | No |\n| Fit-to-width with shrink | Yes | Yes | Partial | Yes | No |\n| WAI-ARIA grid pattern | Yes | Yes | Yes | Yes | No (your markup) |\n| Server-side data, flat (sort / filter / paging / infinite scroll) | Yes (built in) | Yes (built in) | Yes (infinite row model) | Yes (built in) | Partial (manual flags) |\n| Server-side row model (lazy grouping, tree, pivot, transactions, select-all across unloaded rows) | No (Enterprise) | Yes (built in) | No (Enterprise) | Yes (built in) | No |\n| Global search over server-side data | Yes (`filterModel.global`) | Yes | No (the quick filter is client-side only) | No | n/a |\n| CSP-clean (no eval, no inline) | Yes | Yes | Yes | Yes | n/a |\n| Meaningful SSR markup | Yes | Yes | No | No | depends on your markup |\n| CSV / TSV / JSON export | Yes | Yes | Yes (CSV) | Yes | No |\n| Excel (.xlsx) / PDF export | No | Yes | No | Yes (Excel) | No |\n| Print | No | Yes | No | No | No |\n| Excel / CSV import | No | Yes | No | No | No |\n| In-grid AI helpers (bring your own model) | Yes | Yes | No | No | No |\n| MCP server for AI assistants | Yes (`@svgrid/mcp`) | Yes | Yes (`ag-mcp`) | Yes | No (agent skills ship in the package) |\n| Pivot table | No | Yes | No | Yes | No (custom) |\n| Integrated charts | Yes (29 types, builder, financial toolkit) | Yes | No | Yes (AG Charts) | No |\n| Support response time | GitHub (best-effort) | 1 business day; 1h sev-1 on Enterprise | GitHub (best-effort) | no number published | GitHub; paid Enterprise Support offered |\n| Theming via CSS variables | Yes (`--sg-*`) | Yes | Yes (theme builder) | Yes | n/a |\n| Source button per demo | Yes (gallery) | Yes | No | No | No |\n\n## Bundle size\n\nThe facts block at the top of the page has the gzipped size of each\npackage, measured by the same method: each package built alone with Vite\nin library mode, minified, gzip level 9, Svelte external because it is a\npeer dependency. SvGrid's own number comes from `pnpm size:json`\n(`packages/grid/scripts/measure-size.mjs`), the competitors' from\n`pnpm competitors:measure`; both write `docs/_data` and the block is\nregenerated from there, so the page cannot quote a size nobody measured.\n\nWhat the SvGrid number contains: the whole render component -\nvirtualization, Excel-style filters, inline editing, grouping, tree,\nmaster/detail, cell selection and accessibility - in one import, plus a\nseparate stylesheet. Charts, date and time editors, menus and export split\ninto `import()` chunks that load on demand rather than shipping in the\ninitial bundle; the headless core on its own is a small fraction of the\nrender component, and `@svgrid/enterprise` features are separate subpath\nimports. The per-entry breakdown, including the headless core and the\nlazy chunks, is in the [bundle size reference](./bundle-size.md).\n\nWhat the AG Grid number contains: `createGrid` with every Community\nmodule registered and the Quartz theme, whose CSS ships inside the script\nunder the theming API, so there is no separate stylesheet to add. The\nTanStack number is the whole Svelte adapter with its engine: no\nvirtualizer, filter UI or editors, because a headless library has none.\n\n## Measured performance\n\nA vendor's own benchmark is worth nothing unless you can rerun it, so the\nharness is in the repository and takes an adapter per grid. Adding another\ngrid is about forty lines in `examples/src/bench/adapters.ts` and nothing\nelse.\n\n```bash\n# headless, prints the table and writes tests/perf/.last-compare.json\nBENCH_REPEATS=7 BENCH_GRIDS=svgrid,aggrid,svar,tanstack pnpm bench:compare\n\n# move that run into docs/_data/competitors.json, then regenerate this page\nnode tools/record-benchmarks.mjs && node tools/sync-guide-facts.mjs\n\n# or drive it by hand\npnpm --filter @svgrid/grid-example-gallery dev # then open /bench.html\n```\n\nEach operation is timed until the grid's DOM reflects it, plus one frame:\n\n- **Mount** - fresh container, create the grid, until rows are painted.\n- **Sort** - change the sort on one column, until the new order is painted.\n Text sorts `name` (tens of thousands of distinct values), numeric sorts\n `amount`.\n- **Filter** - apply a `contains` filter to one column.\n- **Scroll** - 180 frames at 60 px/frame, sampling frame intervals.\n\n### Results\n\nThe table is generated from the ledger by `tools/sync-guide-facts.mjs`;\nthe versions and the date are part of it.\n\n<!-- bench:start -->\nMeasured 28 Oct 2026 with `pnpm bench:compare` (tests/perf/compare.spec.ts, recorded by tools/record-benchmarks.mjs): 100,000 rows x 9 columns; 1000 x 520 px container, 32 px rows, 140 px columns, each grid with its default theme; fastest of 3 samples per operation, each grid in a fresh page; Chromium through Playwright, headless; win32 10.0.26200 x64, Intel(R) Core(TM) Ultra 7 255U; a developer workstation, not a dedicated bench rig; tick: 1,000 of the rows replaced per tick with a new amount, the grid sorted by amount, on the update path each grid provides, timed until the changed cells paint; 180 ticks after 10 to warm up. Lower is better.\n\n| Operation | SvGrid | AG Grid Community | SVAR Svelte DataGrid | TanStack Table, minimal DOM |\n| --- | --- | --- | --- | --- |\n| Mount | 30.7 ms | 67 ms | 11.4 ms | 170.2 ms |\n| Sort, text column | 77.4 ms | 213.9 ms | 135.4 ms | 360.9 ms |\n| Sort, numeric column | 32.8 ms | 216.7 ms | 141.7 ms | 178.2 ms |\n| Filter, one column (indicative only, see below) | 34.5 ms | 148.8 ms | 26.1 ms | 51.1 ms |\n| Scroll, p95 frame | 34.3 ms | 34.5 ms | 34.6 ms | 34.3 ms |\n| Live tick, 1,000 rows replaced, sorted by that column, p95 | 48.6 ms | 259.2 ms | 152.2 ms | 563.4 ms |\n| Main-thread work per 60 px scroll step, mean | 3.5 ms | 4.5 ms | 3 ms | 2.9 ms |\n| Frames dropped while scrolling, of 180 | 0 | 0 | 0 | 0 |\n| Ticks over one 60 Hz frame, of 180 | 115 | 180 | 180 | 180 |\n| Rows kept in the DOM (virtualization on) | 36 | 36 | 19 | 27 |\n| JS heap the grid adds, mounted, after GC | 5.7 MB | 42.1 MB | 2.3 MB | 109.9 MB |\n| JS heap the grid adds, after sorting and filtering, after GC | 17.6 MB | 26.2 MB | 3.9 MB | 113.3 MB |\n| Elements created per scroll frame | 0 | 30.1 | 16.8 | 18.7 |\n| Elements re-inserted per scroll frame (rows recycled) | 37.3 | 35.8 | 0 | 0 |\n\nVersions: `@svgrid/grid` 3.0.25, `ag-grid-community` 36.1.0, `wx-svelte-grid` 2.7.0, `@tanstack/svelte-table` 9.2.4.\n<!-- bench:end -->\n\nRead that as: **SvGrid sorts and keeps a live sort current faster than the\nother three, scrolling is level across all four, and SVAR is ahead on mount\nand memory** - it paints its first rows in under half of SvGrid's time and\nholds the least heap. Every grid scrolls at the display rate here, so the\np95 frame reads the same for all four; the work row under it is what a\nslower machine or a 120 Hz display would feel. There TanStack and SVAR do\nthe least per scroll step, about half a millisecond under SvGrid, and AG\nGrid the most. The row varies from run to run, so read the order of the\nfirst three as close, not settled. SvGrid makes its row objects the first time a\nsort or filter reads every row rather than at mount, which is why its two\nheap rows differ. The TanStack renderer pays for building a row object per\nrecord before it can draw anything. Anyone claiming a single headline\nnumber for a grid comparison is selling something.\n\n**The heap rows are the JS heap after a forced garbage collection, less the\nsame page with the data built and no grid,** so the 100,000 rows themselves\ncount against no one. The two DOM rows are counted over 60 untimed scroll\nframes after the timed ones. \"Created\" is elements that did not exist\nbefore; \"re-inserted\" is elements the grid already had and moved, which is\nhow a keyed list recycles a row from one end of the window to the other.\nSvGrid creates none and moves the two rows that cross the edge each frame;\na grid that rewrote its rows in place would score 0 on both.\n\n**The filter row is not a like-for-like comparison and is shown only because\nhiding a number we win looks worse than explaining it.** The grids' single-\ncolumn filter APIs differ: the harness drives AG Grid's quick filter, which\nsearches every column and is strictly more work than the single-column\n`contains` SvGrid performs, while SVAR and TanStack run a predicate over the\none column. Do not read a ratio into that row.\n\n**The TanStack column is an engine plus the least DOM an app could draw.**\nTanStack Table renders nothing, so its adapter draws the row model through\na fixed-height windowed table with no virtualizer library, no filter UI and\nno editors. Its mount and sort numbers include creating the engine's row\nobjects for every record; the grids around it do the same work inside their\nown models.\n\nSorting is where SvGrid's distance comes from, and it is not subtle: SvGrid\nresolves each sort clause once and precomputes a key array, and for a\ncolumn whose distinct values are far fewer than its rows it collates the\ndistinct values once and sorts by rank. Mounting is the other direction -\nsee the accounting in [benchmarks](./benchmarks.md).\n\nAt 1,000,000 rows the harness runs one grid per invocation\n(`BENCH_ROWS=1000000 BENCH_GRIDS=<one> BENCH_TICKS=30`); TanStack's\nadapter does not finish at that size. Those runs are not in the table\nbecause only a run that measured every grid together is comparable.\n\nTwo methodology notes, both of which were bugs in this harness before they\nwere notes, and both of which changed the numbers by more than any code\nchange did:\n\n- **Each grid runs in a fresh page.** They used to run one after another in\n the same one, where the first warmed the JIT, fragmented the heap and\n left a hundred thousand rows of garbage for the next. Back-to-back runs\n on an idle machine disagreed with themselves by a factor of two.\n That order effect is gone, but this workstation still varies by about\n 2x between whole runs taken minutes apart, for every grid at once, so\n compare the columns of one run and not one run against another.\n- **Operations are timed until the DOM changes, not for a fixed two\n frames.** The old fixed wait put a two-frame floor under every number -\n an operation that recomputed nothing at all measured the floor, and a\n mount whose rows were already in the DOM measured pure waiting - which\n flattered whichever grid was slower.\n- **Each figure is the fastest of the samples, not the median.** Noise\n only ever adds time, so the minimum is the cleanest estimate of what the\n machine can do, and medians on this box drifted by a third between\n consecutive runs - more than most of the differences being measured.\n Applied identically to every grid.\n\nWhat this table deliberately does not include:\n\n- **Features the grids do not measure the same way.** Grouping, pivot,\n editing and export all differ enough in shape that a single timing would\n compare two different amounts of work. The filter row above is the one\n case we publish anyway, labelled, rather than quietly dropping a result\n that happens to favour us.\n- **Any grid we cannot license for this.** The harness is grid-agnostic on\n purpose, but some commercial grids licence their software in ways that\n restrict using it to produce competitive claims. Where that is the case\n we do not ship an adapter, and we would rather have an obviously\n incomplete table than a legally dubious one. Run your own shortlist.\n- **Your workload.** One dataset shape, one machine, one browser, default\n configuration for every grid. If a grid decision rides on this, clone the\n harness and put your own data in it.\n\n## Migrating from AG Grid\n\nThe most common starting point. See\n[Migrating from AG Grid](./migrating-from-ag-grid.md) for a side-by-side\ntranslation of column defs, features, filtering, editing, and the\nimperative API. The example that guide is built around runs here:\n\n<div data-docs-demo=\"139-migration-from-ag-grid\" data-height=\"560\"></div>\n\n## Migrating from TanStack Table\n\nThe map is one-to-one - SvGrid's headless core speaks the vocabulary\nTanStack Table v9 introduced. The big differences:\n\n- Replace `createTable(opts)` with `createSvGrid(opts)`. Same state\n machine, same features object.\n- Replace the row-model factories with the same names from\n `@svgrid/grid`.\n- The render layer changes - TanStack hands you `FlexRender` + the\n row model; SvGrid lets you keep that headless approach OR drop in\n the default `<SvGrid>` component.\n\nThe headless demo below drives a plain `<table>` from `createSvGrid`, the\nway a TanStack app would:\n\n<div data-docs-demo=\"186-headless-table\" data-height=\"520\"></div>\n\nAnd the same rows through the render component, which is the part TanStack\nleaves to you. The example runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Order = {\n id: number\n customer: string\n region: string\n status: string\n amount: number\n }\n\n const orders: Order[] = [\n { id: 1, customer: 'Ada Lovelace', region: 'EMEA', status: 'open', amount: 1240 },\n { id: 2, customer: 'Grace Hopper', region: 'AMER', status: 'shipped', amount: 860 },\n { id: 3, customer: 'Linus Torvalds', region: 'EMEA', status: 'closed', amount: 2210 },\n { id: 4, customer: 'Radia Perlman', region: 'APAC', status: 'open', amount: 430 },\n { id: 5, customer: 'Barbara Liskov', region: 'AMER', status: 'pending', amount: 1780 },\n ]\n\n let rows = $state<Order[]>(orders)\n\n const columns: GridColumns<Order> = [\n { field: 'customer', header: 'Customer', width: 180 },\n { field: 'region', header: 'Region', width: 110 },\n { field: 'status', header: 'Status', width: 110 },\n { field: 'amount', header: 'Amount', width: 120, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable selectable />\n```\n\n## Pricing\n\nSvGrid Community is MIT - free for commercial use, no attribution\nrequired at runtime. SvGrid Enterprise is a per-developer licence: $599\nper developer per year for the enterprise grid or $999 with the\nspreadsheet and Studio, both for unlimited applications; see\n<https://svgrid.com/pricing/> for what each tier adds.\n\nAG Grid Community is MIT. AG Grid Enterprise is priced per developer with\none year of updates; the figure ag-grid.com listed on the date we read it\nis in the facts block at the top of this page, and the\n[SvGrid vs AG Grid](https://svgrid.com/compare/ag-grid/) page carries the\nlink. Compare what each paid tier adds before comparing prices: most of\nwhat AG Grid sells as Enterprise is in SvGrid's free core.\n\nTanStack Table is MIT and sponsor-funded; tanstack.com offers paid\nEnterprise Support as private consulting.\n\n## Frequently asked questions\n\n### What is the best data grid for Svelte 5?\n\nFor a Svelte-5-native grid with a batteries-included render component, SvGrid is\nbuilt around runes and snippets. TanStack Table is a strong headless-only\nchoice if you want to build the DOM layer yourself across frameworks, and its\nv9 Svelte adapter targets Svelte 5. AG Grid is the most feature-complete but\nlives in React, Angular and Vue first and reaches Svelte through\ncommunity-built integrations.\n\n### Is SvGrid a good AG Grid alternative?\n\nYes, for Svelte projects. SvGrid is a fraction of AG Grid Community's\nmeasured size on a Svelte page (the facts block has both numbers and the\nmethod), is MIT-licensed for commercial use, and offers `@svgrid/enterprise`\nfor export, print, import and pivot at a per-developer price. On the\nbenchmark above it sorts a hundred-thousand-row column faster on both\ncolumn types and scrolls level; AG Grid mounts quicker. It does not match\nevery AG Grid Enterprise feature - see the\n[missing-features list](./missing-features.md) for the gaps.\n\n### SvGrid vs TanStack Table - which should I pick?\n\nPick SvGrid if you want virtualization, Excel-style filters, selection, and\ninline editing working out of the box on Svelte 5. Pick TanStack Table if you\nwant a framework-agnostic headless engine and are happy to build the rendering,\nvirtualization, and editing UI yourself. Both are MIT-licensed.\n\n### Does the TanStack Svelte adapter support Svelte 5?\n\nYes. The `@tanstack/svelte-table` v9 line declares a Svelte 5 peer range\nand passes data through getters rather than stores; the facts block above\nshows the version read from npm. The earlier `createSvelteTable` constructor\nis gone in v9.\n\n### Does AG Grid have an MCP server like SvGrid?\n\nYes. `ag-mcp` (MIT) gives an assistant AG Grid's docs, examples and\nversion-specific upgrade prompts. `@svgrid/mcp` does the same for SvGrid\nand adds a code checker that validates props and imports against the real\nAPI surface, a scaffold tool and a preview. Neither is an in-grid feature;\nSvGrid's natural-language filter, smart fill and summarise helpers are, and\nthey ship free in `@svgrid/grid` with a model provider you register.\n\n### How big is the SvGrid bundle?\n\nThe facts block at the top of this page has the measured gzipped size of the\nfull `<SvGrid>` render component and its stylesheet, read from\n`docs/_data/svgrid-size.json`, which `pnpm size:json` writes. The\n[bundle size reference](./bundle-size.md) breaks it down by entry:\nthe headless core on its own, the core subpath, the charts, and the lazy\nchunks that load on demand.\n\n## See also\n\n- [Why headless?](../why-headless.md) - the design decision behind\n SvGrid's two-layer architecture.\n- [Migrating from AG Grid](./migrating-from-ag-grid.md) - the\n practical recipe.\n- [Migrating from TanStack Table](./migrating-from-tanstack-table.md) - the\n one-to-one API map.\n- [Benchmarks](./benchmarks.md) - how the numbers are produced and what\n they leave out.\n- [Enterprise feature pack](../enterprise/README.md) - what SvGrid charges for.\n- [Missing features](./missing-features.md) - the honest gap list\n versus AG Grid Enterprise.\n- [All comparisons](https://svgrid.com/compare/) - one page per grid, with\n dated sources for every claim.\n"
5650
+ "markdown": "\n# Comparison: SvGrid vs AG Grid vs TanStack Table\n\nThe three projects solve overlapping problems, and the right choice\ndepends on the framework you ship on, how much of the grid you want to\nbuild yourself, and your budget. Every number on this page is read from\nnpm or measured by a script in this repository on the date shown; the\nblock below is regenerated by `node tools/sync-guide-facts.mjs` and the\nper-competitor pages under [/compare/](https://svgrid.com/compare/) list\nthe sources for every feature claim.\n\n<!-- facts:start ag-grid,tanstack-table -->\n> **Facts, checked 9 Nov 2026.** `ag-grid-community` 36.3.0, MIT, last published 4 Nov 2026, 16,400,000 npm downloads in the 30 days to 8 Nov 2026. `@tanstack/svelte-table` 9.3.1, MIT, last published 12 Oct 2026, 539,000 npm downloads in the same window. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026); `ag-grid-community` 36.3.0 346.4 KB JS, no separate stylesheet (measured 9 Nov 2026); `@tanstack/svelte-table` 9.3.1 36.5 KB JS, no separate stylesheet, svelte external (measured 9 Nov 2026). AG Grid pricing, as its site states it: AG Grid Community is free under MIT. AG Grid Enterprise is listed at $999 USD per developer with one year of updates and Zendesk support; the Enterprise Bundle with AG Charts Enterprise is $1,498 USD per developer (https://www.ag-grid.com/license-pricing/, read 12 Sep 2026). TanStack Table pricing, as its site states it: TanStack Table is MIT and free; tanstack.com is sponsor-supported and offers Enterprise Support as private consulting and expert support, with no licence sold for the table (https://tanstack.com/table/latest, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs AG Grid (community + enterprise)](https://svgrid.com/compare/ag-grid/), [SvGrid vs TanStack Table (Svelte)](https://svgrid.com/compare/tanstack-table/).\n<!-- facts:end -->\n\n## TL;DR\n\n| Project | Lives in | Ships | Licence |\n| --------------------- | ---------------------------------------- | ---------------------------------------------------------- | ----------------------------------------- |\n| **SvGrid** | Svelte 5 | Headless core + Svelte render component + Enterprise pack | MIT (Community) / commercial (Enterprise) |\n| **AG Grid Community** | React, Angular, Vue, plain JS | Full grid + renderer; Svelte through community integrations | MIT |\n| **AG Grid Enterprise**| same | Adds the set filter, range selection, master/detail, tree, grouping, pivot, charts, Excel export, server-side row model | Commercial, per developer |\n| **TanStack Table** | React, Vue, Svelte, Solid, Qwik, Lit, JS | Headless engine **only**; the Svelte adapter is Svelte 5 | MIT |\n\nThe bundle sizes and prices are in the facts block above, with the date\nthey were read and the method behind the sizes.\n\n## When SvGrid is the right choice\n\n- You're on **Svelte 5** and want a grid that uses the runtime's idioms\n (snippets for cells, `$state` for data, `$derived` for aggregates) -\n not a React-port pretending to be Svelte.\n- You want a **headless core you can render yourself** AND a\n default-styled component for the 80% case. Most \"headless\" libraries\n make you write the markup; most \"monolith\" libraries make you fight\n the markup. SvGrid does both in one package.\n- You need **clean theming via CSS custom properties** and a documented\n `--sg-*` token surface, not a hard-coded class soup.\n- You ship under **strict CSP** (no `eval`, no `new Function`, no\n inline scripts). SvGrid runs clean; AG Grid Community does too.\n TanStack Table is engine-only so the question doesn't apply.\n- You want **SSR markup that is meaningful before hydration** (good\n first paint, SEO, SvelteKit `+page.server` integration). SvGrid +\n TanStack Table both qualify. AG Grid renders client-side.\n- You want the features AG Grid sells as Enterprise - the set filter,\n range selection, master/detail, tree data, grouping with aggregation,\n integrated charts, flat server-side infinite scroll - **in the MIT\n core**. (Server-side grouping, tree, pivot and transactions are\n Enterprise in both.)\n\n## When AG Grid is the right choice\n\n- You're on **React, Angular, or Vue**, not Svelte. SvGrid is\n Svelte-only, and ag-grid.com points Svelte users to community-built\n integrations rather than an official package.\n- You need a push-based **viewport row model** for a real-time trading\n blotter, where the server streams the visible window over a socket.\n SvGrid's server-side row model covers sort, filter, grouping, tree,\n pivot, transactions and select-all across unloaded rows, and its\n real-time page merges deltas into loaded rows, but it does not have the\n viewport model.\n- You need **custom tool panels**. SvGrid's tool panel is a fixed\n Columns + Filters pair. Custom filter components are covered by a\n column's `customFilter`.\n- You need **AG Charts** for maps, network graphs, 3D or a canvas renderer.\n SvGrid's chart is SVG with decimation, and it ships 29 types, a configurable\n axis model, synchronized charts, a financial toolkit with indicator panes\n and drawing tools, a builder and PDF export in the MIT core; it does not\n draw maps.\n- You want a vendor with **a decade of enterprise procurement paperwork**\n already on file.\n\n## When TanStack Table is the right choice\n\n- You want a **rendering-framework-agnostic engine** so the same\n business logic powers React + Svelte + Solid surfaces in your\n monorepo.\n- You're already in the TanStack ecosystem (Query, Router, Form,\n Virtual) and want one mental model.\n- You're happy writing **all the markup yourself** - the row recycling,\n the keyboard map, the ARIA roles, the focus management, the\n drag-to-resize. That's the cost of \"engine only\".\n\n## Feature parity at a glance\n\nYes: shipped in that edition. Partial: needs extra work or a companion\npackage. No: not available. The AG Grid columns follow ag-grid.com's\nCommunity vs Enterprise page and its Set Filter, Tree Data and CSV export\npages; the dated list of those sources is on the\n[SvGrid vs AG Grid](https://svgrid.com/compare/ag-grid/) page, and the\nTanStack sources on [SvGrid vs TanStack Table](https://svgrid.com/compare/tanstack-table/).\n\n| | SvGrid Community | SvGrid Enterprise | AG Grid Community | AG Grid Enterprise | TanStack Table |\n| ------------------------------- | ---------------- | ----------------- | ----------------- | ------------------ | -------------- |\n| Headless core (engine only) | Yes | Yes | No | No | Yes |\n| Default render component | Yes (Svelte 5) | Yes | Yes (each framework) | Yes | No |\n| Sort (multi-column) | Yes | Yes | Yes | Yes | Yes (engine) |\n| Filter menu (operator + facet) | Yes | Yes | Partial (text and number filters; the set filter is Enterprise) | Yes | No |\n| Filter row | Yes | Yes | Yes | Yes | No |\n| Pagination | Yes | Yes | Yes | Yes | Yes (engine) |\n| Grouping + aggregation | Yes | Yes | No (Enterprise) | Yes | Yes (engine) |\n| Tree / expand-collapse rows | Yes | Yes | No (Enterprise) | Yes | Yes (engine) |\n| Master/detail | Yes | Yes | No (Enterprise) | Yes | No |\n| Cell range selection + copy/paste | Yes | Yes | No (Enterprise) | Yes | No |\n| Fill handle | Yes | Yes | No (Enterprise) | Yes | No |\n| Inline editing (typed editors) | Yes | Yes | Yes | Yes | No |\n| Column virtualization | Yes | Yes | Yes | Yes | No |\n| Row virtualization | Yes | Yes | Yes | Yes | Partial (pair with TanStack Virtual) |\n| Column pinning (left/right) | Yes | Yes | Yes | Yes | No |\n| Column tool panel | Yes | Yes | No (Enterprise) | Yes | No |\n| Context menu | Yes | Yes | No (Enterprise) | Yes | No |\n| Fit-to-width with shrink | Yes | Yes | Partial | Yes | No |\n| WAI-ARIA grid pattern | Yes | Yes | Yes | Yes | No (your markup) |\n| Server-side data, flat (sort / filter / paging / infinite scroll) | Yes (built in) | Yes (built in) | Yes (infinite row model) | Yes (built in) | Partial (manual flags) |\n| Server-side row model (lazy grouping, tree, pivot, transactions, select-all across unloaded rows) | No (Enterprise) | Yes (built in) | No (Enterprise) | Yes (built in) | No |\n| Global search over server-side data | Yes (`filterModel.global`) | Yes | No (the quick filter is client-side only) | No | n/a |\n| CSP-clean (no eval, no inline) | Yes | Yes | Yes | Yes | n/a |\n| Meaningful SSR markup | Yes | Yes | No | No | depends on your markup |\n| CSV / TSV / JSON export | Yes | Yes | Yes (CSV) | Yes | No |\n| Excel (.xlsx) / PDF export | No | Yes | No | Yes (Excel) | No |\n| Print | No | Yes | No | No | No |\n| Excel / CSV import | No | Yes | No | No | No |\n| In-grid AI helpers (bring your own model) | Yes | Yes | No | No | No |\n| MCP server for AI assistants | Yes (`@svgrid/mcp`) | Yes | Yes (`ag-mcp`) | Yes | No (agent skills ship in the package) |\n| Pivot table | No | Yes | No | Yes | No (custom) |\n| Integrated charts | Yes (29 types, builder, financial toolkit) | Yes | No | Yes (AG Charts) | No |\n| Support response time | GitHub (best-effort) | 1 business day; 1h sev-1 on Enterprise | GitHub (best-effort) | no number published | GitHub; paid Enterprise Support offered |\n| Theming via CSS variables | Yes (`--sg-*`) | Yes | Yes (theme builder) | Yes | n/a |\n| Source button per demo | Yes (gallery) | Yes | No | No | No |\n\n## Bundle size\n\nThe facts block at the top of the page has the gzipped size of each\npackage, measured by the same method: each package built alone with Vite\nin library mode, minified, gzip level 9, Svelte external because it is a\npeer dependency. SvGrid's own number comes from `pnpm size:json`\n(`packages/grid/scripts/measure-size.mjs`), the competitors' from\n`pnpm competitors:measure`; both write `docs/_data` and the block is\nregenerated from there, so the page cannot quote a size nobody measured.\n\nWhat the SvGrid number contains: the whole render component -\nvirtualization, Excel-style filters, inline editing, grouping, tree,\nmaster/detail, cell selection and accessibility - in one import, plus a\nseparate stylesheet. Charts, date and time editors, menus and export split\ninto `import()` chunks that load on demand rather than shipping in the\ninitial bundle; the headless core on its own is a small fraction of the\nrender component, and `@svgrid/enterprise` features are separate subpath\nimports. The per-entry breakdown, including the headless core and the\nlazy chunks, is in the [bundle size reference](./bundle-size.md).\n\nWhat the AG Grid number contains: `createGrid` with every Community\nmodule registered and the Quartz theme, whose CSS ships inside the script\nunder the theming API, so there is no separate stylesheet to add. The\nTanStack number is the whole Svelte adapter with its engine: no\nvirtualizer, filter UI or editors, because a headless library has none.\n\n## Measured performance\n\nA vendor's own benchmark is worth nothing unless you can rerun it, so the\nharness is in the repository and takes an adapter per grid. Adding another\ngrid is about forty lines in `examples/src/bench/adapters.ts` and nothing\nelse.\n\n```bash\n# headless, prints the table and writes tests/perf/.last-compare.json\nBENCH_REPEATS=7 BENCH_GRIDS=svgrid,aggrid,svar,tanstack pnpm bench:compare\n\n# move that run into docs/_data/competitors.json, then regenerate this page\nnode tools/record-benchmarks.mjs && node tools/sync-guide-facts.mjs\n\n# or drive it by hand\npnpm --filter @svgrid/grid-example-gallery dev # then open /bench.html\n```\n\nEach operation is timed until the grid's DOM reflects it, plus one frame:\n\n- **Mount** - fresh container, create the grid, until rows are painted.\n- **Sort** - change the sort on one column, until the new order is painted.\n Text sorts `name` (tens of thousands of distinct values), numeric sorts\n `amount`.\n- **Filter** - apply a `contains` filter to one column.\n- **Scroll** - 180 frames at 60 px/frame, sampling frame intervals.\n\n### Results\n\nThe table is generated from the ledger by `tools/sync-guide-facts.mjs`;\nthe versions and the date are part of it.\n\n<!-- bench:start -->\nMeasured 28 Oct 2026 with `pnpm bench:compare` (tests/perf/compare.spec.ts, recorded by tools/record-benchmarks.mjs): 100,000 rows x 9 columns; 1000 x 520 px container, 32 px rows, 140 px columns, each grid with its default theme; fastest of 3 samples per operation, each grid in a fresh page; Chromium through Playwright, headless; win32 10.0.26200 x64, Intel(R) Core(TM) Ultra 7 255U; a developer workstation, not a dedicated bench rig; tick: 1,000 of the rows replaced per tick with a new amount, the grid sorted by amount, on the update path each grid provides, timed until the changed cells paint; 180 ticks after 10 to warm up. Lower is better.\n\n| Operation | SvGrid | AG Grid Community | SVAR Svelte DataGrid | TanStack Table, minimal DOM |\n| --- | --- | --- | --- | --- |\n| Mount | 30.7 ms | 67 ms | 11.4 ms | 170.2 ms |\n| Sort, text column | 77.4 ms | 213.9 ms | 135.4 ms | 360.9 ms |\n| Sort, numeric column | 32.8 ms | 216.7 ms | 141.7 ms | 178.2 ms |\n| Filter, one column (indicative only, see below) | 34.5 ms | 148.8 ms | 26.1 ms | 51.1 ms |\n| Scroll, p95 frame | 34.3 ms | 34.5 ms | 34.6 ms | 34.3 ms |\n| Live tick, 1,000 rows replaced, sorted by that column, p95 | 48.6 ms | 259.2 ms | 152.2 ms | 563.4 ms |\n| Main-thread work per 60 px scroll step, mean | 3.5 ms | 4.5 ms | 3 ms | 2.9 ms |\n| Frames dropped while scrolling, of 180 | 0 | 0 | 0 | 0 |\n| Ticks over one 60 Hz frame, of 180 | 115 | 180 | 180 | 180 |\n| Rows kept in the DOM (virtualization on) | 36 | 36 | 19 | 27 |\n| JS heap the grid adds, mounted, after GC | 5.7 MB | 42.1 MB | 2.3 MB | 109.9 MB |\n| JS heap the grid adds, after sorting and filtering, after GC | 17.6 MB | 26.2 MB | 3.9 MB | 113.3 MB |\n| Elements created per scroll frame | 0 | 30.1 | 16.8 | 18.7 |\n| Elements re-inserted per scroll frame (rows recycled) | 37.3 | 35.8 | 0 | 0 |\n\nVersions: `@svgrid/grid` 3.0.25, `ag-grid-community` 36.1.0, `wx-svelte-grid` 2.7.0, `@tanstack/svelte-table` 9.2.4.\n<!-- bench:end -->\n\nRead that as: **SvGrid sorts and keeps a live sort current faster than the\nother three, scrolling is level across all four, and SVAR is ahead on mount\nand memory** - it paints its first rows in under half of SvGrid's time and\nholds the least heap. Every grid scrolls at the display rate here, so the\np95 frame reads the same for all four; the work row under it is what a\nslower machine or a 120 Hz display would feel. There TanStack and SVAR do\nthe least per scroll step, about half a millisecond under SvGrid, and AG\nGrid the most. The row varies from run to run, so read the order of the\nfirst three as close, not settled. SvGrid makes its row objects the first time a\nsort or filter reads every row rather than at mount, which is why its two\nheap rows differ. The TanStack renderer pays for building a row object per\nrecord before it can draw anything. Anyone claiming a single headline\nnumber for a grid comparison is selling something.\n\n**The heap rows are the JS heap after a forced garbage collection, less the\nsame page with the data built and no grid,** so the 100,000 rows themselves\ncount against no one. The two DOM rows are counted over 60 untimed scroll\nframes after the timed ones. \"Created\" is elements that did not exist\nbefore; \"re-inserted\" is elements the grid already had and moved, which is\nhow a keyed list recycles a row from one end of the window to the other.\nSvGrid creates none and moves the two rows that cross the edge each frame;\na grid that rewrote its rows in place would score 0 on both.\n\n**The filter row is not a like-for-like comparison and is shown only because\nhiding a number we win looks worse than explaining it.** The grids' single-\ncolumn filter APIs differ: the harness drives AG Grid's quick filter, which\nsearches every column and is strictly more work than the single-column\n`contains` SvGrid performs, while SVAR and TanStack run a predicate over the\none column. Do not read a ratio into that row.\n\n**The TanStack column is an engine plus the least DOM an app could draw.**\nTanStack Table renders nothing, so its adapter draws the row model through\na fixed-height windowed table with no virtualizer library, no filter UI and\nno editors. Its mount and sort numbers include creating the engine's row\nobjects for every record; the grids around it do the same work inside their\nown models.\n\nSorting is where SvGrid's distance comes from, and it is not subtle: SvGrid\nresolves each sort clause once and precomputes a key array, and for a\ncolumn whose distinct values are far fewer than its rows it collates the\ndistinct values once and sorts by rank. Mounting is the other direction -\nsee the accounting in [benchmarks](./benchmarks.md).\n\nAt 1,000,000 rows the harness runs one grid per invocation\n(`BENCH_ROWS=1000000 BENCH_GRIDS=<one> BENCH_TICKS=30`); TanStack's\nadapter does not finish at that size. Those runs are not in the table\nbecause only a run that measured every grid together is comparable.\n\nTwo methodology notes, both of which were bugs in this harness before they\nwere notes, and both of which changed the numbers by more than any code\nchange did:\n\n- **Each grid runs in a fresh page.** They used to run one after another in\n the same one, where the first warmed the JIT, fragmented the heap and\n left a hundred thousand rows of garbage for the next. Back-to-back runs\n on an idle machine disagreed with themselves by a factor of two.\n That order effect is gone, but this workstation still varies by about\n 2x between whole runs taken minutes apart, for every grid at once, so\n compare the columns of one run and not one run against another.\n- **Operations are timed until the DOM changes, not for a fixed two\n frames.** The old fixed wait put a two-frame floor under every number -\n an operation that recomputed nothing at all measured the floor, and a\n mount whose rows were already in the DOM measured pure waiting - which\n flattered whichever grid was slower.\n- **Each figure is the fastest of the samples, not the median.** Noise\n only ever adds time, so the minimum is the cleanest estimate of what the\n machine can do, and medians on this box drifted by a third between\n consecutive runs - more than most of the differences being measured.\n Applied identically to every grid.\n\nWhat this table deliberately does not include:\n\n- **Features the grids do not measure the same way.** Grouping, pivot,\n editing and export all differ enough in shape that a single timing would\n compare two different amounts of work. The filter row above is the one\n case we publish anyway, labelled, rather than quietly dropping a result\n that happens to favour us.\n- **Any grid we cannot license for this.** The harness is grid-agnostic on\n purpose, but some commercial grids licence their software in ways that\n restrict using it to produce competitive claims. Where that is the case\n we do not ship an adapter, and we would rather have an obviously\n incomplete table than a legally dubious one. Run your own shortlist.\n- **Your workload.** One dataset shape, one machine, one browser, default\n configuration for every grid. If a grid decision rides on this, clone the\n harness and put your own data in it.\n\n## Migrating from AG Grid\n\nThe most common starting point. See\n[Migrating from AG Grid](./migrating-from-ag-grid.md) for a side-by-side\ntranslation of column defs, features, filtering, editing, and the\nimperative API. The example that guide is built around runs here:\n\n<div data-docs-demo=\"139-migration-from-ag-grid\" data-height=\"560\"></div>\n\n## Migrating from TanStack Table\n\nThe map is one-to-one - SvGrid's headless core speaks the vocabulary\nTanStack Table v9 introduced. The big differences:\n\n- Replace `createTable(opts)` with `createSvGrid(opts)`. Same state\n machine, same features object.\n- Replace the row-model factories with the same names from\n `@svgrid/grid`.\n- The render layer changes - TanStack hands you `FlexRender` + the\n row model; SvGrid lets you keep that headless approach OR drop in\n the default `<SvGrid>` component.\n\nThe headless demo below drives a plain `<table>` from `createSvGrid`, the\nway a TanStack app would:\n\n<div data-docs-demo=\"186-headless-table\" data-height=\"520\"></div>\n\nAnd the same rows through the render component, which is the part TanStack\nleaves to you. The example runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Order = {\n id: number\n customer: string\n region: string\n status: string\n amount: number\n }\n\n const orders: Order[] = [\n { id: 1, customer: 'Ada Lovelace', region: 'EMEA', status: 'open', amount: 1240 },\n { id: 2, customer: 'Grace Hopper', region: 'AMER', status: 'shipped', amount: 860 },\n { id: 3, customer: 'Linus Torvalds', region: 'EMEA', status: 'closed', amount: 2210 },\n { id: 4, customer: 'Radia Perlman', region: 'APAC', status: 'open', amount: 430 },\n { id: 5, customer: 'Barbara Liskov', region: 'AMER', status: 'pending', amount: 1780 },\n ]\n\n let rows = $state<Order[]>(orders)\n\n const columns: GridColumns<Order> = [\n { field: 'customer', header: 'Customer', width: 180 },\n { field: 'region', header: 'Region', width: 110 },\n { field: 'status', header: 'Status', width: 110 },\n { field: 'amount', header: 'Amount', width: 120, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable selectable />\n```\n\n## Pricing\n\nSvGrid Community is MIT - free for commercial use, no attribution\nrequired at runtime. SvGrid Enterprise is a per-developer licence: $599\nper developer per year for the enterprise grid or $999 with the\nspreadsheet and Studio, both for unlimited applications; see\n<https://svgrid.com/pricing/> for what each tier adds.\n\nAG Grid Community is MIT. AG Grid Enterprise is priced per developer with\none year of updates; the figure ag-grid.com listed on the date we read it\nis in the facts block at the top of this page, and the\n[SvGrid vs AG Grid](https://svgrid.com/compare/ag-grid/) page carries the\nlink. Compare what each paid tier adds before comparing prices: most of\nwhat AG Grid sells as Enterprise is in SvGrid's free core.\n\nTanStack Table is MIT and sponsor-funded; tanstack.com offers paid\nEnterprise Support as private consulting.\n\n## Frequently asked questions\n\n### What is the best data grid for Svelte 5?\n\nFor a Svelte-5-native grid with a batteries-included render component, SvGrid is\nbuilt around runes and snippets. TanStack Table is a strong headless-only\nchoice if you want to build the DOM layer yourself across frameworks, and its\nv9 Svelte adapter targets Svelte 5. AG Grid is the most feature-complete but\nlives in React, Angular and Vue first and reaches Svelte through\ncommunity-built integrations.\n\n### Is SvGrid a good AG Grid alternative?\n\nYes, for Svelte projects. SvGrid is a fraction of AG Grid Community's\nmeasured size on a Svelte page (the facts block has both numbers and the\nmethod), is MIT-licensed for commercial use, and offers `@svgrid/enterprise`\nfor export, print, import and pivot at a per-developer price. On the\nbenchmark above it sorts a hundred-thousand-row column faster on both\ncolumn types and scrolls level; AG Grid mounts quicker. It does not match\nevery AG Grid Enterprise feature - see the\n[missing-features list](./missing-features.md) for the gaps.\n\n### SvGrid vs TanStack Table - which should I pick?\n\nPick SvGrid if you want virtualization, Excel-style filters, selection, and\ninline editing working out of the box on Svelte 5. Pick TanStack Table if you\nwant a framework-agnostic headless engine and are happy to build the rendering,\nvirtualization, and editing UI yourself. Both are MIT-licensed.\n\n### Does the TanStack Svelte adapter support Svelte 5?\n\nYes. The `@tanstack/svelte-table` v9 line declares a Svelte 5 peer range\nand passes data through getters rather than stores; the facts block above\nshows the version read from npm. The earlier `createSvelteTable` constructor\nis gone in v9.\n\n### Does AG Grid have an MCP server like SvGrid?\n\nYes. `ag-mcp` (MIT) gives an assistant AG Grid's docs, examples and\nversion-specific upgrade prompts. `@svgrid/mcp` does the same for SvGrid\nand adds a code checker that validates props and imports against the real\nAPI surface, a scaffold tool and a preview. Neither is an in-grid feature;\nSvGrid's natural-language filter, smart fill and summarise helpers are, and\nthey ship free in `@svgrid/grid` with a model provider you register.\n\n### How big is the SvGrid bundle?\n\nThe facts block at the top of this page has the measured gzipped size of the\nfull `<SvGrid>` render component and its stylesheet, read from\n`docs/_data/svgrid-size.json`, which `pnpm size:json` writes. The\n[bundle size reference](./bundle-size.md) breaks it down by entry:\nthe headless core on its own, the core subpath, the charts, and the lazy\nchunks that load on demand.\n\n## See also\n\n- [Why headless?](../why-headless.md) - the design decision behind\n SvGrid's two-layer architecture.\n- [Migrating from AG Grid](./migrating-from-ag-grid.md) - the\n practical recipe.\n- [Migrating from TanStack Table](./migrating-from-tanstack-table.md) - the\n one-to-one API map.\n- [Benchmarks](./benchmarks.md) - how the numbers are produced and what\n they leave out.\n- [Enterprise feature pack](../enterprise/README.md) - what SvGrid charges for.\n- [Missing features](./missing-features.md) - the honest gap list\n versus AG Grid Enterprise.\n- [All comparisons](https://svgrid.com/compare/) - one page per grid, with\n dated sources for every claim.\n"
5651
5651
  },
5652
5652
  {
5653
5653
  "slug": "help/conditional-form-schema",
@@ -6067,7 +6067,7 @@ export const docs = [
6067
6067
  "path": "docs/help/migrating-from-ag-grid.md",
6068
6068
  "title": "Migrating from AG Grid to SvGrid",
6069
6069
  "section": "Help",
6070
- "markdown": "\n# Migrating from AG Grid to SvGrid\n\nIf you tried AG Grid on a Svelte 5 project - via `ag-grid-svelte`, the\nold `ag-grid-community/svelte`, or a hand-rolled wrapper - you probably\nhit the same friction everyone hits: the bridge between AG Grid's\nReact/Angular-first API and Svelte 5 runes is brittle, the bundle is\nheavy, and the Enterprise pricing only makes sense at scale.\n\n<!-- facts:start ag-grid -->\n> **Facts, checked 9 Nov 2026.** `ag-grid-community` 36.3.0, MIT, last published 4 Nov 2026, 16,400,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026); `ag-grid-community` 36.3.0 346.4 KB JS, no separate stylesheet (measured 9 Nov 2026). AG Grid pricing, as its site states it: AG Grid Community is free under MIT. AG Grid Enterprise is listed at $999 USD per developer with one year of updates and Zendesk support; the Enterprise Bundle with AG Charts Enterprise is $1,498 USD per developer (https://www.ag-grid.com/license-pricing/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs AG Grid (community + enterprise)](https://svgrid.com/compare/ag-grid/).\n<!-- facts:end -->\n\nThis page is a 30-minute migration recipe from AG Grid to SvGrid. It\ncovers what maps 1:1, what's different by design, and what you'll lose.\nWe tell you when **not** to switch at the bottom.\n\n## TL;DR\n\n| | AG Grid Community | AG Grid Enterprise | SvGrid Community | @svgrid/enterprise |\n| --- | --- | --- | --- | --- |\n| **Licence** | MIT | Commercial, per developer (the price is in the facts box above) | **MIT** | $599/dev/yr (grid) or $999/dev/yr (grid + spreadsheet + Studio) |\n| **Svelte 5 native** | No (community-built integration) | No (community-built integration) | Yes | Yes |\n| **Bundle (gzipped)** | measured, in the facts box above | not measured (licence) | measured, in the facts box above | lazy-loaded subpaths |\n| **Sorting / filtering** | Yes | Yes | Yes | (in Community) |\n| **Row grouping + aggregation** | No (Enterprise) | Yes | Yes (free) | (in Community) |\n| **Master/detail, tree, range select** | No (Enterprise) | Yes | Yes (free) | (in Community) |\n| **Set filter / Excel-style filter menu** | No (Enterprise) | Yes | Yes (free) | (in Community) |\n| **Server-side data, flat (infinite row model)** | Yes | Yes | Yes (free) | (in Community) |\n| **Server-side row model (grouping, tree, pivot, transactions, selection)** | No (Enterprise) | Yes | No | Yes |\n| **Integrated charts** | No (Enterprise) | Yes, AG Charts | Yes (free) | (in Community) |\n| **CSV export** | Yes (API) | Yes | Yes, with TSV and JSON | (in Community) |\n| **Excel export** | No | Yes | No | Yes |\n| **PDF / styled-HTML export, print** | No | No | No | Yes |\n| **Pivot tables** | No | Yes | No | Yes |\n| **MCP server for AI assistants** | Yes, `ag-mcp` | Yes | Yes, `@svgrid/mcp` | (in Community) |\n| **In-grid AI helpers** | No | No | Yes (bring your own model) | (in Community) |\n\n**SvGrid Community gives you most of what AG Grid sells as Enterprise for\nfree**, and `@svgrid/enterprise` adds Excel, PDF and print output, import,\npivot tables and the server-side row model per developer per year. Compare what each paid tier adds\nbefore comparing prices; both are in the facts box. The trade-offs are\nSvelte-only and a much smaller ecosystem. Every AG Grid cell above follows\nag-grid.com's own pages; the dated list is on the\n[SvGrid vs AG Grid](https://svgrid.com/compare/ag-grid/) page.\n\n## Mental model - what changes\n\nAG Grid is one big object you configure declaratively. SvGrid is a\n**headless engine** (`createSvGrid`) with an optional **render\ncomponent** (`<SvGrid>`) on top - the same split TanStack Table made\npopular. You can use either layer; most projects use the render\ncomponent.\n\nEvery example below runs against this setup:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature, type ColumnDef } from '@svgrid/grid'\n\n type Row = { id: number; make: string; model: string; price: number }\n\n const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n\n let rows = $state<Row[]>([\n { id: 1, make: 'Toyota', model: 'Celica', price: 35000 },\n { id: 2, make: 'Ford', model: 'Mondeo', price: 32000 },\n { id: 3, make: 'Porsche', model: 'Boxster', price: 72000 },\n ])\n const data = rows\n\n const columns: ColumnDef<typeof features, Row>[] = [\n { field: 'make', header: 'Make' },\n { field: 'model', header: 'Model' },\n { field: 'price', header: 'Price', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```svelte\n<!-- AG Grid (via a Svelte wrapper) -->\n<AgGridSvelte\n gridOptions={{\n rowData: rows,\n columnDefs: columns,\n onGridReady: (params) => (gridApi = params.api),\n }}\n/>\n\n<!-- SvGrid -->\n<SvGrid\n data={rows}\n columns={columns}\n features={features}\n onApiReady={(api) => (gridApi = api)}\n/>\n```\n\nThree things to note:\n\n1. **No giant `gridOptions` blob.** Each capability is a top-level prop.\n2. **Features are opt-in.** You pass a `features` object built with\n `tableFeatures({...})` - only the features you list ship JS.\n3. **`onApiReady`** gives you a typed `SvGridApi` that is roughly the\n AG Grid `gridApi` equivalent (see the API-mapping table below).\n\n## Column definitions - direct translation\n\nThe shapes are similar enough that you can usually translate by hand\nwithout thinking too hard.\n\n```ts\n// AG Grid\nconst columnDefs: ColDef[] = [\n { field: 'name', headerName: 'Name', sortable: true, filter: true, width: 200 },\n { field: 'price', headerName: 'Price', type: 'numericColumn',\n valueFormatter: ({ value }) => `$${value.toFixed(2)}` },\n { field: 'date', headerName: 'Date',\n valueGetter: ({ data }) => new Date(data.date).toISOString().slice(0, 10) },\n { field: 'status', headerName: 'Status',\n cellRenderer: StatusCellRenderer,\n cellRendererParams: { onChange: handleStatusChange } },\n]\n```\n\n```ts\n// SvGrid\nimport { renderComponent, type ColumnDef } from '@svgrid/grid'\nimport StatusCell from './StatusCell.svelte'\n\nconst columns: ColumnDef<typeof features, Row>[] = [\n { field: 'name', header: 'Name', width: 200 }, // sortable + filterable by default\n { field: 'price', header: 'Price',\n format: { type: 'currency', currency: 'USD' } },\n { field: 'date', header: 'Date',\n format: { type: 'date', pattern: 'y-m-d' } },\n { field: 'status', header: 'Status',\n cell: renderComponent(StatusCell, (ctx) => ({\n value: ctx.getValue(),\n onChange: handleStatusChange,\n })),\n },\n]\n```\n\n### Property mapping\n\n| AG Grid | SvGrid | Notes |\n| --- | --- | --- |\n| `field` | `field` | Same. |\n| `headerName` | `header` | Accepts a string or a snippet/component. |\n| `width` | `width` | Same. |\n| `minWidth` / `maxWidth` | `minWidth` / `maxWidth` | Same. |\n| `sortable: true` | (default) | Sorting is on when `rowSortingFeature` is registered. |\n| `filter: true` | (default) | Filtering is on when `columnFilteringFeature` is registered. |\n| `valueFormatter` | `format: { ... }` | Built-in types: `number`, `currency`, `percent`, `date`. For custom, use `cell`. |\n| `valueGetter` | `fieldFn` | Returns the value for sorting/filtering. |\n| `cellRenderer` + `cellRendererParams` | `cell: renderComponent(C, ctx => props)` | One call, type-checked. |\n| `cellEditor: 'agTextCellEditor'` | `editorType: 'text'` | Built-in: `text`, `number`, `checkbox`, `date`. |\n| `editable: true` | `enableInlineEditing` prop on `<SvGrid>` | Per-grid, not per-column. (Per-column control on the roadmap.) |\n| `pinned: 'left'` / `'right'` | Right-click column menu → Pin | Set programmatically via the api. |\n| `rowGroup: true` | Via `setGroupBy([colId])` | See Grouping below. |\n| `aggFunc: 'sum'` | `aggregate: 'sum'` | Built-in: `sum`, `avg`, `min`, `max`, `count`. |\n\n## Feature registration - the one new thing\n\nAG Grid auto-enables most features; you turn them off. SvGrid is the\nopposite - features are opt-in. The result is a smaller bundle.\n\n```ts\nimport {\n tableFeatures,\n rowSortingFeature,\n columnFilteringFeature,\n columnGroupingFeature,\n rowExpandingFeature,\n rowPaginationFeature,\n rowSelectionFeature,\n} from '@svgrid/grid'\n\nconst features = tableFeatures({\n rowSortingFeature,\n columnFilteringFeature,\n rowSelectionFeature,\n // omit any you don't need - their code won't ship\n})\n```\n\nPass `features` to `<SvGrid>` once. From then on the grid behaves like\nAG Grid's `enableSorting`, `enableFilter`, `rowSelection`, etc. are all\non for the registered features.\n\n## API mapping (`gridApi` → `SvGridApi`)\n\nYou get the SvGrid API from `onApiReady` (equivalent to AG Grid's\n`onGridReady`).\n\n| AG Grid `gridApi.X()` | SvGrid `api.X()` |\n| --- | --- |\n| `setRowData(rows)` | (declarative - just update `data` prop) |\n| `addRow(row)` / `applyTransaction({ add: [row] })` | `api.addRow(row)` / `api.addRows(rows)` |\n| `applyTransaction({ remove: [row] })` | `api.removeRow(rowIndex)` |\n| `getValue(colId, rowNode)` | `api.getCellValue(rowIndex, columnId)` |\n| `setValue(...)` | `api.setCellValue(rowIndex, columnId, value)` |\n| `setColumnVisible(colId, visible)` | `api.setColumnVisible(columnId, visible)` |\n| `getSortModel()` / `setSortModel()` | `api.setSort(columnId, 'asc'\\|'desc'\\|null)` |\n| `setFilterModel({...})` | `api.setFilter(columnId, { operator, value })` |\n| `getDisplayedRowAtIndex(i)` / `forEachNodeAfterFilterAndSort(...)` | `api.getDisplayedRows()` |\n| `getModel()` (raw rows) | `api.getData()` |\n\n## Common patterns\n\n### Sorting + filtering + pagination (the 80% case)\n\n```svelte\n<script lang=\"ts\">\n import {\n SvGrid,\n tableFeatures,\n rowSortingFeature,\n columnFilteringFeature,\n rowPaginationFeature,\n } from '@svgrid/grid'\n\n const features = tableFeatures({\n rowSortingFeature,\n columnFilteringFeature,\n rowPaginationFeature,\n })\n</script>\n\n<SvGrid\n data={rows}\n columns={columns}\n features={features}\n showPagination\n showColumnFilters\n/>\n```\n\nAG Grid equivalent: `gridOptions: { defaultColDef: { sortable: true, filter: true }, pagination: true }`.\n\n### Cell editing with persistence\n\n```svelte\n<script lang=\"ts\">\n function onCellValueChange(e: { rowIndex: number; columnId: string; value: unknown }) {\n // Persist however you like (fetch to backend, optimistic local update, etc.)\n console.log('cell changed', e)\n }\n</script>\n\n<SvGrid\n data={rows}\n columns={columns}\n features={features}\n enableInlineEditing\n onCellValueChange={onCellValueChange}\n/>\n```\n\nAG Grid equivalent: `onCellValueChanged: ({ data, colDef, newValue, oldValue }) => ...`.\nSvGrid's event payload is column-id + row-index based rather than node-based; the row data is yours\nto mutate (or not) on the `rows` array you passed in.\n\n### Grouping + aggregation\n\n```svelte\n<script lang=\"ts\">\n import {\n SvGrid,\n tableFeatures,\n columnGroupingFeature,\n rowSortingFeature,\n rowExpandingFeature,\n } from '@svgrid/grid'\n\n const features = tableFeatures({\n rowSortingFeature,\n columnGroupingFeature,\n rowExpandingFeature,\n })\n\n const columns = [\n { field: 'department', header: 'Department' },\n { field: 'team', header: 'Team' },\n { field: 'salary', header: 'Salary', aggregate: 'sum',\n format: { type: 'currency', currency: 'USD' } },\n ]\n\n function setGroup(api) {\n api.setGroupBy(['department', 'team'])\n }\n</script>\n\n<SvGrid\n data={rows}\n columns={columns}\n features={features}\n showGroupingControls\n onApiReady={setGroup}\n/>\n```\n\nAG Grid Enterprise's `rowGroupPanelShow: 'always'` + `aggFunc: 'sum'` translates 1:1.\n\n### Master / detail\n\nAG Grid Enterprise feature; **free in SvGrid Community**. See\n[demo 08](https://svgrid.com/demos/08-tree-and-master-detail/) for the exact pattern.\n\n### Server-side data\n\nAG Grid's Infinite Row Model (Community) and Server-Side Row Model\n(Enterprise) both take an `IServerSideDatasource` with a `getRows(params)`\nthat answers through `params.success({ rowData, rowCount })`. SvGrid has one\n`ServerDataSource` whose `getRows(request)` returns `{ rows, rowCount }`,\nand two controllers over it: `createServerDataSource` (free: paging or\ninfinite block scroll, sort, filter, CRUD) and `createServerRowModel`\n(Enterprise: lazy grouping, tree, pivot, transactions, selection). Both\nmount through one prop, `<SvGrid rowModel={ctl} />`.\n\nAn existing datasource written for AG Grid keeps working behind one call:\n\n```ts\nimport { adaptCallbackDatasource, createServerRowModel } from '@svgrid/enterprise'\n\nconst ctl = createServerRowModel(adaptCallbackDatasource(myServerSideDatasource), {\n groupBy: ['country'],\n aggregations: [{ col: 'amount', fn: 'sum' }],\n})\n```\n\n`adaptCallbackDatasource` maps the request both ways (`rowGroupCols` ->\n`groupBy`, `valueCols` -> `aggregations`, `pivotCols` -> `pivotBy`, the\nsort and filter models, `context`, `parentNode`) and turns `success` /\n`fail` into a resolved or rejected promise.\n\nMore often the datasource is a thin `fetch` and the real investment is the\nendpoint behind it - a Java or Node service that parses AG Grid's\n`IServerSideGetRowsRequest` JSON. That endpoint stays as it is: post\n`toCallbackRequest(request)` and read the answer back.\n\n```ts\nimport { toCallbackRequest } from '@svgrid/enterprise'\n\nconst source = {\n async getRows(request) {\n const res = await fetch('/api/sales', {\n method: 'POST',\n headers: { 'content-type': 'application/json' },\n body: JSON.stringify(toCallbackRequest(request)),\n })\n const { rowData, rowCount, pivotResultFields } = await res.json()\n return { rows: rowData, rowCount: rowCount ?? -1, pivotResultFields }\n },\n}\n```\n\n`fromCallbackRequest` is the other direction, for a SvelteKit endpoint that\nhas to keep serving an AG Grid client during the switch. A saved selection\nor a bulk endpoint written against `getServerSideSelectionState()` keeps\nits shape the same way: `toCallbackSelectionState(ctl.getSelectionState())`\nproduces `{ selectAll, toggledNodes }` (or the `nodeId` /\n`selectAllChildren` / `toggledNodes` tree), `ctl.setSelectionState` takes\nthat shape as it is when your group node ids are the group keys, and\n`fromCallbackSelectionState(state, { groupKey, isGroup })` maps them when\na `getRowId` gave group rows ids of their own. Option by option:\n\n| AG Grid | SvGrid |\n| --- | --- |\n| `rowModelType: 'infinite'` + `datasource` | `createServerDataSource(source, { mode: 'infinite' })` + `rowModel={ctl}` |\n| `rowModelType: 'serverSide'` + `serverSideDatasource` | `createServerRowModel(source, options)` + `rowModel={ctl}` |\n| `getRows(params)` + `params.success({ rowData, rowCount })` / `params.fail()` | `getRows(request)` returning `{ rows, rowCount }` / throwing |\n| `cacheBlockSize`, `maxBlocksInCache`, `maxConcurrentDatasourceRequests`, `blockLoadDebounceMillis` | `blockSize`, `maxBlocksInCache`, `maxConcurrentRequests`, `blockLoadDebounceMs` |\n| `infiniteInitialRowCount` / `serverSideInitialRowCount` | `initialRowCount` |\n| `rowCount: -1` (unknown) | `rowCount: -1` |\n| `refreshInfiniteCache()` / `purgeInfiniteCache()` | `ctl.refresh()` / `ctl.purge()` |\n| `request.rowGroupCols`, `groupKeys`, `valueCols`, `pivotCols`, `pivotMode` | `request.groupBy`, `groupKeys`, `aggregations`, `pivotBy`, `pivotMode` |\n| `getChildCount(data)` | `childCount: (row) => row.childCount` |\n| `isServerSideGroupOpenByDefault` | `isGroupOpenByDefault(route, row)` |\n| `getServerSideGroupLevelParams` | `levelParams(level, route)` |\n| `isServerSideGroup` / `getServerSideGroupKey` (tree) | `treeData: true` + `hasChildren` / `getRowId` |\n| `grandTotalRow` / `groupTotalRow` | `grandTotalRow` / `groupFooters` |\n| `refreshServerSide({ route, purge })` / `retryServerSideLoads()` | `ctl.refresh({ route, purge })` / `ctl.retryLoads()` |\n| `applyServerSideTransaction` / `applyServerSideTransactionAsync` / `flushServerSideAsyncTransactions` | `ctl.applyTransaction` / `applyTransactionAsync` / `flushAsyncTransactions` |\n| `applyServerSideRowData` | `ctl.applyRowData` |\n| `serverSideSortAllLevels`, `serverSideEnableClientSideSort`, `serverSideOnlyRefreshFilteredGroups` | `sortAllLevels`, `clientSideSort`, `onlyRefreshFilteredGroups` |\n| `getServerSideSelectionState` / `setServerSideSelectionState` | `ctl.getSelectionState()` / `setSelectionState()` (the `toggledNodes` shape is accepted; `toCallbackSelectionState` / `fromCallbackSelectionState` convert) |\n| `ServerSideTransactionResult.status`: `Applied`, `StoreNotFound`, `StoreLoading`, `StoreWaitingToLoad`, `StoreLoadingFailed`, `Cancelled` | `ServerTransactionResult.status`: the same six, lower camel case (`applied`, `storeNotFound`, ...) - a `switch` on the old spelling falls through silently |\n| `groupSelects: 'descendants'` | `selection: { groupSelects: 'descendants' }` |\n| `pivotResultFields` in `success`, `setPivotResultColumns`, `processPivotResultColDef` | `pivotResultFields` / `pivotResultColumns` in the result, `pivotResultColumn(field, def)` |\n| `pagination` + `paginateChildRows` | `pagination: { pageSize, paginateChildRows }` |\n| `getCacheBlockState()` / `getServerSideGroupLevelState()` | `ctl.getCacheState()` / `ctl.levelStates()` |\n| `serverSideDatasource.destroy()` | `source.destroy()` |\n\nTwo differences worth knowing before you start: SvGrid sends the global\nsearch box to the server as `filterModel.global` (AG Grid's quick filter is\nclient-side only and unsupported under its infinite and server-side models),\nand SvGrid has no viewport row model. See\n[Server grouping](./server/server-grouping.md) and\n[demo 467](https://svgrid.com/demos/467-server-row-model-1m/).\n\n### Excel / PDF export\n\nAG Grid: `gridApi.exportDataAsExcel({...})` (Enterprise-only).\nSvGrid: install `@svgrid/enterprise`, call `api.exportData({ format: 'xlsx', ... })`. See [Data export and printing](./export.md).\n\n```ts\nimport { installEnterprise, setLicenseKey } from '@svgrid/enterprise'\nsetLicenseKey('YOUR-LICENSE-KEY') // your Enterprise key\n\n// inside onApiReady:\nconst pro = installEnterprise(api)\nawait pro.exportData({ format: 'xlsx', filename: 'orders' })\n```\n\n## Gotchas - things that don't translate directly\n\n### 1. Per-column `editable: true`\nEditing is switched on at the grid level (`enableInlineEditing`) and\nnarrowed per column with `editable: boolean | (ctx) => boolean` on the\ncolumn definition, so AG Grid's per-column flag and its callback form both\nmap directly. What does not map is AG Grid's `editable` on a column\ngroup: set it on each child column.\n\n### 2. Column drag-to-reorder\nHeader drag is `enableColumnReorder` on `<SvGrid>`; `setColumnOrder`\non the API does the same from code. See\n[column moving](./columns/column-moving.md) for the events.\n\n### 3. AG Grid `valueGetter` chains\nAG Grid's `valueGetter` can read other column values via the API. In\nSvGrid, `fieldFn` only receives the row; if you need cross-column\ncomputed values, do it in the cell renderer with `ctx.row.original` or\ncompute the derived value upstream and store it in the row.\n\n### 4. `cellClass` / `rowClass` callbacks\nOn the roadmap. For now, render a wrapper element in your `cell` snippet\nwith the conditional class.\n\n### 5. The Status Bar / Side Bar / Tool Panels\nAG Grid's chrome (status bar with row count, side bar with filters and\ncolumns panels) doesn't exist in SvGrid - build it as plain Svelte\nmarkup around the grid. Most teams build their own anyway because\nAG Grid's defaults rarely match a polished design system.\n\n### 6. Set filter (the Excel-style funnel popup)\nSvGrid ships an Excel-style filter menu (free in Community). API surface\nis similar but not identical - see [Set filter](./filtering/set-filter.md).\n\n## When NOT to migrate\n\nBe honest. Stay on AG Grid if you:\n\n- **Use multiple frameworks** - AG Grid has React, Angular, Vue, Solid, Qwik, vanilla adapters. SvGrid is Svelte-only.\n- **Need a push-based viewport row model** - SvGrid's server-side row model covers grouping, tree, pivot, transactions and select-all across unloaded rows, and its real-time page merges deltas into loaded rows, but the server cannot push the visible window over a socket the way the viewport model does.\n- **Need custom tool panels** - SvGrid's tool panel is a fixed Columns + Filters pair. (Custom filter components are covered: a column's `customFilter` renders your own control in the filter menu, the floating filter row and the Filters tab.)\n- **Are mid-project and shipping in <2 weeks** - the migration is a few hours per grid, but only do it when you have buffer.\n- **Have a Svelte 4 codebase you can't upgrade** - SvGrid requires Svelte 5 runes. (Consider [htmlelements.com](https://www.htmlelements.com) for vanilla / multi-framework.)\n\nIf none of those apply: switching drops a per-developer Enterprise licence\nfor features that are in SvGrid's MIT core, cuts the bundle by the\ndifference in the facts box above, and gives you a Svelte-native API that\nplays well with runes.\n\n## Step-by-step migration\n\nA typical migration of a single grid takes 1-3 hours:\n\n1. **Install** - `pnpm add @svgrid/grid` (and `@svgrid/enterprise` if you need export).\n2. **Translate columnDefs** - use the mapping table above. Most columns are 1:1.\n3. **Wrap features** - figure out which AG Grid features you actually use; register only those in `tableFeatures({...})`.\n4. **Swap the component** - `<AgGridSvelte gridOptions={...}>` → `<SvGrid data={rows} columns={columns} features={features}>`.\n5. **Move event handlers** - AG Grid `onCellValueChanged` → SvGrid `onCellValueChange` (signature differs slightly, see above).\n6. **Move API calls** - AG Grid `gridApi.X()` → SvGrid `api.X()` per the API table.\n7. **Test interactions** - sort, filter, edit, select. Most \"just works.\"\n8. **Remove `ag-grid-*` packages** - `pnpm remove ag-grid-community ag-grid-svelte` etc. Inspect your bundle to confirm the drop; the facts box above has both measured sizes.\n\n## Need help migrating?\n\nEnterprise customers get **migration help included** with the support plan\n(architecture review, port one grid for you as a reference). Email\n`support@jqwidgets.com` after purchase, or `sales@jqwidgets.com` for\npre-sales questions.\n\n## Frequently asked questions\n\n### Is SvGrid a drop-in replacement for AG Grid in Svelte?\n\nNot a literal drop-in - there is no `ag-grid-svelte` shim to swap. But the\nconcepts map closely: column definitions, row models, sorting, filtering,\ngrouping, and an imperative API all have direct SvGrid equivalents, so most\nteams port a grid in 30 minutes to a day. It is a configuration translation,\nnot a rewrite.\n\n### What is the SvGrid equivalent of AG Grid Enterprise?\n\n`@svgrid/enterprise`. It adds Excel/PDF/styled-HTML export (CSV, TSV and JSON export are already free in the grid), a printable view, pivot\ntables and data import. The in-grid AI helpers are free in `@svgrid/grid`.\nIt is licensed per developer ($599 for the grid, $999 with the spreadsheet\nand Studio, both covering unlimited apps), and the\nCommunity package is MIT-licensed and free for commercial use.\n\n### Does SvGrid use Svelte 5 runes, or is it a wrapper?\n\nIt is Svelte-5-native. State is `$state` / `$derived` / `$effect` and cells\nrender through Svelte snippets - there is no React or Angular core underneath\nand no framework bridge to keep in sync.\n\n### Will my AG Grid bundle size shrink?\n\nAlmost always. The facts box at the top of this page has both packages\nmeasured the same way on the same date: the full SvGrid render component\nwith its stylesheet against `createGrid` with every AG Grid Community\nmodule registered. You add `@svgrid/enterprise` features only where you\nimport them, and the headless core on its own is a small fraction of the\nrender component.\n\n## More examples\n\n### AG Grid ↔ sv-grid side-by-side\n\nTwo real grids over the same dataset: the installed AG Grid Community on the left, sv-grid on the right. Same global filter drives both. Source code panels for either side.\n\n<div data-docs-demo=\"139-migration-from-ag-grid\" data-height=\"460\"></div>\n\n## See also\n\n- [Getting started](../getting-started.md) - full SvGrid walkthrough\n- [Why headless?](../why-headless.md) - the headless / render-component split\n- [Data export and printing](./export.md) - the `@svgrid/enterprise` feature pack\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](./comparison.md) - the\n measured benchmark and the feature matrix\n- [SvGrid vs AG Grid comparison page](https://svgrid.com/compare/ag-grid/) -\n every claim with its source and date\n"
6070
+ "markdown": "\n# Migrating from AG Grid to SvGrid\n\nIf you tried AG Grid on a Svelte 5 project - via `ag-grid-svelte`, the\nold `ag-grid-community/svelte`, or a hand-rolled wrapper - you probably\nhit the same friction everyone hits: the bridge between AG Grid's\nReact/Angular-first API and Svelte 5 runes is brittle, the bundle is\nheavy, and the Enterprise pricing only makes sense at scale.\n\n<!-- facts:start ag-grid -->\n> **Facts, checked 9 Nov 2026.** `ag-grid-community` 36.3.0, MIT, last published 4 Nov 2026, 16,400,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026); `ag-grid-community` 36.3.0 346.4 KB JS, no separate stylesheet (measured 9 Nov 2026). AG Grid pricing, as its site states it: AG Grid Community is free under MIT. AG Grid Enterprise is listed at $999 USD per developer with one year of updates and Zendesk support; the Enterprise Bundle with AG Charts Enterprise is $1,498 USD per developer (https://www.ag-grid.com/license-pricing/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs AG Grid (community + enterprise)](https://svgrid.com/compare/ag-grid/).\n<!-- facts:end -->\n\nThis page is a 30-minute migration recipe from AG Grid to SvGrid. It\ncovers what maps 1:1, what's different by design, and what you'll lose.\nWe tell you when **not** to switch at the bottom.\n\n## TL;DR\n\n| | AG Grid Community | AG Grid Enterprise | SvGrid Community | @svgrid/enterprise |\n| --- | --- | --- | --- | --- |\n| **Licence** | MIT | Commercial, per developer (the price is in the facts box above) | **MIT** | $599/dev/yr (grid) or $999/dev/yr (grid + spreadsheet + Studio) |\n| **Svelte 5 native** | No (community-built integration) | No (community-built integration) | Yes | Yes |\n| **Bundle (gzipped)** | measured, in the facts box above | not measured (licence) | measured, in the facts box above | lazy-loaded subpaths |\n| **Sorting / filtering** | Yes | Yes | Yes | (in Community) |\n| **Row grouping + aggregation** | No (Enterprise) | Yes | Yes (free) | (in Community) |\n| **Master/detail, tree, range select** | No (Enterprise) | Yes | Yes (free) | (in Community) |\n| **Set filter / Excel-style filter menu** | No (Enterprise) | Yes | Yes (free) | (in Community) |\n| **Server-side data, flat (infinite row model)** | Yes | Yes | Yes (free) | (in Community) |\n| **Server-side row model (grouping, tree, pivot, transactions, selection)** | No (Enterprise) | Yes | No | Yes |\n| **Integrated charts** | No (Enterprise) | Yes, AG Charts | Yes (free) | (in Community) |\n| **CSV export** | Yes (API) | Yes | Yes, with TSV and JSON | (in Community) |\n| **Excel export** | No | Yes | No | Yes |\n| **PDF / styled-HTML export, print** | No | No | No | Yes |\n| **Pivot tables** | No | Yes | No | Yes |\n| **MCP server for AI assistants** | Yes, `ag-mcp` | Yes | Yes, `@svgrid/mcp` | (in Community) |\n| **In-grid AI helpers** | No | No | Yes (bring your own model) | (in Community) |\n\n**SvGrid Community gives you most of what AG Grid sells as Enterprise for\nfree**, and `@svgrid/enterprise` adds Excel, PDF and print output, import,\npivot tables and the server-side row model per developer per year. Compare what each paid tier adds\nbefore comparing prices; both are in the facts box. The trade-offs are\nSvelte-only and a much smaller ecosystem. Every AG Grid cell above follows\nag-grid.com's own pages; the dated list is on the\n[SvGrid vs AG Grid](https://svgrid.com/compare/ag-grid/) page.\n\n## Mental model - what changes\n\nAG Grid is one big object you configure declaratively. SvGrid is a\n**headless engine** (`createSvGrid`) with an optional **render\ncomponent** (`<SvGrid>`) on top - the same split TanStack Table made\npopular. You can use either layer; most projects use the render\ncomponent.\n\nEvery example below runs against this setup:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature, type ColumnDef } from '@svgrid/grid'\n\n type Row = { id: number; make: string; model: string; price: number }\n\n const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n\n let rows = $state<Row[]>([\n { id: 1, make: 'Toyota', model: 'Celica', price: 35000 },\n { id: 2, make: 'Ford', model: 'Mondeo', price: 32000 },\n { id: 3, make: 'Porsche', model: 'Boxster', price: 72000 },\n ])\n const data = rows\n\n const columns: ColumnDef<typeof features, Row>[] = [\n { field: 'make', header: 'Make' },\n { field: 'model', header: 'Model' },\n { field: 'price', header: 'Price', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```svelte\n<!-- AG Grid (via a Svelte wrapper) -->\n<AgGridSvelte\n gridOptions={{\n rowData: rows,\n columnDefs: columns,\n onGridReady: (params) => (gridApi = params.api),\n }}\n/>\n\n<!-- SvGrid -->\n<SvGrid\n data={rows}\n columns={columns}\n features={features}\n onApiReady={(api) => (gridApi = api)}\n/>\n```\n\nThree things to note:\n\n1. **No giant `gridOptions` blob.** Each capability is a top-level prop.\n2. **Features are opt-in.** You pass a `features` object built with\n `tableFeatures({...})` - only the features you list ship JS.\n3. **`onApiReady`** gives you a typed `SvGridApi` that is roughly the\n AG Grid `gridApi` equivalent (see the API-mapping table below).\n\n## Column definitions - direct translation\n\nThe shapes are similar enough that you can usually translate by hand\nwithout thinking too hard.\n\n```ts\n// AG Grid\nconst columnDefs: ColDef[] = [\n { field: 'name', headerName: 'Name', sortable: true, filter: true, width: 200 },\n { field: 'price', headerName: 'Price', type: 'numericColumn',\n valueFormatter: ({ value }) => `$${value.toFixed(2)}` },\n { field: 'date', headerName: 'Date',\n valueGetter: ({ data }) => new Date(data.date).toISOString().slice(0, 10) },\n { field: 'status', headerName: 'Status',\n cellRenderer: StatusCellRenderer,\n cellRendererParams: { onChange: handleStatusChange } },\n]\n```\n\n```ts\n// SvGrid\nimport { renderComponent, type ColumnDef } from '@svgrid/grid'\nimport StatusCell from './StatusCell.svelte'\n\nconst columns: ColumnDef<typeof features, Row>[] = [\n { field: 'name', header: 'Name', width: 200 }, // sortable + filterable by default\n { field: 'price', header: 'Price',\n format: { type: 'currency', currency: 'USD' } },\n { field: 'date', header: 'Date',\n format: { type: 'date', pattern: 'y-m-d' } },\n { field: 'status', header: 'Status',\n cell: renderComponent(StatusCell, (ctx) => ({\n value: ctx.getValue(),\n onChange: handleStatusChange,\n })),\n },\n]\n```\n\n### Property mapping\n\n| AG Grid | SvGrid | Notes |\n| --- | --- | --- |\n| `field` | `field` | Same. |\n| `headerName` | `header` | Accepts a string or a snippet/component. |\n| `width` | `width` | Same. |\n| `minWidth` / `maxWidth` | `minWidth` / `maxWidth` | Same. |\n| `sortable: true` | (default) | Sorting is on when `rowSortingFeature` is registered. |\n| `filter: true` | (default) | Filtering is on when `columnFilteringFeature` is registered. |\n| `valueFormatter` | `format: { ... }` | Built-in types: `number`, `currency`, `percent`, `date`. For custom, use `cell`. |\n| `valueGetter` | `fieldFn` | Returns the value for sorting/filtering. |\n| `cellRenderer` + `cellRendererParams` | `cell: renderComponent(C, ctx => props)` | One call, type-checked. |\n| `cellEditor: 'agTextCellEditor'` | `editorType: 'text'` | Built-in: `text`, `number`, `checkbox`, `date`. |\n| `editable: true` | `enableInlineEditing` prop on `<SvGrid>` | Per-grid, not per-column. (Per-column control on the roadmap.) |\n| `pinned: 'left'` / `'right'` | Right-click column menu → Pin | Set programmatically via the api. |\n| `rowGroup: true` | Via `setGroupBy([colId])` | See Grouping below. |\n| `aggFunc: 'sum'` | `aggregate: 'sum'` | Built-in: `sum`, `avg`, `min`, `max`, `count`. |\n\n## Feature registration - the one new thing\n\nAG Grid auto-enables most features; you turn them off. SvGrid is the\nopposite - features are opt-in. The result is a smaller bundle.\n\n```ts\nimport {\n tableFeatures,\n rowSortingFeature,\n columnFilteringFeature,\n columnGroupingFeature,\n rowExpandingFeature,\n rowPaginationFeature,\n rowSelectionFeature,\n} from '@svgrid/grid'\n\nconst features = tableFeatures({\n rowSortingFeature,\n columnFilteringFeature,\n rowSelectionFeature,\n // omit any you don't need - their code won't ship\n})\n```\n\nPass `features` to `<SvGrid>` once. From then on the grid behaves like\nAG Grid's `enableSorting`, `enableFilter`, `rowSelection`, etc. are all\non for the registered features.\n\n## API mapping (`gridApi` → `SvGridApi`)\n\nYou get the SvGrid API from `onApiReady` (equivalent to AG Grid's\n`onGridReady`).\n\n| AG Grid `gridApi.X()` | SvGrid `api.X()` |\n| --- | --- |\n| `setRowData(rows)` | (declarative - just update `data` prop) |\n| `addRow(row)` / `applyTransaction({ add: [row] })` | `api.addRow(row)` / `api.addRows(rows)` |\n| `applyTransaction({ remove: [row] })` | `api.removeRow(rowIndex)` |\n| `getValue(colId, rowNode)` | `api.getCellValue(rowIndex, columnId)` |\n| `setValue(...)` | `api.setCellValue(rowIndex, columnId, value)` |\n| `setColumnVisible(colId, visible)` | `api.setColumnVisible(columnId, visible)` |\n| `getSortModel()` / `setSortModel()` | `api.setSort(columnId, 'asc'\\|'desc'\\|null)` |\n| `setFilterModel({...})` | `api.setFilter(columnId, { operator, value })` |\n| `getDisplayedRowAtIndex(i)` / `forEachNodeAfterFilterAndSort(...)` | `api.getDisplayedRows()` |\n| `getModel()` (raw rows) | `api.getData()` |\n\n## Common patterns\n\n### Sorting + filtering + pagination (the 80% case)\n\n```svelte\n<script lang=\"ts\">\n import {\n SvGrid,\n tableFeatures,\n rowSortingFeature,\n columnFilteringFeature,\n rowPaginationFeature,\n } from '@svgrid/grid'\n\n const features = tableFeatures({\n rowSortingFeature,\n columnFilteringFeature,\n rowPaginationFeature,\n })\n</script>\n\n<SvGrid\n data={rows}\n columns={columns}\n features={features}\n showPagination\n showColumnFilters\n/>\n```\n\nAG Grid equivalent: `gridOptions: { defaultColDef: { sortable: true, filter: true }, pagination: true }`.\n\n### Cell editing with persistence\n\n```svelte\n<script lang=\"ts\">\n function onCellValueChange(e: { rowIndex: number; columnId: string; value: unknown }) {\n // Persist however you like (fetch to backend, optimistic local update, etc.)\n console.log('cell changed', e)\n }\n</script>\n\n<SvGrid\n data={rows}\n columns={columns}\n features={features}\n enableInlineEditing\n onCellValueChange={onCellValueChange}\n/>\n```\n\nAG Grid equivalent: `onCellValueChanged: ({ data, colDef, newValue, oldValue }) => ...`.\nSvGrid's event payload is column-id + row-index based rather than node-based; the row data is yours\nto mutate (or not) on the `rows` array you passed in.\n\n### Grouping + aggregation\n\n```svelte\n<script lang=\"ts\">\n import {\n SvGrid,\n tableFeatures,\n columnGroupingFeature,\n rowSortingFeature,\n rowExpandingFeature,\n } from '@svgrid/grid'\n\n const features = tableFeatures({\n rowSortingFeature,\n columnGroupingFeature,\n rowExpandingFeature,\n })\n\n const columns = [\n { field: 'department', header: 'Department' },\n { field: 'team', header: 'Team' },\n { field: 'salary', header: 'Salary', aggregate: 'sum',\n format: { type: 'currency', currency: 'USD' } },\n ]\n\n function setGroup(api) {\n api.setGroupBy(['department', 'team'])\n }\n</script>\n\n<SvGrid\n data={rows}\n columns={columns}\n features={features}\n showGroupingControls\n onApiReady={setGroup}\n/>\n```\n\nAG Grid Enterprise's `rowGroupPanelShow: 'always'` + `aggFunc: 'sum'` translates 1:1.\n\n### Master / detail\n\nAG Grid Enterprise feature; **free in SvGrid Community**. See\n[demo 08](https://svgrid.com/demos/08-tree-and-master-detail/) for the exact pattern.\n\n### Server-side data\n\nAG Grid's Infinite Row Model (Community) and Server-Side Row Model\n(Enterprise) both take an `IServerSideDatasource` with a `getRows(params)`\nthat answers through `params.success({ rowData, rowCount })`. SvGrid has one\n`ServerDataSource` whose `getRows(request)` returns `{ rows, rowCount }`,\nand two controllers over it: `createServerDataSource` (free: paging or\ninfinite block scroll, sort, filter, CRUD) and `createServerRowModel`\n(Enterprise: lazy grouping, tree, pivot, transactions, selection). Both\nmount through one prop, `<SvGrid rowModel={ctl} />`.\n\nAn existing datasource written for AG Grid keeps working behind one call:\n\n```ts\nimport { adaptCallbackDatasource, createServerRowModel } from '@svgrid/enterprise'\n\nconst ctl = createServerRowModel(adaptCallbackDatasource(myServerSideDatasource), {\n groupBy: ['country'],\n aggregations: [{ col: 'amount', fn: 'sum' }],\n})\n```\n\n`adaptCallbackDatasource` maps the request both ways (`rowGroupCols` ->\n`groupBy`, `valueCols` -> `aggregations`, `pivotCols` -> `pivotBy`, the\nsort and filter models, `context`, `parentNode`) and turns `success` /\n`fail` into a resolved or rejected promise.\n\nMore often the datasource is a thin `fetch` and the real investment is the\nendpoint behind it - a Java or Node service that parses AG Grid's\n`IServerSideGetRowsRequest` JSON. That endpoint stays as it is: post\n`toCallbackRequest(request)` and read the answer back.\n\n```ts\nimport { toCallbackRequest } from '@svgrid/enterprise'\n\nconst source = {\n async getRows(request) {\n const res = await fetch('/api/sales', {\n method: 'POST',\n headers: { 'content-type': 'application/json' },\n body: JSON.stringify(toCallbackRequest(request)),\n })\n const { rowData, rowCount, pivotResultFields } = await res.json()\n return { rows: rowData, rowCount: rowCount ?? -1, pivotResultFields }\n },\n}\n```\n\n`fromCallbackRequest` is the other direction, for a SvelteKit endpoint that\nhas to keep serving an AG Grid client during the switch. A saved selection\nor a bulk endpoint written against `getServerSideSelectionState()` keeps\nits shape the same way: `toCallbackSelectionState(ctl.getSelectionState())`\nproduces `{ selectAll, toggledNodes }` (or the `nodeId` /\n`selectAllChildren` / `toggledNodes` tree), `ctl.setSelectionState` takes\nthat shape as it is when your group node ids are the group keys, and\n`fromCallbackSelectionState(state, { groupKey, isGroup })` maps them when\na `getRowId` gave group rows ids of their own. Option by option:\n\n| AG Grid | SvGrid |\n| --- | --- |\n| `rowModelType: 'infinite'` + `datasource` | `createServerDataSource(source, { mode: 'infinite' })` + `rowModel={ctl}` |\n| `rowModelType: 'serverSide'` + `serverSideDatasource` | `createServerRowModel(source, options)` + `rowModel={ctl}` |\n| `getRows(params)` + `params.success({ rowData, rowCount })` / `params.fail()` | `getRows(request)` returning `{ rows, rowCount }` / throwing |\n| `cacheBlockSize`, `maxBlocksInCache`, `maxConcurrentDatasourceRequests`, `blockLoadDebounceMillis` | `blockSize`, `maxBlocksInCache`, `maxConcurrentRequests`, `blockLoadDebounceMs` |\n| `infiniteInitialRowCount` / `serverSideInitialRowCount` | `initialRowCount` |\n| `rowCount: -1` (unknown) | `rowCount: -1` |\n| `refreshInfiniteCache()` / `purgeInfiniteCache()` | `ctl.refresh()` / `ctl.purge()` |\n| `request.rowGroupCols`, `groupKeys`, `valueCols`, `pivotCols`, `pivotMode` | `request.groupBy`, `groupKeys`, `aggregations`, `pivotBy`, `pivotMode` |\n| `getChildCount(data)` | `childCount: (row) => row.childCount` |\n| `isServerSideGroupOpenByDefault` | `isGroupOpenByDefault(route, row)` |\n| `getServerSideGroupLevelParams` | `levelParams(level, route)` |\n| `isServerSideGroup` / `getServerSideGroupKey` (tree) | `treeData: true` + `hasChildren` / `getRowId` |\n| `grandTotalRow` / `groupTotalRow` | `grandTotalRow` / `groupFooters` |\n| `refreshServerSide({ route, purge })` / `retryServerSideLoads()` | `ctl.refresh({ route, purge })` / `ctl.retryLoads()` |\n| `applyServerSideTransaction` / `applyServerSideTransactionAsync` / `flushServerSideAsyncTransactions` | `ctl.applyTransaction` / `applyTransactionAsync` / `flushAsyncTransactions` |\n| `applyServerSideRowData` | `ctl.applyRowData` |\n| `serverSideSortAllLevels`, `serverSideEnableClientSideSort`, `serverSideOnlyRefreshFilteredGroups` | `sortAllLevels`, `clientSideSort`, `onlyRefreshFilteredGroups` |\n| `getServerSideSelectionState` / `setServerSideSelectionState` | `ctl.getSelectionState()` / `setSelectionState()` (the `toggledNodes` shape is accepted; `toCallbackSelectionState` / `fromCallbackSelectionState` convert) |\n| `ServerSideTransactionResult.status`: `Applied`, `StoreNotFound`, `StoreLoading`, `StoreWaitingToLoad`, `StoreLoadingFailed`, `Cancelled` | `ServerTransactionResult.status`: the same six, lower camel case (`applied`, `storeNotFound`, ...) - a `switch` on the old spelling falls through silently |\n| `groupSelects: 'descendants'` | `selection: { groupSelects: 'descendants' }` |\n| `pivotResultFields` in `success`, `setPivotResultColumns`, `processPivotResultColDef` | `pivotResultFields` / `pivotResultColumns` in the result, `pivotResultColumn(field, def)` |\n| `pagination` + `paginateChildRows` | `pagination: { pageSize, paginateChildRows }` |\n| `getCacheBlockState()` / `getServerSideGroupLevelState()` | `ctl.getCacheState()` / `ctl.levelStates()` |\n| `serverSideDatasource.destroy()` | `source.destroy()` |\n\nTwo differences worth knowing before you start: SvGrid sends the global\nsearch box to the server as `filterModel.global` (AG Grid's quick filter is\nclient-side only and unsupported under its infinite and server-side models),\nand SvGrid has no viewport row model. See\n[Server grouping](./server/server-grouping.md) and\n[demo 467](https://svgrid.com/demos/467-server-row-model-1m/).\n\n### Excel / PDF export\n\nAG Grid: `gridApi.exportDataAsExcel({...})` (Enterprise-only).\nSvGrid: install `@svgrid/enterprise`, call `api.exportData({ format: 'xlsx', ... })`. See [Data export and printing](./export.md).\n\n```ts\nimport { installEnterprise, setLicenseKey } from '@svgrid/enterprise'\nsetLicenseKey('YOUR-LICENSE-KEY') // your Enterprise key\n\n// inside onApiReady:\nconst pro = installEnterprise(api)\nawait pro.exportData({ format: 'xlsx', filename: 'orders' })\n```\n\n## Gotchas - things that don't translate directly\n\n### 1. Per-column `editable: true`\nEditing is switched on at the grid level (`enableInlineEditing`) and\nnarrowed per column with `editable: boolean | (ctx) => boolean` on the\ncolumn definition, so AG Grid's per-column flag and its callback form both\nmap directly. What does not map is AG Grid's `editable` on a column\ngroup: set it on each child column.\n\n### 2. Column drag-to-reorder\nHeader drag is `enableColumnReorder` on `<SvGrid>`; `setColumnOrder`\non the API does the same from code. See\n[column moving](./columns/column-moving.md) for the events.\n\n### 3. AG Grid `valueGetter` chains\nAG Grid's `valueGetter` can read other column values via the API. In\nSvGrid, `fieldFn` only receives the row; if you need cross-column\ncomputed values, do it in the cell renderer with `ctx.row.original` or\ncompute the derived value upstream and store it in the row.\n\n### 4. `cellClass` / `rowClass` callbacks\nOn the roadmap. For now, render a wrapper element in your `cell` snippet\nwith the conditional class.\n\n### 5. The Status Bar / Side Bar / Tool Panels\nAG Grid's chrome (status bar with row count, side bar with filters and\ncolumns panels) doesn't exist in SvGrid - build it as plain Svelte\nmarkup around the grid. Most teams build their own anyway because\nAG Grid's defaults rarely match a polished design system.\n\n### 6. Set filter (the Excel-style funnel popup)\nSvGrid ships an Excel-style filter menu (free in Community). API surface\nis similar but not identical - see [Set filter](./filtering/set-filter.md).\n\n## When NOT to migrate\n\nBe honest. Stay on AG Grid if you:\n\n- **Use multiple frameworks** - AG Grid has React, Angular, Vue, Solid, Qwik, vanilla adapters. SvGrid is Svelte-only.\n- **Need a push-based viewport row model** - SvGrid's server-side row model covers grouping, tree, pivot, transactions and select-all across unloaded rows, and its real-time page merges deltas into loaded rows, but the server cannot push the visible window over a socket the way the viewport model does.\n- **Need custom tool panels** - SvGrid's tool panel is a fixed Columns + Filters pair. (Custom filter components are covered: a column's `customFilter` renders your own control in the filter menu, the floating filter row and the Filters tab.)\n- **Are mid-project and shipping in <2 weeks** - the migration is a few hours per grid, but only do it when you have buffer.\n- **Have a Svelte 4 codebase you can't upgrade** - SvGrid requires Svelte 5 runes. (Consider [htmlelements.com](https://www.htmlelements.com) for vanilla / multi-framework.)\n\nIf none of those apply: switching drops a per-developer Enterprise licence\nfor features that are in SvGrid's MIT core, cuts the bundle by the\ndifference in the facts box above, and gives you a Svelte-native API that\nplays well with runes.\n\n## Step-by-step migration\n\nA typical migration of a single grid takes 1-3 hours:\n\n1. **Install** - `pnpm add @svgrid/grid` (and `@svgrid/enterprise` if you need export).\n2. **Translate columnDefs** - use the mapping table above. Most columns are 1:1.\n3. **Wrap features** - figure out which AG Grid features you actually use; register only those in `tableFeatures({...})`.\n4. **Swap the component** - `<AgGridSvelte gridOptions={...}>` → `<SvGrid data={rows} columns={columns} features={features}>`.\n5. **Move event handlers** - AG Grid `onCellValueChanged` → SvGrid `onCellValueChange` (signature differs slightly, see above).\n6. **Move API calls** - AG Grid `gridApi.X()` → SvGrid `api.X()` per the API table.\n7. **Test interactions** - sort, filter, edit, select. Most \"just works.\"\n8. **Remove `ag-grid-*` packages** - `pnpm remove ag-grid-community ag-grid-svelte` etc. Inspect your bundle to confirm the drop; the facts box above has both measured sizes.\n\n## Need help migrating?\n\nEnterprise customers get **migration help included** with the support plan\n(architecture review, port one grid for you as a reference). Email\n`support@jqwidgets.com` after purchase, or `sales@jqwidgets.com` for\npre-sales questions.\n\n## Frequently asked questions\n\n### Is SvGrid a drop-in replacement for AG Grid in Svelte?\n\nNot a literal drop-in - there is no `ag-grid-svelte` shim to swap. But the\nconcepts map closely: column definitions, row models, sorting, filtering,\ngrouping, and an imperative API all have direct SvGrid equivalents, so most\nteams port a grid in 30 minutes to a day. It is a configuration translation,\nnot a rewrite.\n\n### What is the SvGrid equivalent of AG Grid Enterprise?\n\n`@svgrid/enterprise`. It adds Excel/PDF/styled-HTML export (CSV, TSV and JSON export are already free in the grid), a printable view, pivot\ntables and data import. The in-grid AI helpers are free in `@svgrid/grid`.\nIt is licensed per developer ($599 for the grid, $999 with the spreadsheet\nand Studio, both covering unlimited apps), and the\nCommunity package is MIT-licensed and free for commercial use.\n\n### Does SvGrid use Svelte 5 runes, or is it a wrapper?\n\nIt is Svelte-5-native. State is `$state` / `$derived` / `$effect` and cells\nrender through Svelte snippets - there is no React or Angular core underneath\nand no framework bridge to keep in sync.\n\n### Will my AG Grid bundle size shrink?\n\nAlmost always. The facts box at the top of this page has both packages\nmeasured the same way on the same date: the full SvGrid render component\nwith its stylesheet against `createGrid` with every AG Grid Community\nmodule registered. You add `@svgrid/enterprise` features only where you\nimport them, and the headless core on its own is a small fraction of the\nrender component.\n\n## More examples\n\n### AG Grid ↔ sv-grid side-by-side\n\nTwo real grids over the same dataset: the installed AG Grid Community on the left, sv-grid on the right. Same global filter drives both. Source code panels for either side.\n\n<div data-docs-demo=\"139-migration-from-ag-grid\" data-height=\"460\"></div>\n\n## See also\n\n- [Getting started](../getting-started.md) - full SvGrid walkthrough\n- [Why headless?](../why-headless.md) - the headless / render-component split\n- [Data export and printing](./export.md) - the `@svgrid/enterprise` feature pack\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](./comparison.md) - the\n measured benchmark and the feature matrix\n- [SvGrid vs AG Grid comparison page](https://svgrid.com/compare/ag-grid/) -\n every claim with its source and date\n"
6071
6071
  },
6072
6072
  {
6073
6073
  "slug": "help/migrating-from-airtable",
@@ -6088,49 +6088,49 @@ export const docs = [
6088
6088
  "path": "docs/help/migrating-from-devextreme.md",
6089
6089
  "title": "Migrating from DevExtreme DataGrid (DevExpress)",
6090
6090
  "section": "Help",
6091
- "markdown": "# Migrating from DevExtreme DataGrid (DevExpress)\n\nDevExtreme DataGrid is a deep, commercial multi-framework grid from\nDevExpress (jQuery, React, Vue, Angular). Moving to SvGrid trades the\ncommercial suite for a Svelte-5-native grid with an MIT core and a far\nlower-cost paid tier.\n\n> Estimated effort: **3-6 hours** per grid.\n>\n> DevExtreme's option names vary by framework flavour; map your version's\n> columns and events onto the SvGrid equivalents below.\n\n<!-- facts:start devextreme-datagrid -->\n> **Facts, checked 9 Nov 2026.** `devextreme` 26.1.6, Commercial (see licence file), last published 23 Oct 2026, 1,180,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026). DevExtreme DataGrid pricing, as its site states it: js.devexpress.com lists DevExtreme Complete at $899.99 per developer for a 12-month subscription with updates and support, renewing at $449.99; no free or non-commercial tier is shown (https://js.devexpress.com/Buy/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs DevExtreme DataGrid (DevExpress)](https://svgrid.com/compare/devextreme-datagrid/).\n<!-- facts:end -->\n\n## Concept map\n\n| DevExtreme DataGrid | sv-grid |\n| ---------------------------------------- | ----------------------------------------- |\n| `columns: [{ dataField, caption }]` | `columns: [{ field, header }]` |\n| `cellTemplate` | `cell: (c) => renderSnippet(...)` |\n| `editing: { mode, allowUpdating }` | `enableInlineEditing` + `editorType` |\n| `sorting` / `filterRow` / `headerFilter` | `rowSortingFeature` / `columnFilteringFeature` |\n| `grouping` + `summary` | `columnGroupingFeature` + aggregates |\n| `masterDetail` | `rowExpandingFeature` / master-detail rows |\n| `dataSource` (store / remote) | `data` array or `externalSort/Filter` |\n| `paging` + `pager` | `showPagination` |\n| `export` | `@svgrid/enterprise` export pack |\n| `stateStoring` | persist column state yourself (saved views) |\n\n## Shape of the change\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- $('#grid').dxDataGrid({\n- dataSource: rows,\n- paging: { pageSize: 25 },\n- sorting: { mode: 'multiple' }, filterRow: { visible: true },\n- editing: { mode: 'cell', allowUpdating: true },\n- columns: [\n- { dataField: 'name', caption: 'Name' },\n- { dataField: 'amount', caption: 'Amount', format: 'currency' },\n- ],\n- })\n\n+ <SvGrid\n+ data={rows}\n+ columns={[\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]}\n+ features={tableFeatures({ rowSortingFeature, columnFilteringFeature })}\n+ showPagination enableInlineEditing />\n```\n\n## Why teams switch\n\n- **Svelte 5 native** instead of a multi-framework commercial library.\n- **MIT community core** plus an optional Enterprise pack for export / import /\n pivot / AI.\n- **Much lower-cost paid tier.**\n\n## What to weigh\n\n- DevExtreme has a **larger built-in feature surface** (state storing,\n broad export, a full suite). If you depend on those, factor them in -\n `stateStoring` in particular becomes a saved-views pattern you wire up.\n\n## Frequently asked questions\n\n### How do DevExtreme columns map to SvGrid?\n\n`dataField` becomes `field`, `caption` becomes `header`, and `cellTemplate`\nbecomes a `renderSnippet` cell. Sorting / filtering / grouping move from grid\noptions to registered features.\n\n### Is SvGrid cheaper than DevExtreme?\n\nFor a Svelte stack, yes - the core is MIT and the paid tier is far below\ncommercial-suite pricing. You give up DevExtreme's multi-framework reach and\nsome built-in features like `stateStoring`.\n\n### Does SvGrid export like DevExtreme?\n\nYes, via the `@svgrid/enterprise` pack: Excel, PDF, CSV, TSV, and HTML export plus a\nprintable view.\n\n## What you end up with\n\nGrouping with totals plus the filter row, the DevExtreme default layout.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} groupBy={['department']} summary groupable sortable filterMode=\"row\" />\n```\n\n## See also\n\n- [SvGrid vs DevExtreme DataGrid](https://svgrid.com/compare/devextreme-datagrid/) - the side-by-side comparison\n- [Saved views](./saved-views.md) - the state-persistence pattern\n- [Data export and printing - Enterprise](./export.md) - the Enterprise export pack\n"
6091
+ "markdown": "# Migrating from DevExtreme DataGrid (DevExpress)\n\nDevExtreme DataGrid is a deep, commercial multi-framework grid from\nDevExpress (jQuery, React, Vue, Angular). Moving to SvGrid trades the\ncommercial suite for a Svelte-5-native grid with an MIT core and a far\nlower-cost paid tier.\n\n> Estimated effort: **3-6 hours** per grid.\n>\n> DevExtreme's option names vary by framework flavour; map your version's\n> columns and events onto the SvGrid equivalents below.\n\n<!-- facts:start devextreme-datagrid -->\n> **Facts, checked 9 Nov 2026.** `devextreme` 26.1.6, Commercial (see licence file), last published 23 Oct 2026, 1,180,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026). DevExtreme DataGrid pricing, as its site states it: js.devexpress.com lists DevExtreme Complete at $899.99 per developer for a 12-month subscription with updates and support, renewing at $449.99; no free or non-commercial tier is shown (https://js.devexpress.com/Buy/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs DevExtreme DataGrid (DevExpress)](https://svgrid.com/compare/devextreme-datagrid/).\n<!-- facts:end -->\n\n## Concept map\n\n| DevExtreme DataGrid | sv-grid |\n| ---------------------------------------- | ----------------------------------------- |\n| `columns: [{ dataField, caption }]` | `columns: [{ field, header }]` |\n| `cellTemplate` | `cell: (c) => renderSnippet(...)` |\n| `editing: { mode, allowUpdating }` | `enableInlineEditing` + `editorType` |\n| `sorting` / `filterRow` / `headerFilter` | `rowSortingFeature` / `columnFilteringFeature` |\n| `grouping` + `summary` | `columnGroupingFeature` + aggregates |\n| `masterDetail` | `rowExpandingFeature` / master-detail rows |\n| `dataSource` (store / remote) | `data` array or `externalSort/Filter` |\n| `paging` + `pager` | `showPagination` |\n| `export` | `@svgrid/enterprise` export pack |\n| `stateStoring` | persist column state yourself (saved views) |\n\n## Shape of the change\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- $('#grid').dxDataGrid({\n- dataSource: rows,\n- paging: { pageSize: 25 },\n- sorting: { mode: 'multiple' }, filterRow: { visible: true },\n- editing: { mode: 'cell', allowUpdating: true },\n- columns: [\n- { dataField: 'name', caption: 'Name' },\n- { dataField: 'amount', caption: 'Amount', format: 'currency' },\n- ],\n- })\n\n+ <SvGrid\n+ data={rows}\n+ columns={[\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]}\n+ features={tableFeatures({ rowSortingFeature, columnFilteringFeature })}\n+ showPagination enableInlineEditing />\n```\n\n## Why teams switch\n\n- **Svelte 5 native** instead of a multi-framework commercial library.\n- **MIT community core** plus an optional Enterprise pack for export / import /\n pivot / AI.\n- **Much lower-cost paid tier.**\n\n## What to weigh\n\n- DevExtreme has a **larger built-in feature surface** (state storing,\n broad export, a full suite). If you depend on those, factor them in -\n `stateStoring` in particular becomes a saved-views pattern you wire up.\n\n## Frequently asked questions\n\n### How do DevExtreme columns map to SvGrid?\n\n`dataField` becomes `field`, `caption` becomes `header`, and `cellTemplate`\nbecomes a `renderSnippet` cell. Sorting / filtering / grouping move from grid\noptions to registered features.\n\n### Is SvGrid cheaper than DevExtreme?\n\nFor a Svelte stack, yes - the core is MIT and the paid tier is far below\ncommercial-suite pricing. You give up DevExtreme's multi-framework reach and\nsome built-in features like `stateStoring`.\n\n### Does SvGrid export like DevExtreme?\n\nYes, via the `@svgrid/enterprise` pack: Excel, PDF, CSV, TSV, and HTML export plus a\nprintable view.\n\n## What you end up with\n\nGrouping with totals plus the filter row, the DevExtreme default layout.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} groupBy={['department']} summary groupable sortable filterMode=\"row\" />\n```\n\n## See also\n\n- [SvGrid vs DevExtreme DataGrid](https://svgrid.com/compare/devextreme-datagrid/) - the side-by-side comparison\n- [Saved views](./saved-views.md) - the state-persistence pattern\n- [Data export and printing - Enterprise](./export.md) - the Enterprise export pack\n"
6092
6092
  },
6093
6093
  {
6094
6094
  "slug": "help/migrating-from-glide",
6095
6095
  "path": "docs/help/migrating-from-glide.md",
6096
6096
  "title": "Migrating from Glide Data Grid",
6097
6097
  "section": "Help",
6098
- "markdown": "# Migrating from Glide Data Grid\n\nGlide Data Grid is the canvas-rendered, ultra-high-performance choice\nfor very wide datasets (100k+ rows, 100+ columns). Sv-grid renders to\nDOM with virtualization, which trades peak FPS for\naccessibility + standards-compliant HTML.\n\n> Estimated effort: **3-6 hours** per grid. Glide's getCellContent /\n> onCellEdited cell-data model is the opposite of sv-grid's\n> data-array model; the mental flip takes the most time.\n\n<!-- facts:start glide-data-grid -->\n> **Facts, checked 9 Nov 2026.** `@glideapps/glide-data-grid` 6.0.3, MIT, last published 3 Feb 2024, 2,010,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026); `@glideapps/glide-data-grid` 6.0.3 71.1 KB JS + 0.2 KB CSS, lodash + marked + react + react-dom + react-responsive-carousel external (measured 9 Nov 2026). Glide Data Grid pricing, as its site states it: Glide Data Grid is MIT and, in its own words, fully free and open source; no licence is sold for the grid (https://grid.glideapps.com/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Glide Data Grid](https://svgrid.com/compare/glide-data-grid/).\n<!-- facts:end -->\n\n## Mental-model flip\n\nGlide gives you a **canvas + a `getCellContent` callback**: the grid\nasks you for each visible cell on demand. Sv-grid wants the\n**whole data array up front** (`<SvGrid data={rows}>`); the engine\nslices for virtualization.\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- function getCellContent([col, row]) {\n- const r = rows[row]\n- if (col === 0) return { kind: 'text', data: r.name, displayData: r.name, allowOverlay: true }\n- if (col === 1) return { kind: 'number', data: r.amount, displayData: fmt(r.amount), allowOverlay: true }\n- }\n- <DataEditor columns={[...]} getCellContent={getCellContent} rows={rows.length} />\n\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name', editorType: 'text' },\n+ { field: 'amount', header: 'Amount', editorType: 'number',\n+ format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ <SvGrid data={rows} columns={columns} features={features} />\n```\n\nThis change is **good** for 99% of apps: it's less code, less risk\nof typos in cell coordinates, full TypeScript type checking on the\nrow shape. For the 1% of apps with rows that don't fit in memory,\nsee \"Out-of-memory data\" below.\n\n## Cell editing\n\n```diff\n- function onCellEdited([col, row], newValue) {\n- rows[row] = { ...rows[row], [colToField(col)]: newValue.data }\n- }\n- <DataEditor onCellEdited={onCellEdited} />\n\n+ <SvGrid\n+ data={rows} columns={columns} features={features}\n+ onCellValueChange={(e) => {\n+ rows[e.rowIndex] = { ...rows[e.rowIndex], [e.columnId]: e.newValue }\n+ }}\n+ />\n```\n\nYou can also rely on sv-grid's built-in write-back if `data` is a\nSvelte 5 `$state` array - mutations propagate automatically.\n\n## Sorting + filtering\n\nGlide doesn't ship sort / filter UI; you wrap your own. Sv-grid\nships them:\n\n```diff\n- // Build your own sort buttons in the toolbar; sort rows yourself.\n\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ <SvGrid data={rows} columns={columns} features={features} filterMode=\"menu\" />\n```\n\n## Frozen columns / row markers\n\n| Glide | sv-grid |\n| -------------------------------------- | --------------------------------------------- |\n| `freezeColumns={1}` | `api.setColumnPinning({ left: ['firstColId'] })` |\n| `rowMarkers=\"number\"` | `showRowNumbers={true}` prop |\n| `rowMarkers=\"checkbox\"` | `selectionMode=\"row\"` prop |\n\n## Custom drawing → custom snippets\n\nGlide's `drawCustomCell` lets you render anything via canvas. The\nsv-grid equivalent is a Svelte snippet (DOM):\n\n```diff\n- drawCustomCell(args) {\n- const ctx = args.ctx\n- ctx.fillStyle = args.cell.data.color\n- ctx.fillRect(args.rect.x, args.rect.y, args.rect.width, args.rect.height)\n- return true\n- }\n\n+ {\n+ field: 'color',\n+ cell: (ctx) => renderSnippet(ColorChip, { color: ctx.row.original.color }),\n+ }\n```\n\n```svelte\n{#snippet ColorChip(props)}\n <span style=\"display: inline-block; width: 18px; height: 18px; background: {props.color};\"></span>\n{/snippet}\n```\n\n## Out-of-memory data\n\nFor \"10M rows, fetched on scroll\" workloads (the only case Glide\ngenuinely beats sv-grid on), use sv-grid's\n[server-side / infinite-scroll pattern](./server-side-data.md):\n\n```svelte\n<SvGrid\n data={loadedSlice}\n columns={columns} features={features}\n externalSort={true}\n externalFilter={true}\n onSortingChange={async (s) => { loadedSlice = await fetchPage({ sort: s, offset: 0, limit: 200 }) }}\n/>\n```\n\nYou'll cap practical perf at ~100k rendered rows; for true 10M+\ndatasets Glide's canvas approach has a perf edge sv-grid won't\nmatch. Most apps don't need 10M rows on screen at once - they need\nfast server-side filtering, which both libraries support equally.\n\n## Theming\n\nGlide: huge `theme` prop object. Sv-grid: CSS custom properties (`--sg-*`).\n\n```diff\n- <DataEditor theme={{\n- accentColor: '#4F5DFF',\n- accentLight: 'rgba(62, 116, 253, 0.2)',\n- bgCell: '#1c1c20',\n- /* …40 more properties… */\n- }} />\n\n+ <div style=\"--sg-accent: #4F5DFF; --sg-bg: #1c1c20;\">\n+ <SvGrid {data} {columns} features={features} />\n+ </div>\n```\n\nSee [design tokens](./tokens.md) for the full list (≤ 30 tokens\ncovers everything; Glide's theme has ~40).\n\n## What you get for free vs Glide\n\n- **Accessibility.** Glide's canvas is invisible to screen readers\n unless you build an off-screen ARIA buffer. Sv-grid is WAI-ARIA\n 1.2 grid pattern out of the box; demo 17 covers axe-core CI.\n- **Standard HTML.** SEO crawlers, browser Find-in-Page, browser\n zoom, OS-level text scaling - all work because the grid emits\n actual `<table><tr><td>`.\n- **Familiar editing.** Browser-native `<input>` / `<select>` for\n cells, with autofill / clipboard / autocorrect intact.\n- **Built-in sort / filter / pagination UI.**\n\n## What you give up\n\n- **Peak FPS on >200k visible rows.** Canvas wins here. For most\n apps the gap is invisible; if you've actually measured it on real\n hardware and need the FPS, Glide remains the right call.\n- **Per-pixel cell drawing.** DOM cells are sub-pixel-uniform but\n not arbitrarily drawn.\n\n## Frequently asked questions\n\n### Should I move from Glide Data Grid to SvGrid?\n\nMove if you need accessibility, standards-compliant HTML, SEO-friendly markup,\nor DOM-based custom cells. Stay on Glide only if you have measured a need for\npeak canvas FPS on 200k+ simultaneously visible rows. For most apps the\nperformance gap is invisible, and SvGrid virtualizes comfortably to 100k+ rows.\n\n### How long does a Glide migration take?\n\nAbout 3-6 hours per grid. The biggest shift is conceptual: Glide's\n`getCellContent` / `onCellEdited` cell-data model is the inverse of SvGrid's\nplain data-array model, so the mental flip takes the most time, not the code.\n\n### Does SvGrid render to canvas or DOM?\n\nDOM, with row and column virtualization. That is what gives you WAI-ARIA roles,\nkeyboard navigation, screen-reader support, and selectable/indexable text -\nthings a canvas grid like Glide cannot offer.\n\n## What you end up with\n\nInline editing over a virtualized body, without a canvas to draw into.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} editable enableCellSelection sortable />\n```\n\n## See also\n\n- [SvGrid vs Glide Data Grid](https://svgrid.com/compare/glide-data-grid/) - the side-by-side comparison\n- [Performance benchmarks](./benchmarks.md) - measured numbers\n- [Server-side data](./server-side-data.md) - the >100k-row pattern\n- [Accessibility](./accessibility.md) - the standards compliance Glide doesn't ship\n"
6098
+ "markdown": "# Migrating from Glide Data Grid\n\nGlide Data Grid is the canvas-rendered, ultra-high-performance choice\nfor very wide datasets (100k+ rows, 100+ columns). Sv-grid renders to\nDOM with virtualization, which trades peak FPS for\naccessibility + standards-compliant HTML.\n\n> Estimated effort: **3-6 hours** per grid. Glide's getCellContent /\n> onCellEdited cell-data model is the opposite of sv-grid's\n> data-array model; the mental flip takes the most time.\n\n<!-- facts:start glide-data-grid -->\n> **Facts, checked 9 Nov 2026.** `@glideapps/glide-data-grid` 6.0.3, MIT, last published 3 Feb 2024, 2,010,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026); `@glideapps/glide-data-grid` 6.0.3 71.1 KB JS + 0.2 KB CSS, lodash + marked + react + react-dom + react-responsive-carousel external (measured 9 Nov 2026). Glide Data Grid pricing, as its site states it: Glide Data Grid is MIT and, in its own words, fully free and open source; no licence is sold for the grid (https://grid.glideapps.com/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Glide Data Grid](https://svgrid.com/compare/glide-data-grid/).\n<!-- facts:end -->\n\n## Mental-model flip\n\nGlide gives you a **canvas + a `getCellContent` callback**: the grid\nasks you for each visible cell on demand. Sv-grid wants the\n**whole data array up front** (`<SvGrid data={rows}>`); the engine\nslices for virtualization.\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- function getCellContent([col, row]) {\n- const r = rows[row]\n- if (col === 0) return { kind: 'text', data: r.name, displayData: r.name, allowOverlay: true }\n- if (col === 1) return { kind: 'number', data: r.amount, displayData: fmt(r.amount), allowOverlay: true }\n- }\n- <DataEditor columns={[...]} getCellContent={getCellContent} rows={rows.length} />\n\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name', editorType: 'text' },\n+ { field: 'amount', header: 'Amount', editorType: 'number',\n+ format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ <SvGrid data={rows} columns={columns} features={features} />\n```\n\nThis change is **good** for 99% of apps: it's less code, less risk\nof typos in cell coordinates, full TypeScript type checking on the\nrow shape. For the 1% of apps with rows that don't fit in memory,\nsee \"Out-of-memory data\" below.\n\n## Cell editing\n\n```diff\n- function onCellEdited([col, row], newValue) {\n- rows[row] = { ...rows[row], [colToField(col)]: newValue.data }\n- }\n- <DataEditor onCellEdited={onCellEdited} />\n\n+ <SvGrid\n+ data={rows} columns={columns} features={features}\n+ onCellValueChange={(e) => {\n+ rows[e.rowIndex] = { ...rows[e.rowIndex], [e.columnId]: e.newValue }\n+ }}\n+ />\n```\n\nYou can also rely on sv-grid's built-in write-back if `data` is a\nSvelte 5 `$state` array - mutations propagate automatically.\n\n## Sorting + filtering\n\nGlide doesn't ship sort / filter UI; you wrap your own. Sv-grid\nships them:\n\n```diff\n- // Build your own sort buttons in the toolbar; sort rows yourself.\n\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ <SvGrid data={rows} columns={columns} features={features} filterMode=\"menu\" />\n```\n\n## Frozen columns / row markers\n\n| Glide | sv-grid |\n| -------------------------------------- | --------------------------------------------- |\n| `freezeColumns={1}` | `api.setColumnPinning({ left: ['firstColId'] })` |\n| `rowMarkers=\"number\"` | `showRowNumbers={true}` prop |\n| `rowMarkers=\"checkbox\"` | `selectionMode=\"row\"` prop |\n\n## Custom drawing → custom snippets\n\nGlide's `drawCustomCell` lets you render anything via canvas. The\nsv-grid equivalent is a Svelte snippet (DOM):\n\n```diff\n- drawCustomCell(args) {\n- const ctx = args.ctx\n- ctx.fillStyle = args.cell.data.color\n- ctx.fillRect(args.rect.x, args.rect.y, args.rect.width, args.rect.height)\n- return true\n- }\n\n+ {\n+ field: 'color',\n+ cell: (ctx) => renderSnippet(ColorChip, { color: ctx.row.original.color }),\n+ }\n```\n\n```svelte\n{#snippet ColorChip(props)}\n <span style=\"display: inline-block; width: 18px; height: 18px; background: {props.color};\"></span>\n{/snippet}\n```\n\n## Out-of-memory data\n\nFor \"10M rows, fetched on scroll\" workloads (the only case Glide\ngenuinely beats sv-grid on), use sv-grid's\n[server-side / infinite-scroll pattern](./server-side-data.md):\n\n```svelte\n<SvGrid\n data={loadedSlice}\n columns={columns} features={features}\n externalSort={true}\n externalFilter={true}\n onSortingChange={async (s) => { loadedSlice = await fetchPage({ sort: s, offset: 0, limit: 200 }) }}\n/>\n```\n\nYou'll cap practical perf at ~100k rendered rows; for true 10M+\ndatasets Glide's canvas approach has a perf edge sv-grid won't\nmatch. Most apps don't need 10M rows on screen at once - they need\nfast server-side filtering, which both libraries support equally.\n\n## Theming\n\nGlide: huge `theme` prop object. Sv-grid: CSS custom properties (`--sg-*`).\n\n```diff\n- <DataEditor theme={{\n- accentColor: '#4F5DFF',\n- accentLight: 'rgba(62, 116, 253, 0.2)',\n- bgCell: '#1c1c20',\n- /* …40 more properties… */\n- }} />\n\n+ <div style=\"--sg-accent: #4F5DFF; --sg-bg: #1c1c20;\">\n+ <SvGrid {data} {columns} features={features} />\n+ </div>\n```\n\nSee [design tokens](./tokens.md) for the full list (≤ 30 tokens\ncovers everything; Glide's theme has ~40).\n\n## What you get for free vs Glide\n\n- **Accessibility.** Glide's canvas is invisible to screen readers\n unless you build an off-screen ARIA buffer. Sv-grid is WAI-ARIA\n 1.2 grid pattern out of the box; demo 17 covers axe-core CI.\n- **Standard HTML.** SEO crawlers, browser Find-in-Page, browser\n zoom, OS-level text scaling - all work because the grid emits\n actual `<table><tr><td>`.\n- **Familiar editing.** Browser-native `<input>` / `<select>` for\n cells, with autofill / clipboard / autocorrect intact.\n- **Built-in sort / filter / pagination UI.**\n\n## What you give up\n\n- **Peak FPS on >200k visible rows.** Canvas wins here. For most\n apps the gap is invisible; if you've actually measured it on real\n hardware and need the FPS, Glide remains the right call.\n- **Per-pixel cell drawing.** DOM cells are sub-pixel-uniform but\n not arbitrarily drawn.\n\n## Frequently asked questions\n\n### Should I move from Glide Data Grid to SvGrid?\n\nMove if you need accessibility, standards-compliant HTML, SEO-friendly markup,\nor DOM-based custom cells. Stay on Glide only if you have measured a need for\npeak canvas FPS on 200k+ simultaneously visible rows. For most apps the\nperformance gap is invisible, and SvGrid virtualizes comfortably to 100k+ rows.\n\n### How long does a Glide migration take?\n\nAbout 3-6 hours per grid. The biggest shift is conceptual: Glide's\n`getCellContent` / `onCellEdited` cell-data model is the inverse of SvGrid's\nplain data-array model, so the mental flip takes the most time, not the code.\n\n### Does SvGrid render to canvas or DOM?\n\nDOM, with row and column virtualization. That is what gives you WAI-ARIA roles,\nkeyboard navigation, screen-reader support, and selectable/indexable text -\nthings a canvas grid like Glide cannot offer.\n\n## What you end up with\n\nInline editing over a virtualized body, without a canvas to draw into.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} editable enableCellSelection sortable />\n```\n\n## See also\n\n- [SvGrid vs Glide Data Grid](https://svgrid.com/compare/glide-data-grid/) - the side-by-side comparison\n- [Performance benchmarks](./benchmarks.md) - measured numbers\n- [Server-side data](./server-side-data.md) - the >100k-row pattern\n- [Accessibility](./accessibility.md) - the standards compliance Glide doesn't ship\n"
6099
6099
  },
6100
6100
  {
6101
6101
  "slug": "help/migrating-from-gridjs",
6102
6102
  "path": "docs/help/migrating-from-gridjs.md",
6103
6103
  "title": "Migrating from Grid.js",
6104
6104
  "section": "Help",
6105
- "markdown": "# Migrating from Grid.js\n\nGrid.js is a small vanilla-JS table for search, sort, and pagination\nthat you render into a DOM element. SvGrid does the same in a\nSvelte-5-native component and keeps going - virtualization, Excel-style\nfilters, editing, grouping - when you outgrow the basics.\n\n> Estimated effort: **30 min - 1 hour** per table.\n\n<!-- facts:start gridjs -->\n> **Facts, checked 9 Nov 2026.** `gridjs` 6.2.0, MIT, last published 3 Mar 2024, 393,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026); `gridjs` 6.2.0 17.8 KB JS + 2.4 KB CSS (measured 9 Nov 2026). Grid.js pricing, as its site states it: Grid.js is MIT, free and open source; no licence is sold (https://gridjs.io/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Grid.js](https://svgrid.com/compare/gridjs/).\n<!-- facts:end -->\n\n## Vocabulary cheat sheet\n\n| Grid.js | sv-grid |\n| ----------------------------------------- | ----------------------------------------- |\n| `new Grid({ ... }).render(el)` | `<SvGrid ... />` |\n| `columns: ['Name', 'Amount']` | `columns: [{ field, header }]` |\n| `columns: [{ name, formatter }]` | `{ header, cell: (c) => renderSnippet(...) }` |\n| `sort: true` | `rowSortingFeature` |\n| `search: true` | `api.setState({ globalFilter: query })` / filter feature |\n| `pagination: { limit: 25 }` | `showPagination` (+ page size) |\n| `server: { url, then }` | `externalSort` / `externalFilter` + refetch |\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- import { Grid } from 'gridjs'\n- import 'gridjs/dist/theme/mermaid.css'\n-\n- new Grid({\n- data: rows,\n- columns: ['Name', 'Amount'],\n- sort: true, search: true,\n- pagination: { limit: 25 },\n- }).render(document.getElementById('grid'))\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} showPagination />\n```\n\n## What you gain\n\n- **Virtualization** for large datasets (Grid.js renders the page).\n- **Excel-style filter menu**, **inline editing**, **grouping**, and\n **tree / master-detail** when you need them.\n- **Reactive data** - no `.render(el)` re-instantiation.\n- A **headless engine** and an **imperative API** plus `@svgrid/mcp`.\n\n## Frequently asked questions\n\n### When should I move from Grid.js to SvGrid?\n\nWhen you need more than search / sort / paginate - virtualization for big\ndatasets, inline editing, Excel-style filters, grouping, or tree data. For a\nsmall table, Grid.js stays lighter.\n\n### Is SvGrid MIT-licensed like Grid.js?\n\nYes. `@svgrid/grid` is MIT. Only the optional `@svgrid/enterprise` add-on is paid.\n\n### Does SvGrid support server-side data like Grid.js?\n\nYes. Set `externalSort` / `externalFilter` and refetch on the\n`onSortingChange` / `onFiltersChange` events.\n\n## What you end up with\n\nSearch, sort and pagination - the whole Grid.js surface, plus editing.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable pageable pageSize={3} editable />\n```\n\n## See also\n\n- [SvGrid vs Grid.js](https://svgrid.com/compare/gridjs/) - the side-by-side comparison\n- [Getting started](../getting-started.md) - a working grid in ~15 lines\n- [Server-side data](./server-side-data.md) - the external-data pattern\n"
6105
+ "markdown": "# Migrating from Grid.js\n\nGrid.js is a small vanilla-JS table for search, sort, and pagination\nthat you render into a DOM element. SvGrid does the same in a\nSvelte-5-native component and keeps going - virtualization, Excel-style\nfilters, editing, grouping - when you outgrow the basics.\n\n> Estimated effort: **30 min - 1 hour** per table.\n\n<!-- facts:start gridjs -->\n> **Facts, checked 9 Nov 2026.** `gridjs` 6.2.0, MIT, last published 3 Mar 2024, 393,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026); `gridjs` 6.2.0 17.8 KB JS + 2.4 KB CSS (measured 9 Nov 2026). Grid.js pricing, as its site states it: Grid.js is MIT, free and open source; no licence is sold (https://gridjs.io/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Grid.js](https://svgrid.com/compare/gridjs/).\n<!-- facts:end -->\n\n## Vocabulary cheat sheet\n\n| Grid.js | sv-grid |\n| ----------------------------------------- | ----------------------------------------- |\n| `new Grid({ ... }).render(el)` | `<SvGrid ... />` |\n| `columns: ['Name', 'Amount']` | `columns: [{ field, header }]` |\n| `columns: [{ name, formatter }]` | `{ header, cell: (c) => renderSnippet(...) }` |\n| `sort: true` | `rowSortingFeature` |\n| `search: true` | `api.setState({ globalFilter: query })` / filter feature |\n| `pagination: { limit: 25 }` | `showPagination` (+ page size) |\n| `server: { url, then }` | `externalSort` / `externalFilter` + refetch |\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- import { Grid } from 'gridjs'\n- import 'gridjs/dist/theme/mermaid.css'\n-\n- new Grid({\n- data: rows,\n- columns: ['Name', 'Amount'],\n- sort: true, search: true,\n- pagination: { limit: 25 },\n- }).render(document.getElementById('grid'))\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} showPagination />\n```\n\n## What you gain\n\n- **Virtualization** for large datasets (Grid.js renders the page).\n- **Excel-style filter menu**, **inline editing**, **grouping**, and\n **tree / master-detail** when you need them.\n- **Reactive data** - no `.render(el)` re-instantiation.\n- A **headless engine** and an **imperative API** plus `@svgrid/mcp`.\n\n## Frequently asked questions\n\n### When should I move from Grid.js to SvGrid?\n\nWhen you need more than search / sort / paginate - virtualization for big\ndatasets, inline editing, Excel-style filters, grouping, or tree data. For a\nsmall table, Grid.js stays lighter.\n\n### Is SvGrid MIT-licensed like Grid.js?\n\nYes. `@svgrid/grid` is MIT. Only the optional `@svgrid/enterprise` add-on is paid.\n\n### Does SvGrid support server-side data like Grid.js?\n\nYes. Set `externalSort` / `externalFilter` and refetch on the\n`onSortingChange` / `onFiltersChange` events.\n\n## What you end up with\n\nSearch, sort and pagination - the whole Grid.js surface, plus editing.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable pageable pageSize={3} editable />\n```\n\n## See also\n\n- [SvGrid vs Grid.js](https://svgrid.com/compare/gridjs/) - the side-by-side comparison\n- [Getting started](../getting-started.md) - a working grid in ~15 lines\n- [Server-side data](./server-side-data.md) - the external-data pattern\n"
6106
6106
  },
6107
6107
  {
6108
6108
  "slug": "help/migrating-from-handsontable",
6109
6109
  "path": "docs/help/migrating-from-handsontable.md",
6110
6110
  "title": "Migrating from Handsontable",
6111
6111
  "section": "Help",
6112
- "markdown": "# Migrating from Handsontable\n\nHandsontable's mental model is \"spreadsheet-in-a-page\": every cell\neditable, formulas, copy/paste with the OS clipboard, frozen rows\nand columns. Sv-grid covers ~90% of the same surface; the port is\nmostly a configuration translation, except for HyperFormula (see\nthe Formulas section below).\n\n> Estimated effort: **2-4 hours** per grid for typical spreadsheet\n> workflows. **Add 1-2 days** if you depend heavily on\n> HyperFormula features sv-grid doesn't ship.\n\n<!-- facts:start handsontable -->\n> **Facts, checked 9 Nov 2026.** `handsontable` 18.1.2, Commercial (see licence file), last published 7 Oct 2026, 1,250,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026). Handsontable pricing, as its site states it: Handsontable's Hobby licence is free for personal, exploratory projects and cannot be used in commercial settings; handsontable.com lists Standard from $999 per developer and Priority from $1,299 per developer, with Enterprise on custom terms (https://handsontable.com/pricing, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Handsontable](https://svgrid.com/compare/handsontable/).\n<!-- facts:end -->\n\n## Imports\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- import Handsontable from 'handsontable'\n- import 'handsontable/dist/handsontable.full.min.css'\n\n+ import {\n+ SvGrid, tableFeatures,\n+ rowSortingFeature, columnFilteringFeature, rowSelectionFeature,\n+ + } from '@svgrid/grid'\n```\n\n## Schema → columns\n\nHandsontable accepts a 2D array OR an array of objects. Sv-grid\nexpects the array-of-objects form:\n\n```diff\n- const hot = new Handsontable(container, {\n- data: [\n- ['Tesla', 2017, 'black', false],\n- ['Nissan', 2018, 'blue', true ],\n- ],\n- colHeaders: ['Make', 'Year', 'Color', 'In stock'],\n- columns: [\n- {},\n- { type: 'numeric' },\n- {},\n- { type: 'checkbox' },\n- ],\n- })\n\n+ type Car = { make: string; year: number; color: string; inStock: boolean }\n+ const rows: Car[] = [\n+ { make: 'Tesla', year: 2017, color: 'black', inStock: false },\n+ { make: 'Nissan', year: 2018, color: 'blue', inStock: true },\n+ ]\n+ const columns: ColumnDef<typeof features, Car>[] = [\n+ { field: 'make', header: 'Make' },\n+ { field: 'year', header: 'Year', editorType: 'number' },\n+ { field: 'color', header: 'Color' },\n+ { field: 'inStock', header: 'In stock', editorType: 'checkbox' },\n+ ]\n+ <SvGrid data={rows} columns={columns} features={features} />\n```\n\nIf your existing data is a 2D array, transform once at boot:\n\n```ts\nconst headerRow = raw[0]\nconst rows = raw.slice(1).map((cells) =>\n Object.fromEntries(cells.map((v, i) => [headerRow[i], v])),\n)\n```\n\n## Editor types\n\n| Handsontable | sv-grid |\n| ---------------------------------------------- | ------------------------------------------------ |\n| `type: 'text'` | `editorType: 'text'` |\n| `type: 'numeric'` | `editorType: 'number'` |\n| `type: 'date'` | `editorType: 'date'` |\n| `type: 'checkbox'` | `editorType: 'checkbox'` |\n| `type: 'dropdown', source: [...]` | `editorType: 'list', editorOptions: [...]` |\n| `type: 'autocomplete'` | `editorType: 'list'` (combobox UI ships) |\n| `type: 'time'` | `editorType: 'time'` |\n| `type: 'password'` | Use `editorType: 'text'` + a custom snippet |\n\n## Selection + clipboard\n\n| Handsontable | sv-grid |\n| --------------------------------------- | ------------------------------------------------------- |\n| `selectCells([[0,0,2,5]])` | `api.selectCells(ranges)`, with `selectionMode='cell'` |\n| `getSelected()` | `api.getSelected()`: the same `[[startRow, startCol, endRow, endCol], ...]`, normalised to top-left / bottom-right and `[]` rather than `undefined` when nothing is selected |\n| `getSelectedLast()` | `api.getSelectedLast()`: `[startRow, startCol, endRow, endCol]` with the orientation kept (a range dragged upwards has `startRow > endRow`), or `undefined` |\n| `getSelectedRange()` / `getSelectedRangeLast()` | `api.getSelectedRange()` / `api.getSelectedRangeLast()`: `{ from, to, highlight }` per rectangle, the same three fields as `CellRange`; plain data rather than a class, so use `Math.min` / `Math.max` for the corners |\n| `copyPaste: true` (default) | Ships built-in; `enableCellSelection={true}`. The spreadsheet shell also exchanges formats, number formats and formulas with Excel and Google Sheets through the HTML clipboard |\n| `fillHandle: true` | Ships built-in (drag-to-fill on selected range) |\n| `moveCells: true` | `moveCells` - drag the range border to move it, Ctrl / Cmd to copy. On by default; see [move or copy a range](./editing/move-cells.md) |\n\n## Frozen rows / columns\n\n| Handsontable | sv-grid |\n| ---------------------------------- | ------------------------------------------------------ |\n| `fixedColumnsStart: 2` | `api.setColumnPinning({ left: ['firstColId', 'secondColId'] })` |\n| `fixedRowsTop: 1` | `pinnedTopRows` (and `pinnedBottomRows`) |\n| `manualColumnFreeze: true` | Ships via the column-header right-click menu |\n| `mergeCells: [{ row, col, rowspan, colspan }]` | `mergedCells={[{ rowIndex, colIndex, rowSpan, colSpan }]}` on `<SvGrid>`; the spreadsheet shell adds Merge & Center, Merge Across, Merge Cells and Unmerge on the ribbon and the cell menu |\n\nFreeze panes on a plain `<SvGrid>`: two pinned columns and the sticky\nletter and number headers, with formulas underneath.\n\n<div data-docs-demo=\"208-freeze-panes\" data-height=\"520\"></div>\n\n## Hooks → callbacks\n\n| Handsontable hook | sv-grid |\n| -------------------------------------- | ------------------------------------------------------- |\n| `afterChange((changes, src) => {})` | `onCellValueChange((e) => {...})` |\n| `afterSelection(...)` | `onActiveCellChange((cell) => {...})` |\n| `afterFilter(...)` | `onFiltersChange((f) => {...})` |\n| `afterColumnSort(...)` | `onSortingChange((s) => {...})` |\n| `beforeChange((changes) => false)` | Throw / return `false` from your inline validator; see [validation](./editing/validation.md) |\n| `afterCreateRow / afterRemoveRow` | Wrap `api.addRow / removeRow` in your own emitter; on the spreadsheet shell, `onChange` reports a `structure` reason with the edit |\n| `afterMergeCells / afterUnmergeCells` | On the spreadsheet shell, `onChange` reports `merges`; `api.getMergedCells()` reads the grid's list |\n| `afterSetCellMeta` (comments, validation) | `onChange` reports `comments`, `validation`, `conditional-formats` and `protection` on the shell |\n| `afterFilter` (the Filters plugin) | `onChange` reports `filter` on the shell; `getState().sheets[name].autoFilter` is the state |\n\nOn the spreadsheet shell (`<SvSheet>` in `@svgrid/enterprise`) one callback\ncovers the lot: `onChange(reasons)` fires once per tick with every kind of\nchange since the last call (`cells`, `formats`, `sizes`, `hidden`,\n`freeze`, `sheets`, `comments`, `protection`, `validation`,\n`conditional-formats`, `merges`, `filter`, `structure` with the insert or\ndelete, `restore`), which is where Handsontable's `afterChange` autosave\ngoes. `getState()` gives the document to save and `setState()` puts it back.\n\n## Cell meta → the sheet document\n\nHandsontable keeps comments, validators, read-only flags and merges as cell\nmeta on the instance. On the spreadsheet shell they are parts of the\ndocument, per sheet, saved with it and moved by inserts and deletes:\n\n| Handsontable | sv-grid spreadsheet shell |\n| --------------------------------------------------- | --------------------------------------------------------------- |\n| `comments: true`, `cell: [{ row, col, comment }]` | Review > New Comment, Shift+F2, the cell menu; `getState().sheets[name].comments` |\n| `validator: 'numeric'`, `allowInvalid: false` | Data > Data Validation (Whole number, Decimal, List, Date, Text length, Custom), Stop or Warning; `validation` in the state |\n| `readOnly: true` on a cell | Format Cells > Protection unlocks the cells that may change, Review > Protect Sheet locks the rest; `locked: false` in the format entry, `protected` per sheet |\n| `mergeCells` | Merge & Center on the ribbon and the cell menu; `merges` in the state |\n| `filters: true` + `dropdownMenu` | Ctrl+Shift+L or Data > Filter: Excel's AutoFilter arrows and menus; `autoFilter` in the state |\n| conditional formatting (a custom renderer) | Home > Styles > Conditional Formatting: Highlight Cells, Top/Bottom, Data Bars, Color Scales, Icon Sets, Manage Rules; `conditionalFormats` in the state |\n| `autofill` rules | The fill handle's own series: numbers, dates by day or by the set gap, `Item 1`, weekdays and months |\n\nOn a plain `<SvGrid>` the free grid has the primitives instead: `notes`\nand `editableComments` for comments, `editable` and `valueParser` on a\ncolumn for read-only cells and validation, `mergedCells` for merges, the\nfilter row and its Excel-style menu for filtering, and value-driven\n`conditionalFormats` by column.\n\n## Formulas (HyperFormula)\n\nSv-grid ships a focused subset under\n[`spreadsheet-formulas`](./spreadsheet-formulas.md) (SUM, IF, COUNTIF\n+ cell refs + ranges + cycle detection). It does NOT ship the full\nHyperFormula library.\n\nIf you need HyperFormula's full surface (~400 functions, complex\ndate math, R1C1 refs), the integration pattern is:\n\n```ts\nimport { HyperFormula } from 'hyperformula'\n\nconst hf = HyperFormula.buildFromArray(rowsAsMatrix, { licenseKey: 'gpl-v3' })\n\n// On every cell edit, push to HF + read back the computed value:\nfunction onCellValueChange(e) {\n hf.setCellContents({ sheet: 0, row: e.rowIndex, col: columnIndex }, e.newValue)\n // ...read computed cells you depend on + push back via api.setCellValue\n}\n```\n\nThis is the only piece where the swap isn't 1:1. Most teams find\nsv-grid's shipped subset covers 80% of real-world formula usage; if\nyours is in the 20%, HyperFormula plugs in with the pattern above.\n\n## Licence\n\nHandsontable's grid needs a commercial licence for commercial use; its free\nHobby licence is for personal, exploratory projects, as its pricing page\nstates (the wording and the date are in the facts box at the top of this\npage). Sv-grid's `@svgrid/grid` is MIT with no licence key, and the\n[Enterprise tier](../enterprise/licensing.md) needs no key to evaluate:\nit works without one and displays a watermark and a console\nmessage until you add one, so there is no cutoff to plan around.\n\n## What you get for free vs Handsontable\n\n- **No commercial licence for the grid.** @svgrid/grid is MIT.\n- **Modern Svelte 5 ergonomics.** `$state` arrays beat\n `loadData(...)`.\n- **Grid features a spreadsheet does not have.** Row grouping with\n aggregation, master/detail, server-side data (grouping, tree, pivot and transactions on the server are Enterprise) and integrated\n charts in the same package.\n- **CSP-clean.** Handsontable's HyperFormula path needs CSP `eval`\n exceptions in some configurations.\n\n## What you give up\n\n- **Full HyperFormula surface as a supported feature.** Sv-grid ships a\n subset and lets you wire HyperFormula yourself; see above.\n- **Nested headers.** Handsontable's `nestedHeaders` have no\n counterpart beyond column groups.\n- **Threaded comments and a validation Input Message.** Comments on the\n shell are Excel's notes, one text per cell; validation shows its message\n on a refusal, not on arrival.\n- **Excel export without a paid pack.** Handsontable's export plugin writes\n XLSX through its asynchronous method; on sv-grid, CSV, TSV and JSON export\n are free and Excel, PDF and print output are in `@svgrid/enterprise`.\n\n## Frequently asked questions\n\n### Can SvGrid replace Handsontable's spreadsheet features?\n\nIt covers roughly 90% of the surface - inline editing on every cell, copy/paste\nas TSV, range selection, column groups, and a built-in formula engine. Budget\n2-4 hours per grid for typical spreadsheet workflows, plus 1-2 days if you lean\nheavily on the full HyperFormula function set.\n\n### Does SvGrid support formulas like Handsontable?\n\nYes, a built-in formula engine with cell references, ranges, and common\nfunctions (see the spreadsheet-formulas guide and demo 27). It is a practical\nsubset rather than the complete HyperFormula library, so verify your specific\nfunctions before porting.\n\n### Is SvGrid licensed like Handsontable?\n\nNo. The `@svgrid/grid` core is MIT and free for commercial use - no per-seat\nlicence key - whereas Handsontable's free licence excludes commercial use and\nits commercial plans are per developer; the facts box has the statement as\nread from handsontable.com. The optional `@svgrid/enterprise` pack (Excel and\nPDF export, print, pivot, import) is priced per developer.\n\n### Does SvGrid have a blank spreadsheet like Handsontable?\n\nYes, on the plain grid: column-letter headers, a row gutter, a name box\nand formula bar, gridlines, range selection and a fill handle, with\nHyperFormula underneath when you want its function library.\n\n<div data-docs-demo=\"207-blank-sheet\" data-height=\"560\"></div>\n\n## What you end up with\n\nSpreadsheet behaviour: inline edit, drag a cell range, copy it out as TSV.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} editable enableCellSelection statusBar />\n```\n\n## See also\n\n- [SvGrid vs Handsontable](https://svgrid.com/compare/handsontable/) - the side-by-side comparison, with a source and date for every claim\n- [Spreadsheet formulas](./spreadsheet-formulas.md) - sv-grid's\n built-in formula engine, and the rest of the spreadsheet demos\n- [Demo 27 (Spreadsheet + Ribbon)](https://svgrid.com/demos/27-spreadsheet-ribbon/) - live\n- [Migrating from AG Grid](./migrating-from-ag-grid.md)\n"
6112
+ "markdown": "# Migrating from Handsontable\n\nHandsontable's mental model is \"spreadsheet-in-a-page\": every cell\neditable, formulas, copy/paste with the OS clipboard, frozen rows\nand columns. Sv-grid covers ~90% of the same surface; the port is\nmostly a configuration translation, except for HyperFormula (see\nthe Formulas section below).\n\n> Estimated effort: **2-4 hours** per grid for typical spreadsheet\n> workflows. **Add 1-2 days** if you depend heavily on\n> HyperFormula features sv-grid doesn't ship.\n\n<!-- facts:start handsontable -->\n> **Facts, checked 9 Nov 2026.** `handsontable` 18.1.2, Commercial (see licence file), last published 7 Oct 2026, 1,250,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026). Handsontable pricing, as its site states it: Handsontable's Hobby licence is free for personal, exploratory projects and cannot be used in commercial settings; handsontable.com lists Standard from $999 per developer and Priority from $1,299 per developer, with Enterprise on custom terms (https://handsontable.com/pricing, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Handsontable](https://svgrid.com/compare/handsontable/).\n<!-- facts:end -->\n\n## Imports\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- import Handsontable from 'handsontable'\n- import 'handsontable/dist/handsontable.full.min.css'\n\n+ import {\n+ SvGrid, tableFeatures,\n+ rowSortingFeature, columnFilteringFeature, rowSelectionFeature,\n+ + } from '@svgrid/grid'\n```\n\n## Schema → columns\n\nHandsontable accepts a 2D array OR an array of objects. Sv-grid\nexpects the array-of-objects form:\n\n```diff\n- const hot = new Handsontable(container, {\n- data: [\n- ['Tesla', 2017, 'black', false],\n- ['Nissan', 2018, 'blue', true ],\n- ],\n- colHeaders: ['Make', 'Year', 'Color', 'In stock'],\n- columns: [\n- {},\n- { type: 'numeric' },\n- {},\n- { type: 'checkbox' },\n- ],\n- })\n\n+ type Car = { make: string; year: number; color: string; inStock: boolean }\n+ const rows: Car[] = [\n+ { make: 'Tesla', year: 2017, color: 'black', inStock: false },\n+ { make: 'Nissan', year: 2018, color: 'blue', inStock: true },\n+ ]\n+ const columns: ColumnDef<typeof features, Car>[] = [\n+ { field: 'make', header: 'Make' },\n+ { field: 'year', header: 'Year', editorType: 'number' },\n+ { field: 'color', header: 'Color' },\n+ { field: 'inStock', header: 'In stock', editorType: 'checkbox' },\n+ ]\n+ <SvGrid data={rows} columns={columns} features={features} />\n```\n\nIf your existing data is a 2D array, transform once at boot:\n\n```ts\nconst headerRow = raw[0]\nconst rows = raw.slice(1).map((cells) =>\n Object.fromEntries(cells.map((v, i) => [headerRow[i], v])),\n)\n```\n\n## Editor types\n\n| Handsontable | sv-grid |\n| ---------------------------------------------- | ------------------------------------------------ |\n| `type: 'text'` | `editorType: 'text'` |\n| `type: 'numeric'` | `editorType: 'number'` |\n| `type: 'date'` | `editorType: 'date'` |\n| `type: 'checkbox'` | `editorType: 'checkbox'` |\n| `type: 'dropdown', source: [...]` | `editorType: 'list', editorOptions: [...]` |\n| `type: 'autocomplete'` | `editorType: 'list'` (combobox UI ships) |\n| `type: 'time'` | `editorType: 'time'` |\n| `type: 'password'` | Use `editorType: 'text'` + a custom snippet |\n\n## Selection + clipboard\n\n| Handsontable | sv-grid |\n| --------------------------------------- | ------------------------------------------------------- |\n| `selectCells([[0,0,2,5]])` | `api.selectCells(ranges)`, with `selectionMode='cell'` |\n| `getSelected()` | `api.getSelected()`: the same `[[startRow, startCol, endRow, endCol], ...]`, normalised to top-left / bottom-right and `[]` rather than `undefined` when nothing is selected |\n| `getSelectedLast()` | `api.getSelectedLast()`: `[startRow, startCol, endRow, endCol]` with the orientation kept (a range dragged upwards has `startRow > endRow`), or `undefined` |\n| `getSelectedRange()` / `getSelectedRangeLast()` | `api.getSelectedRange()` / `api.getSelectedRangeLast()`: `{ from, to, highlight }` per rectangle, the same three fields as `CellRange`; plain data rather than a class, so use `Math.min` / `Math.max` for the corners |\n| `copyPaste: true` (default) | Ships built-in; `enableCellSelection={true}`. The spreadsheet shell also exchanges formats, number formats and formulas with Excel and Google Sheets through the HTML clipboard |\n| `fillHandle: true` | Ships built-in (drag-to-fill on selected range) |\n| `moveCells: true` | `moveCells` - drag the range border to move it, Ctrl / Cmd to copy. On by default; see [move or copy a range](./editing/move-cells.md) |\n\n## Frozen rows / columns\n\n| Handsontable | sv-grid |\n| ---------------------------------- | ------------------------------------------------------ |\n| `fixedColumnsStart: 2` | `api.setColumnPinning({ left: ['firstColId', 'secondColId'] })` |\n| `fixedRowsTop: 1` | `pinnedTopRows` (and `pinnedBottomRows`) |\n| `manualColumnFreeze: true` | Ships via the column-header right-click menu |\n| `mergeCells: [{ row, col, rowspan, colspan }]` | `mergedCells={[{ rowIndex, colIndex, rowSpan, colSpan }]}` on `<SvGrid>`; the spreadsheet shell adds Merge & Center, Merge Across, Merge Cells and Unmerge on the ribbon and the cell menu |\n\nFreeze panes on a plain `<SvGrid>`: two pinned columns and the sticky\nletter and number headers, with formulas underneath.\n\n<div data-docs-demo=\"208-freeze-panes\" data-height=\"520\"></div>\n\n## Hooks → callbacks\n\n| Handsontable hook | sv-grid |\n| -------------------------------------- | ------------------------------------------------------- |\n| `afterChange((changes, src) => {})` | `onCellValueChange((e) => {...})` |\n| `afterSelection(...)` | `onActiveCellChange((cell) => {...})` |\n| `afterFilter(...)` | `onFiltersChange((f) => {...})` |\n| `afterColumnSort(...)` | `onSortingChange((s) => {...})` |\n| `beforeChange((changes) => false)` | Throw / return `false` from your inline validator; see [validation](./editing/validation.md) |\n| `afterCreateRow / afterRemoveRow` | Wrap `api.addRow / removeRow` in your own emitter; on the spreadsheet shell, `onChange` reports a `structure` reason with the edit |\n| `afterMergeCells / afterUnmergeCells` | On the spreadsheet shell, `onChange` reports `merges`; `api.getMergedCells()` reads the grid's list |\n| `afterSetCellMeta` (comments, validation) | `onChange` reports `comments`, `validation`, `conditional-formats` and `protection` on the shell |\n| `afterFilter` (the Filters plugin) | `onChange` reports `filter` on the shell; `getState().sheets[name].autoFilter` is the state |\n\nOn the spreadsheet shell (`<SvSheet>` in `@svgrid/enterprise`) one callback\ncovers the lot: `onChange(reasons)` fires once per tick with every kind of\nchange since the last call (`cells`, `formats`, `sizes`, `hidden`,\n`freeze`, `sheets`, `comments`, `protection`, `validation`,\n`conditional-formats`, `merges`, `filter`, `structure` with the insert or\ndelete, `restore`), which is where Handsontable's `afterChange` autosave\ngoes. `getState()` gives the document to save and `setState()` puts it back.\n\n## Cell meta → the sheet document\n\nHandsontable keeps comments, validators, read-only flags and merges as cell\nmeta on the instance. On the spreadsheet shell they are parts of the\ndocument, per sheet, saved with it and moved by inserts and deletes:\n\n| Handsontable | sv-grid spreadsheet shell |\n| --------------------------------------------------- | --------------------------------------------------------------- |\n| `comments: true`, `cell: [{ row, col, comment }]` | Review > New Comment, Shift+F2, the cell menu; `getState().sheets[name].comments` |\n| `validator: 'numeric'`, `allowInvalid: false` | Data > Data Validation (Whole number, Decimal, List, Date, Text length, Custom), Stop or Warning; `validation` in the state |\n| `readOnly: true` on a cell | Format Cells > Protection unlocks the cells that may change, Review > Protect Sheet locks the rest; `locked: false` in the format entry, `protected` per sheet |\n| `mergeCells` | Merge & Center on the ribbon and the cell menu; `merges` in the state |\n| `filters: true` + `dropdownMenu` | Ctrl+Shift+L or Data > Filter: Excel's AutoFilter arrows and menus; `autoFilter` in the state |\n| conditional formatting (a custom renderer) | Home > Styles > Conditional Formatting: Highlight Cells, Top/Bottom, Data Bars, Color Scales, Icon Sets, Manage Rules; `conditionalFormats` in the state |\n| `autofill` rules | The fill handle's own series: numbers, dates by day or by the set gap, `Item 1`, weekdays and months |\n\nOn a plain `<SvGrid>` the free grid has the primitives instead: `notes`\nand `editableComments` for comments, `editable` and `valueParser` on a\ncolumn for read-only cells and validation, `mergedCells` for merges, the\nfilter row and its Excel-style menu for filtering, and value-driven\n`conditionalFormats` by column.\n\n## Formulas (HyperFormula)\n\nSv-grid ships a focused subset under\n[`spreadsheet-formulas`](./spreadsheet-formulas.md) (SUM, IF, COUNTIF\n+ cell refs + ranges + cycle detection). It does NOT ship the full\nHyperFormula library.\n\nIf you need HyperFormula's full surface (~400 functions, complex\ndate math, R1C1 refs), the integration pattern is:\n\n```ts\nimport { HyperFormula } from 'hyperformula'\n\nconst hf = HyperFormula.buildFromArray(rowsAsMatrix, { licenseKey: 'gpl-v3' })\n\n// On every cell edit, push to HF + read back the computed value:\nfunction onCellValueChange(e) {\n hf.setCellContents({ sheet: 0, row: e.rowIndex, col: columnIndex }, e.newValue)\n // ...read computed cells you depend on + push back via api.setCellValue\n}\n```\n\nThis is the only piece where the swap isn't 1:1. Most teams find\nsv-grid's shipped subset covers 80% of real-world formula usage; if\nyours is in the 20%, HyperFormula plugs in with the pattern above.\n\n## Licence\n\nHandsontable's grid needs a commercial licence for commercial use; its free\nHobby licence is for personal, exploratory projects, as its pricing page\nstates (the wording and the date are in the facts box at the top of this\npage). Sv-grid's `@svgrid/grid` is MIT with no licence key, and the\n[Enterprise tier](../enterprise/licensing.md) needs no key to evaluate:\nit works without one and displays a watermark and a console\nmessage until you add one, so there is no cutoff to plan around.\n\n## What you get for free vs Handsontable\n\n- **No commercial licence for the grid.** @svgrid/grid is MIT.\n- **Modern Svelte 5 ergonomics.** `$state` arrays beat\n `loadData(...)`.\n- **Grid features a spreadsheet does not have.** Row grouping with\n aggregation, master/detail, server-side data (grouping, tree, pivot and transactions on the server are Enterprise) and integrated\n charts in the same package.\n- **CSP-clean.** Handsontable's HyperFormula path needs CSP `eval`\n exceptions in some configurations.\n\n## What you give up\n\n- **Full HyperFormula surface as a supported feature.** Sv-grid ships a\n subset and lets you wire HyperFormula yourself; see above.\n- **Nested headers.** Handsontable's `nestedHeaders` have no\n counterpart beyond column groups.\n- **Threaded comments and a validation Input Message.** Comments on the\n shell are Excel's notes, one text per cell; validation shows its message\n on a refusal, not on arrival.\n- **Excel export without a paid pack.** Handsontable's export plugin writes\n XLSX through its asynchronous method; on sv-grid, CSV, TSV and JSON export\n are free and Excel, PDF and print output are in `@svgrid/enterprise`.\n\n## Frequently asked questions\n\n### Can SvGrid replace Handsontable's spreadsheet features?\n\nIt covers roughly 90% of the surface - inline editing on every cell, copy/paste\nas TSV, range selection, column groups, and a built-in formula engine. Budget\n2-4 hours per grid for typical spreadsheet workflows, plus 1-2 days if you lean\nheavily on the full HyperFormula function set.\n\n### Does SvGrid support formulas like Handsontable?\n\nYes, a built-in formula engine with cell references, ranges, and common\nfunctions (see the spreadsheet-formulas guide and demo 27). It is a practical\nsubset rather than the complete HyperFormula library, so verify your specific\nfunctions before porting.\n\n### Is SvGrid licensed like Handsontable?\n\nNo. The `@svgrid/grid` core is MIT and free for commercial use - no per-seat\nlicence key - whereas Handsontable's free licence excludes commercial use and\nits commercial plans are per developer; the facts box has the statement as\nread from handsontable.com. The optional `@svgrid/enterprise` pack (Excel and\nPDF export, print, pivot, import) is priced per developer.\n\n### Does SvGrid have a blank spreadsheet like Handsontable?\n\nYes, on the plain grid: column-letter headers, a row gutter, a name box\nand formula bar, gridlines, range selection and a fill handle, with\nHyperFormula underneath when you want its function library.\n\n<div data-docs-demo=\"207-blank-sheet\" data-height=\"560\"></div>\n\n## What you end up with\n\nSpreadsheet behaviour: inline edit, drag a cell range, copy it out as TSV.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} editable enableCellSelection statusBar />\n```\n\n## See also\n\n- [SvGrid vs Handsontable](https://svgrid.com/compare/handsontable/) - the side-by-side comparison, with a source and date for every claim\n- [Spreadsheet formulas](./spreadsheet-formulas.md) - sv-grid's\n built-in formula engine, and the rest of the spreadsheet demos\n- [Demo 27 (Spreadsheet + Ribbon)](https://svgrid.com/demos/27-spreadsheet-ribbon/) - live\n- [Migrating from AG Grid](./migrating-from-ag-grid.md)\n"
6113
6113
  },
6114
6114
  {
6115
6115
  "slug": "help/migrating-from-jqxgrid",
6116
6116
  "path": "docs/help/migrating-from-jqxgrid.md",
6117
6117
  "title": "Migrating from jqxGrid (jQWidgets)",
6118
6118
  "section": "Help",
6119
- "markdown": "# Migrating from jqxGrid (jQWidgets)\n\njqxGrid and SvGrid come from the **same team**. jqxGrid is the mature,\nmulti-framework grid (jQuery core with Angular, React, and Vue\nintegrations); SvGrid is the Svelte-5-native member of the family. If\nyour team is consolidating on Svelte 5, this guide maps a jqxGrid setup\nonto SvGrid - and the concepts will feel familiar because the\nengineering lineage is shared.\n\n> Estimated effort: **2-4 hours** per grid. Most of the work is moving\n> from the imperative jQuery source / API to reactive `$state`.\n\n<!-- facts:start jqxgrid -->\n> **Facts, checked 9 Nov 2026.** `jqwidgets-scripts` 27.2.0, https://www.jqwidgets.com/license/, last published 31 Oct 2026, 50,500 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026). jqxGrid pricing, as its site states it: jqwidgets.com lists the Developer License at $499 (on sale at $399) per developer, perpetual and royalty-free with one year of updates and support, and the Team License at $1,499 for five or more developers; the free Community License excludes the Grid (https://www.jqwidgets.com/license/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs jqxGrid (jQWidgets)](https://svgrid.com/compare/jqxgrid/).\n<!-- facts:end -->\n\n## Vocabulary cheat sheet\n\n| jqxGrid | sv-grid |\n| ---------------------------------------- | ----------------------------------------- |\n| `$('#grid').jqxGrid({ ... })` | `<SvGrid ... />` |\n| `source` / `jqxDataAdapter` | `data` array (or `externalSort/Filter`) |\n| `{ text: 'Name', datafield: 'name' }` | `{ header: 'Name', field: 'name' }` |\n| `cellsrenderer` | `cell: (c) => renderSnippet(...)` |\n| `columntype` / cell editor | `editorType` |\n| `cellsformat: 'c2'` | `format: { type: 'currency', currency: 'USD' }` |\n| `sortable` / `filterable` | `rowSortingFeature` / `columnFilteringFeature` |\n| `groupable` + `groups` | `columnGroupingFeature` + `api.setGroupBy()` |\n| `pageable` | `showPagination` |\n| `jqxGrid('updatebounddata')` | reassign the `$state` data array |\n| `editable` + `cellendedit` event | `enableInlineEditing` + `onCellValueChange` |\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- const source = { localdata: rows, datatype: 'array' }\n- const adapter = new $.jqx.dataAdapter(source)\n- $('#grid').jqxGrid({\n- source: adapter, sortable: true, filterable: true, pageable: true, editable: true,\n- columns: [\n- { text: 'Name', datafield: 'name' },\n- { text: 'Amount', datafield: 'amount', cellsformat: 'c2' },\n- ],\n- })\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} showPagination enableInlineEditing />\n```\n\n## What changes\n\n- **jQuery source / dataAdapter → reactive `$state`.** No\n `updatebounddata()`; reassign the array.\n- **`cellsrenderer` → snippet cells** via `renderSnippet`.\n- **jQWidgets theme → `--sg-*` tokens** (or your Tailwind theme).\n\n## A note on family\n\nMoving to SvGrid keeps you with the same team's Svelte-5 grid rather\nthan switching vendors. The Enterprise tier and support come from the same people behind jqxGrid.\nIf your app is still on jQuery / Angular / React / Vue, jqxGrid remains\nthe right tool; reach for SvGrid when the codebase is Svelte 5.\n\n## Frequently asked questions\n\n### Is SvGrid made by the same team as jqxGrid?\n\nYes. SvGrid is built by jQWidgets - the same team behind jqxGrid - specifically\nfor Svelte 5, rebuilt around runes and snippets with an MIT community core.\n\n### How do jqxGrid columns map to SvGrid?\n\n`text` becomes `header`, `datafield` becomes `field`, `cellsrenderer` becomes a\n`renderSnippet` cell, and `cellsformat` maps onto the `format` config. Sorting /\nfiltering / grouping move to registered features.\n\n### Should I migrate my jQuery jqxGrid app to SvGrid?\n\nOnly if you are moving that app to Svelte 5. If it stays on jQuery / Angular /\nReact / Vue, jqxGrid is the better fit. SvGrid is the native choice once the\nstack is Svelte.\n\n## What you end up with\n\nEditing plus range selection and a totals row - the jqxGrid working set.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} editable enableCellSelection summary sortable />\n```\n\n## See also\n\n- [SvGrid vs jqxGrid](https://svgrid.com/compare/jqxgrid/) - the side-by-side comparison\n- [About SvGrid](https://svgrid.com/about/) - built by jQWidgets\n- [Getting started](../getting-started.md) - a working grid in ~15 lines\n"
6119
+ "markdown": "# Migrating from jqxGrid (jQWidgets)\n\njqxGrid and SvGrid come from the **same team**. jqxGrid is the mature,\nmulti-framework grid (jQuery core with Angular, React, and Vue\nintegrations); SvGrid is the Svelte-5-native member of the family. If\nyour team is consolidating on Svelte 5, this guide maps a jqxGrid setup\nonto SvGrid - and the concepts will feel familiar because the\nengineering lineage is shared.\n\n> Estimated effort: **2-4 hours** per grid. Most of the work is moving\n> from the imperative jQuery source / API to reactive `$state`.\n\n<!-- facts:start jqxgrid -->\n> **Facts, checked 9 Nov 2026.** `jqwidgets-scripts` 27.2.0, https://www.jqwidgets.com/license/, last published 31 Oct 2026, 50,500 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026). jqxGrid pricing, as its site states it: jqwidgets.com lists the Developer License at $499 (on sale at $399) per developer, perpetual and royalty-free with one year of updates and support, and the Team License at $1,499 for five or more developers; the free Community License excludes the Grid (https://www.jqwidgets.com/license/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs jqxGrid (jQWidgets)](https://svgrid.com/compare/jqxgrid/).\n<!-- facts:end -->\n\n## Vocabulary cheat sheet\n\n| jqxGrid | sv-grid |\n| ---------------------------------------- | ----------------------------------------- |\n| `$('#grid').jqxGrid({ ... })` | `<SvGrid ... />` |\n| `source` / `jqxDataAdapter` | `data` array (or `externalSort/Filter`) |\n| `{ text: 'Name', datafield: 'name' }` | `{ header: 'Name', field: 'name' }` |\n| `cellsrenderer` | `cell: (c) => renderSnippet(...)` |\n| `columntype` / cell editor | `editorType` |\n| `cellsformat: 'c2'` | `format: { type: 'currency', currency: 'USD' }` |\n| `sortable` / `filterable` | `rowSortingFeature` / `columnFilteringFeature` |\n| `groupable` + `groups` | `columnGroupingFeature` + `api.setGroupBy()` |\n| `pageable` | `showPagination` |\n| `jqxGrid('updatebounddata')` | reassign the `$state` data array |\n| `editable` + `cellendedit` event | `enableInlineEditing` + `onCellValueChange` |\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- const source = { localdata: rows, datatype: 'array' }\n- const adapter = new $.jqx.dataAdapter(source)\n- $('#grid').jqxGrid({\n- source: adapter, sortable: true, filterable: true, pageable: true, editable: true,\n- columns: [\n- { text: 'Name', datafield: 'name' },\n- { text: 'Amount', datafield: 'amount', cellsformat: 'c2' },\n- ],\n- })\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} showPagination enableInlineEditing />\n```\n\n## What changes\n\n- **jQuery source / dataAdapter → reactive `$state`.** No\n `updatebounddata()`; reassign the array.\n- **`cellsrenderer` → snippet cells** via `renderSnippet`.\n- **jQWidgets theme → `--sg-*` tokens** (or your Tailwind theme).\n\n## A note on family\n\nMoving to SvGrid keeps you with the same team's Svelte-5 grid rather\nthan switching vendors. The Enterprise tier and support come from the same people behind jqxGrid.\nIf your app is still on jQuery / Angular / React / Vue, jqxGrid remains\nthe right tool; reach for SvGrid when the codebase is Svelte 5.\n\n## Frequently asked questions\n\n### Is SvGrid made by the same team as jqxGrid?\n\nYes. SvGrid is built by jQWidgets - the same team behind jqxGrid - specifically\nfor Svelte 5, rebuilt around runes and snippets with an MIT community core.\n\n### How do jqxGrid columns map to SvGrid?\n\n`text` becomes `header`, `datafield` becomes `field`, `cellsrenderer` becomes a\n`renderSnippet` cell, and `cellsformat` maps onto the `format` config. Sorting /\nfiltering / grouping move to registered features.\n\n### Should I migrate my jQuery jqxGrid app to SvGrid?\n\nOnly if you are moving that app to Svelte 5. If it stays on jQuery / Angular /\nReact / Vue, jqxGrid is the better fit. SvGrid is the native choice once the\nstack is Svelte.\n\n## What you end up with\n\nEditing plus range selection and a totals row - the jqxGrid working set.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} editable enableCellSelection summary sortable />\n```\n\n## See also\n\n- [SvGrid vs jqxGrid](https://svgrid.com/compare/jqxgrid/) - the side-by-side comparison\n- [About SvGrid](https://svgrid.com/about/) - built by jQWidgets\n- [Getting started](../getting-started.md) - a working grid in ~15 lines\n"
6120
6120
  },
6121
6121
  {
6122
6122
  "slug": "help/migrating-from-kendo-grid",
6123
6123
  "path": "docs/help/migrating-from-kendo-grid.md",
6124
6124
  "title": "Migrating from Kendo UI Grid (Telerik)",
6125
6125
  "section": "Help",
6126
- "markdown": "# Migrating from Kendo UI Grid (Telerik)\n\nKendo UI Grid is the polished, commercial enterprise grid from Telerik /\nProgress, available for jQuery, React, Vue, and Angular. Moving to SvGrid\ntrades the multi-framework commercial suite for a Svelte-5-native grid\nwith an MIT core - and a much cheaper paid tier.\n\n> Estimated effort: **3-6 hours** per grid - column / event translation\n> plus re-theming.\n>\n> Kendo's exact API differs across its jQuery / React / Vue / Angular\n> flavours; map your version's column and event names onto the SvGrid\n> equivalents below.\n\n<!-- facts:start kendo-ui-grid -->\n> **Facts, checked 9 Nov 2026.** `@progress/kendo-react-grid` 16.3.0, Commercial (see licence file), last published 2 Nov 2026, 406,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026). Kendo UI Grid pricing, as its site states it: telerik.com lists the Kendo UI bundle at $799, $849 or $1,299 per developer per year depending on the support tier, and KendoReact alone from $649 per developer per year; no free tier for the grid (https://www.telerik.com/purchase.aspx, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Kendo UI Grid (Telerik)](https://svgrid.com/compare/kendo-ui-grid/).\n<!-- facts:end -->\n\n## Concept map\n\n| Kendo UI Grid | sv-grid |\n| ---------------------------------------- | ----------------------------------------- |\n| `columns: [{ field, title }]` | `columns: [{ field, header }]` |\n| `template` / cell render | `cell: (c) => renderSnippet(...)` |\n| `editable` + editor | `enableInlineEditing` + `editorType` |\n| `sortable` / `filterable` | `rowSortingFeature` / `columnFilteringFeature` |\n| `group` / aggregates | `columnGroupingFeature` + `api.setGroupBy()` |\n| `dataSource` (local / remote) | `data` array or `externalSort/Filter` |\n| `pageable` | `showPagination` |\n| Kendo themes (Default / Bootstrap) | `--sg-*` tokens / Tailwind |\n| Grid events (`change`, `dataBound`) | `onCellValueChange`, `onApiReady`, ... |\n\n## Shape of the change\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- $('#grid').kendoGrid({\n- dataSource: { data: rows, pageSize: 25 },\n- sortable: true, filterable: true, pageable: true, editable: true,\n- columns: [\n- { field: 'name', title: 'Name' },\n- { field: 'amount', title: 'Amount', format: '{0:c}' },\n- ],\n- })\n\n+ <SvGrid\n+ data={rows}\n+ columns={[\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]}\n+ features={tableFeatures({ rowSortingFeature, columnFilteringFeature })}\n+ showPagination enableInlineEditing />\n```\n\n## Why teams switch\n\n- **Svelte 5 native** instead of a jQuery / multi-framework suite.\n- **MIT community core** - no per-developer license for the grid itself.\n- **Paid support at a fraction of enterprise-suite pricing.**\n- **No design-system lock-in** - theme via `--sg-*` tokens.\n\n## What to weigh\n\n- Kendo bundles a **huge component suite** (charts, scheduler, editor)\n and decades of vendor support. If you need the whole suite across\n several frameworks, that has real value.\n\n## Frequently asked questions\n\n### Is SvGrid a cheaper alternative to Kendo UI Grid?\n\nFor a Svelte stack, yes: the `@svgrid/grid` core is MIT (free, including\ncommercial use), and the paid `@svgrid/enterprise` tier is a fraction of enterprise\ncomponent-suite pricing.\n\n### How long does a Kendo Grid migration take?\n\nAbout 3-6 hours per grid. It is a column / event rename pass plus re-theming;\nthe columns and editing concepts map closely.\n\n### Does SvGrid match Kendo's feature set?\n\nFor the grid itself it covers the common enterprise surface - sorting,\nExcel-style filters, grouping, virtualization, editing, master/detail, tree.\nKendo's value beyond that is the wider suite and multi-framework parity.\n\n## What you end up with\n\nSorting, filtering, grouping and editing, with the column menu Kendo users expect.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} groupBy={['department']} groupable sortable filterable editable />\n```\n\n## See also\n\n- [SvGrid vs Kendo UI Grid](https://svgrid.com/compare/kendo-ui-grid/) - the side-by-side comparison\n- [Pricing](https://svgrid.com/pricing/) - the SvGrid Enterprise tiers\n- [Architecture](./architecture.md) - engine + render-component split\n"
6126
+ "markdown": "# Migrating from Kendo UI Grid (Telerik)\n\nKendo UI Grid is the polished, commercial enterprise grid from Telerik /\nProgress, available for jQuery, React, Vue, and Angular. Moving to SvGrid\ntrades the multi-framework commercial suite for a Svelte-5-native grid\nwith an MIT core - and a much cheaper paid tier.\n\n> Estimated effort: **3-6 hours** per grid - column / event translation\n> plus re-theming.\n>\n> Kendo's exact API differs across its jQuery / React / Vue / Angular\n> flavours; map your version's column and event names onto the SvGrid\n> equivalents below.\n\n<!-- facts:start kendo-ui-grid -->\n> **Facts, checked 9 Nov 2026.** `@progress/kendo-react-grid` 16.3.0, Commercial (see licence file), last published 2 Nov 2026, 406,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026). Kendo UI Grid pricing, as its site states it: telerik.com lists the Kendo UI bundle at $799, $849 or $1,299 per developer per year depending on the support tier, and KendoReact alone from $649 per developer per year; no free tier for the grid (https://www.telerik.com/purchase.aspx, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Kendo UI Grid (Telerik)](https://svgrid.com/compare/kendo-ui-grid/).\n<!-- facts:end -->\n\n## Concept map\n\n| Kendo UI Grid | sv-grid |\n| ---------------------------------------- | ----------------------------------------- |\n| `columns: [{ field, title }]` | `columns: [{ field, header }]` |\n| `template` / cell render | `cell: (c) => renderSnippet(...)` |\n| `editable` + editor | `enableInlineEditing` + `editorType` |\n| `sortable` / `filterable` | `rowSortingFeature` / `columnFilteringFeature` |\n| `group` / aggregates | `columnGroupingFeature` + `api.setGroupBy()` |\n| `dataSource` (local / remote) | `data` array or `externalSort/Filter` |\n| `pageable` | `showPagination` |\n| Kendo themes (Default / Bootstrap) | `--sg-*` tokens / Tailwind |\n| Grid events (`change`, `dataBound`) | `onCellValueChange`, `onApiReady`, ... |\n\n## Shape of the change\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- $('#grid').kendoGrid({\n- dataSource: { data: rows, pageSize: 25 },\n- sortable: true, filterable: true, pageable: true, editable: true,\n- columns: [\n- { field: 'name', title: 'Name' },\n- { field: 'amount', title: 'Amount', format: '{0:c}' },\n- ],\n- })\n\n+ <SvGrid\n+ data={rows}\n+ columns={[\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]}\n+ features={tableFeatures({ rowSortingFeature, columnFilteringFeature })}\n+ showPagination enableInlineEditing />\n```\n\n## Why teams switch\n\n- **Svelte 5 native** instead of a jQuery / multi-framework suite.\n- **MIT community core** - no per-developer license for the grid itself.\n- **Paid support at a fraction of enterprise-suite pricing.**\n- **No design-system lock-in** - theme via `--sg-*` tokens.\n\n## What to weigh\n\n- Kendo bundles a **huge component suite** (charts, scheduler, editor)\n and decades of vendor support. If you need the whole suite across\n several frameworks, that has real value.\n\n## Frequently asked questions\n\n### Is SvGrid a cheaper alternative to Kendo UI Grid?\n\nFor a Svelte stack, yes: the `@svgrid/grid` core is MIT (free, including\ncommercial use), and the paid `@svgrid/enterprise` tier is a fraction of enterprise\ncomponent-suite pricing.\n\n### How long does a Kendo Grid migration take?\n\nAbout 3-6 hours per grid. It is a column / event rename pass plus re-theming;\nthe columns and editing concepts map closely.\n\n### Does SvGrid match Kendo's feature set?\n\nFor the grid itself it covers the common enterprise surface - sorting,\nExcel-style filters, grouping, virtualization, editing, master/detail, tree.\nKendo's value beyond that is the wider suite and multi-framework parity.\n\n## What you end up with\n\nSorting, filtering, grouping and editing, with the column menu Kendo users expect.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} groupBy={['department']} groupable sortable filterable editable />\n```\n\n## See also\n\n- [SvGrid vs Kendo UI Grid](https://svgrid.com/compare/kendo-ui-grid/) - the side-by-side comparison\n- [Pricing](https://svgrid.com/pricing/) - the SvGrid Enterprise tiers\n- [Architecture](./architecture.md) - engine + render-component split\n"
6127
6127
  },
6128
6128
  {
6129
6129
  "slug": "help/migrating-from-mui-x",
6130
6130
  "path": "docs/help/migrating-from-mui-x.md",
6131
6131
  "title": "Migrating from MUI X DataGrid",
6132
6132
  "section": "Help",
6133
- "markdown": "# Migrating from MUI X DataGrid\n\nMUI X DataGrid is the most common starting point for teams already\non Material UI. Its MIT Community edition plus paid Pro and Premium\ntiers is a split similar to sv-grid's, except that column pinning,\nmaster/detail, tree data, row grouping, aggregation and cell selection\nare paid in MUI X and free here. The port is mostly mechanical.\n\n> Estimated effort: **1-3 hours** per grid, depending on how heavily\n> you've leant on `apiRef.current.*` calls.\n\n<!-- facts:start mui-x-datagrid -->\n> **Facts, checked 9 Nov 2026.** `@mui/x-data-grid` 9.17.0, MIT, last published 30 Oct 2026, 13,100,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026); `@mui/x-data-grid` 9.17.0 158.4 KB JS, no separate stylesheet, @emotion/react + @emotion/styled + @mui/material + @mui/system + react + react-dom external (measured 9 Nov 2026). MUI X DataGrid pricing, as its site states it: MUI X Community is free under MIT. mui.com lists Pro at $299 per year per developer, Premium at $599 per year per developer and Enterprise at $1,399 per year per developer, with perpetual and annual licence models (https://mui.com/pricing/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs MUI X DataGrid](https://svgrid.com/compare/mui-x-datagrid/).\n<!-- facts:end -->\n\n## Package map\n\n| MUI X | sv-grid |\n| ------------------------------------ | ---------------------------------------- |\n| `@mui/x-data-grid` | `@svgrid/grid` |\n| `@mui/x-data-grid-pro` | `@svgrid/enterprise` (export, import, pivot, AI) |\n| `@mui/x-data-grid-premium` | All of `@svgrid/enterprise` ships in one tier |\n\n## Imports\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- import { DataGrid, GridColDef, GridRowsProp } from '@mui/x-data-grid'\n\n+ import { SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef } from '@svgrid/grid'\n```\n\n## Column defs\n\n```diff\n- const columns: GridColDef[] = [\n- { field: 'id', headerName: 'ID', width: 90 },\n- { field: 'lastName', headerName: 'Last', width: 150, editable: true },\n- { field: 'age', headerName: 'Age', type: 'number', width: 110, editable: true },\n- ]\n\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'id', header: 'ID', width: 90 },\n+ { field: 'lastName', header: 'Last', width: 150 },\n+ { field: 'age', header: 'Age', width: 110, editorType: 'number' },\n+ ]\n```\n\n- `headerName` → `header`\n- `type: 'number'` → `editorType: 'number'`\n- `editable: true` → omit (every column is editable by default; set\n `editable: false` to OPT OUT)\n\n## Mounting\n\n```diff\n- <DataGrid rows={rows} columns={columns} pageSize={25} checkboxSelection />\n\n+ <SvGrid\n+ data={rows} columns={columns} features={features}\n+ showPagination={true} pageSize={25}\n+ selectionMode=\"row\" />\n```\n\n`tableFeatures({ rowSortingFeature, columnFilteringFeature,\nrowSelectionFeature })` registers what you'd implicitly get from\nMUI X.\n\n## `apiRef` translation\n\n| MUI X (`apiRef.current.*`) | sv-grid (`api.*`) |\n| -------------------------------------------- | ------------------------------------------ |\n| `setRows(rows)` | mutate the `$state` array you bound to `data` |\n| `updateRows([{id, ...patch}])` | `api.setCellValue(rowIndex, field, value)` |\n| `setSortModel([{field, sort}])` | `api.setSort(field, sort)` |\n| `setFilterModel({items: [...]})` | `api.setFilter(field, {operator, value})` |\n| `setPage(0)` / `setPageSize(50)` | Use the built-in pager; for headless control register `pageSize` prop |\n| `selectRow(id)` | Toggle the row checkbox via the wrapper's UI; programmatic select is `api.selectRows([id])` (`api.toggleRowSelected(id)` to flip one) |\n| `getSelectedRows()` | `api.getSelectedRows()` (ids via `api.getSelectedRowIds()`) |\n| `exportDataAsExcel()` | `api.exportData({ format: 'xlsx' })` (Enterprise) |\n| `setColumnVisibilityModel({field: false})` | `api.setColumnVisible('field', false)` |\n\n## Custom cells\n\n```diff\n- {\n- field: 'status',\n- renderCell: ({ row }) => <Chip label={row.status} color={row.status === 'active' ? 'success' : 'default'} />,\n- }\n\n+ {\n+ field: 'status',\n+ cell: (ctx) => renderSnippet(StatusChip, { status: ctx.row.original.status }),\n+ }\n```\n\n## Selection\n\n```diff\n- <DataGrid checkboxSelection\n- onRowSelectionModelChange={(ids) => setSelected(ids)} />\n\n+ <SvGrid\n+ {data} {columns} features={features}\n+ selectionMode=\"row\"\n+ onRowSelectionChange={(selection, rows) => setSelected(rows)} />\n```\n\n`selectionMode` values: `'row'` (the MUI X equivalent), `'cell'`\n(spreadsheet-style range), `'both'`, `'none'`.\n\n## Inline editing\n\nMUI X had `processRowUpdate(newRow, oldRow)` returning the new row.\nSv-grid's equivalent is `onCellValueChange`:\n\n```diff\n- <DataGrid processRowUpdate={async (newRow) => {\n- await api.savePatch(newRow)\n- return newRow\n- }} />\n\n+ <SvGrid\n+ onCellValueChange={async (e) => {\n+ await api.savePatch({ id: e.row.id, [e.columnId]: e.newValue })\n+ }}\n+ />\n```\n\nFor full-row editing (one Save button per row), see\n[Full-row editing](./editing/full-row.md).\n\n## Server-side data\n\nMUI X's `pagination + serverSideMode + filterMode='server'` maps to\nsv-grid's `externalSort + externalFilter`, or to `createServerDataSource` (free:\npaging or infinite scroll, sort, filter) when the server pages, and to the\nEnterprise `createServerRowModel` when it also groups; the demo below runs\nthe free controller against a fake API with sort, filter and infinite scroll:\n\n<div data-docs-demo=\"148-server-row-model\" data-height=\"520\"></div>\n\nMUI X's server-side row grouping and aggregation (Premium) map to the\nEnterprise row model, which loads each group level on expand and pages,\nedits and selects across rows the grid never fetched:\n\n<div data-docs-demo=\"467-server-row-model-1m\" data-height=\"600\"></div>\n\n```svelte\n<SvGrid\n data={rows} columns={columns} features={features}\n externalSort={true}\n externalFilter={true}\n onSortingChange={async (s) => { rows = await fetchPage({ sort: s }) }}\n onFiltersChange={async (f) => { rows = await fetchPage({ filters: f.columns }) }}\n/>\n```\n\n## Slots / customisation\n\nMUI X exposes a `slots` object. Sv-grid doesn't - instead, every\nvisual piece is a CSS custom property (`--sg-*`); see\n[design tokens](./tokens.md). Override at any DOM level:\n\n```css\n.grid-host { --sg-accent: #db2777; --sg-radius: 10px; }\n```\n\nRow height is the exception: it is the `rowHeight` prop rather than a\ntoken, because the virtualizer needs it as a number.\n\nFor full theme presets (Ant, MUI, Fluent, Base Web, shadcn) see\n[demo 74](https://svgrid.com/demos/74-theme-integrations/).\n\n## What you get for free vs MUI X\n\n- **No Emotion / no Material theme dependency.** The facts box at the\n top of the page has both packages measured the same way; the MUI X\n figure excludes React, Material UI, Emotion and the MUI system, which\n it needs and sv-grid does not.\n- **Pro and Premium features in the MIT core.** Column pinning, master/detail,\n tree data, row grouping, aggregation and cell selection carry Pro or\n Premium badges on mui.com; they are free here. Excel export and pivot\n are paid on both sides.\n- **In-grid AI helpers against your own model.** MUI X's AI assistant is a\n Premium feature that routes prompts through MUI's hosted service unless\n you build your own; sv-grid's natural-language filter, smart fill and\n summarise helpers are free and run against a provider you register.\n- **CSP-clean.** No `eval`.\n\n## What you give up\n\n- **The Material Design look out of the box.** Sv-grid ships\n unstyled-by-token; the [MUI preset in demo 74](https://svgrid.com/demos/74-theme-integrations/)\n is one drop-in.\n- **MUI form-field integration.** Bind directly to your own MUI\n inputs in custom cell components if you want them.\n- **The rest of MUI X in one design system.** Date pickers, charts and\n the tree view share MUI X's theme; sv-grid ships its own date and time\n editors and charts, themed through the same `--sg-*` tokens.\n- **A hosted AI assistant with starter credits.** Premium licence holders\n get MUI's service; sv-grid's helpers need a model provider you host or\n pay for yourself.\n\n## Frequently asked questions\n\n### How hard is it to migrate from MUI X DataGrid to SvGrid?\n\nMostly mechanical - typically 1-3 hours per grid, depending on how heavily you\nrelied on `apiRef.current.*`. The Community/Enterprise split mirrors MUI X's, so the\nlicensing mental model carries over directly.\n\n### Can SvGrid keep the Material Design look?\n\nYes. SvGrid ships unstyled-by-token and re-themes through `--sg-*` CSS\nvariables; the MUI preset in demo 74 is a drop-in starting point. You can also\nbind your own MUI inputs inside custom cell components.\n\n### Is SvGrid cheaper than MUI X Pro/Premium?\n\nSvGrid's Community tier is MIT and free for commercial use, and `@svgrid/enterprise`\nis priced per developer ($599 for the grid, $999 with the spreadsheet and\nStudio, both covering unlimited apps). MUI X Pro and\nPremium are also per developer per year; the prices mui.com listed on the\ndate we read it are in the facts box at the top of this page. The difference\nis what the free tier holds: most of what MUI X sells in Pro and Premium is\nin SvGrid's MIT core, so compare feature needs before prices on the\n[pricing page](https://svgrid.com/pricing/).\n\n## What you end up with\n\nSorting, filtering, pagination and inline editing - the MUI X DataGrid feature set.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable editable pageable pageSize={3} />\n```\n\n## See also\n\n- [SvGrid vs MUI X DataGrid](https://svgrid.com/compare/mui-x-datagrid/) - the side-by-side comparison, with a source and date for every claim\n- [Server-side data](./server-side-data.md) - the row model the demo above uses\n- [AI assistant](./ai.md) - the free in-grid helpers\n- [Migrating from AG Grid](./migrating-from-ag-grid.md)\n- [Migrating from TanStack Table](./migrating-from-tanstack-table.md)\n- [Design tokens](./tokens.md)\n"
6133
+ "markdown": "# Migrating from MUI X DataGrid\n\nMUI X DataGrid is the most common starting point for teams already\non Material UI. Its MIT Community edition plus paid Pro and Premium\ntiers is a split similar to sv-grid's, except that column pinning,\nmaster/detail, tree data, row grouping, aggregation and cell selection\nare paid in MUI X and free here. The port is mostly mechanical.\n\n> Estimated effort: **1-3 hours** per grid, depending on how heavily\n> you've leant on `apiRef.current.*` calls.\n\n<!-- facts:start mui-x-datagrid -->\n> **Facts, checked 9 Nov 2026.** `@mui/x-data-grid` 9.17.0, MIT, last published 30 Oct 2026, 13,100,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026); `@mui/x-data-grid` 9.17.0 158.4 KB JS, no separate stylesheet, @emotion/react + @emotion/styled + @mui/material + @mui/system + react + react-dom external (measured 9 Nov 2026). MUI X DataGrid pricing, as its site states it: MUI X Community is free under MIT. mui.com lists Pro at $299 per year per developer, Premium at $599 per year per developer and Enterprise at $1,399 per year per developer, with perpetual and annual licence models (https://mui.com/pricing/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs MUI X DataGrid](https://svgrid.com/compare/mui-x-datagrid/).\n<!-- facts:end -->\n\n## Package map\n\n| MUI X | sv-grid |\n| ------------------------------------ | ---------------------------------------- |\n| `@mui/x-data-grid` | `@svgrid/grid` |\n| `@mui/x-data-grid-pro` | `@svgrid/enterprise` (export, import, pivot, AI) |\n| `@mui/x-data-grid-premium` | All of `@svgrid/enterprise` ships in one tier |\n\n## Imports\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- import { DataGrid, GridColDef, GridRowsProp } from '@mui/x-data-grid'\n\n+ import { SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef } from '@svgrid/grid'\n```\n\n## Column defs\n\n```diff\n- const columns: GridColDef[] = [\n- { field: 'id', headerName: 'ID', width: 90 },\n- { field: 'lastName', headerName: 'Last', width: 150, editable: true },\n- { field: 'age', headerName: 'Age', type: 'number', width: 110, editable: true },\n- ]\n\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'id', header: 'ID', width: 90 },\n+ { field: 'lastName', header: 'Last', width: 150 },\n+ { field: 'age', header: 'Age', width: 110, editorType: 'number' },\n+ ]\n```\n\n- `headerName` → `header`\n- `type: 'number'` → `editorType: 'number'`\n- `editable: true` → omit (every column is editable by default; set\n `editable: false` to OPT OUT)\n\n## Mounting\n\n```diff\n- <DataGrid rows={rows} columns={columns} pageSize={25} checkboxSelection />\n\n+ <SvGrid\n+ data={rows} columns={columns} features={features}\n+ showPagination={true} pageSize={25}\n+ selectionMode=\"row\" />\n```\n\n`tableFeatures({ rowSortingFeature, columnFilteringFeature,\nrowSelectionFeature })` registers what you'd implicitly get from\nMUI X.\n\n## `apiRef` translation\n\n| MUI X (`apiRef.current.*`) | sv-grid (`api.*`) |\n| -------------------------------------------- | ------------------------------------------ |\n| `setRows(rows)` | mutate the `$state` array you bound to `data` |\n| `updateRows([{id, ...patch}])` | `api.setCellValue(rowIndex, field, value)` |\n| `setSortModel([{field, sort}])` | `api.setSort(field, sort)` |\n| `setFilterModel({items: [...]})` | `api.setFilter(field, {operator, value})` |\n| `setPage(0)` / `setPageSize(50)` | Use the built-in pager; for headless control register `pageSize` prop |\n| `selectRow(id)` | Toggle the row checkbox via the wrapper's UI; programmatic select is `api.selectRows([id])` (`api.toggleRowSelected(id)` to flip one) |\n| `getSelectedRows()` | `api.getSelectedRows()` (ids via `api.getSelectedRowIds()`) |\n| `exportDataAsExcel()` | `api.exportData({ format: 'xlsx' })` (Enterprise) |\n| `setColumnVisibilityModel({field: false})` | `api.setColumnVisible('field', false)` |\n\n## Custom cells\n\n```diff\n- {\n- field: 'status',\n- renderCell: ({ row }) => <Chip label={row.status} color={row.status === 'active' ? 'success' : 'default'} />,\n- }\n\n+ {\n+ field: 'status',\n+ cell: (ctx) => renderSnippet(StatusChip, { status: ctx.row.original.status }),\n+ }\n```\n\n## Selection\n\n```diff\n- <DataGrid checkboxSelection\n- onRowSelectionModelChange={(ids) => setSelected(ids)} />\n\n+ <SvGrid\n+ {data} {columns} features={features}\n+ selectionMode=\"row\"\n+ onRowSelectionChange={(selection, rows) => setSelected(rows)} />\n```\n\n`selectionMode` values: `'row'` (the MUI X equivalent), `'cell'`\n(spreadsheet-style range), `'both'`, `'none'`.\n\n## Inline editing\n\nMUI X had `processRowUpdate(newRow, oldRow)` returning the new row.\nSv-grid's equivalent is `onCellValueChange`:\n\n```diff\n- <DataGrid processRowUpdate={async (newRow) => {\n- await api.savePatch(newRow)\n- return newRow\n- }} />\n\n+ <SvGrid\n+ onCellValueChange={async (e) => {\n+ await api.savePatch({ id: e.row.id, [e.columnId]: e.newValue })\n+ }}\n+ />\n```\n\nFor full-row editing (one Save button per row), see\n[Full-row editing](./editing/full-row.md).\n\n## Server-side data\n\nMUI X's `pagination + serverSideMode + filterMode='server'` maps to\nsv-grid's `externalSort + externalFilter`, or to `createServerDataSource` (free:\npaging or infinite scroll, sort, filter) when the server pages, and to the\nEnterprise `createServerRowModel` when it also groups; the demo below runs\nthe free controller against a fake API with sort, filter and infinite scroll:\n\n<div data-docs-demo=\"148-server-row-model\" data-height=\"520\"></div>\n\nMUI X's server-side row grouping and aggregation (Premium) map to the\nEnterprise row model, which loads each group level on expand and pages,\nedits and selects across rows the grid never fetched:\n\n<div data-docs-demo=\"467-server-row-model-1m\" data-height=\"600\"></div>\n\n```svelte\n<SvGrid\n data={rows} columns={columns} features={features}\n externalSort={true}\n externalFilter={true}\n onSortingChange={async (s) => { rows = await fetchPage({ sort: s }) }}\n onFiltersChange={async (f) => { rows = await fetchPage({ filters: f.columns }) }}\n/>\n```\n\n## Slots / customisation\n\nMUI X exposes a `slots` object. Sv-grid doesn't - instead, every\nvisual piece is a CSS custom property (`--sg-*`); see\n[design tokens](./tokens.md). Override at any DOM level:\n\n```css\n.grid-host { --sg-accent: #db2777; --sg-radius: 10px; }\n```\n\nRow height is the exception: it is the `rowHeight` prop rather than a\ntoken, because the virtualizer needs it as a number.\n\nFor full theme presets (Ant, MUI, Fluent, Base Web, shadcn) see\n[demo 74](https://svgrid.com/demos/74-theme-integrations/).\n\n## What you get for free vs MUI X\n\n- **No Emotion / no Material theme dependency.** The facts box at the\n top of the page has both packages measured the same way; the MUI X\n figure excludes React, Material UI, Emotion and the MUI system, which\n it needs and sv-grid does not.\n- **Pro and Premium features in the MIT core.** Column pinning, master/detail,\n tree data, row grouping, aggregation and cell selection carry Pro or\n Premium badges on mui.com; they are free here. Excel export and pivot\n are paid on both sides.\n- **In-grid AI helpers against your own model.** MUI X's AI assistant is a\n Premium feature that routes prompts through MUI's hosted service unless\n you build your own; sv-grid's natural-language filter, smart fill and\n summarise helpers are free and run against a provider you register.\n- **CSP-clean.** No `eval`.\n\n## What you give up\n\n- **The Material Design look out of the box.** Sv-grid ships\n unstyled-by-token; the [MUI preset in demo 74](https://svgrid.com/demos/74-theme-integrations/)\n is one drop-in.\n- **MUI form-field integration.** Bind directly to your own MUI\n inputs in custom cell components if you want them.\n- **The rest of MUI X in one design system.** Date pickers, charts and\n the tree view share MUI X's theme; sv-grid ships its own date and time\n editors and charts, themed through the same `--sg-*` tokens.\n- **A hosted AI assistant with starter credits.** Premium licence holders\n get MUI's service; sv-grid's helpers need a model provider you host or\n pay for yourself.\n\n## Frequently asked questions\n\n### How hard is it to migrate from MUI X DataGrid to SvGrid?\n\nMostly mechanical - typically 1-3 hours per grid, depending on how heavily you\nrelied on `apiRef.current.*`. The Community/Enterprise split mirrors MUI X's, so the\nlicensing mental model carries over directly.\n\n### Can SvGrid keep the Material Design look?\n\nYes. SvGrid ships unstyled-by-token and re-themes through `--sg-*` CSS\nvariables; the MUI preset in demo 74 is a drop-in starting point. You can also\nbind your own MUI inputs inside custom cell components.\n\n### Is SvGrid cheaper than MUI X Pro/Premium?\n\nSvGrid's Community tier is MIT and free for commercial use, and `@svgrid/enterprise`\nis priced per developer ($599 for the grid, $999 with the spreadsheet and\nStudio, both covering unlimited apps). MUI X Pro and\nPremium are also per developer per year; the prices mui.com listed on the\ndate we read it are in the facts box at the top of this page. The difference\nis what the free tier holds: most of what MUI X sells in Pro and Premium is\nin SvGrid's MIT core, so compare feature needs before prices on the\n[pricing page](https://svgrid.com/pricing/).\n\n## What you end up with\n\nSorting, filtering, pagination and inline editing - the MUI X DataGrid feature set.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable editable pageable pageSize={3} />\n```\n\n## See also\n\n- [SvGrid vs MUI X DataGrid](https://svgrid.com/compare/mui-x-datagrid/) - the side-by-side comparison, with a source and date for every claim\n- [Server-side data](./server-side-data.md) - the row model the demo above uses\n- [AI assistant](./ai.md) - the free in-grid helpers\n- [Migrating from AG Grid](./migrating-from-ag-grid.md)\n- [Migrating from TanStack Table](./migrating-from-tanstack-table.md)\n- [Design tokens](./tokens.md)\n"
6134
6134
  },
6135
6135
  {
6136
6136
  "slug": "help/migrating-from-nocodb",
@@ -6144,77 +6144,77 @@ export const docs = [
6144
6144
  "path": "docs/help/migrating-from-primevue-datatable.md",
6145
6145
  "title": "Migrating from PrimeVue / PrimeNG / PrimeReact DataTable",
6146
6146
  "section": "Help",
6147
- "markdown": "\n# Migrating from PrimeVue / PrimeNG / PrimeReact DataTable\n\nThe Prime DataTable is the grid in the Prime UI suites for Vue, Angular,\nand React. Its columns are declared as `<Column>` children with `field`\n/ `header` props - a shape that maps cleanly onto SvGrid's `ColumnDef`\narray. The port is mostly translating columns and events into a Svelte 5\ncomponent. Since PrimeVue 5 the package ships under the PrimeUI licence\nrather than MIT: free for individuals and small organisations under the\nlimits in its licence file, per developer with a licence key otherwise.\nThe facts box below quotes the terms as read on the date shown.\n\n> Estimated effort: **2-4 hours** per grid.\n\n<!-- facts:start primevue-datatable -->\n> **Facts, checked 9 Nov 2026.** `primevue` 5.0.4, Commercial (see licence file), last published 22 Oct 2026, 3,290,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026). PrimeVue / PrimeNG / PrimeReact DataTable pricing, as its site states it: primeui.dev lists the Commercial Suite at a launch price of $599 per developer (standard $799) as a perpetual licence with one year of updates, renewable at $399 per developer per year; the Community License is free for individuals, non-profits and organisations under $1M revenue, fewer than five developers, fewer than ten employees and under $3M in venture funding (https://primeui.dev/pricing, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs PrimeVue / PrimeNG / PrimeReact DataTable](https://svgrid.com/compare/primevue-datatable/).\n<!-- facts:end -->\n\n## Vocabulary cheat sheet\n\n| Prime DataTable | sv-grid |\n| ---------------------------------------- | ----------------------------------------- |\n| `<DataTable :value=\"rows\">` | `<SvGrid data={rows}>` |\n| `<Column field=\"name\" header=\"Name\" />` | `{ field: 'name', header: 'Name' }` |\n| `sortable` | `rowSortingFeature` |\n| `:filters` / filter display | `columnFilteringFeature` |\n| `<template #body>` cell slot | `cell: (c) => renderSnippet(...)` |\n| `editMode` + cell editor template | `editorType` (+ custom `cellEditor`) |\n| `:expandedRows` / row expansion | `rowExpandingFeature` |\n| `lazy` + `@page` / `@sort` / `@filter` | `externalSort` / `externalFilter` + events |\n| `paginator` + `:rows` | `showPagination` (+ page size) |\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- <DataTable :value=\"rows\" paginator :rows=\"25\" sortMode=\"multiple\">\n- <Column field=\"name\" header=\"Name\" sortable />\n- <Column field=\"amount\" header=\"Amount\" sortable>\n- <template #body=\"{ data }\">{{ fmt(data.amount) }}</template>\n- </Column>\n- </DataTable>\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} showPagination />\n```\n\n## What changes\n\n- **`<Column>` children → a `ColumnDef[]` array.**\n- **`#body` slots → `cell` snippets** via `renderSnippet`.\n- **Prime theming → `--sg-*` tokens / Tailwind** - no Prime theme\n dependency.\n- **`lazy` → `externalSort` / `externalFilter`** with refetch on events.\n\n## Frequently asked questions\n\n### How do Prime `<Column>` definitions map to SvGrid?\n\nEach `<Column field header />` becomes a `{ field, header }` object in SvGrid's\n`columns` array, and `#body` templates become `renderSnippet` cells. Sorting and\nfiltering move from per-column props to the `rowSortingFeature` /\n`columnFilteringFeature` registration.\n\n### Is SvGrid open-source like the Prime grid core?\n\n`@svgrid/grid` is MIT with no licence key or eligibility conditions. The\nPrime cores were MIT through PrimeVue 4; from PrimeVue 5 the npm package\ncarries the PrimeUI licence, whose free Community License depends on your\nrevenue, developer count, headcount and funding, and whose Commercial\nLicense is per developer with a key. The other difference is framework:\nSvGrid is Svelte 5, not Vue / Angular / React.\n\n### Do I lose Prime theming?\n\nYou re-create the look with `--sg-*` tokens (optionally driven by your Tailwind\ntheme), so the grid matches your design system without a Prime theme dependency.\n\n## What you end up with\n\nSorting, filtering, pagination and row selection in one pass.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable pageable pageSize={3} selectable />\n```\n\n## See also\n\n- [SvGrid vs Prime DataTable](https://svgrid.com/compare/primevue-datatable/) - the side-by-side comparison\n- [Tailwind integration](./tailwind.md) - match your design system\n- [Cell components](./cells/cell-components.md) - snippet cells + editors\n"
6147
+ "markdown": "\n# Migrating from PrimeVue / PrimeNG / PrimeReact DataTable\n\nThe Prime DataTable is the grid in the Prime UI suites for Vue, Angular,\nand React. Its columns are declared as `<Column>` children with `field`\n/ `header` props - a shape that maps cleanly onto SvGrid's `ColumnDef`\narray. The port is mostly translating columns and events into a Svelte 5\ncomponent. Since PrimeVue 5 the package ships under the PrimeUI licence\nrather than MIT: free for individuals and small organisations under the\nlimits in its licence file, per developer with a licence key otherwise.\nThe facts box below quotes the terms as read on the date shown.\n\n> Estimated effort: **2-4 hours** per grid.\n\n<!-- facts:start primevue-datatable -->\n> **Facts, checked 9 Nov 2026.** `primevue` 5.0.4, Commercial (see licence file), last published 22 Oct 2026, 3,290,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026). PrimeVue / PrimeNG / PrimeReact DataTable pricing, as its site states it: primeui.dev lists the Commercial Suite at a launch price of $599 per developer (standard $799) as a perpetual licence with one year of updates, renewable at $399 per developer per year; the Community License is free for individuals, non-profits and organisations under $1M revenue, fewer than five developers, fewer than ten employees and under $3M in venture funding (https://primeui.dev/pricing, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs PrimeVue / PrimeNG / PrimeReact DataTable](https://svgrid.com/compare/primevue-datatable/).\n<!-- facts:end -->\n\n## Vocabulary cheat sheet\n\n| Prime DataTable | sv-grid |\n| ---------------------------------------- | ----------------------------------------- |\n| `<DataTable :value=\"rows\">` | `<SvGrid data={rows}>` |\n| `<Column field=\"name\" header=\"Name\" />` | `{ field: 'name', header: 'Name' }` |\n| `sortable` | `rowSortingFeature` |\n| `:filters` / filter display | `columnFilteringFeature` |\n| `<template #body>` cell slot | `cell: (c) => renderSnippet(...)` |\n| `editMode` + cell editor template | `editorType` (+ custom `cellEditor`) |\n| `:expandedRows` / row expansion | `rowExpandingFeature` |\n| `lazy` + `@page` / `@sort` / `@filter` | `externalSort` / `externalFilter` + events |\n| `paginator` + `:rows` | `showPagination` (+ page size) |\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- <DataTable :value=\"rows\" paginator :rows=\"25\" sortMode=\"multiple\">\n- <Column field=\"name\" header=\"Name\" sortable />\n- <Column field=\"amount\" header=\"Amount\" sortable>\n- <template #body=\"{ data }\">{{ fmt(data.amount) }}</template>\n- </Column>\n- </DataTable>\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} showPagination />\n```\n\n## What changes\n\n- **`<Column>` children → a `ColumnDef[]` array.**\n- **`#body` slots → `cell` snippets** via `renderSnippet`.\n- **Prime theming → `--sg-*` tokens / Tailwind** - no Prime theme\n dependency.\n- **`lazy` → `externalSort` / `externalFilter`** with refetch on events.\n\n## Frequently asked questions\n\n### How do Prime `<Column>` definitions map to SvGrid?\n\nEach `<Column field header />` becomes a `{ field, header }` object in SvGrid's\n`columns` array, and `#body` templates become `renderSnippet` cells. Sorting and\nfiltering move from per-column props to the `rowSortingFeature` /\n`columnFilteringFeature` registration.\n\n### Is SvGrid open-source like the Prime grid core?\n\n`@svgrid/grid` is MIT with no licence key or eligibility conditions. The\nPrime cores were MIT through PrimeVue 4; from PrimeVue 5 the npm package\ncarries the PrimeUI licence, whose free Community License depends on your\nrevenue, developer count, headcount and funding, and whose Commercial\nLicense is per developer with a key. The other difference is framework:\nSvGrid is Svelte 5, not Vue / Angular / React.\n\n### Do I lose Prime theming?\n\nYou re-create the look with `--sg-*` tokens (optionally driven by your Tailwind\ntheme), so the grid matches your design system without a Prime theme dependency.\n\n## What you end up with\n\nSorting, filtering, pagination and row selection in one pass.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable pageable pageSize={3} selectable />\n```\n\n## See also\n\n- [SvGrid vs Prime DataTable](https://svgrid.com/compare/primevue-datatable/) - the side-by-side comparison\n- [Tailwind integration](./tailwind.md) - match your design system\n- [Cell components](./cells/cell-components.md) - snippet cells + editors\n"
6148
6148
  },
6149
6149
  {
6150
6150
  "slug": "help/migrating-from-react-data-grid",
6151
6151
  "path": "docs/help/migrating-from-react-data-grid.md",
6152
6152
  "title": "Migrating from React Data Grid (adazzle)",
6153
6153
  "section": "Help",
6154
- "markdown": "# Migrating from React Data Grid (adazzle)\n\n`react-data-grid` is a fast, Excel-like React grid with a clean column\nAPI. SvGrid mirrors its shape - virtualized DOM, typed columns, inline\nediting, custom cells - on Svelte 5 runes instead of React, so the port\nis mostly a column rename pass.\n\n> Estimated effort: **2-4 hours** per grid, more if you lean on custom\n> editors.\n\n<!-- facts:start react-data-grid -->\n> **Facts, checked 9 Nov 2026.** `react-data-grid` 7.0.0-beta.64, MIT, last published 5 Nov 2026, 2,650,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026); `react-data-grid` 7.0.0-beta.64 25.6 KB JS + 2.3 KB CSS, react + react-dom external (measured 9 Nov 2026). React Data Grid pricing, as its site states it: react-data-grid is MIT on npm and free; no licence is sold (https://github.com/adazzle/react-data-grid, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs React Data Grid (adazzle)](https://svgrid.com/compare/react-data-grid/).\n<!-- facts:end -->\n\n## Vocabulary cheat sheet\n\n| react-data-grid | sv-grid |\n| ---------------------------------------- | ----------------------------------------- |\n| `<DataGrid columns rows />` | `<SvGrid columns data />` |\n| `{ key: 'name', name: 'Name' }` | `{ field: 'name', header: 'Name' }` |\n| `renderCell: (p) => <Badge .../>` | `cell: (c) => renderSnippet(Badge, {...})` |\n| `renderEditCell` / `editor` | `editorType` (+ custom `cellEditor`) |\n| `rowKeyGetter={(r) => r.id}` | `getRowId={(r) => r.id}` |\n| `onRowsChange={setRows}` | `onCellValueChange` (+ your state) |\n| `sortColumns` / `onSortColumnsChange` | `rowSortingFeature` + `onSortingChange` |\n| `<DataGrid className=...>` theming | `--sg-*` tokens / Tailwind |\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- import DataGrid, { textEditor } from 'react-data-grid'\n- const columns = [\n- { key: 'name', name: 'Name' },\n- { key: 'amount', name: 'Amount', renderEditCell: textEditor },\n- ]\n- <DataGrid columns={columns} rows={rows} rowKeyGetter={(r) => r.id} onRowsChange={setRows} />\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', editorType: 'text' },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features}\n+ getRowId={(r) => r.id} enableInlineEditing\n+ onCellValueChange={(e) => save(e)} />\n```\n\n## What changes\n\n- **React → Svelte 5.** `renderCell` / `renderEditCell` become\n `renderSnippet` snippets and `editorType`.\n- **`onRowsChange` → `onCellValueChange`.** SvGrid writes to its own\n working copy; subscribe to commits and persist where you like.\n- **Filtering UI is built in.** react-data-grid leaves the filter row to\n you; SvGrid ships the Excel-style menu.\n\n## Frequently asked questions\n\n### How do react-data-grid columns map to SvGrid?\n\n`key` becomes `field`, `name` becomes `header`, `renderCell` becomes a\n`renderSnippet` cell, and editors map to `editorType` (or a custom `cellEditor`\nsnippet). `rowKeyGetter` becomes `getRowId`.\n\n### Is SvGrid free like react-data-grid?\n\nYes - `@svgrid/grid` is MIT-licensed, like react-data-grid. SvGrid adds an\noptional paid Enterprise pack for export, import, pivot, and AI.\n\n### Does SvGrid have built-in filtering?\n\nYes. react-data-grid asks you to build the filter UI; SvGrid ships an\nExcel-style column filter menu and a global filter out of the box.\n\n## What you end up with\n\nInline editing with cell-range selection, which is the reason most people picked it.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} editable enableCellSelection sortable />\n```\n\n## See also\n\n- [SvGrid vs React Data Grid](https://svgrid.com/compare/react-data-grid/) - the side-by-side comparison\n- [Migrating from TanStack Table](./migrating-from-tanstack-table.md) - sibling React-to-Svelte guide\n- [Cell components](./cells/cell-components.md) - custom cells + editors\n"
6154
+ "markdown": "# Migrating from React Data Grid (adazzle)\n\n`react-data-grid` is a fast, Excel-like React grid with a clean column\nAPI. SvGrid mirrors its shape - virtualized DOM, typed columns, inline\nediting, custom cells - on Svelte 5 runes instead of React, so the port\nis mostly a column rename pass.\n\n> Estimated effort: **2-4 hours** per grid, more if you lean on custom\n> editors.\n\n<!-- facts:start react-data-grid -->\n> **Facts, checked 9 Nov 2026.** `react-data-grid` 7.0.0-beta.64, MIT, last published 5 Nov 2026, 2,650,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026); `react-data-grid` 7.0.0-beta.64 25.6 KB JS + 2.3 KB CSS, react + react-dom external (measured 9 Nov 2026). React Data Grid pricing, as its site states it: react-data-grid is MIT on npm and free; no licence is sold (https://github.com/adazzle/react-data-grid, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs React Data Grid (adazzle)](https://svgrid.com/compare/react-data-grid/).\n<!-- facts:end -->\n\n## Vocabulary cheat sheet\n\n| react-data-grid | sv-grid |\n| ---------------------------------------- | ----------------------------------------- |\n| `<DataGrid columns rows />` | `<SvGrid columns data />` |\n| `{ key: 'name', name: 'Name' }` | `{ field: 'name', header: 'Name' }` |\n| `renderCell: (p) => <Badge .../>` | `cell: (c) => renderSnippet(Badge, {...})` |\n| `renderEditCell` / `editor` | `editorType` (+ custom `cellEditor`) |\n| `rowKeyGetter={(r) => r.id}` | `getRowId={(r) => r.id}` |\n| `onRowsChange={setRows}` | `onCellValueChange` (+ your state) |\n| `sortColumns` / `onSortColumnsChange` | `rowSortingFeature` + `onSortingChange` |\n| `<DataGrid className=...>` theming | `--sg-*` tokens / Tailwind |\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- import DataGrid, { textEditor } from 'react-data-grid'\n- const columns = [\n- { key: 'name', name: 'Name' },\n- { key: 'amount', name: 'Amount', renderEditCell: textEditor },\n- ]\n- <DataGrid columns={columns} rows={rows} rowKeyGetter={(r) => r.id} onRowsChange={setRows} />\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', editorType: 'text' },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features}\n+ getRowId={(r) => r.id} enableInlineEditing\n+ onCellValueChange={(e) => save(e)} />\n```\n\n## What changes\n\n- **React → Svelte 5.** `renderCell` / `renderEditCell` become\n `renderSnippet` snippets and `editorType`.\n- **`onRowsChange` → `onCellValueChange`.** SvGrid writes to its own\n working copy; subscribe to commits and persist where you like.\n- **Filtering UI is built in.** react-data-grid leaves the filter row to\n you; SvGrid ships the Excel-style menu.\n\n## Frequently asked questions\n\n### How do react-data-grid columns map to SvGrid?\n\n`key` becomes `field`, `name` becomes `header`, `renderCell` becomes a\n`renderSnippet` cell, and editors map to `editorType` (or a custom `cellEditor`\nsnippet). `rowKeyGetter` becomes `getRowId`.\n\n### Is SvGrid free like react-data-grid?\n\nYes - `@svgrid/grid` is MIT-licensed, like react-data-grid. SvGrid adds an\noptional paid Enterprise pack for export, import, pivot, and AI.\n\n### Does SvGrid have built-in filtering?\n\nYes. react-data-grid asks you to build the filter UI; SvGrid ships an\nExcel-style column filter menu and a global filter out of the box.\n\n## What you end up with\n\nInline editing with cell-range selection, which is the reason most people picked it.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} editable enableCellSelection sortable />\n```\n\n## See also\n\n- [SvGrid vs React Data Grid](https://svgrid.com/compare/react-data-grid/) - the side-by-side comparison\n- [Migrating from TanStack Table](./migrating-from-tanstack-table.md) - sibling React-to-Svelte guide\n- [Cell components](./cells/cell-components.md) - custom cells + editors\n"
6155
6155
  },
6156
6156
  {
6157
6157
  "slug": "help/migrating-from-shadcn-data-table",
6158
6158
  "path": "docs/help/migrating-from-shadcn-data-table.md",
6159
6159
  "title": "Migrating from the shadcn-svelte data table",
6160
6160
  "section": "Help",
6161
- "markdown": "# Migrating from the shadcn-svelte data table\n\nThe shadcn-svelte **Data Table** is not the same thing as its `<Table>`\ncomponent. `<Table>` is presentation only. The data table is a recipe\nbuilt on TanStack Table v9 that you copy into your own repo: it already\ndoes sorting, filtering, pagination, row selection, and column\nvisibility. If that is what you have, this is your page. If you have the\nplain styled `<Table>` and hand-wrote the sorting yourself, read\n[Migrating from a UI-kit table](./migrating-from-ui-kit-tables.md)\ninstead.\n\n> Estimated effort: **20-40 min** per table. Your column definitions and\n> your feature registration carry over almost unchanged. Most of the work\n> is deleting files.\n\n<!-- facts:start tanstack-table,svelte-ui-kit-tables -->\n> **Facts, checked 9 Nov 2026.** `@tanstack/svelte-table` 9.3.1, MIT, last published 12 Oct 2026, 539,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026); `@tanstack/svelte-table` 9.3.1 36.5 KB JS, no separate stylesheet, svelte external (measured 9 Nov 2026). TanStack Table pricing, as its site states it: TanStack Table is MIT and free; tanstack.com is sponsor-supported and offers Enterprise Support as private consulting and expert support, with no licence sold for the table (https://tanstack.com/table/latest, read 12 Sep 2026). Flowbite / Skeleton / shadcn-svelte tables pricing, as its site states it: Flowbite Svelte, Skeleton and shadcn-svelte are MIT component libraries; their table components are free and no grid licence is sold (https://github.com/themesberg/flowbite-svelte, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs TanStack Table (Svelte)](https://svgrid.com/compare/tanstack-table/), [SvGrid vs Flowbite / Skeleton / shadcn-svelte tables](https://svgrid.com/compare/svelte-ui-kit-tables/).\n<!-- facts:end -->\n\n## Why this port is small\n\nSvGrid speaks the same vocabulary TanStack Table v9 introduced. These are\nreal exports from `@svgrid/grid`, not lookalikes:\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```ts\nimport {\n tableFeatures,\n rowSortingFeature,\n columnFilteringFeature,\n rowPaginationFeature,\n rowSelectionFeature,\n rowExpandingFeature,\n columnGroupingFeature,\n} from '@svgrid/grid'\n```\n\nSo `data-table-features.ts` moves over as-is, and `columns.ts` keeps its\nshape. What does not move is the rendering scaffolding, because SvGrid\nships a renderer and there is nothing to translate it into.\n\n## What happens to each file\n\nThe shadcn recipe generates seven files. Five of them stop existing.\n\n| Their file | Becomes |\n| --- | --- |\n| `data-table-features.ts` | Kept. Same `tableFeatures({...})` call. |\n| `columns.ts` | Kept, minus the `header` render helpers. `{ accessorKey: 'email' }` becomes `{ field: 'email' }`. |\n| `data-table.svelte` | Deleted. It is `<table>` markup over `getHeaderGroups()` / `getRowModel()`, which `<SvGrid>` does. |\n| `data-table-checkbox.svelte` | Deleted. `showRowSelection` renders the column and the select-all header. |\n| `data-table-email-button.svelte` | Deleted. `sortable` makes every header a sort toggle. |\n| `data-table-actions.svelte` | Kept if you want it, as a cell snippet. |\n| `+page.svelte` | Kept. It now renders one component instead of wiring state. |\n\n## Let the codemod do the mechanical part\n\n```bash\nnpx @svgrid/migrate src/routes/payments # preview\nnpx @svgrid/migrate src/routes/payments --write # apply\n```\n\nIt previews by default and only writes with `--write`. Point it at the whole\nroute directory rather than a single file: the shadcn layout keeps `features`\nin its own module, and the codemod follows that import to work out which\nprops the component needs.\n\nIt renames the column keys, re-points the imports, strips the features SvGrid\ndoes not have, and deletes the markup along with the `$state` / `onXChange`\npairs. Custom `cell` and `header` render functions are kept and reported, never\nguessed at. Run your type-checker afterwards - the markup is regenerated rather\nthan edited.\n\n## Before and after\n\n```diff\n- <script lang=\"ts\">\n- import { createSvelteTable, FlexRender } from '$lib/components/ui/data-table'\n- import { columns } from './columns'\n- import { features } from './data-table-features'\n-\n- let sorting = $state([])\n- let filters = $state([])\n- let selection = $state({})\n- let pagination = $state({ pageIndex: 0, pageSize: 10 })\n-\n- const table = createSvelteTable({\n- get data() { return data },\n- columns, features,\n- state: { get sorting() { return sorting }, /* ...and three more... */ },\n- onSortingChange: (u) => (sorting = typeof u === 'function' ? u(sorting) : u),\n- // ...one of these per piece of state...\n- })\n- </script>\n-\n- <Table.Root>\n- <Table.Header>\n- {#each table.getHeaderGroups() as headerGroup}\n- <!-- ...twenty more lines of markup... -->\n- {/each}\n- </Table.Header>\n- <Table.Body>\n- {#each table.getRowModel().rows as row}\n- <!-- ...and twenty more... -->\n- {/each}\n- </Table.Body>\n- </Table.Root>\n\n+ <script lang=\"ts\">\n+ import { SvGrid } from '@svgrid/grid'\n+ import '@svgrid/grid/themes/shadcn.css'\n+ import { columns } from './columns'\n+ import { features } from './data-table-features'\n+ </script>\n+\n+ <SvGrid\n+ {data} {columns} {features}\n+ sortable filterable showGlobalFilter showRowSelection\n+ pageable showPagination pageSize={10}\n+ fitColumns\n+ />\n```\n\nThe four `$state` declarations and their four `onXChange` updaters go\naway with the markup. Sorting, filtering, paging, and selection state\nlive in the grid.\n\nColumn visibility moves too: mark a column `visible: false` to start it\nhidden, and users toggle it from the header column menu. You no longer\nmaintain a dropdown for it.\n\n## One command\n\nUse the CLI you already have:\n\n```sh\nnpx shadcn-svelte@latest add https://svgrid.com/r/data-table.json\n```\n\nThat writes a ready-to-edit `data-table.svelte` into\n`$lib/components/ui/data-table/`, beside your other components, and\ninstalls `@svgrid/grid`. It is a normal registry item, so `components.json`\naliases and your existing setup are respected.\n\nIf you are not in a shadcn project, the same component ships through\nSvGrid's own scaffolder:\n\n```sh\nnpx @svgrid/ui add data-table\n```\n\nBoth routes write the identical file. It is yours to edit, exactly like a\nshadcn recipe. The difference is where the engine lives.\n\n## The upgrade path is the real difference\n\nBoth approaches put a file you own in your repo. Only one puts the\n*engine* in a package.\n\nWhen TanStack Table went from v8 to v9, `useReactTable` became `useTable`,\nthe `get*RowModel()` options became a features object, and `flexRender`\nbecame a component. Every copied data-table had to be hand-fixed, because\nthere is no `npm update` for code you pasted. With SvGrid the file you own\nstays a thin call site, and the behaviour behind it updates with a version\nbump.\n\nThe cost scales with how much you pasted. A seven-file starter is an\nafternoon. The richer community grids paste a whole subsystem - row\nrendering, virtualization, context menus, paste dialogs, hooks, config -\nand every one of those files is now yours to carry through the next\nupstream change.\n\n## Keep your design system\n\nYou do not have to leave shadcn's look, and you do not have to leave its\nmarkup either.\n\n- **Tokens.** `import '@svgrid/grid/themes/shadcn.css'` is a one-line\n match for the default palette in light and dark. To follow a customized\n theme, map your `--background` / `--border` / `--primary` onto the\n `--sg-*` properties - see the [shadcn integration\n guide](./shadcn.md).\n- **Your own markup.** If you want to keep shadcn's `Table.Root` /\n `Table.Row` elements exactly as they are, use the headless core from\n `@svgrid/grid/core` and swap only the engine. See\n [Why headless?](../why-headless.md).\n\n## What you gain\n\nThe official recipe stops where its docs stop: sorting, filtering,\npagination, row selection, column visibility. Community registry items go\nfurther, at the cost of pasting a whole multi-file subsystem into your\nrepo. In SvGrid each of these is a prop:\n\n- **Virtualization** (`virtualization`) - the official recipe has none, so\n a large table is a rewrite rather than a prop.\n- **Inline editing** (`editable`) and cell-range selection\n (`enableCellSelection`).\n- **Grouping with aggregation** (`groupable`) and tree data (`treeData`).\n- **Export** to CSV, and to Excel / PDF on the paid tier.\n- **WAI-ARIA grid semantics and keyboard navigation**, instead of a plain\n `<table>` you keep accessible yourself.\n\n## What you give up\n\n- **A file you can read top to bottom.** The recipe's behaviour is\n visible in your repo; SvGrid's is behind a prop. That is the trade the\n whole page is about.\n- **Pixel-level control of the markup**, unless you go headless.\n- **Weight.** For a short static list that never sorts, the copied\n recipe is smaller.\n\n## Frequently asked questions\n\n### Does SvGrid replace shadcn-svelte?\n\nNo. It replaces one recipe in it. Your buttons, dialogs, and inputs stay\nexactly as they are, and the grid reads the same theme variables they do.\n\n### Can I keep my existing columns.ts?\n\nMostly. Rename `accessorKey` to `field`, drop the `header` render\nhelpers that only existed to draw a sort button, and the rest carries\nover. Custom cells become snippets via `renderSnippet`.\n\n### Do I have to give up owning the code?\n\nYou still own the call site - `npx @svgrid/ui add data-table` writes a\nfile into your project that you edit freely. What you stop owning is the\nrow-model plumbing, which is the part that broke on the v8 to v9 upgrade.\n\n### Is this worth it for a 50-row table?\n\nProbably not, unless you want editing, grouping, or export later. The\ncase gets strong when the table grows past what fits on a page, or when\nthe next feature request is one you would otherwise hand-build.\n\n## What you end up with\n\nSorting, filtering, pagination and selection - the shadcn data-table demo, as props.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable pageable pageSize={3} selectable />\n```\n\n## See also\n\n- [shadcn-svelte integration](./shadcn.md) - matching the theme\n- [Migrating from TanStack Table](./migrating-from-tanstack-table.md) - the\n underlying API map\n- [Migrating from a UI-kit table](./migrating-from-ui-kit-tables.md) - for\n the plain styled `<Table>`\n- [Why headless?](../why-headless.md) - keeping your own markup\n"
6161
+ "markdown": "# Migrating from the shadcn-svelte data table\n\nThe shadcn-svelte **Data Table** is not the same thing as its `<Table>`\ncomponent. `<Table>` is presentation only. The data table is a recipe\nbuilt on TanStack Table v9 that you copy into your own repo: it already\ndoes sorting, filtering, pagination, row selection, and column\nvisibility. If that is what you have, this is your page. If you have the\nplain styled `<Table>` and hand-wrote the sorting yourself, read\n[Migrating from a UI-kit table](./migrating-from-ui-kit-tables.md)\ninstead.\n\n> Estimated effort: **20-40 min** per table. Your column definitions and\n> your feature registration carry over almost unchanged. Most of the work\n> is deleting files.\n\n<!-- facts:start tanstack-table,svelte-ui-kit-tables -->\n> **Facts, checked 9 Nov 2026.** `@tanstack/svelte-table` 9.3.1, MIT, last published 12 Oct 2026, 539,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026); `@tanstack/svelte-table` 9.3.1 36.5 KB JS, no separate stylesheet, svelte external (measured 9 Nov 2026). TanStack Table pricing, as its site states it: TanStack Table is MIT and free; tanstack.com is sponsor-supported and offers Enterprise Support as private consulting and expert support, with no licence sold for the table (https://tanstack.com/table/latest, read 12 Sep 2026). Flowbite / Skeleton / shadcn-svelte tables pricing, as its site states it: Flowbite Svelte, Skeleton and shadcn-svelte are MIT component libraries; their table components are free and no grid licence is sold (https://github.com/themesberg/flowbite-svelte, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs TanStack Table (Svelte)](https://svgrid.com/compare/tanstack-table/), [SvGrid vs Flowbite / Skeleton / shadcn-svelte tables](https://svgrid.com/compare/svelte-ui-kit-tables/).\n<!-- facts:end -->\n\n## Why this port is small\n\nSvGrid speaks the same vocabulary TanStack Table v9 introduced. These are\nreal exports from `@svgrid/grid`, not lookalikes:\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```ts\nimport {\n tableFeatures,\n rowSortingFeature,\n columnFilteringFeature,\n rowPaginationFeature,\n rowSelectionFeature,\n rowExpandingFeature,\n columnGroupingFeature,\n} from '@svgrid/grid'\n```\n\nSo `data-table-features.ts` moves over as-is, and `columns.ts` keeps its\nshape. What does not move is the rendering scaffolding, because SvGrid\nships a renderer and there is nothing to translate it into.\n\n## What happens to each file\n\nThe shadcn recipe generates seven files. Five of them stop existing.\n\n| Their file | Becomes |\n| --- | --- |\n| `data-table-features.ts` | Kept. Same `tableFeatures({...})` call. |\n| `columns.ts` | Kept, minus the `header` render helpers. `{ accessorKey: 'email' }` becomes `{ field: 'email' }`. |\n| `data-table.svelte` | Deleted. It is `<table>` markup over `getHeaderGroups()` / `getRowModel()`, which `<SvGrid>` does. |\n| `data-table-checkbox.svelte` | Deleted. `showRowSelection` renders the column and the select-all header. |\n| `data-table-email-button.svelte` | Deleted. `sortable` makes every header a sort toggle. |\n| `data-table-actions.svelte` | Kept if you want it, as a cell snippet. |\n| `+page.svelte` | Kept. It now renders one component instead of wiring state. |\n\n## Let the codemod do the mechanical part\n\n```bash\nnpx @svgrid/migrate src/routes/payments # preview\nnpx @svgrid/migrate src/routes/payments --write # apply\n```\n\nIt previews by default and only writes with `--write`. Point it at the whole\nroute directory rather than a single file: the shadcn layout keeps `features`\nin its own module, and the codemod follows that import to work out which\nprops the component needs.\n\nIt renames the column keys, re-points the imports, strips the features SvGrid\ndoes not have, and deletes the markup along with the `$state` / `onXChange`\npairs. Custom `cell` and `header` render functions are kept and reported, never\nguessed at. Run your type-checker afterwards - the markup is regenerated rather\nthan edited.\n\n## Before and after\n\n```diff\n- <script lang=\"ts\">\n- import { createSvelteTable, FlexRender } from '$lib/components/ui/data-table'\n- import { columns } from './columns'\n- import { features } from './data-table-features'\n-\n- let sorting = $state([])\n- let filters = $state([])\n- let selection = $state({})\n- let pagination = $state({ pageIndex: 0, pageSize: 10 })\n-\n- const table = createSvelteTable({\n- get data() { return data },\n- columns, features,\n- state: { get sorting() { return sorting }, /* ...and three more... */ },\n- onSortingChange: (u) => (sorting = typeof u === 'function' ? u(sorting) : u),\n- // ...one of these per piece of state...\n- })\n- </script>\n-\n- <Table.Root>\n- <Table.Header>\n- {#each table.getHeaderGroups() as headerGroup}\n- <!-- ...twenty more lines of markup... -->\n- {/each}\n- </Table.Header>\n- <Table.Body>\n- {#each table.getRowModel().rows as row}\n- <!-- ...and twenty more... -->\n- {/each}\n- </Table.Body>\n- </Table.Root>\n\n+ <script lang=\"ts\">\n+ import { SvGrid } from '@svgrid/grid'\n+ import '@svgrid/grid/themes/shadcn.css'\n+ import { columns } from './columns'\n+ import { features } from './data-table-features'\n+ </script>\n+\n+ <SvGrid\n+ {data} {columns} {features}\n+ sortable filterable showGlobalFilter showRowSelection\n+ pageable showPagination pageSize={10}\n+ fitColumns\n+ />\n```\n\nThe four `$state` declarations and their four `onXChange` updaters go\naway with the markup. Sorting, filtering, paging, and selection state\nlive in the grid.\n\nColumn visibility moves too: mark a column `visible: false` to start it\nhidden, and users toggle it from the header column menu. You no longer\nmaintain a dropdown for it.\n\n## One command\n\nUse the CLI you already have:\n\n```sh\nnpx shadcn-svelte@latest add https://svgrid.com/r/data-table.json\n```\n\nThat writes a ready-to-edit `data-table.svelte` into\n`$lib/components/ui/data-table/`, beside your other components, and\ninstalls `@svgrid/grid`. It is a normal registry item, so `components.json`\naliases and your existing setup are respected.\n\nIf you are not in a shadcn project, the same component ships through\nSvGrid's own scaffolder:\n\n```sh\nnpx @svgrid/ui add data-table\n```\n\nBoth routes write the identical file. It is yours to edit, exactly like a\nshadcn recipe. The difference is where the engine lives.\n\n## The upgrade path is the real difference\n\nBoth approaches put a file you own in your repo. Only one puts the\n*engine* in a package.\n\nWhen TanStack Table went from v8 to v9, `useReactTable` became `useTable`,\nthe `get*RowModel()` options became a features object, and `flexRender`\nbecame a component. Every copied data-table had to be hand-fixed, because\nthere is no `npm update` for code you pasted. With SvGrid the file you own\nstays a thin call site, and the behaviour behind it updates with a version\nbump.\n\nThe cost scales with how much you pasted. A seven-file starter is an\nafternoon. The richer community grids paste a whole subsystem - row\nrendering, virtualization, context menus, paste dialogs, hooks, config -\nand every one of those files is now yours to carry through the next\nupstream change.\n\n## Keep your design system\n\nYou do not have to leave shadcn's look, and you do not have to leave its\nmarkup either.\n\n- **Tokens.** `import '@svgrid/grid/themes/shadcn.css'` is a one-line\n match for the default palette in light and dark. To follow a customized\n theme, map your `--background` / `--border` / `--primary` onto the\n `--sg-*` properties - see the [shadcn integration\n guide](./shadcn.md).\n- **Your own markup.** If you want to keep shadcn's `Table.Root` /\n `Table.Row` elements exactly as they are, use the headless core from\n `@svgrid/grid/core` and swap only the engine. See\n [Why headless?](../why-headless.md).\n\n## What you gain\n\nThe official recipe stops where its docs stop: sorting, filtering,\npagination, row selection, column visibility. Community registry items go\nfurther, at the cost of pasting a whole multi-file subsystem into your\nrepo. In SvGrid each of these is a prop:\n\n- **Virtualization** (`virtualization`) - the official recipe has none, so\n a large table is a rewrite rather than a prop.\n- **Inline editing** (`editable`) and cell-range selection\n (`enableCellSelection`).\n- **Grouping with aggregation** (`groupable`) and tree data (`treeData`).\n- **Export** to CSV, and to Excel / PDF on the paid tier.\n- **WAI-ARIA grid semantics and keyboard navigation**, instead of a plain\n `<table>` you keep accessible yourself.\n\n## What you give up\n\n- **A file you can read top to bottom.** The recipe's behaviour is\n visible in your repo; SvGrid's is behind a prop. That is the trade the\n whole page is about.\n- **Pixel-level control of the markup**, unless you go headless.\n- **Weight.** For a short static list that never sorts, the copied\n recipe is smaller.\n\n## Frequently asked questions\n\n### Does SvGrid replace shadcn-svelte?\n\nNo. It replaces one recipe in it. Your buttons, dialogs, and inputs stay\nexactly as they are, and the grid reads the same theme variables they do.\n\n### Can I keep my existing columns.ts?\n\nMostly. Rename `accessorKey` to `field`, drop the `header` render\nhelpers that only existed to draw a sort button, and the rest carries\nover. Custom cells become snippets via `renderSnippet`.\n\n### Do I have to give up owning the code?\n\nYou still own the call site - `npx @svgrid/ui add data-table` writes a\nfile into your project that you edit freely. What you stop owning is the\nrow-model plumbing, which is the part that broke on the v8 to v9 upgrade.\n\n### Is this worth it for a 50-row table?\n\nProbably not, unless you want editing, grouping, or export later. The\ncase gets strong when the table grows past what fits on a page, or when\nthe next feature request is one you would otherwise hand-build.\n\n## What you end up with\n\nSorting, filtering, pagination and selection - the shadcn data-table demo, as props.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable pageable pageSize={3} selectable />\n```\n\n## See also\n\n- [shadcn-svelte integration](./shadcn.md) - matching the theme\n- [Migrating from TanStack Table](./migrating-from-tanstack-table.md) - the\n underlying API map\n- [Migrating from a UI-kit table](./migrating-from-ui-kit-tables.md) - for\n the plain styled `<Table>`\n- [Why headless?](../why-headless.md) - keeping your own markup\n"
6162
6162
  },
6163
6163
  {
6164
6164
  "slug": "help/migrating-from-smart-grid",
6165
6165
  "path": "docs/help/migrating-from-smart-grid.md",
6166
6166
  "title": "Migrating from Smart.Grid (Smart Web Components)",
6167
6167
  "section": "Help",
6168
- "markdown": "\n# Migrating from Smart.Grid (Smart Web Components)\n\nSmart.Grid (htmlelements.com) and SvGrid come from the **same team**.\nSmart.Grid is a framework-agnostic custom element - it even works inside\nSvelte today - while SvGrid is the reactive, Svelte-5-native option. If\nyou are standardising a Svelte app on idiomatic components, this guide\nmaps a Smart.Grid setup onto SvGrid.\n\n> Estimated effort: **2-4 hours** per grid. The main shift is from a\n> custom element bound through properties / attributes to a reactive\n> Svelte component.\n\n<!-- facts:start smart-grid -->\n> **Facts, checked 9 Nov 2026.** `smart-webcomponents` 27.1.0, ISC, last published 2 Oct 2026, 5,690 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026). Smart.Grid pricing, as its site states it: htmlelements.com lists the Developer License at $499 (on sale at $399) per developer, perpetual, or $39 per month, and the Team License at $1,499 per five developers; the free Community License covers the core components but not the Grid (https://www.htmlelements.com/license/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Smart.Grid (Smart Web Components)](https://svgrid.com/compare/smart-grid/).\n<!-- facts:end -->\n\n## Vocabulary cheat sheet\n\n| Smart.Grid (web component) | sv-grid |\n| ---------------------------------------- | ----------------------------------------- |\n| `<smart-grid>` element | `<SvGrid ... />` |\n| `grid.dataSource = new Smart.DataAdapter`| `data` array (or `externalSort/Filter`) |\n| `{ label: 'Name', dataField: 'name' }` | `{ header: 'Name', field: 'name' }` |\n| `template` / cell template | `cell: (c) => renderSnippet(...)` |\n| `editing` + editor | `enableInlineEditing` + `editorType` |\n| `sorting` / `filtering` | `rowSortingFeature` / `columnFilteringFeature` |\n| `grouping` | `columnGroupingFeature` + `api.setGroupBy()` |\n| `paging` + `pager` | `showPagination` |\n| element events (`change`, ...) | `onCellValueChange`, `onApiReady` |\n| `theme` attribute | `--sg-*` tokens / Tailwind |\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- <smart-grid id=\"grid\" sorting filtering paging></smart-grid>\n- <script>\n- const grid = document.querySelector('#grid')\n- grid.dataSource = new Smart.DataAdapter({ dataSource: rows, dataFields: [...] })\n- grid.columns = [\n- { label: 'Name', dataField: 'name' },\n- { label: 'Amount', dataField: 'amount' },\n- ]\n- </script>\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} showPagination />\n```\n\n## What changes\n\n- **Custom element + DataAdapter → reactive `$state`.** Data binding is a\n prop, not an assigned `dataSource`.\n- **Element templates → Svelte snippets** via `renderSnippet`.\n- **`theme` attribute → `--sg-*` tokens.**\n\n## A note on family\n\nSmart.Grid is a genuinely good framework-agnostic grid from the same\nteam, and it runs in Svelte as a web component. The reason to pick SvGrid\nis *idiomatic* Svelte: runes, snippets, and an MIT core. If you need one\ngrid across Angular, React, Vue, Svelte, and vanilla, Smart.Grid is the\nright call.\n\n## Frequently asked questions\n\n### Is SvGrid from the same team as Smart.Grid?\n\nYes. Smart Web Components (htmlelements.com) and SvGrid are built by the same\nteam. SvGrid is the Svelte-5-native option with an MIT community core.\n\n### Can I keep using Smart.Grid in Svelte instead?\n\nYes - Smart.Grid is a web component and works inside Svelte. Choose SvGrid when\nyou want an idiomatic Svelte component (runes + snippets) rather than a custom\nelement bound through properties.\n\n### How do Smart.Grid columns map to SvGrid?\n\n`label` becomes `header`, `dataField` becomes `field`, and element templates\nbecome `renderSnippet` cells. Sorting / filtering / grouping move to registered\nfeatures.\n\n## More examples\n\n### Smart.Chart integration\n\nMounts a <smart-chart> web component (htmlelements.com) and pipes the grid's displayed rows into its dataSource. Re-aggregates on every filter / sort.\n\n<div data-docs-demo=\"77-smart-chart\" data-height=\"460\"></div>\n\n## What you end up with\n\nSorting, filtering and editing with a footer summary.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable editable summary />\n```\n\n## The ported grid, running\n\nSorting, filtering, editing and a totals row - the working set a Smart grid\nusually carries, as props.\n\n```svelte {runnable}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n city: string\n age: number\n salary: number\n }\n\n const seed: Person[] = [\n { id: 1, name: 'Ada Lovelace', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', city: 'Portland', age: 54, salary: 155000 },\n ]\n\n let rows = $state<Person[]>(seed.map((p) => ({ ...p })))\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 180, editorType: 'text' },\n { field: 'city', header: 'City', width: 150, editorType: 'text' },\n { field: 'salary', header: 'Salary', width: 150, editorType: 'number', summary: 'sum',\n format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n\n<SvGrid data={rows} {columns} sortable filterable editable summary />\n```\n\n## See also\n\n- [SvGrid vs Smart.Grid](https://svgrid.com/compare/smart-grid/) - the side-by-side comparison\n- [About SvGrid](https://svgrid.com/about/) - built by jQWidgets / htmlelements.com\n- [Cell components](./cells/cell-components.md) - snippet-based custom cells\n"
6168
+ "markdown": "\n# Migrating from Smart.Grid (Smart Web Components)\n\nSmart.Grid (htmlelements.com) and SvGrid come from the **same team**.\nSmart.Grid is a framework-agnostic custom element - it even works inside\nSvelte today - while SvGrid is the reactive, Svelte-5-native option. If\nyou are standardising a Svelte app on idiomatic components, this guide\nmaps a Smart.Grid setup onto SvGrid.\n\n> Estimated effort: **2-4 hours** per grid. The main shift is from a\n> custom element bound through properties / attributes to a reactive\n> Svelte component.\n\n<!-- facts:start smart-grid -->\n> **Facts, checked 9 Nov 2026.** `smart-webcomponents` 27.1.0, ISC, last published 2 Oct 2026, 5,690 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026). Smart.Grid pricing, as its site states it: htmlelements.com lists the Developer License at $499 (on sale at $399) per developer, perpetual, or $39 per month, and the Team License at $1,499 per five developers; the free Community License covers the core components but not the Grid (https://www.htmlelements.com/license/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Smart.Grid (Smart Web Components)](https://svgrid.com/compare/smart-grid/).\n<!-- facts:end -->\n\n## Vocabulary cheat sheet\n\n| Smart.Grid (web component) | sv-grid |\n| ---------------------------------------- | ----------------------------------------- |\n| `<smart-grid>` element | `<SvGrid ... />` |\n| `grid.dataSource = new Smart.DataAdapter`| `data` array (or `externalSort/Filter`) |\n| `{ label: 'Name', dataField: 'name' }` | `{ header: 'Name', field: 'name' }` |\n| `template` / cell template | `cell: (c) => renderSnippet(...)` |\n| `editing` + editor | `enableInlineEditing` + `editorType` |\n| `sorting` / `filtering` | `rowSortingFeature` / `columnFilteringFeature` |\n| `grouping` | `columnGroupingFeature` + `api.setGroupBy()` |\n| `paging` + `pager` | `showPagination` |\n| element events (`change`, ...) | `onCellValueChange`, `onApiReady` |\n| `theme` attribute | `--sg-*` tokens / Tailwind |\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- <smart-grid id=\"grid\" sorting filtering paging></smart-grid>\n- <script>\n- const grid = document.querySelector('#grid')\n- grid.dataSource = new Smart.DataAdapter({ dataSource: rows, dataFields: [...] })\n- grid.columns = [\n- { label: 'Name', dataField: 'name' },\n- { label: 'Amount', dataField: 'amount' },\n- ]\n- </script>\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} showPagination />\n```\n\n## What changes\n\n- **Custom element + DataAdapter → reactive `$state`.** Data binding is a\n prop, not an assigned `dataSource`.\n- **Element templates → Svelte snippets** via `renderSnippet`.\n- **`theme` attribute → `--sg-*` tokens.**\n\n## A note on family\n\nSmart.Grid is a genuinely good framework-agnostic grid from the same\nteam, and it runs in Svelte as a web component. The reason to pick SvGrid\nis *idiomatic* Svelte: runes, snippets, and an MIT core. If you need one\ngrid across Angular, React, Vue, Svelte, and vanilla, Smart.Grid is the\nright call.\n\n## Frequently asked questions\n\n### Is SvGrid from the same team as Smart.Grid?\n\nYes. Smart Web Components (htmlelements.com) and SvGrid are built by the same\nteam. SvGrid is the Svelte-5-native option with an MIT community core.\n\n### Can I keep using Smart.Grid in Svelte instead?\n\nYes - Smart.Grid is a web component and works inside Svelte. Choose SvGrid when\nyou want an idiomatic Svelte component (runes + snippets) rather than a custom\nelement bound through properties.\n\n### How do Smart.Grid columns map to SvGrid?\n\n`label` becomes `header`, `dataField` becomes `field`, and element templates\nbecome `renderSnippet` cells. Sorting / filtering / grouping move to registered\nfeatures.\n\n## More examples\n\n### Smart.Chart integration\n\nMounts a <smart-chart> web component (htmlelements.com) and pipes the grid's displayed rows into its dataSource. Re-aggregates on every filter / sort.\n\n<div data-docs-demo=\"77-smart-chart\" data-height=\"460\"></div>\n\n## What you end up with\n\nSorting, filtering and editing with a footer summary.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable editable summary />\n```\n\n## The ported grid, running\n\nSorting, filtering, editing and a totals row - the working set a Smart grid\nusually carries, as props.\n\n```svelte {runnable}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n city: string\n age: number\n salary: number\n }\n\n const seed: Person[] = [\n { id: 1, name: 'Ada Lovelace', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', city: 'Portland', age: 54, salary: 155000 },\n ]\n\n let rows = $state<Person[]>(seed.map((p) => ({ ...p })))\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 180, editorType: 'text' },\n { field: 'city', header: 'City', width: 150, editorType: 'text' },\n { field: 'salary', header: 'Salary', width: 150, editorType: 'number', summary: 'sum',\n format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n\n<SvGrid data={rows} {columns} sortable filterable editable summary />\n```\n\n## See also\n\n- [SvGrid vs Smart.Grid](https://svgrid.com/compare/smart-grid/) - the side-by-side comparison\n- [About SvGrid](https://svgrid.com/about/) - built by jQWidgets / htmlelements.com\n- [Cell components](./cells/cell-components.md) - snippet-based custom cells\n"
6169
6169
  },
6170
6170
  {
6171
6171
  "slug": "help/migrating-from-svar-svelte-datagrid",
6172
6172
  "path": "docs/help/migrating-from-svar-svelte-datagrid.md",
6173
6173
  "title": "Migrating from SVAR Svelte DataGrid",
6174
6174
  "section": "Help",
6175
- "markdown": "# Migrating from SVAR Svelte DataGrid\n\nSVAR Svelte DataGrid (`@svar-ui/svelte-grid`, formerly `wx-svelte-grid`) is, like SvGrid, an actual\nSvelte-native grid rather than a wrapper, and both are MIT-licensed and\nfree for commercial use. Because both are component-first with\narray-of-object column definitions, a port is mostly a configuration\ntranslation. The reasons people switch are **capability** (SvGrid adds\nrow grouping with aggregation, master-detail, Excel-style cell-range\nselection, integrated charts, and pivot) and **architecture** (SvGrid\nalso exposes a headless engine and an MCP server).\n\n> Estimated effort: **2-4 hours** per grid - a prop and event rename\n> pass, plus re-theming.\n>\n> SVAR's exact prop and event names evolve across releases; check the\n> current SVAR docs and map them onto the SvGrid equivalents below.\n\n<!-- facts:start svar-svelte-datagrid -->\n> **Facts, checked 9 Nov 2026.** `@svar-ui/svelte-grid` 2.7.6, MIT, last published 7 Nov 2026, 106,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026); `@svar-ui/svelte-grid` 2.7.6 53.1 KB JS, no separate stylesheet, svelte external (measured 9 Nov 2026). SVAR Svelte DataGrid pricing, as its site states it: The DataGrid is MIT and free for commercial use with no paid tier; svar.dev sells PRO editions of its Gantt, Calendar and Kanban components and offers paid consulting and custom development, with no price list for the grid (https://svar.dev/svelte/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs SVAR Svelte DataGrid](https://svgrid.com/compare/svar-svelte-datagrid/).\n<!-- facts:end -->\n\n## Concept map\n\n| SVAR DataGrid (@svar-ui/svelte-grid) | sv-grid |\n| ----------------------------------------- | ----------------------------------------- |\n| `<Grid {data} {columns} />` | `<SvGrid data={...} columns={...} />` |\n| `columns: [{ id, header, width, ... }]` | `columns: [{ field, header, width, ... }]` |\n| `sizes={{ rowHeight, columnWidth }}` | `rowHeight` prop, `width` per column |\n| `autoRowHeight` | `autoRowHeight` |\n| Per-column `editor` / `template` | `editorType` + `cell` snippet |\n| `sort: true` on a column, `sortMarks` | `rowSortingFeature`; `initialSorting` |\n| Header filters, the Filter component | `columnFilteringFeature`; Excel-style menu and filter row built in |\n| `tree` prop + `data` with children | `treeData={{ parentField }}` or `rowExpandingFeature` with sub rows |\n| `select` / `multiselect` | `selectionMode=\"row\"` (+ checkbox column) |\n| `split={{ left: n }}` (pinned columns) | `initialColumnPinning` or `pinned: 'left' \\| 'right'` per column |\n| `reorder` (row drag) | `rowDragManaged` |\n| `undo` prop, undo/redo hotkeys | `history` prop; `api.undo()` / `api.redo()` |\n| Context menu component | `contextMenu` prop with items |\n| `init={(api) => ...}` | `onApiReady={(api) => ...}` |\n| `api.exec('sort-rows', { key, order })` | `api.setSort(field, 'asc' \\| 'desc')` |\n| `api.exec('filter-rows', { filter })` | `api.setFilter(field, { operator, value })` |\n| `api.on('...')` event bus | `onXxx` callback props |\n| Export to CSV, print API | `api.exportCsv()` (free); print in `@svgrid/enterprise` |\n| `RestDataProvider` | server-side row model / `externalSort` + `externalFilter` |\n| Theme / skin components (Willow, Material)| `--sg-*` CSS custom properties / Tailwind |\n\n## Before / after (shape, not exact prop names)\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- <script>\n- import { Grid } from '@svar-ui/svelte-grid'\n- const columns = [\n- { id: 'name', header: 'Name', width: 200 },\n- { id: 'amount', header: 'Amount', width: 120, editor: 'text' },\n- ]\n- </script>\n-\n- <Grid {data} {columns} />\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name', width: 200 },\n+ { field: 'amount', header: 'Amount', width: 120, editorType: 'text' },\n+ ]\n+ </script>\n+\n+ <SvGrid data={data} columns={columns} features={features} enableInlineEditing />\n```\n\n## Licensing note\n\nBoth grids are MIT and free for commercial use, so licensing is not the\ndeciding factor. The difference is monetization: SVAR keeps the whole\ngrid free (including CSV export and print) and sells PRO editions of its\nGantt, Calendar and Kanban instead, whereas SvGrid's `@svgrid/grid` core is\nMIT and the optional `@svgrid/enterprise` pack (XLSX/PDF export, print,\npivot, import, support) is the paid piece. CSV, TSV and JSON export and the\nin-grid AI helpers are free on SvGrid too. If all you need is CSV export and\nprint, SVAR gives both free; if you need pivot, Excel or PDF output, or a\nsupport SLA, that is Enterprise on SvGrid.\n\n## What you get with SvGrid\n\n- **Row grouping with aggregation**, **master-detail**, **pinned rows**,\n and left/right column freezing - beyond SVAR's documented surface.\n- A **headless engine** (`createSvGrid` + row models) in addition to the\n component, if you want to compose your own layer.\n- **Excel-style filter menu**, **cell-range selection + TSV copy**, a\n **fill handle**, **integrated charts**, and a documented **imperative API**.\n- **In-grid AI helpers** (natural-language filter, smart fill, summarise),\n free against a model you register, and **@svgrid/mcp** so AI assistants\n answer accurately about your grid and can check the code they write.\n\nThe two features most SVAR teams port for:\n\n<div data-docs-demo=\"07-grouping-aggregation\" data-height=\"520\"></div>\n\n<div data-docs-demo=\"181-master-detail-grid\" data-height=\"520\"></div>\n\n## What you give up\n\n- **Free printing.** SVAR's print API is in the MIT grid; SvGrid's print\n view is in `@svgrid/enterprise`.\n- **The React and Vue versions** of the same grid. SvGrid is Svelte-only.\n- **A smaller bundle.** The facts box at the top of the page has both\n packages measured the same way; the difference is the grouping,\n master/detail, range editing, charts and server-side data (flat paging and infinite scroll free; grouping, tree, pivot and transactions on the server are Enterprise) SvGrid\n carries, and features you never import load as separate chunks.\n- **The SVAR suite around the grid.** Gantt, Calendar, Kanban and File\n Manager share SVAR's core; SvGrid's Kanban and scheduler are views of the\n grid in `@svgrid/enterprise`.\n\n## What to check on the SVAR side\n\n- The **wider SVAR suite** (Gantt, Calendar, Kanban) - if you use several\n SVAR components together, staying on SVAR may be simpler.\n- Any **SVAR-specific column features** you rely on; map each to a SvGrid\n `cell` snippet, `editorType`, or feature before porting.\n- **Filter functions.** SVAR filters with a predicate you write; SvGrid's\n filter takes an operator and a value per column, and `externalFilter`\n hands you the rows when you want to keep a custom predicate.\n\n## Frequently asked questions\n\n### Why move from SVAR Svelte DataGrid to SvGrid?\n\nCapability and architecture, not licensing (both are MIT). SvGrid adds row\ngrouping with aggregation, master-detail, Excel-style cell-range selection,\nintegrated charts, and pivot, and it ships a headless engine plus an MCP server\nalongside the component. Both are Svelte-native, so the core grid\nbehaviour is comparable; SvGrid covers more ground.\n\n### Is the migration a rewrite?\n\nNo. Both are component-first with array-of-object columns, so it is mostly a\nprop / event rename pass (`id` → `field`, edit events → `onCellValueChange`)\nplus re-theming through `--sg-*` tokens.\n\n### Are SvGrid and SVAR both free and MIT?\n\nYes. `@svgrid/grid` and the SVAR DataGrid are both MIT and free for\ncommercial, closed-source use. SVAR keeps the whole grid free and sells PRO\neditions of its Gantt, Calendar and Kanban; on SvGrid, only the optional\n`@svgrid/enterprise` add-on (Excel and PDF export, print, pivot, import,\nsupport) is paid. The dated statement from svar.dev is in the facts box at\nthe top of this page.\n\n### How does SVAR's tree data map to SvGrid?\n\nSVAR takes hierarchical data with the `tree` prop. SvGrid takes either a\nflat array with a parent field (`treeData={{ parentField: 'parentId' }}`)\nor nested rows through `rowExpandingFeature`, and the same grid also does\nmaster/detail, which SVAR's docs do not list. The example below runs the\nflat shape:\n\n## What you end up with\n\nGrouping with aggregation and a totals row, the main capability step up.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} groupBy={['department']} summary groupable sortable filterable />\n```\n\nAnd the tree shape, from the same rows with a parent link, which is what SVAR's `tree` prop becomes:\n\n```svelte {runnable}\n<SvGrid data={rows.map((r, i) => ({ ...r, parentId: i === 0 ? null : rows[0].id }))} {columns} treeData={{ parentField: 'parentId' }} sortable />\n```\n\n## See also\n\n- [SvGrid vs SVAR Svelte DataGrid](https://svgrid.com/compare/svar-svelte-datagrid/) - the side-by-side comparison, with a source and date for every claim and the measured benchmark\n- [Grouping and aggregation](./grouping-aggregation.md) - the first demo above\n- [Master/detail](./rows/master-detail.md) - the second demo above\n- [Architecture](./architecture.md) - the engine + render-component split\n- [Cell components](./cells/cell-components.md) - custom cells and editors\n"
6175
+ "markdown": "# Migrating from SVAR Svelte DataGrid\n\nSVAR Svelte DataGrid (`@svar-ui/svelte-grid`, formerly `wx-svelte-grid`) is, like SvGrid, an actual\nSvelte-native grid rather than a wrapper, and both are MIT-licensed and\nfree for commercial use. Because both are component-first with\narray-of-object column definitions, a port is mostly a configuration\ntranslation. The reasons people switch are **capability** (SvGrid adds\nrow grouping with aggregation, master-detail, Excel-style cell-range\nselection, integrated charts, and pivot) and **architecture** (SvGrid\nalso exposes a headless engine and an MCP server).\n\n> Estimated effort: **2-4 hours** per grid - a prop and event rename\n> pass, plus re-theming.\n>\n> SVAR's exact prop and event names evolve across releases; check the\n> current SVAR docs and map them onto the SvGrid equivalents below.\n\n<!-- facts:start svar-svelte-datagrid -->\n> **Facts, checked 9 Nov 2026.** `@svar-ui/svelte-grid` 2.7.6, MIT, last published 7 Nov 2026, 106,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026); `@svar-ui/svelte-grid` 2.7.6 53.1 KB JS, no separate stylesheet, svelte external (measured 9 Nov 2026). SVAR Svelte DataGrid pricing, as its site states it: The DataGrid is MIT and free for commercial use with no paid tier; svar.dev sells PRO editions of its Gantt, Calendar and Kanban components and offers paid consulting and custom development, with no price list for the grid (https://svar.dev/svelte/, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs SVAR Svelte DataGrid](https://svgrid.com/compare/svar-svelte-datagrid/).\n<!-- facts:end -->\n\n## Concept map\n\n| SVAR DataGrid (@svar-ui/svelte-grid) | sv-grid |\n| ----------------------------------------- | ----------------------------------------- |\n| `<Grid {data} {columns} />` | `<SvGrid data={...} columns={...} />` |\n| `columns: [{ id, header, width, ... }]` | `columns: [{ field, header, width, ... }]` |\n| `sizes={{ rowHeight, columnWidth }}` | `rowHeight` prop, `width` per column |\n| `autoRowHeight` | `autoRowHeight` |\n| Per-column `editor` / `template` | `editorType` + `cell` snippet |\n| `sort: true` on a column, `sortMarks` | `rowSortingFeature`; `initialSorting` |\n| Header filters, the Filter component | `columnFilteringFeature`; Excel-style menu and filter row built in |\n| `tree` prop + `data` with children | `treeData={{ parentField }}` or `rowExpandingFeature` with sub rows |\n| `select` / `multiselect` | `selectionMode=\"row\"` (+ checkbox column) |\n| `split={{ left: n }}` (pinned columns) | `initialColumnPinning` or `pinned: 'left' \\| 'right'` per column |\n| `reorder` (row drag) | `rowDragManaged` |\n| `undo` prop, undo/redo hotkeys | `history` prop; `api.undo()` / `api.redo()` |\n| Context menu component | `contextMenu` prop with items |\n| `init={(api) => ...}` | `onApiReady={(api) => ...}` |\n| `api.exec('sort-rows', { key, order })` | `api.setSort(field, 'asc' \\| 'desc')` |\n| `api.exec('filter-rows', { filter })` | `api.setFilter(field, { operator, value })` |\n| `api.on('...')` event bus | `onXxx` callback props |\n| Export to CSV, print API | `api.exportCsv()` (free); print in `@svgrid/enterprise` |\n| `RestDataProvider` | server-side row model / `externalSort` + `externalFilter` |\n| Theme / skin components (Willow, Material)| `--sg-*` CSS custom properties / Tailwind |\n\n## Before / after (shape, not exact prop names)\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- <script>\n- import { Grid } from '@svar-ui/svelte-grid'\n- const columns = [\n- { id: 'name', header: 'Name', width: 200 },\n- { id: 'amount', header: 'Amount', width: 120, editor: 'text' },\n- ]\n- </script>\n-\n- <Grid {data} {columns} />\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name', width: 200 },\n+ { field: 'amount', header: 'Amount', width: 120, editorType: 'text' },\n+ ]\n+ </script>\n+\n+ <SvGrid data={data} columns={columns} features={features} enableInlineEditing />\n```\n\n## Licensing note\n\nBoth grids are MIT and free for commercial use, so licensing is not the\ndeciding factor. The difference is monetization: SVAR keeps the whole\ngrid free (including CSV export and print) and sells PRO editions of its\nGantt, Calendar and Kanban instead, whereas SvGrid's `@svgrid/grid` core is\nMIT and the optional `@svgrid/enterprise` pack (XLSX/PDF export, print,\npivot, import, support) is the paid piece. CSV, TSV and JSON export and the\nin-grid AI helpers are free on SvGrid too. If all you need is CSV export and\nprint, SVAR gives both free; if you need pivot, Excel or PDF output, or a\nsupport SLA, that is Enterprise on SvGrid.\n\n## What you get with SvGrid\n\n- **Row grouping with aggregation**, **master-detail**, **pinned rows**,\n and left/right column freezing - beyond SVAR's documented surface.\n- A **headless engine** (`createSvGrid` + row models) in addition to the\n component, if you want to compose your own layer.\n- **Excel-style filter menu**, **cell-range selection + TSV copy**, a\n **fill handle**, **integrated charts**, and a documented **imperative API**.\n- **In-grid AI helpers** (natural-language filter, smart fill, summarise),\n free against a model you register, and **@svgrid/mcp** so AI assistants\n answer accurately about your grid and can check the code they write.\n\nThe two features most SVAR teams port for:\n\n<div data-docs-demo=\"07-grouping-aggregation\" data-height=\"520\"></div>\n\n<div data-docs-demo=\"181-master-detail-grid\" data-height=\"520\"></div>\n\n## What you give up\n\n- **Free printing.** SVAR's print API is in the MIT grid; SvGrid's print\n view is in `@svgrid/enterprise`.\n- **The React and Vue versions** of the same grid. SvGrid is Svelte-only.\n- **A smaller bundle.** The facts box at the top of the page has both\n packages measured the same way; the difference is the grouping,\n master/detail, range editing, charts and server-side data (flat paging and infinite scroll free; grouping, tree, pivot and transactions on the server are Enterprise) SvGrid\n carries, and features you never import load as separate chunks.\n- **The SVAR suite around the grid.** Gantt, Calendar, Kanban and File\n Manager share SVAR's core; SvGrid's Kanban and scheduler are views of the\n grid in `@svgrid/enterprise`.\n\n## What to check on the SVAR side\n\n- The **wider SVAR suite** (Gantt, Calendar, Kanban) - if you use several\n SVAR components together, staying on SVAR may be simpler.\n- Any **SVAR-specific column features** you rely on; map each to a SvGrid\n `cell` snippet, `editorType`, or feature before porting.\n- **Filter functions.** SVAR filters with a predicate you write; SvGrid's\n filter takes an operator and a value per column, and `externalFilter`\n hands you the rows when you want to keep a custom predicate.\n\n## Frequently asked questions\n\n### Why move from SVAR Svelte DataGrid to SvGrid?\n\nCapability and architecture, not licensing (both are MIT). SvGrid adds row\ngrouping with aggregation, master-detail, Excel-style cell-range selection,\nintegrated charts, and pivot, and it ships a headless engine plus an MCP server\nalongside the component. Both are Svelte-native, so the core grid\nbehaviour is comparable; SvGrid covers more ground.\n\n### Is the migration a rewrite?\n\nNo. Both are component-first with array-of-object columns, so it is mostly a\nprop / event rename pass (`id` → `field`, edit events → `onCellValueChange`)\nplus re-theming through `--sg-*` tokens.\n\n### Are SvGrid and SVAR both free and MIT?\n\nYes. `@svgrid/grid` and the SVAR DataGrid are both MIT and free for\ncommercial, closed-source use. SVAR keeps the whole grid free and sells PRO\neditions of its Gantt, Calendar and Kanban; on SvGrid, only the optional\n`@svgrid/enterprise` add-on (Excel and PDF export, print, pivot, import,\nsupport) is paid. The dated statement from svar.dev is in the facts box at\nthe top of this page.\n\n### How does SVAR's tree data map to SvGrid?\n\nSVAR takes hierarchical data with the `tree` prop. SvGrid takes either a\nflat array with a parent field (`treeData={{ parentField: 'parentId' }}`)\nor nested rows through `rowExpandingFeature`, and the same grid also does\nmaster/detail, which SVAR's docs do not list. The example below runs the\nflat shape:\n\n## What you end up with\n\nGrouping with aggregation and a totals row, the main capability step up.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} groupBy={['department']} summary groupable sortable filterable />\n```\n\nAnd the tree shape, from the same rows with a parent link, which is what SVAR's `tree` prop becomes:\n\n```svelte {runnable}\n<SvGrid data={rows.map((r, i) => ({ ...r, parentId: i === 0 ? null : rows[0].id }))} {columns} treeData={{ parentField: 'parentId' }} sortable />\n```\n\n## See also\n\n- [SvGrid vs SVAR Svelte DataGrid](https://svgrid.com/compare/svar-svelte-datagrid/) - the side-by-side comparison, with a source and date for every claim and the measured benchmark\n- [Grouping and aggregation](./grouping-aggregation.md) - the first demo above\n- [Master/detail](./rows/master-detail.md) - the second demo above\n- [Architecture](./architecture.md) - the engine + render-component split\n- [Cell components](./cells/cell-components.md) - custom cells and editors\n"
6176
6176
  },
6177
6177
  {
6178
6178
  "slug": "help/migrating-from-svelte-headless-table",
6179
6179
  "path": "docs/help/migrating-from-svelte-headless-table.md",
6180
6180
  "title": "Migrating from svelte-headless-table",
6181
6181
  "section": "Help",
6182
- "markdown": "\n# Migrating from svelte-headless-table\n\nsvelte-headless-table popularised the headless-table pattern in the\nSvelte ecosystem. It is built on Svelte 4 stores and plugins\n(`addSortBy`, `addColumnFilters`, `addPagination`, ...), and it leaves\nthe markup to you. SvGrid keeps the same headless idea but runs on\nSvelte 5 runes and ships a render component, so the port mostly\n*removes* the table you used to hand-author.\n\n> Estimated effort: **1-3 hours** per grid. Most of the time is deleting\n> the `<table>` markup and `Subscribe` blocks you no longer need.\n\n<!-- facts:start svelte-headless-table pkg:@humanspeak/svelte-headless-table -->\n> **Facts, checked 9 Nov 2026.** `svelte-headless-table` 0.18.3, MIT, last published 28 Oct 2024, 96,400 npm downloads in the 30 days to 8 Nov 2026. `@humanspeak/svelte-headless-table` 7.1.0, MIT, last published 28 Oct 2026, 10,600 npm downloads in the same window. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026); `svelte-headless-table` 0.18.3 5.7 KB JS, no separate stylesheet, svelte external (measured 9 Nov 2026). svelte-headless-table pricing, as its site states it: svelte-headless-table is MIT and free; no paid licence or support is offered, and the author states there are no plans for a Svelte 5 port (https://github.com/bryanmylee/svelte-headless-table, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs svelte-headless-table](https://svgrid.com/compare/svelte-headless-table/).\n<!-- facts:end -->\n\n## Know your options first\n\nThe original package's last release and its Svelte 4 peer range are in the\nfacts box above, and its README states there are no current plans for a\nSvelte 5 port, so a Svelte 5 upgrade forces a decision. There are three\nhonest answers and you should know all of them:\n\n1. **`@humanspeak/svelte-headless-table`** - a maintained fork on Svelte 5 with\n the same API; its version, publish date and downloads are in the facts box\n too. Changing one package name is the cheapest path by a wide margin. If\n your table works and you only need Svelte 5, do that.\n2. **TanStack Table v9** - its Svelte adapter declares a Svelte 5 peer range.\n Still headless-only, so you keep writing and maintaining the markup.\n3. **SvGrid** - this page. A different trade: you delete the markup and take a\n renderer instead.\n\nPick SvGrid when the markup is the part you are tired of. Note that the blocker\nis not the syntax and not really the install either: `svelte-headless-table@0.18.3`\ndeclares `svelte@^4`, which npm 11 overrides with a warning (older npm needed\n`--legacy-peer-deps`), and the untouched component then type-checks clean in\nlegacy mode. Slots and `let:` still work in Svelte 5 - they are deprecated in\nfavour of snippets, not removed - so the `Subscribe` blocks below keep\nrendering. The trouble starts when that component moves to runes: the library\ntakes a store, your data is a rune, and the bridge between them is yours to\nwrite and maintain. We ran the whole upgrade and captured every line of it in\n[Upgrading a Svelte 4 table to Svelte 5](./svelte-5-upgrade-data-tables.md).\n\n## Run the codemod\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```bash\nnpx @svgrid/migrate # preview the result\nnpx @svgrid/migrate src --write # apply it\n```\n\nIt translates column definitions and plugin config, deletes the\n`Subscribe`/`Render` scaffolding, and reports anything it cannot map rather than\ndropping it silently. It previews by default. See\n[`@svgrid/migrate`](https://www.npmjs.com/package/@svgrid/migrate) for the full\nmapping and its limits.\n\n## Vocabulary cheat sheet\n\n| svelte-headless-table | sv-grid |\n| ----------------------------------------- | ----------------------------------------- |\n| `createTable(data, plugins)` | `createSvGrid({...})` or `<SvGrid>` |\n| `table.createColumns((t) => [...])` | `columns: ColumnDef[]` |\n| `t.column({ accessor: 'x', header })` | `{ field: 'x', header }` |\n| `t.column({ accessor: (r) => ... })` | `{ id, fieldFn: (r) => ... }` |\n| `t.group({ header, columns })` | `{ header, columns: [...] }` (column group) |\n| `addSortBy()` | `rowSortingFeature` |\n| `addColumnFilters()` / `addTableFilter()` | `columnFilteringFeature` |\n| `addPagination()` | Built in; toggle `showPagination` |\n| `addExpandedRows()` / `addSubRows()` | `rowExpandingFeature` |\n| `addGroupBy()` | `columnGroupingFeature` + `api.setGroupBy()` |\n| `addSelectedRows()` | `rowSelectionFeature` |\n| `addDataExport()` | `@svgrid/enterprise` export pack |\n| `createViewModel(columns)` + `Subscribe` | `<SvGrid>` (no view model to wire) |\n| `pluginStates.sort.sortKeys` | `api.setSort(id, dir)` / `onSortingChange` |\n\n### The shortcut form\n\nThat table maps plugins onto the headless *features*, which is what you want if\nyou keep driving the engine yourself. If you are moving to the `<SvGrid>`\ncomponent, every capability also has a boolean prop, and that is what the\ncodemod emits:\n\n| Plugin | `<SvGrid>` prop |\n| --- | --- |\n| `addSortBy()` | `sortable` |\n| `addTableFilter()` | `filterable showGlobalFilter` |\n| `addColumnFilters()` | `filterable showColumnFilters` |\n| `addPagination({ initialPageSize: 25 })` | `pageable pageSize={25}` |\n| `addSelectedRows()` | `showRowSelection` |\n| `addGroupBy()` | `groupable` |\n| `addSubRows()` | `treeData` |\n| `addColumnOrder()` | `enableColumnReorder` |\n| `addResizedColumns()` | nothing - resizing is built in |\n| `addHiddenColumns()` | `visible: false` on the column |\n| `addExpandedRows()` | `treeData`, or `isDetailRow` + `renderDetailRow` |\n| `addGridLayout()` | nothing - SvGrid owns its layout |\n\nEvery capability is off by default and turned on by its prop; there is no\nplugin registration step.\n\n## Before / after\n\n```diff\n- <script>\n- import { createTable } from 'svelte-headless-table'\n- import { addSortBy, addColumnFilters, addPagination } from 'svelte-headless-table/plugins'\n- import { readable } from 'svelte/store'\n-\n- const table = createTable(readable(data), {\n- sort: addSortBy(), filter: addColumnFilters(), page: addPagination(),\n- })\n- const columns = table.createColumns((t) => [\n- t.column({ accessor: 'name', header: 'Name' }),\n- t.column({ accessor: 'amount', header: 'Amount' }),\n- ])\n- const { headerRows, rows, tableAttrs, tableBodyAttrs } = table.createViewModel(columns)\n- </script>\n-\n- <table {...$tableAttrs}>\n- <thead> ...Subscribe over headerRows... </thead>\n- <tbody {...$tableBodyAttrs}> ...Subscribe over rows... </tbody>\n- </table>\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} showPagination />\n```\n\nType the column array against your row type. `GridColumns<(typeof data)[number]>`\nis the shortest form; a bare `GridColumns` widens the row to\n`Record<string, unknown>` and stops checking `field` against your real keys.\n\n## What you get for free\n\n- **The renderer.** No `createViewModel`, no `Subscribe`, no hand-built\n `<table>`. SvGrid ships virtualization, sticky headers, column\n resize, keyboard nav, and ARIA.\n- **Excel-style filter menu** and **cell-range selection + TSV copy**,\n which are BYO in svelte-headless-table.\n- **Inline editing** with typed editors and validation hooks.\n- **In-grid AI helpers** - natural-language filter, smart fill, summarise -\n free in `@svgrid/grid` against a model you register.\n- **Enterprise features** - Excel and PDF export, print, import and pivot -\n in one paid add-on; CSV, TSV and JSON export are free.\n\nIf you would rather keep driving your own `<table>`, the headless demo\nbelow does exactly that on `createSvGrid`, plugins replaced by features:\n\n<div data-docs-demo=\"186-headless-table\" data-height=\"520\"></div>\n\n## What changes\n\n- **Stores → runes.** Reactive data is `$state` / a plain array, not a\n Svelte store you pass to `createTable`. If your rows came from a `derived`\n store, read it with `$` at the call site or move it to `$derived`.\n- **Plugins → features.** Register `rowSortingFeature` etc. in\n `tableFeatures({...})` instead of `addSortBy()` in the plugin bag.\n- **View model → component.** You stop owning the markup; style through\n `--sg-*` tokens (and Tailwind) instead of `tableAttrs`.\n\n## What does not come across\n\n- **Custom `cell` renderers.** `createRender(MyComponent, props)` has no direct\n equivalent; SvGrid uses a `cell` snippet. The codemod preserves yours as a\n `// TODO port:` comment.\n- **Your own plugins.** There is no plugin system to port them into.\n- **`tableAttrs` / `attrs()` spreading.** The component owns its attributes.\n\n## When not to migrate\n\n- You need control of the exact DOM. Use the fork, or SvGrid's\n [headless core](../why-headless.md) at `@svgrid/grid/core`.\n- Your table is a handful of rows with no interaction. A plain `{#each}` is\n less code than either library.\n- You depend on custom plugins. That is a rewrite, not a migration.\n- You only need Svelte 5 support. Use the fork.\n\n## Frequently asked questions\n\n### How hard is it to move from svelte-headless-table to SvGrid?\n\nUsually 1-3 hours per grid, and `npx @svgrid/migrate` does the mechanical part.\nThe plugin-to-feature mapping is almost one-to-one; most of the work is deleting\nthe `createViewModel` + `Subscribe` + `<table>` markup, because SvGrid renders\nthat for you.\n\n### Does SvGrid use Svelte 5 runes instead of stores?\n\nYes. svelte-headless-table is built on Svelte 4 stores; SvGrid is Svelte-5\nnative (`$state` / `$derived` / `$effect`) with snippets for custom cells.\n\n### Is SvGrid still headless like svelte-headless-table?\n\nYes - `createSvGrid` plus the row-model factories is a headless engine you can\ndrive with your own markup, importable on its own from `@svgrid/grid/core`. The\ndifference is that SvGrid *also* ships a batteries-included `<SvGrid>` component\nso you usually do not have to.\n\n### Is svelte-headless-table still maintained?\n\nThe original's last publish date and Svelte 4 peer range are in the facts box\nat the top of the page, read from npm on the date shown, and its README says\nthere are no current plans for a Svelte 5 port. A community fork,\n`@humanspeak/svelte-headless-table`, is maintained and runs on Svelte 5 with\nthe same API; the facts box has its release line too. The fork is the\nlowest-effort option if you are happy with the library and only need Svelte 5.\n\n## What you end up with\n\nSorting, filtering and selection, on a library that still ships for Svelte 5.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable selectable />\n```\n\n## See also\n\n- [Upgrading a Svelte 4 table to Svelte 5](./svelte-5-upgrade-data-tables.md) - the whole upgrade run and captured, step by step\n- [SvGrid vs svelte-headless-table](https://svgrid.com/compare/svelte-headless-table/) - the side-by-side comparison, with a source and date for every claim\n- [Headless: build a table](./headless/build-a-table.md) - the demo above, step by step\n- [Migrating from TanStack Table](./migrating-from-tanstack-table.md) - sibling headless guide\n- [Why headless?](../why-headless.md) - the design rationale\n- [Architecture](./architecture.md) - the engine + render-component split\n"
6182
+ "markdown": "\n# Migrating from svelte-headless-table\n\nsvelte-headless-table popularised the headless-table pattern in the\nSvelte ecosystem. It is built on Svelte 4 stores and plugins\n(`addSortBy`, `addColumnFilters`, `addPagination`, ...), and it leaves\nthe markup to you. SvGrid keeps the same headless idea but runs on\nSvelte 5 runes and ships a render component, so the port mostly\n*removes* the table you used to hand-author.\n\n> Estimated effort: **1-3 hours** per grid. Most of the time is deleting\n> the `<table>` markup and `Subscribe` blocks you no longer need.\n\n<!-- facts:start svelte-headless-table pkg:@humanspeak/svelte-headless-table -->\n> **Facts, checked 9 Nov 2026.** `svelte-headless-table` 0.18.3, MIT, last published 28 Oct 2024, 96,400 npm downloads in the 30 days to 8 Nov 2026. `@humanspeak/svelte-headless-table` 7.1.0, MIT, last published 28 Oct 2026, 10,600 npm downloads in the same window. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026); `svelte-headless-table` 0.18.3 5.7 KB JS, no separate stylesheet, svelte external (measured 9 Nov 2026). svelte-headless-table pricing, as its site states it: svelte-headless-table is MIT and free; no paid licence or support is offered, and the author states there are no plans for a Svelte 5 port (https://github.com/bryanmylee/svelte-headless-table, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs svelte-headless-table](https://svgrid.com/compare/svelte-headless-table/).\n<!-- facts:end -->\n\n## Know your options first\n\nThe original package's last release and its Svelte 4 peer range are in the\nfacts box above, and its README states there are no current plans for a\nSvelte 5 port, so a Svelte 5 upgrade forces a decision. There are three\nhonest answers and you should know all of them:\n\n1. **`@humanspeak/svelte-headless-table`** - a maintained fork on Svelte 5 with\n the same API; its version, publish date and downloads are in the facts box\n too. Changing one package name is the cheapest path by a wide margin. If\n your table works and you only need Svelte 5, do that.\n2. **TanStack Table v9** - its Svelte adapter declares a Svelte 5 peer range.\n Still headless-only, so you keep writing and maintaining the markup.\n3. **SvGrid** - this page. A different trade: you delete the markup and take a\n renderer instead.\n\nPick SvGrid when the markup is the part you are tired of. Note that the blocker\nis not the syntax and not really the install either: `svelte-headless-table@0.18.3`\ndeclares `svelte@^4`, which npm 11 overrides with a warning (older npm needed\n`--legacy-peer-deps`), and the untouched component then type-checks clean in\nlegacy mode. Slots and `let:` still work in Svelte 5 - they are deprecated in\nfavour of snippets, not removed - so the `Subscribe` blocks below keep\nrendering. The trouble starts when that component moves to runes: the library\ntakes a store, your data is a rune, and the bridge between them is yours to\nwrite and maintain. We ran the whole upgrade and captured every line of it in\n[Upgrading a Svelte 4 table to Svelte 5](./svelte-5-upgrade-data-tables.md).\n\n## Run the codemod\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```bash\nnpx @svgrid/migrate # preview the result\nnpx @svgrid/migrate src --write # apply it\n```\n\nIt translates column definitions and plugin config, deletes the\n`Subscribe`/`Render` scaffolding, and reports anything it cannot map rather than\ndropping it silently. It previews by default. See\n[`@svgrid/migrate`](https://www.npmjs.com/package/@svgrid/migrate) for the full\nmapping and its limits.\n\n## Vocabulary cheat sheet\n\n| svelte-headless-table | sv-grid |\n| ----------------------------------------- | ----------------------------------------- |\n| `createTable(data, plugins)` | `createSvGrid({...})` or `<SvGrid>` |\n| `table.createColumns((t) => [...])` | `columns: ColumnDef[]` |\n| `t.column({ accessor: 'x', header })` | `{ field: 'x', header }` |\n| `t.column({ accessor: (r) => ... })` | `{ id, fieldFn: (r) => ... }` |\n| `t.group({ header, columns })` | `{ header, columns: [...] }` (column group) |\n| `addSortBy()` | `rowSortingFeature` |\n| `addColumnFilters()` / `addTableFilter()` | `columnFilteringFeature` |\n| `addPagination()` | Built in; toggle `showPagination` |\n| `addExpandedRows()` / `addSubRows()` | `rowExpandingFeature` |\n| `addGroupBy()` | `columnGroupingFeature` + `api.setGroupBy()` |\n| `addSelectedRows()` | `rowSelectionFeature` |\n| `addDataExport()` | `@svgrid/enterprise` export pack |\n| `createViewModel(columns)` + `Subscribe` | `<SvGrid>` (no view model to wire) |\n| `pluginStates.sort.sortKeys` | `api.setSort(id, dir)` / `onSortingChange` |\n\n### The shortcut form\n\nThat table maps plugins onto the headless *features*, which is what you want if\nyou keep driving the engine yourself. If you are moving to the `<SvGrid>`\ncomponent, every capability also has a boolean prop, and that is what the\ncodemod emits:\n\n| Plugin | `<SvGrid>` prop |\n| --- | --- |\n| `addSortBy()` | `sortable` |\n| `addTableFilter()` | `filterable showGlobalFilter` |\n| `addColumnFilters()` | `filterable showColumnFilters` |\n| `addPagination({ initialPageSize: 25 })` | `pageable pageSize={25}` |\n| `addSelectedRows()` | `showRowSelection` |\n| `addGroupBy()` | `groupable` |\n| `addSubRows()` | `treeData` |\n| `addColumnOrder()` | `enableColumnReorder` |\n| `addResizedColumns()` | nothing - resizing is built in |\n| `addHiddenColumns()` | `visible: false` on the column |\n| `addExpandedRows()` | `treeData`, or `isDetailRow` + `renderDetailRow` |\n| `addGridLayout()` | nothing - SvGrid owns its layout |\n\nEvery capability is off by default and turned on by its prop; there is no\nplugin registration step.\n\n## Before / after\n\n```diff\n- <script>\n- import { createTable } from 'svelte-headless-table'\n- import { addSortBy, addColumnFilters, addPagination } from 'svelte-headless-table/plugins'\n- import { readable } from 'svelte/store'\n-\n- const table = createTable(readable(data), {\n- sort: addSortBy(), filter: addColumnFilters(), page: addPagination(),\n- })\n- const columns = table.createColumns((t) => [\n- t.column({ accessor: 'name', header: 'Name' }),\n- t.column({ accessor: 'amount', header: 'Amount' }),\n- ])\n- const { headerRows, rows, tableAttrs, tableBodyAttrs } = table.createViewModel(columns)\n- </script>\n-\n- <table {...$tableAttrs}>\n- <thead> ...Subscribe over headerRows... </thead>\n- <tbody {...$tableBodyAttrs}> ...Subscribe over rows... </tbody>\n- </table>\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} showPagination />\n```\n\nType the column array against your row type. `GridColumns<(typeof data)[number]>`\nis the shortest form; a bare `GridColumns` widens the row to\n`Record<string, unknown>` and stops checking `field` against your real keys.\n\n## What you get for free\n\n- **The renderer.** No `createViewModel`, no `Subscribe`, no hand-built\n `<table>`. SvGrid ships virtualization, sticky headers, column\n resize, keyboard nav, and ARIA.\n- **Excel-style filter menu** and **cell-range selection + TSV copy**,\n which are BYO in svelte-headless-table.\n- **Inline editing** with typed editors and validation hooks.\n- **In-grid AI helpers** - natural-language filter, smart fill, summarise -\n free in `@svgrid/grid` against a model you register.\n- **Enterprise features** - Excel and PDF export, print, import and pivot -\n in one paid add-on; CSV, TSV and JSON export are free.\n\nIf you would rather keep driving your own `<table>`, the headless demo\nbelow does exactly that on `createSvGrid`, plugins replaced by features:\n\n<div data-docs-demo=\"186-headless-table\" data-height=\"520\"></div>\n\n## What changes\n\n- **Stores → runes.** Reactive data is `$state` / a plain array, not a\n Svelte store you pass to `createTable`. If your rows came from a `derived`\n store, read it with `$` at the call site or move it to `$derived`.\n- **Plugins → features.** Register `rowSortingFeature` etc. in\n `tableFeatures({...})` instead of `addSortBy()` in the plugin bag.\n- **View model → component.** You stop owning the markup; style through\n `--sg-*` tokens (and Tailwind) instead of `tableAttrs`.\n\n## What does not come across\n\n- **Custom `cell` renderers.** `createRender(MyComponent, props)` has no direct\n equivalent; SvGrid uses a `cell` snippet. The codemod preserves yours as a\n `// TODO port:` comment.\n- **Your own plugins.** There is no plugin system to port them into.\n- **`tableAttrs` / `attrs()` spreading.** The component owns its attributes.\n\n## When not to migrate\n\n- You need control of the exact DOM. Use the fork, or SvGrid's\n [headless core](../why-headless.md) at `@svgrid/grid/core`.\n- Your table is a handful of rows with no interaction. A plain `{#each}` is\n less code than either library.\n- You depend on custom plugins. That is a rewrite, not a migration.\n- You only need Svelte 5 support. Use the fork.\n\n## Frequently asked questions\n\n### How hard is it to move from svelte-headless-table to SvGrid?\n\nUsually 1-3 hours per grid, and `npx @svgrid/migrate` does the mechanical part.\nThe plugin-to-feature mapping is almost one-to-one; most of the work is deleting\nthe `createViewModel` + `Subscribe` + `<table>` markup, because SvGrid renders\nthat for you.\n\n### Does SvGrid use Svelte 5 runes instead of stores?\n\nYes. svelte-headless-table is built on Svelte 4 stores; SvGrid is Svelte-5\nnative (`$state` / `$derived` / `$effect`) with snippets for custom cells.\n\n### Is SvGrid still headless like svelte-headless-table?\n\nYes - `createSvGrid` plus the row-model factories is a headless engine you can\ndrive with your own markup, importable on its own from `@svgrid/grid/core`. The\ndifference is that SvGrid *also* ships a batteries-included `<SvGrid>` component\nso you usually do not have to.\n\n### Is svelte-headless-table still maintained?\n\nThe original's last publish date and Svelte 4 peer range are in the facts box\nat the top of the page, read from npm on the date shown, and its README says\nthere are no current plans for a Svelte 5 port. A community fork,\n`@humanspeak/svelte-headless-table`, is maintained and runs on Svelte 5 with\nthe same API; the facts box has its release line too. The fork is the\nlowest-effort option if you are happy with the library and only need Svelte 5.\n\n## What you end up with\n\nSorting, filtering and selection, on a library that still ships for Svelte 5.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable selectable />\n```\n\n## See also\n\n- [Upgrading a Svelte 4 table to Svelte 5](./svelte-5-upgrade-data-tables.md) - the whole upgrade run and captured, step by step\n- [SvGrid vs svelte-headless-table](https://svgrid.com/compare/svelte-headless-table/) - the side-by-side comparison, with a source and date for every claim\n- [Headless: build a table](./headless/build-a-table.md) - the demo above, step by step\n- [Migrating from TanStack Table](./migrating-from-tanstack-table.md) - sibling headless guide\n- [Why headless?](../why-headless.md) - the design rationale\n- [Architecture](./architecture.md) - the engine + render-component split\n"
6183
6183
  },
6184
6184
  {
6185
6185
  "slug": "help/migrating-from-syncfusion",
6186
6186
  "path": "docs/help/migrating-from-syncfusion.md",
6187
6187
  "title": "Migrating from Syncfusion Grid",
6188
6188
  "section": "Help",
6189
- "markdown": "# Migrating from Syncfusion Grid\n\nSyncfusion Grid is a comprehensive commercial grid across JavaScript,\nReact, Vue, Angular, and Blazor, with a free community license for\nqualifying small teams. Moving to SvGrid trades the multi-framework suite\nfor a Svelte-5-native grid with an unconditional MIT core.\n\n> Estimated effort: **3-6 hours** per grid.\n>\n> Syncfusion's option names vary across its framework flavours; map your\n> version's columns and events onto the SvGrid equivalents below.\n\n<!-- facts:start syncfusion-grid -->\n> **Facts, checked 9 Nov 2026.** `@syncfusion/ej2-grids` 35.1.42, Commercial (see licence file), last published 27 Oct 2026, 1,060,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026). Syncfusion Grid pricing, as its site states it: syncfusion.com lists the Grid SDK at $959 per developer per year and the UI Component Suite at $1,199 per developer per year, minimum five developers; a free Community License applies to companies and individuals with under $1M annual revenue, up to five developers and no more than ten employees (https://www.syncfusion.com/sales/products, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Syncfusion Grid](https://svgrid.com/compare/syncfusion-grid/).\n<!-- facts:end -->\n\n## Concept map\n\n| Syncfusion Grid | sv-grid |\n| ---------------------------------------- | ----------------------------------------- |\n| `columns: [{ field, headerText }]` | `columns: [{ field, header }]` |\n| `template` / cell template | `cell: (c) => renderSnippet(...)` |\n| `editSettings` + `editType` | `enableInlineEditing` + `editorType` |\n| `allowSorting` / `allowFiltering` | `rowSortingFeature` / `columnFilteringFeature` |\n| `allowGrouping` + `aggregates` | `columnGroupingFeature` + aggregates |\n| `detailTemplate` | `rowExpandingFeature` / master-detail rows |\n| `dataSource` (local / `DataManager`) | `data` array or `externalSort/Filter` |\n| `allowPaging` + `pageSettings` | `showPagination` |\n| `toolbar` export | `@svgrid/enterprise` export pack |\n\n## Shape of the change\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- <ejs-grid [dataSource]=\"rows\" [allowSorting]=\"true\" [allowFiltering]=\"true\"\n- [allowPaging]=\"true\" [editSettings]=\"{ allowEditing: true }\">\n- <e-columns>\n- <e-column field=\"name\" headerText=\"Name\"></e-column>\n- <e-column field=\"amount\" headerText=\"Amount\" format=\"C2\"></e-column>\n- </e-columns>\n- </ejs-grid>\n\n+ <SvGrid\n+ data={rows}\n+ columns={[\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]}\n+ features={tableFeatures({ rowSortingFeature, columnFilteringFeature })}\n+ showPagination enableInlineEditing />\n```\n\n## Why teams switch\n\n- **Svelte 5 native** instead of a multi-framework commercial suite.\n- **Unconditional MIT core** - no revenue / headcount threshold like the\n Syncfusion community license.\n- **Optional Enterprise pack** for export / import / pivot / AI.\n\n## What to weigh\n\n- Syncfusion ships **one of the largest feature sets and suites**\n available, plus Blazor support. If you need that breadth or Blazor,\n weigh it against the Svelte-native fit.\n\n## Frequently asked questions\n\n### Is SvGrid free, unlike the Syncfusion commercial license?\n\n`@svgrid/grid` is MIT - free for everyone, with no revenue or team-size\nconditions. Syncfusion's community license is free only for qualifying small\nteams; otherwise it is commercial.\n\n### How do Syncfusion columns map to SvGrid?\n\n`field` stays `field`, `headerText` becomes `header`, and `template` becomes a\n`renderSnippet` cell. Sorting / filtering / grouping move to registered\nfeatures.\n\n### Does SvGrid support Blazor?\n\nNo - SvGrid is Svelte 5 only. If you need Blazor, that is a genuine reason to\nstay on Syncfusion. For a Svelte stack, SvGrid is the native fit.\n\n## What you end up with\n\nSort, filter, group and inline edit - the four things a Syncfusion grid is usually doing.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} groupBy={['department']} groupable sortable filterable editable />\n```\n\n## See also\n\n- [SvGrid vs Syncfusion Grid](https://svgrid.com/compare/syncfusion-grid/) - the side-by-side comparison\n- [Data export and printing - Enterprise](./export.md) - the Enterprise export pack\n- [Getting started](../getting-started.md) - a working grid in ~15 lines\n"
6189
+ "markdown": "# Migrating from Syncfusion Grid\n\nSyncfusion Grid is a comprehensive commercial grid across JavaScript,\nReact, Vue, Angular, and Blazor, with a free community license for\nqualifying small teams. Moving to SvGrid trades the multi-framework suite\nfor a Svelte-5-native grid with an unconditional MIT core.\n\n> Estimated effort: **3-6 hours** per grid.\n>\n> Syncfusion's option names vary across its framework flavours; map your\n> version's columns and events onto the SvGrid equivalents below.\n\n<!-- facts:start syncfusion-grid -->\n> **Facts, checked 9 Nov 2026.** `@syncfusion/ej2-grids` 35.1.42, Commercial (see licence file), last published 27 Oct 2026, 1,060,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026). Syncfusion Grid pricing, as its site states it: syncfusion.com lists the Grid SDK at $959 per developer per year and the UI Component Suite at $1,199 per developer per year, minimum five developers; a free Community License applies to companies and individuals with under $1M annual revenue, up to five developers and no more than ten employees (https://www.syncfusion.com/sales/products, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Syncfusion Grid](https://svgrid.com/compare/syncfusion-grid/).\n<!-- facts:end -->\n\n## Concept map\n\n| Syncfusion Grid | sv-grid |\n| ---------------------------------------- | ----------------------------------------- |\n| `columns: [{ field, headerText }]` | `columns: [{ field, header }]` |\n| `template` / cell template | `cell: (c) => renderSnippet(...)` |\n| `editSettings` + `editType` | `enableInlineEditing` + `editorType` |\n| `allowSorting` / `allowFiltering` | `rowSortingFeature` / `columnFilteringFeature` |\n| `allowGrouping` + `aggregates` | `columnGroupingFeature` + aggregates |\n| `detailTemplate` | `rowExpandingFeature` / master-detail rows |\n| `dataSource` (local / `DataManager`) | `data` array or `externalSort/Filter` |\n| `allowPaging` + `pageSettings` | `showPagination` |\n| `toolbar` export | `@svgrid/enterprise` export pack |\n\n## Shape of the change\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- <ejs-grid [dataSource]=\"rows\" [allowSorting]=\"true\" [allowFiltering]=\"true\"\n- [allowPaging]=\"true\" [editSettings]=\"{ allowEditing: true }\">\n- <e-columns>\n- <e-column field=\"name\" headerText=\"Name\"></e-column>\n- <e-column field=\"amount\" headerText=\"Amount\" format=\"C2\"></e-column>\n- </e-columns>\n- </ejs-grid>\n\n+ <SvGrid\n+ data={rows}\n+ columns={[\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]}\n+ features={tableFeatures({ rowSortingFeature, columnFilteringFeature })}\n+ showPagination enableInlineEditing />\n```\n\n## Why teams switch\n\n- **Svelte 5 native** instead of a multi-framework commercial suite.\n- **Unconditional MIT core** - no revenue / headcount threshold like the\n Syncfusion community license.\n- **Optional Enterprise pack** for export / import / pivot / AI.\n\n## What to weigh\n\n- Syncfusion ships **one of the largest feature sets and suites**\n available, plus Blazor support. If you need that breadth or Blazor,\n weigh it against the Svelte-native fit.\n\n## Frequently asked questions\n\n### Is SvGrid free, unlike the Syncfusion commercial license?\n\n`@svgrid/grid` is MIT - free for everyone, with no revenue or team-size\nconditions. Syncfusion's community license is free only for qualifying small\nteams; otherwise it is commercial.\n\n### How do Syncfusion columns map to SvGrid?\n\n`field` stays `field`, `headerText` becomes `header`, and `template` becomes a\n`renderSnippet` cell. Sorting / filtering / grouping move to registered\nfeatures.\n\n### Does SvGrid support Blazor?\n\nNo - SvGrid is Svelte 5 only. If you need Blazor, that is a genuine reason to\nstay on Syncfusion. For a Svelte stack, SvGrid is the native fit.\n\n## What you end up with\n\nSort, filter, group and inline edit - the four things a Syncfusion grid is usually doing.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} groupBy={['department']} groupable sortable filterable editable />\n```\n\n## See also\n\n- [SvGrid vs Syncfusion Grid](https://svgrid.com/compare/syncfusion-grid/) - the side-by-side comparison\n- [Data export and printing - Enterprise](./export.md) - the Enterprise export pack\n- [Getting started](../getting-started.md) - a working grid in ~15 lines\n"
6190
6190
  },
6191
6191
  {
6192
6192
  "slug": "help/migrating-from-tabulator",
6193
6193
  "path": "docs/help/migrating-from-tabulator.md",
6194
6194
  "title": "Migrating from Tabulator",
6195
6195
  "section": "Help",
6196
- "markdown": "# Migrating from Tabulator\n\nTabulator is a feature-rich vanilla-JS table you instantiate against a\nDOM element and drive imperatively (`table.setData(...)`,\n`table.on('cellEdited', ...)`). SvGrid covers a similar feature surface\nbut as a Svelte 5 component: data is a reactive `$state` array, custom\ncells are snippets, and there is no manual mount / teardown.\n\n> Estimated effort: **2-4 hours** per grid - column translation plus\n> swapping imperative `setData` for reactive state.\n\n<!-- facts:start tabulator -->\n> **Facts, checked 9 Nov 2026.** `tabulator-tables` 6.7.1, MIT, last published 22 Oct 2026, 826,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026); `tabulator-tables` 6.7.1 109.5 KB JS + 3.8 KB CSS (measured 9 Nov 2026). Tabulator pricing, as its site states it: Tabulator is MIT and free; no licence or support plan is sold (https://github.com/olifolkerd/tabulator, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Tabulator](https://svgrid.com/compare/tabulator/).\n<!-- facts:end -->\n\n## Vocabulary cheat sheet\n\n| Tabulator | sv-grid |\n| -------------------------------------- | ----------------------------------------- |\n| `new Tabulator(el, { data, columns })` | `<SvGrid data={...} columns={...} />` |\n| `{ title: 'Name', field: 'name' }` | `{ header: 'Name', field: 'name' }` |\n| `formatter: fn` / `formatter: 'money'` | `cell: (c) => renderSnippet(...)` or `format` |\n| `editor: 'input' / 'number' / ...` | `editorType: 'text' / 'number' / ...` |\n| `headerFilter: true` | `columnFilteringFeature` |\n| `dataTree: true` | `rowExpandingFeature` + tree row shape |\n| `table.setData(rows)` | reassign the `$state` data array |\n| `table.on('cellEdited', ...)` | `onCellValueChange` |\n| `table.setSort(field, dir)` | `api.setSort(field, dir)` |\n| `layout: 'fitColumns'` | `fitColumns` prop |\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- import { TabulatorFull as Tabulator } from 'tabulator-tables'\n-\n- const table = new Tabulator('#grid', {\n- data: rows,\n- layout: 'fitColumns',\n- columns: [\n- { title: 'Name', field: 'name' },\n- { title: 'Amount', field: 'amount', formatter: 'money', editor: 'number' },\n- ],\n- })\n- table.on('cellEdited', (cell) => save(cell.getData()))\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' }, editorType: 'number' },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} fitColumns enableInlineEditing\n+ onCellValueChange={(e) => save(e)} />\n```\n\n## What changes\n\n- **Imperative → reactive.** No `setData()` - reassign the `$state`\n array and the grid updates.\n- **String formatters → snippets.** Custom cells are Svelte snippets /\n components, not HTML-string formatters.\n- **Mount / teardown disappears.** No `new Tabulator(el)` and no manual\n destroy on unmount.\n\n## Frequently asked questions\n\n### Is migrating from Tabulator to SvGrid hard?\n\nIt is a configuration translation plus one mindset shift: you stop calling\n`setData()` and instead let a reactive `$state` array drive the grid. Budget\n2-4 hours per grid.\n\n### Is SvGrid free like Tabulator?\n\nYes. `@svgrid/grid` is MIT-licensed like Tabulator. The optional\n`@svgrid/enterprise` pack (export, import, pivot, AI) is the only paid piece.\n\n### Can I keep Tabulator's custom formatters?\n\nYou re-create them as Svelte snippets via `renderSnippet`. Any Svelte\ncomponent or markup works, not just an HTML string.\n\n## What you end up with\n\nSort, filter and edit, with pagination underneath.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable editable pageable pageSize={3} />\n```\n\n## See also\n\n- [SvGrid vs Tabulator](https://svgrid.com/compare/tabulator/) - the side-by-side comparison\n- [Cell components](./cells/cell-components.md) - snippet-based custom cells\n- [Architecture](./architecture.md) - engine + render-component split\n"
6196
+ "markdown": "# Migrating from Tabulator\n\nTabulator is a feature-rich vanilla-JS table you instantiate against a\nDOM element and drive imperatively (`table.setData(...)`,\n`table.on('cellEdited', ...)`). SvGrid covers a similar feature surface\nbut as a Svelte 5 component: data is a reactive `$state` array, custom\ncells are snippets, and there is no manual mount / teardown.\n\n> Estimated effort: **2-4 hours** per grid - column translation plus\n> swapping imperative `setData` for reactive state.\n\n<!-- facts:start tabulator -->\n> **Facts, checked 9 Nov 2026.** `tabulator-tables` 6.7.1, MIT, last published 22 Oct 2026, 826,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026); `tabulator-tables` 6.7.1 109.5 KB JS + 3.8 KB CSS (measured 9 Nov 2026). Tabulator pricing, as its site states it: Tabulator is MIT and free; no licence or support plan is sold (https://github.com/olifolkerd/tabulator, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Tabulator](https://svgrid.com/compare/tabulator/).\n<!-- facts:end -->\n\n## Vocabulary cheat sheet\n\n| Tabulator | sv-grid |\n| -------------------------------------- | ----------------------------------------- |\n| `new Tabulator(el, { data, columns })` | `<SvGrid data={...} columns={...} />` |\n| `{ title: 'Name', field: 'name' }` | `{ header: 'Name', field: 'name' }` |\n| `formatter: fn` / `formatter: 'money'` | `cell: (c) => renderSnippet(...)` or `format` |\n| `editor: 'input' / 'number' / ...` | `editorType: 'text' / 'number' / ...` |\n| `headerFilter: true` | `columnFilteringFeature` |\n| `dataTree: true` | `rowExpandingFeature` + tree row shape |\n| `table.setData(rows)` | reassign the `$state` data array |\n| `table.on('cellEdited', ...)` | `onCellValueChange` |\n| `table.setSort(field, dir)` | `api.setSort(field, dir)` |\n| `layout: 'fitColumns'` | `fitColumns` prop |\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- import { TabulatorFull as Tabulator } from 'tabulator-tables'\n-\n- const table = new Tabulator('#grid', {\n- data: rows,\n- layout: 'fitColumns',\n- columns: [\n- { title: 'Name', field: 'name' },\n- { title: 'Amount', field: 'amount', formatter: 'money', editor: 'number' },\n- ],\n- })\n- table.on('cellEdited', (cell) => save(cell.getData()))\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' }, editorType: 'number' },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} fitColumns enableInlineEditing\n+ onCellValueChange={(e) => save(e)} />\n```\n\n## What changes\n\n- **Imperative → reactive.** No `setData()` - reassign the `$state`\n array and the grid updates.\n- **String formatters → snippets.** Custom cells are Svelte snippets /\n components, not HTML-string formatters.\n- **Mount / teardown disappears.** No `new Tabulator(el)` and no manual\n destroy on unmount.\n\n## Frequently asked questions\n\n### Is migrating from Tabulator to SvGrid hard?\n\nIt is a configuration translation plus one mindset shift: you stop calling\n`setData()` and instead let a reactive `$state` array drive the grid. Budget\n2-4 hours per grid.\n\n### Is SvGrid free like Tabulator?\n\nYes. `@svgrid/grid` is MIT-licensed like Tabulator. The optional\n`@svgrid/enterprise` pack (export, import, pivot, AI) is the only paid piece.\n\n### Can I keep Tabulator's custom formatters?\n\nYou re-create them as Svelte snippets via `renderSnippet`. Any Svelte\ncomponent or markup works, not just an HTML string.\n\n## What you end up with\n\nSort, filter and edit, with pagination underneath.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable editable pageable pageSize={3} />\n```\n\n## See also\n\n- [SvGrid vs Tabulator](https://svgrid.com/compare/tabulator/) - the side-by-side comparison\n- [Cell components](./cells/cell-components.md) - snippet-based custom cells\n- [Architecture](./architecture.md) - engine + render-component split\n"
6197
6197
  },
6198
6198
  {
6199
6199
  "slug": "help/migrating-from-tanstack-table",
6200
6200
  "path": "docs/help/migrating-from-tanstack-table.md",
6201
6201
  "title": "Migrating from TanStack Table",
6202
6202
  "section": "Help",
6203
- "markdown": "# Migrating from TanStack Table\n\nTanStack Table (formerly React Table) is the closest conceptual\nsibling to sv-grid - both are \"headless data grid\" libraries with\nexplicit row-model pipelines, and the v9 Svelte adapter,\n`@tanstack/svelte-table`, targets Svelte 5 with the same runes-first\nshape. If you already think in `createTable()` + a features object,\nthis is a half-day port; the vocabulary below covers the v8 names too.\n\n> Estimated effort: **30 min** per grid for read-only views, **2-4\n> hours** for editing-heavy grids.\n\n<!-- facts:start tanstack-table -->\n> **Facts, checked 9 Nov 2026.** `@tanstack/svelte-table` 9.3.1, MIT, last published 12 Oct 2026, 539,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026); `@tanstack/svelte-table` 9.3.1 36.5 KB JS, no separate stylesheet, svelte external (measured 9 Nov 2026). TanStack Table pricing, as its site states it: TanStack Table is MIT and free; tanstack.com is sponsor-supported and offers Enterprise Support as private consulting and expert support, with no licence sold for the table (https://tanstack.com/table/latest, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs TanStack Table (Svelte)](https://svgrid.com/compare/tanstack-table/).\n<!-- facts:end -->\n\n> **On v9?** SvGrid exports the same feature vocabulary, so most of this\n> page is automated. Run `npx @svgrid/migrate src` to preview the port, and\n> see [Migrating from the shadcn-svelte data table](./migrating-from-shadcn-data-table.md)\n> if that is where your table came from.\n\n## Vocabulary cheat sheet\n\n| TanStack Table | sv-grid |\n| ------------------------------- | ---------------------------------------- |\n| `useReactTable({...})` | `createSvGrid({...})` or `<SvGrid>` |\n| `getCoreRowModel()` | `createCoreRowModel()` |\n| `getSortedRowModel()` | Auto-registered by `rowSortingFeature` |\n| `getFilteredRowModel()` | Auto-registered by `columnFilteringFeature` |\n| `getPaginationRowModel()` | Built in; toggle with `showPagination` |\n| `getGroupedRowModel()` | `columnGroupingFeature` + `api.setGroupBy()` |\n| `getExpandedRowModel()` | `rowExpandingFeature` |\n| `flexRender(col.cell, ctx)` | `renderSnippet(MyCell, props)` OR string field |\n| `columnHelper.accessor('field')` | `{ field: 'field' }` directly |\n| `table.getRowModel().rows` | `api.getDisplayedRows()` |\n| `table.setColumnFilters(...)` | `api.setFilter(id, {...})` per column |\n| `meta` (column / table) | n/a - use column `cellClass` / `cell` instead |\n\n## Imports\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- import {\n- useReactTable, getCoreRowModel, getSortedRowModel, getFilteredRowModel,\n- flexRender, createColumnHelper,\n- } from '@tanstack/react-table'\n\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ renderSnippet,\n+ } from '@svgrid/grid'\n```\n\n## Column definitions\n\n```diff\n- const columnHelper = createColumnHelper<Order>()\n- const columns = [\n- columnHelper.accessor('orderId', { header: 'Order ID' }),\n- columnHelper.accessor('amount', { header: 'Amount', cell: ({ getValue }) => fmt(getValue<number>()) }),\n- ]\n\n+ const columns: ColumnDef<typeof features, Order>[] = [\n+ { field: 'orderId', header: 'Order ID' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n```\n\nThe `fieldFn` form is the same:\n\n```diff\n- columnHelper.accessor((row) => row.profile.name, { id: 'name', header: 'Name' })\n\n+ { id: 'name', fieldFn: (row) => row.profile.name, header: 'Name' }\n```\n\n## Mounting\n\n```diff\n- const table = useReactTable({\n- data, columns,\n- getCoreRowModel: getCoreRowModel(),\n- getSortedRowModel: getSortedRowModel(),\n- getFilteredRowModel: getFilteredRowModel(),\n- })\n- return (\n- <table>\n- <thead>{table.getHeaderGroups().map(/* ... */)}</thead>\n- <tbody>{table.getRowModel().rows.map(/* ... */)}</tbody>\n- </table>\n- )\n\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+\n+ <SvGrid data={rows} columns={columns} features={features} />\n```\n\nSv-grid bundles the render + virtualization. No `<table>` you have\nto author yourself.\n\n## Imperative state\n\n| TanStack Table | sv-grid |\n| ------------------------------------------- | ---------------------------------------- |\n| `table.setColumnFilters([{id, value}])` | `api.setFilter(id, { operator: 'contains', value })` |\n| `table.getColumn('id')?.setFilterValue(v)` | `api.setFilter(id, { operator: 'contains', value: v })` |\n| `table.setSorting([{id, desc}])` | `api.setSort(id, desc ? 'desc' : 'asc')` |\n| `table.setRowSelection(state)` | n/a - use `api.clearRowSelection()` + UI events |\n| `table.toggleAllRowsExpanded()` | `api.expandAllGroups()` |\n| `table.getColumn('x').toggleVisibility()` | `api.setColumnVisible('x', false)` |\n| `table.options.meta?.foo` | Pass through component props / `$state` |\n\n## Custom cells\n\n```diff\n- {\n- header: 'Status',\n- cell: ({ row }) => <Badge tone={row.original.status} />,\n- }\n\n+ {\n+ field: 'status', header: 'Status',\n+ cell: (ctx) => renderSnippet(StatusCell, { tone: ctx.row.original.status }),\n+ }\n```\n\n`renderSnippet` accepts any Svelte 5 snippet; `renderComponent`\naccepts a regular component if you prefer SFCs.\n\n## Server-side data\n\n```diff\n- const [pagination, setPagination] = useState({pageIndex: 0, pageSize: 25})\n- const [sorting, setSorting] = useState([])\n- const table = useReactTable({\n- data, columns, manualPagination: true, manualSorting: true,\n- state: { pagination, sorting },\n- onPaginationChange: setPagination,\n- onSortingChange: setSorting,\n- })\n\n+ <SvGrid\n+ data={rows} columns={columns} features={features}\n+ externalSort={true}\n+ externalFilter={true}\n+ onSortingChange={(clauses) => refetch({ sort: clauses })}\n+ onFiltersChange={(f) => refetch({ filters: f.columns })}\n+ />\n```\n\nOr hand the fetching to a controller and pass it as one prop:\n`createServerDataSource(source, { mode: 'infinite' })` owns the blocks,\nthe sort and filter round trips and the placeholder rows, and the\nmanual-flag wiring above disappears. TanStack Table has no server row\nmodel; per-group fetching is yours to write, where the Enterprise\n`createServerRowModel` does it over the same contract.\n\n<div data-docs-demo=\"148-server-row-model\" data-height=\"480\"></div>\n\n## What you get for free vs TanStack Table\n\n- **Renderer**. TanStack is headless-only; you draw the `<table>`.\n Sv-grid ships an opinionated, fast renderer with virtualization,\n scroll, sticky headers, column resize, keyboard nav, ARIA.\n- **Inline editing**. `editorType: 'text' | 'number' | 'date' |\n 'list' | ...` - built-in editors with parsing + validation hooks.\n- **CSP-clean**. No `eval`. The shipped tests confirm.\n- **In-grid AI helpers**. Natural-language filter, smart fill, summarise\n and classify, free in `@svgrid/grid` against a model you register.\n- **Enterprise features**. Excel and PDF export, print, import and pivot\n in one paid add-on; CSV, TSV and JSON export are free.\n\nThe headless demo below is the shape a TanStack app has today - a plain\n`<table>` driven by the engine - running on `createSvGrid`:\n\n<div data-docs-demo=\"186-headless-table\" data-height=\"520\"></div>\n\n## What you give up\n\n- **One engine across frameworks.** TanStack has adapters for React,\n Vue, Solid, Qwik, Lit and Svelte; sv-grid is Svelte 5-native and has\n no React wrapper.\n- **The smallest engine-only bundle.** The facts box at the top of the\n page has both packages measured the same way; the difference is the\n renderer, virtualizer, filter UI and editors you would otherwise write.\n- **TanStack Virtual and the shadcn-svelte data table recipe.** Sv-grid\n virtualizes on its own and has its own\n [shadcn-svelte guide](./migrating-from-shadcn-data-table.md).\n- **`meta` for arbitrary side-channel state.** Pass props directly.\n- **`@tanstack/match-sorter-utils` integration**. The grid's filter\n has a `contains` operator; if you need fuzzy match, plug your\n matcher in via the column's `cell` snippet or use\n `externalFilter={true}` and run the matcher yourself.\n\n## Frequently asked questions\n\n### How long does it take to migrate from TanStack Table to SvGrid?\n\nAbout 30 minutes per read-only grid and 2-4 hours for editing-heavy grids.\nBoth libraries use explicit row-model pipelines, so `createTable()` +\n`getCoreRowModel()` maps almost directly onto `createSvGrid()` +\n`createCoreRowModel()`.\n\n### Why switch from TanStack Table to SvGrid on Svelte 5?\n\nTanStack Table is headless-only and multi-framework, so you build the entire\nDOM, virtualization, filter UI, and editing layer yourself. SvGrid keeps the\nheadless core but ships a batteries-included `<SvGrid>` render component -\nvirtualization, Excel-style filters, cell selection, and inline editing work\nin one prop pass.\n\n### Is SvGrid free like TanStack Table?\n\nYes - `@svgrid/grid` is MIT-licensed, like TanStack Table. SvGrid\nadditionally offers an optional paid `@svgrid/enterprise` pack for Excel and\nPDF export, print, pivot and import, which TanStack Table does not provide at\nall; TanStack sells Enterprise Support as consulting instead, as the facts box\nabove notes.\n\n### Does the TanStack Svelte adapter support Svelte 5?\n\nYes. The v9 line of `@tanstack/svelte-table` declares a Svelte 5 peer range\nand reads rune data through getters; the version in the facts box above is\nthe one read from npm. If you are on the v8 adapter with Svelte 4 stores,\nthe port to sv-grid is the same work as the port to v9, minus the markup.\n\n## What you end up with\n\nThe same model you had, with the rendering already written.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable pageable pageSize={3} selectable />\n```\n\n## See also\n\n- [SvGrid vs TanStack Table](https://svgrid.com/compare/tanstack-table/) -\n the side-by-side comparison, with a source and date for every claim\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](./comparison.md) -\n the measured benchmark, TanStack column included\n- [Architecture](./architecture.md) - the headless engine + render\n component split\n- [Migrating from AG Grid](./migrating-from-ag-grid.md) - sibling guide\n- [Why headless?](../why-headless.md) - the design rationale\n"
6203
+ "markdown": "# Migrating from TanStack Table\n\nTanStack Table (formerly React Table) is the closest conceptual\nsibling to sv-grid - both are \"headless data grid\" libraries with\nexplicit row-model pipelines, and the v9 Svelte adapter,\n`@tanstack/svelte-table`, targets Svelte 5 with the same runes-first\nshape. If you already think in `createTable()` + a features object,\nthis is a half-day port; the vocabulary below covers the v8 names too.\n\n> Estimated effort: **30 min** per grid for read-only views, **2-4\n> hours** for editing-heavy grids.\n\n<!-- facts:start tanstack-table -->\n> **Facts, checked 9 Nov 2026.** `@tanstack/svelte-table` 9.3.1, MIT, last published 12 Oct 2026, 539,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026); `@tanstack/svelte-table` 9.3.1 36.5 KB JS, no separate stylesheet, svelte external (measured 9 Nov 2026). TanStack Table pricing, as its site states it: TanStack Table is MIT and free; tanstack.com is sponsor-supported and offers Enterprise Support as private consulting and expert support, with no licence sold for the table (https://tanstack.com/table/latest, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs TanStack Table (Svelte)](https://svgrid.com/compare/tanstack-table/).\n<!-- facts:end -->\n\n> **On v9?** SvGrid exports the same feature vocabulary, so most of this\n> page is automated. Run `npx @svgrid/migrate src` to preview the port, and\n> see [Migrating from the shadcn-svelte data table](./migrating-from-shadcn-data-table.md)\n> if that is where your table came from.\n\n## Vocabulary cheat sheet\n\n| TanStack Table | sv-grid |\n| ------------------------------- | ---------------------------------------- |\n| `useReactTable({...})` | `createSvGrid({...})` or `<SvGrid>` |\n| `getCoreRowModel()` | `createCoreRowModel()` |\n| `getSortedRowModel()` | Auto-registered by `rowSortingFeature` |\n| `getFilteredRowModel()` | Auto-registered by `columnFilteringFeature` |\n| `getPaginationRowModel()` | Built in; toggle with `showPagination` |\n| `getGroupedRowModel()` | `columnGroupingFeature` + `api.setGroupBy()` |\n| `getExpandedRowModel()` | `rowExpandingFeature` |\n| `flexRender(col.cell, ctx)` | `renderSnippet(MyCell, props)` OR string field |\n| `columnHelper.accessor('field')` | `{ field: 'field' }` directly |\n| `table.getRowModel().rows` | `api.getDisplayedRows()` |\n| `table.setColumnFilters(...)` | `api.setFilter(id, {...})` per column |\n| `meta` (column / table) | n/a - use column `cellClass` / `cell` instead |\n\n## Imports\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- import {\n- useReactTable, getCoreRowModel, getSortedRowModel, getFilteredRowModel,\n- flexRender, createColumnHelper,\n- } from '@tanstack/react-table'\n\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ renderSnippet,\n+ } from '@svgrid/grid'\n```\n\n## Column definitions\n\n```diff\n- const columnHelper = createColumnHelper<Order>()\n- const columns = [\n- columnHelper.accessor('orderId', { header: 'Order ID' }),\n- columnHelper.accessor('amount', { header: 'Amount', cell: ({ getValue }) => fmt(getValue<number>()) }),\n- ]\n\n+ const columns: ColumnDef<typeof features, Order>[] = [\n+ { field: 'orderId', header: 'Order ID' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n```\n\nThe `fieldFn` form is the same:\n\n```diff\n- columnHelper.accessor((row) => row.profile.name, { id: 'name', header: 'Name' })\n\n+ { id: 'name', fieldFn: (row) => row.profile.name, header: 'Name' }\n```\n\n## Mounting\n\n```diff\n- const table = useReactTable({\n- data, columns,\n- getCoreRowModel: getCoreRowModel(),\n- getSortedRowModel: getSortedRowModel(),\n- getFilteredRowModel: getFilteredRowModel(),\n- })\n- return (\n- <table>\n- <thead>{table.getHeaderGroups().map(/* ... */)}</thead>\n- <tbody>{table.getRowModel().rows.map(/* ... */)}</tbody>\n- </table>\n- )\n\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+\n+ <SvGrid data={rows} columns={columns} features={features} />\n```\n\nSv-grid bundles the render + virtualization. No `<table>` you have\nto author yourself.\n\n## Imperative state\n\n| TanStack Table | sv-grid |\n| ------------------------------------------- | ---------------------------------------- |\n| `table.setColumnFilters([{id, value}])` | `api.setFilter(id, { operator: 'contains', value })` |\n| `table.getColumn('id')?.setFilterValue(v)` | `api.setFilter(id, { operator: 'contains', value: v })` |\n| `table.setSorting([{id, desc}])` | `api.setSort(id, desc ? 'desc' : 'asc')` |\n| `table.setRowSelection(state)` | n/a - use `api.clearRowSelection()` + UI events |\n| `table.toggleAllRowsExpanded()` | `api.expandAllGroups()` |\n| `table.getColumn('x').toggleVisibility()` | `api.setColumnVisible('x', false)` |\n| `table.options.meta?.foo` | Pass through component props / `$state` |\n\n## Custom cells\n\n```diff\n- {\n- header: 'Status',\n- cell: ({ row }) => <Badge tone={row.original.status} />,\n- }\n\n+ {\n+ field: 'status', header: 'Status',\n+ cell: (ctx) => renderSnippet(StatusCell, { tone: ctx.row.original.status }),\n+ }\n```\n\n`renderSnippet` accepts any Svelte 5 snippet; `renderComponent`\naccepts a regular component if you prefer SFCs.\n\n## Server-side data\n\n```diff\n- const [pagination, setPagination] = useState({pageIndex: 0, pageSize: 25})\n- const [sorting, setSorting] = useState([])\n- const table = useReactTable({\n- data, columns, manualPagination: true, manualSorting: true,\n- state: { pagination, sorting },\n- onPaginationChange: setPagination,\n- onSortingChange: setSorting,\n- })\n\n+ <SvGrid\n+ data={rows} columns={columns} features={features}\n+ externalSort={true}\n+ externalFilter={true}\n+ onSortingChange={(clauses) => refetch({ sort: clauses })}\n+ onFiltersChange={(f) => refetch({ filters: f.columns })}\n+ />\n```\n\nOr hand the fetching to a controller and pass it as one prop:\n`createServerDataSource(source, { mode: 'infinite' })` owns the blocks,\nthe sort and filter round trips and the placeholder rows, and the\nmanual-flag wiring above disappears. TanStack Table has no server row\nmodel; per-group fetching is yours to write, where the Enterprise\n`createServerRowModel` does it over the same contract.\n\n<div data-docs-demo=\"148-server-row-model\" data-height=\"480\"></div>\n\n## What you get for free vs TanStack Table\n\n- **Renderer**. TanStack is headless-only; you draw the `<table>`.\n Sv-grid ships an opinionated, fast renderer with virtualization,\n scroll, sticky headers, column resize, keyboard nav, ARIA.\n- **Inline editing**. `editorType: 'text' | 'number' | 'date' |\n 'list' | ...` - built-in editors with parsing + validation hooks.\n- **CSP-clean**. No `eval`. The shipped tests confirm.\n- **In-grid AI helpers**. Natural-language filter, smart fill, summarise\n and classify, free in `@svgrid/grid` against a model you register.\n- **Enterprise features**. Excel and PDF export, print, import and pivot\n in one paid add-on; CSV, TSV and JSON export are free.\n\nThe headless demo below is the shape a TanStack app has today - a plain\n`<table>` driven by the engine - running on `createSvGrid`:\n\n<div data-docs-demo=\"186-headless-table\" data-height=\"520\"></div>\n\n## What you give up\n\n- **One engine across frameworks.** TanStack has adapters for React,\n Vue, Solid, Qwik, Lit and Svelte; sv-grid is Svelte 5-native and has\n no React wrapper.\n- **The smallest engine-only bundle.** The facts box at the top of the\n page has both packages measured the same way; the difference is the\n renderer, virtualizer, filter UI and editors you would otherwise write.\n- **TanStack Virtual and the shadcn-svelte data table recipe.** Sv-grid\n virtualizes on its own and has its own\n [shadcn-svelte guide](./migrating-from-shadcn-data-table.md).\n- **`meta` for arbitrary side-channel state.** Pass props directly.\n- **`@tanstack/match-sorter-utils` integration**. The grid's filter\n has a `contains` operator; if you need fuzzy match, plug your\n matcher in via the column's `cell` snippet or use\n `externalFilter={true}` and run the matcher yourself.\n\n## Frequently asked questions\n\n### How long does it take to migrate from TanStack Table to SvGrid?\n\nAbout 30 minutes per read-only grid and 2-4 hours for editing-heavy grids.\nBoth libraries use explicit row-model pipelines, so `createTable()` +\n`getCoreRowModel()` maps almost directly onto `createSvGrid()` +\n`createCoreRowModel()`.\n\n### Why switch from TanStack Table to SvGrid on Svelte 5?\n\nTanStack Table is headless-only and multi-framework, so you build the entire\nDOM, virtualization, filter UI, and editing layer yourself. SvGrid keeps the\nheadless core but ships a batteries-included `<SvGrid>` render component -\nvirtualization, Excel-style filters, cell selection, and inline editing work\nin one prop pass.\n\n### Is SvGrid free like TanStack Table?\n\nYes - `@svgrid/grid` is MIT-licensed, like TanStack Table. SvGrid\nadditionally offers an optional paid `@svgrid/enterprise` pack for Excel and\nPDF export, print, pivot and import, which TanStack Table does not provide at\nall; TanStack sells Enterprise Support as consulting instead, as the facts box\nabove notes.\n\n### Does the TanStack Svelte adapter support Svelte 5?\n\nYes. The v9 line of `@tanstack/svelte-table` declares a Svelte 5 peer range\nand reads rune data through getters; the version in the facts box above is\nthe one read from npm. If you are on the v8 adapter with Svelte 4 stores,\nthe port to sv-grid is the same work as the port to v9, minus the markup.\n\n## What you end up with\n\nThe same model you had, with the rendering already written.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable pageable pageSize={3} selectable />\n```\n\n## See also\n\n- [SvGrid vs TanStack Table](https://svgrid.com/compare/tanstack-table/) -\n the side-by-side comparison, with a source and date for every claim\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](./comparison.md) -\n the measured benchmark, TanStack column included\n- [Architecture](./architecture.md) - the headless engine + render\n component split\n- [Migrating from AG Grid](./migrating-from-ag-grid.md) - sibling guide\n- [Why headless?](../why-headless.md) - the design rationale\n"
6204
6204
  },
6205
6205
  {
6206
6206
  "slug": "help/migrating-from-ui-kit-tables",
6207
6207
  "path": "docs/help/migrating-from-ui-kit-tables.md",
6208
6208
  "title": "Migrating from a UI-kit table (Flowbite / Skeleton / shadcn-svelte)",
6209
6209
  "section": "Help",
6210
- "markdown": "\n# Migrating from a UI-kit table (Flowbite / Skeleton / shadcn-svelte)\n\nFlowbite-Svelte, Skeleton, and shadcn-svelte all ship a styled `<Table>`\ncomponent. They are presentation components: they render the rows you\npass and match your design tokens, but sorting, filtering,\nvirtualization, and editing are yours to write by hand. Moving to SvGrid\nreplaces that hand-rolled logic with built-in features - while still\nletting you match the design system.\n\n> **Not the shadcn-svelte data table.** That one is a separate recipe\n> built on TanStack Table v9, and it already does sorting, filtering,\n> pagination, and row selection. If that is what you have, read\n> [Migrating from the shadcn-svelte data table](./migrating-from-shadcn-data-table.md)\n> instead - the port is different, and smaller.\n\n<!-- facts:start svelte-ui-kit-tables -->\n> **Facts, checked 9 Nov 2026.** `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the 30 days to 8 Nov 2026. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026). Flowbite / Skeleton / shadcn-svelte tables pricing, as its site states it: Flowbite Svelte, Skeleton and shadcn-svelte are MIT component libraries; their table components are free and no grid licence is sold (https://github.com/themesberg/flowbite-svelte, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Flowbite / Skeleton / shadcn-svelte tables](https://svgrid.com/compare/svelte-ui-kit-tables/).\n<!-- facts:end -->\n\n> Estimated effort: **30 min - 1 hour** per table. You are mostly\n> deleting `{#each}` markup and the sort / filter state you wrote\n> yourself.\n\n## When this guide applies\n\nYou have a table that started simple and has grown:\n\n- You added a click-to-sort handler and a sort-state variable.\n- You added a search box and an array `.filter(...)`.\n- The list got long and now you want virtualization or pagination.\n- You started editing cells inline and it got messy.\n\nThat is the moment a styled `<Table>` stops paying for itself.\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- <script>\n- import { Table, TableHead, TableHeadCell, TableBody, TableBodyRow, TableBodyCell } from 'flowbite-svelte'\n- let sortKey = 'name', asc = true\n- $: sorted = [...rows].sort((a, b) => (a[sortKey] > b[sortKey] ? 1 : -1) * (asc ? 1 : -1))\n- </script>\n-\n- <Table>\n- <TableHead>\n- <TableHeadCell on:click={() => (sortKey = 'name')}>Name</TableHeadCell>\n- <TableHeadCell on:click={() => (sortKey = 'amount')}>Amount</TableHeadCell>\n- </TableHead>\n- <TableBody>\n- {#each sorted as row}\n- <TableBodyRow>\n- <TableBodyCell>{row.name}</TableBodyCell>\n- <TableBodyCell>{row.amount}</TableBodyCell>\n- </TableBodyRow>\n- {/each}\n- </TableBody>\n- </Table>\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} showPagination />\n```\n\nThe sort handler, the `sorted` derivation, and the `{#each}` all go\naway. Sorting is a click on the header; filtering is the column menu.\n\n## Keep your design system\n\nSvGrid is unstyled-by-token, so it can match Flowbite / Skeleton /\nshadcn:\n\n- Re-theme through the `--sg-*` CSS custom properties (borders, header\n background, zebra rows, hover, selection, density).\n- Or drive those tokens from your Tailwind theme - see the\n [Tailwind integration](./tailwind.md) guide.\n\n## What you get for free\n\n- **Sorting, filtering, and pagination** without writing handlers.\n- **Row + column virtualization** so thousands of rows stay smooth.\n- **Inline editing**, **cell-range selection + copy**, grouping, tree,\n and master/detail when you need them.\n- **Accessibility** - WAI-ARIA grid roles and keyboard navigation built\n in, instead of a plain `<table>`.\n\n## What you give up\n\n- The **tiny footprint** of a styled `<table>` for a truly static list.\n- A **pixel-perfect**, zero-config match with the rest of the kit - you\n re-create the look with tokens instead (a one-time setup).\n\n## Frequently asked questions\n\n### When should I replace a Flowbite / Skeleton / shadcn table with a data grid?\n\nWhen the table needs sorting, filtering, virtualization, inline editing, or\nlarge datasets. These styled `<Table>` components are presentation only;\nonce you are hand-writing table behaviour, a data grid like SvGrid removes\nthat code. (shadcn-svelte also ships a separate TanStack-based data table -\nsee [that migration guide](./migrating-from-shadcn-data-table.md).)\n\n### Can SvGrid match my existing UI-kit styling?\n\nYes. SvGrid themes through `--sg-*` CSS variables, which you can wire to your\nTailwind / design-system tokens so it matches Flowbite, Skeleton, or\nshadcn-svelte.\n\n### Is it overkill for a small static table?\n\nFor a small, static table that never sorts or filters, a styled `<table>` is\nlighter and fine. Switch when the behaviour - not just the styling - becomes the\nwork.\n\n## What you end up with\n\nEverything the presentational table could not do: sort, filter, page, edit.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable pageable pageSize={3} editable />\n```\n\n## See also\n\n- [SvGrid vs UI-kit tables](https://svgrid.com/compare/svelte-ui-kit-tables/) - the side-by-side comparison\n- [Tailwind integration](./tailwind.md) - match your design system\n- [Getting started](../getting-started.md) - a working grid in ~15 lines\n"
6210
+ "markdown": "\n# Migrating from a UI-kit table (Flowbite / Skeleton / shadcn-svelte)\n\nFlowbite-Svelte, Skeleton, and shadcn-svelte all ship a styled `<Table>`\ncomponent. They are presentation components: they render the rows you\npass and match your design tokens, but sorting, filtering,\nvirtualization, and editing are yours to write by hand. Moving to SvGrid\nreplaces that hand-rolled logic with built-in features - while still\nletting you match the design system.\n\n> **Not the shadcn-svelte data table.** That one is a separate recipe\n> built on TanStack Table v9, and it already does sorting, filtering,\n> pagination, and row selection. If that is what you have, read\n> [Migrating from the shadcn-svelte data table](./migrating-from-shadcn-data-table.md)\n> instead - the port is different, and smaller.\n\n<!-- facts:start svelte-ui-kit-tables -->\n> **Facts, checked 9 Nov 2026.** `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the 30 days to 8 Nov 2026. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026). Flowbite / Skeleton / shadcn-svelte tables pricing, as its site states it: Flowbite Svelte, Skeleton and shadcn-svelte are MIT component libraries; their table components are free and no grid licence is sold (https://github.com/themesberg/flowbite-svelte, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs Flowbite / Skeleton / shadcn-svelte tables](https://svgrid.com/compare/svelte-ui-kit-tables/).\n<!-- facts:end -->\n\n> Estimated effort: **30 min - 1 hour** per table. You are mostly\n> deleting `{#each}` markup and the sort / filter state you wrote\n> yourself.\n\n## When this guide applies\n\nYou have a table that started simple and has grown:\n\n- You added a click-to-sort handler and a sort-state variable.\n- You added a search box and an array `.filter(...)`.\n- The list got long and now you want virtualization or pagination.\n- You started editing cells inline and it got messy.\n\nThat is the moment a styled `<Table>` stops paying for itself.\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- <script>\n- import { Table, TableHead, TableHeadCell, TableBody, TableBodyRow, TableBodyCell } from 'flowbite-svelte'\n- let sortKey = 'name', asc = true\n- $: sorted = [...rows].sort((a, b) => (a[sortKey] > b[sortKey] ? 1 : -1) * (asc ? 1 : -1))\n- </script>\n-\n- <Table>\n- <TableHead>\n- <TableHeadCell on:click={() => (sortKey = 'name')}>Name</TableHeadCell>\n- <TableHeadCell on:click={() => (sortKey = 'amount')}>Amount</TableHeadCell>\n- </TableHead>\n- <TableBody>\n- {#each sorted as row}\n- <TableBodyRow>\n- <TableBodyCell>{row.name}</TableBodyCell>\n- <TableBodyCell>{row.amount}</TableBodyCell>\n- </TableBodyRow>\n- {/each}\n- </TableBody>\n- </Table>\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} showPagination />\n```\n\nThe sort handler, the `sorted` derivation, and the `{#each}` all go\naway. Sorting is a click on the header; filtering is the column menu.\n\n## Keep your design system\n\nSvGrid is unstyled-by-token, so it can match Flowbite / Skeleton /\nshadcn:\n\n- Re-theme through the `--sg-*` CSS custom properties (borders, header\n background, zebra rows, hover, selection, density).\n- Or drive those tokens from your Tailwind theme - see the\n [Tailwind integration](./tailwind.md) guide.\n\n## What you get for free\n\n- **Sorting, filtering, and pagination** without writing handlers.\n- **Row + column virtualization** so thousands of rows stay smooth.\n- **Inline editing**, **cell-range selection + copy**, grouping, tree,\n and master/detail when you need them.\n- **Accessibility** - WAI-ARIA grid roles and keyboard navigation built\n in, instead of a plain `<table>`.\n\n## What you give up\n\n- The **tiny footprint** of a styled `<table>` for a truly static list.\n- A **pixel-perfect**, zero-config match with the rest of the kit - you\n re-create the look with tokens instead (a one-time setup).\n\n## Frequently asked questions\n\n### When should I replace a Flowbite / Skeleton / shadcn table with a data grid?\n\nWhen the table needs sorting, filtering, virtualization, inline editing, or\nlarge datasets. These styled `<Table>` components are presentation only;\nonce you are hand-writing table behaviour, a data grid like SvGrid removes\nthat code. (shadcn-svelte also ships a separate TanStack-based data table -\nsee [that migration guide](./migrating-from-shadcn-data-table.md).)\n\n### Can SvGrid match my existing UI-kit styling?\n\nYes. SvGrid themes through `--sg-*` CSS variables, which you can wire to your\nTailwind / design-system tokens so it matches Flowbite, Skeleton, or\nshadcn-svelte.\n\n### Is it overkill for a small static table?\n\nFor a small, static table that never sorts or filters, a styled `<table>` is\nlighter and fine. Switch when the behaviour - not just the styling - becomes the\nwork.\n\n## What you end up with\n\nEverything the presentational table could not do: sort, filter, page, edit.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable pageable pageSize={3} editable />\n```\n\n## See also\n\n- [SvGrid vs UI-kit tables](https://svgrid.com/compare/svelte-ui-kit-tables/) - the side-by-side comparison\n- [Tailwind integration](./tailwind.md) - match your design system\n- [Getting started](../getting-started.md) - a working grid in ~15 lines\n"
6211
6211
  },
6212
6212
  {
6213
6213
  "slug": "help/migrating-from-vincjo-datatables",
6214
6214
  "path": "docs/help/migrating-from-vincjo-datatables.md",
6215
6215
  "title": "Migrating from @vincjo/datatables",
6216
6216
  "section": "Help",
6217
- "markdown": "# Migrating from @vincjo/datatables\n\n`@vincjo/datatables` is a small, ergonomic Svelte datatable helper: you\nwrap your data in a handler and it gives you reactive sorting,\nfiltering, and pagination while you keep your own table markup. SvGrid\ncovers the same job and then keeps going - virtualization, an\nExcel-style filter menu, inline editing, and a render component - so the\nport is mostly about deciding how much markup you want to keep.\n\n> Estimated effort: **30 min - 2 hours** per table. A simple list is a\n> 30-minute swap; a feature-heavy one trends toward two hours.\n\n<!-- facts:start vincjo-datatables -->\n> **Facts, checked 9 Nov 2026.** `@vincjo/datatables` 2.8.1, MIT, last published 4 Jun 2026, 107,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026); `@vincjo/datatables` 2.8.1 10.2 KB JS, no separate stylesheet, svelte external (measured 9 Nov 2026). @vincjo/datatables pricing, as its site states it: @vincjo/datatables is MIT on npm and free; no licence is sold (https://github.com/vincjo/datatables, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs @vincjo/datatables](https://svgrid.com/compare/vincjo-datatables/).\n<!-- facts:end -->\n\n## Vocabulary cheat sheet\n\n| @vincjo/datatables | sv-grid |\n| ------------------------------------------ | ----------------------------------------- |\n| `new TableHandler(data, { rowsPerPage })` | `createSvGrid({...})` or `<SvGrid>` |\n| `<ThSort {table} field=\"name\">` | `rowSortingFeature` (header sort built in) |\n| `<ThFilter {table} field=\"name\">` | `columnFilteringFeature` |\n| `table.global.set(query)` (search) | `api.setState({ globalFilter: query })` |\n| `<Pagination {table} />` / `<RowCount>` | Built in; toggle `showPagination` |\n| `table.rows` (current page rows) | `api.getDisplayedRows()` |\n| Server mode (`table.load(...)`) | `externalSort` / `externalFilter` + refetch |\n| Your own `<table>` + `{#each table.rows}` | `<SvGrid>` render component |\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- <script>\n- import { TableHandler, ThSort, ThFilter, Pagination } from '@vincjo/datatables'\n- const table = new TableHandler(rows, { rowsPerPage: 25 })\n- </script>\n-\n- <table>\n- <thead><tr>\n- <ThSort {table} field=\"name\">Name</ThSort>\n- <ThSort {table} field=\"amount\">Amount</ThSort>\n- </tr></thead>\n- <tbody>\n- {#each table.rows as row}\n- <tr><td>{row.name}</td><td>{row.amount}</td></tr>\n- {/each}\n- </tbody>\n- </table>\n- <Pagination {table} />\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} showPagination />\n```\n\n## Server-side data\n\n```diff\n- // @vincjo/datatables: drive a server with the handler's load hook\n- const table = new TableHandler(rows, { rowsPerPage: 25 })\n- table.load((state) => fetchRows(state)) // sort/filter/page sent to your API\n\n+ <SvGrid\n+ data={rows} columns={columns} features={features}\n+ externalSort={true} externalFilter={true}\n+ onSortingChange={(clauses) => refetch({ sort: clauses })}\n+ onFiltersChange={(f) => refetch({ filters: f.columns })}\n+ />\n```\n\n## What you get for free\n\n- **A render component** with virtualization - you stop authoring the\n `<table>` and the `{#each}`.\n- **Excel-style filter menu**, **cell-range selection + copy**, and\n **inline editing** with typed editors.\n- **Grouping, tree data, and master/detail** when the table grows up.\n- **Enterprise features** - export, import, pivot, AI.\n\n## What you give up\n\n- **The tiny footprint.** If all you ever need is sort / filter /\n paginate over a small list, `@vincjo/datatables` stays smaller.\n- **Total markup control.** SvGrid renders the table; you theme it with\n `--sg-*` tokens and Tailwind rather than writing every `<td>`.\n\n## Frequently asked questions\n\n### Should I move from @vincjo/datatables to SvGrid?\n\nMove when a hand-rolled table stops being enough - when you need virtualization\nfor large datasets, an Excel-style filter menu, inline editing, grouping, or\ntree data. For a small sort/filter/paginate list, `@vincjo/datatables` is a fine,\nlighter choice.\n\n### Is SvGrid also MIT-licensed like @vincjo/datatables?\n\nYes. `@svgrid/grid` is MIT, like `@vincjo/datatables`. SvGrid adds an\noptional paid `@svgrid/enterprise` pack (export, import, pivot, AI).\n\n### Can I keep my own table markup after switching?\n\nYes. SvGrid has a headless core (`createSvGrid` + row-model factories) you can\ndrive with your own markup, the same way `@vincjo/datatables` lets you. Most\nteams use the `<SvGrid>` component instead because it removes the boilerplate.\n\n## What you end up with\n\nSorting, filtering and pagination without the hand-written table around it.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable pageable pageSize={3} />\n```\n\n## See also\n\n- [SvGrid vs @vincjo/datatables](https://svgrid.com/compare/vincjo-datatables/) - the side-by-side comparison\n- [Migrating from svelte-headless-table](./migrating-from-svelte-headless-table.md) - sibling Svelte guide\n- [Why headless?](../why-headless.md) - keep your own markup if you want to\n"
6217
+ "markdown": "# Migrating from @vincjo/datatables\n\n`@vincjo/datatables` is a small, ergonomic Svelte datatable helper: you\nwrap your data in a handler and it gives you reactive sorting,\nfiltering, and pagination while you keep your own table markup. SvGrid\ncovers the same job and then keeps going - virtualization, an\nExcel-style filter menu, inline editing, and a render component - so the\nport is mostly about deciding how much markup you want to keep.\n\n> Estimated effort: **30 min - 2 hours** per table. A simple list is a\n> 30-minute swap; a feature-heavy one trends toward two hours.\n\n<!-- facts:start vincjo-datatables -->\n> **Facts, checked 9 Nov 2026.** `@vincjo/datatables` 2.8.1, MIT, last published 4 Jun 2026, 107,000 npm downloads in the 30 days to 8 Nov 2026. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026); `@vincjo/datatables` 2.8.1 10.2 KB JS, no separate stylesheet, svelte external (measured 9 Nov 2026). @vincjo/datatables pricing, as its site states it: @vincjo/datatables is MIT on npm and free; no licence is sold (https://github.com/vincjo/datatables, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs @vincjo/datatables](https://svgrid.com/compare/vincjo-datatables/).\n<!-- facts:end -->\n\n## Vocabulary cheat sheet\n\n| @vincjo/datatables | sv-grid |\n| ------------------------------------------ | ----------------------------------------- |\n| `new TableHandler(data, { rowsPerPage })` | `createSvGrid({...})` or `<SvGrid>` |\n| `<ThSort {table} field=\"name\">` | `rowSortingFeature` (header sort built in) |\n| `<ThFilter {table} field=\"name\">` | `columnFilteringFeature` |\n| `table.global.set(query)` (search) | `api.setState({ globalFilter: query })` |\n| `<Pagination {table} />` / `<RowCount>` | Built in; toggle `showPagination` |\n| `table.rows` (current page rows) | `api.getDisplayedRows()` |\n| Server mode (`table.load(...)`) | `externalSort` / `externalFilter` + refetch |\n| Your own `<table>` + `{#each table.rows}` | `<SvGrid>` render component |\n\n## Before / after\n\nThe example at the end of this page runs against these rows:\n\n```svelte {preamble}\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n\n type Person = {\n id: number\n name: string\n department: string\n city: string\n age: number\n salary: number\n }\n\n const people: Person[] = [\n { id: 1, name: 'Ada Lovelace', department: 'Engineering', city: 'London', age: 36, salary: 142000 },\n { id: 2, name: 'Grace Hopper', department: 'Engineering', city: 'New York', age: 45, salary: 168000 },\n { id: 3, name: 'Linus Torvalds', department: 'Platform', city: 'Portland', age: 54, salary: 155000 },\n { id: 4, name: 'Radia Perlman', department: 'Networking', city: 'Seattle', age: 49, salary: 161000 },\n { id: 5, name: 'Barbara Liskov', department: 'Platform', city: 'Boston', age: 52, salary: 172000 },\n ]\n\n let rows = $state<Person[]>(people)\n\n const columns: GridColumns<Person> = [\n { field: 'name', header: 'Name', width: 200, editorType: 'text' },\n { field: 'department', header: 'Department', width: 150, editorType: 'text' },\n { field: 'city', header: 'City', width: 140, editorType: 'text' },\n { field: 'age', header: 'Age', width: 90, editorType: 'number' },\n { field: 'salary', header: 'Salary', width: 130, editorType: 'number', format: { type: 'currency', currency: 'USD' } },\n ]\n</script>\n```\n\n```diff\n- <script>\n- import { TableHandler, ThSort, ThFilter, Pagination } from '@vincjo/datatables'\n- const table = new TableHandler(rows, { rowsPerPage: 25 })\n- </script>\n-\n- <table>\n- <thead><tr>\n- <ThSort {table} field=\"name\">Name</ThSort>\n- <ThSort {table} field=\"amount\">Amount</ThSort>\n- </tr></thead>\n- <tbody>\n- {#each table.rows as row}\n- <tr><td>{row.name}</td><td>{row.amount}</td></tr>\n- {/each}\n- </tbody>\n- </table>\n- <Pagination {table} />\n\n+ <script lang=\"ts\">\n+ import {\n+ SvGrid, tableFeatures, rowSortingFeature, columnFilteringFeature,\n+ type ColumnDef,\n+ } from '@svgrid/grid'\n+\n+ const features = tableFeatures({ rowSortingFeature, columnFilteringFeature })\n+ const columns: ColumnDef<typeof features, Row>[] = [\n+ { field: 'name', header: 'Name' },\n+ { field: 'amount', header: 'Amount', format: { type: 'currency', currency: 'USD' } },\n+ ]\n+ </script>\n+\n+ <SvGrid data={rows} columns={columns} features={features} showPagination />\n```\n\n## Server-side data\n\n```diff\n- // @vincjo/datatables: drive a server with the handler's load hook\n- const table = new TableHandler(rows, { rowsPerPage: 25 })\n- table.load((state) => fetchRows(state)) // sort/filter/page sent to your API\n\n+ <SvGrid\n+ data={rows} columns={columns} features={features}\n+ externalSort={true} externalFilter={true}\n+ onSortingChange={(clauses) => refetch({ sort: clauses })}\n+ onFiltersChange={(f) => refetch({ filters: f.columns })}\n+ />\n```\n\n## What you get for free\n\n- **A render component** with virtualization - you stop authoring the\n `<table>` and the `{#each}`.\n- **Excel-style filter menu**, **cell-range selection + copy**, and\n **inline editing** with typed editors.\n- **Grouping, tree data, and master/detail** when the table grows up.\n- **Enterprise features** - export, import, pivot, AI.\n\n## What you give up\n\n- **The tiny footprint.** If all you ever need is sort / filter /\n paginate over a small list, `@vincjo/datatables` stays smaller.\n- **Total markup control.** SvGrid renders the table; you theme it with\n `--sg-*` tokens and Tailwind rather than writing every `<td>`.\n\n## Frequently asked questions\n\n### Should I move from @vincjo/datatables to SvGrid?\n\nMove when a hand-rolled table stops being enough - when you need virtualization\nfor large datasets, an Excel-style filter menu, inline editing, grouping, or\ntree data. For a small sort/filter/paginate list, `@vincjo/datatables` is a fine,\nlighter choice.\n\n### Is SvGrid also MIT-licensed like @vincjo/datatables?\n\nYes. `@svgrid/grid` is MIT, like `@vincjo/datatables`. SvGrid adds an\noptional paid `@svgrid/enterprise` pack (export, import, pivot, AI).\n\n### Can I keep my own table markup after switching?\n\nYes. SvGrid has a headless core (`createSvGrid` + row-model factories) you can\ndrive with your own markup, the same way `@vincjo/datatables` lets you. Most\nteams use the `<SvGrid>` component instead because it removes the boilerplate.\n\n## What you end up with\n\nSorting, filtering and pagination without the hand-written table around it.\n\n```svelte {runnable}\n<SvGrid data={rows} {columns} sortable filterable pageable pageSize={3} />\n```\n\n## See also\n\n- [SvGrid vs @vincjo/datatables](https://svgrid.com/compare/vincjo-datatables/) - the side-by-side comparison\n- [Migrating from svelte-headless-table](./migrating-from-svelte-headless-table.md) - sibling Svelte guide\n- [Why headless?](../why-headless.md) - keep your own markup if you want to\n"
6218
6218
  },
6219
6219
  {
6220
6220
  "slug": "help/missing-features",
@@ -6634,7 +6634,7 @@ export const docs = [
6634
6634
  "path": "docs/help/svelte-5-upgrade-data-tables.md",
6635
6635
  "title": "Upgrading a Svelte 4 table to Svelte 5: what breaks, what does not, and the three ways out",
6636
6636
  "section": "Help",
6637
- "markdown": "\n# Upgrading a Svelte 4 table to Svelte 5: what breaks, what does not, and the three ways out\n\nIf your Svelte 4 app has a table built on `svelte-headless-table`, the Svelte 5\nupgrade forces a decision about it, and most of what is written about that\ndecision is guesswork. This page is not. We put the table from the library's\nown documentation into a Svelte 4 project, upgraded it to Svelte 5 one step at a\ntime, and captured every line the tools printed. The script and the captures\nare in the repo at\n[tools/migration-lab](https://github.com/sv-grid/sv-grid/tree/main/tools/migration-lab);\nevery code block below is a quote from those files, checked by a test, and the\nfirst line of each capture records the versions it was made with.\n\n<!-- facts:start svelte-headless-table pkg:@humanspeak/svelte-headless-table -->\n> **Facts, checked 9 Nov 2026.** `svelte-headless-table` 0.18.3, MIT, last published 28 Oct 2024, 96,400 npm downloads in the 30 days to 8 Nov 2026. `@humanspeak/svelte-headless-table` 7.1.0, MIT, last published 28 Oct 2026, 10,600 npm downloads in the same window. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.33 99.9 KB JS + 11.3 KB CSS (measured 10 Nov 2026); `svelte-headless-table` 0.18.3 5.7 KB JS, no separate stylesheet, svelte external (measured 9 Nov 2026). svelte-headless-table pricing, as its site states it: svelte-headless-table is MIT and free; no paid licence or support is offered, and the author states there are no plans for a Svelte 5 port (https://github.com/bryanmylee/svelte-headless-table, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs svelte-headless-table](https://svgrid.com/compare/svelte-headless-table/).\n<!-- facts:end -->\n\nThe short version: the install warns and goes through, the untouched component\nkeeps compiling, and the trouble starts the day you write your first rune in\nthat component. The three exits are a maintained fork, TanStack Table v9, and\nSvGrid, and they trade different things.\n\n## The component we upgraded\n\nA `PeopleTable` written the way svelte-headless-table's docs teach it: a\n`writable` over a prop, a `$:` to keep it in sync, three plugins, the view model\nread through `<Subscribe>` and `<Render>`, a pager on `pluginStates.page`, and a\n`select` event dispatched from the row.\n\n<!-- captured: fixture/svelte4/PeopleTable.svelte -->\n```svelte\n<script lang=\"ts\">\n // The table as svelte-headless-table's own docs show it: a store for the\n // data, plugins for behaviour, and a view model read through <Subscribe>\n // and <Render>. Svelte 4 throughout: `export let`, `$:`, a dispatcher,\n // `on:click`, and `let:` slot props.\n import { createEventDispatcher } from 'svelte'\n import { writable } from 'svelte/store'\n import { createTable, Subscribe, Render } from 'svelte-headless-table'\n import { addSortBy, addColumnFilters, addPagination } from 'svelte-headless-table/plugins'\n import type { Person } from './people'\n\n export let people: Person[] = []\n export let pageSize = 5\n\n const dispatch = createEventDispatcher<{ select: Person }>()\n\n const data = writable<Person[]>(people)\n $: data.set(people)\n\n const table = createTable(data, {\n sort: addSortBy(),\n filter: addColumnFilters(),\n page: addPagination({ initialPageSize: pageSize }),\n })\n```\n\nThe full file is 83 lines; the 40 that follow are the `<table>`, three levels\nof `<Subscribe let:...>` and a `<p>` with the pager. On the pinned Svelte 4\ntoolchain it checks clean:\n\n<!-- captured: 01-svelte4-baseline.txt -->\n```text\n$ npx svelte-check --tsconfig ./tsconfig.json --output human --threshold warning\nsvelte-check found 0 errors and 0 warnings\n```\n\n## Step 1: the install warns and goes through\n\n`svelte-headless-table` declares `peerDependencies: { svelte: \"^4.0.0\" }`, and\nthat range is not going to change: the facts box above has the last release\ndate, and the project's README says there are no plans for a Svelte 5 port.\nSo what does `npm install svelte@5` do against it? On npm 11, this:\n\n<!-- captured: 02-npm-install-svelte5.txt -->\n```text\n$ npm install svelte@5.57.1\n\nadded 10 packages, removed 10 packages, and changed 2 packages in <time>\nnpm warn ERESOLVE overriding peer dependency\nnpm warn While resolving: svgrid-migration-lab@undefined\nnpm warn Found: svelte@4.2.20\nnpm warn node_modules/svelte\nnpm warn peer svelte@\"^4.0.0 || ^5.0.0-next.0\" from svelte-check@4.7.6\nnpm warn node_modules/svelte-check\nnpm warn dev svelte-check@\"4.7.6\" from the root project\nnpm warn 5 more (svelte-headless-table, svelte-keyed, svelte-render, ...)\nnpm warn\nnpm warn Could not resolve dependency:\nnpm warn peer svelte@\"^4.0.0\" from svelte-headless-table@0.18.3\nnpm warn node_modules/svelte-headless-table\nnpm warn dev svelte-headless-table@\"0.18.3\" from the root project\nnpm warn ERESOLVE overriding peer dependency\nnpm warn ERESOLVE overriding peer dependency\nnpm warn ERESOLVE overriding peer dependency\n\n(exit 0)\n```\n\nExit 0. npm 11 overrides the conflict and tells you so; older npm releases\nstopped with an `ERESOLVE` error until you added `--legacy-peer-deps`, and\npnpm prints an unmet-peer warning of its own. Either way, the peer range is a\nstatement, not a lock: the library's author is telling you it was never run\nagainst the Svelte you now have. Nothing enforces it.\n\n## Step 2: the untouched component still compiles\n\nSvelte 5 compiles Svelte 4 components in legacy mode, so `export let`, `$:`,\n`createEventDispatcher`, `on:click` and `let:` slot props all keep working\nuntil you opt a file into runes. With Svelte 5 installed and the component\nexactly as it was:\n\n<!-- captured: 03-svelte5-legacy-component.txt -->\n```text\n$ npx svelte-check --tsconfig ./tsconfig.json --output human --threshold warning\nsvelte-check found 0 errors and 0 warnings\n```\n\nThis is the part the scare stories leave out. If your only goal is to be on\nSvelte 5, you can install it, keep the table exactly as it is, and ship. The\nlibrary's own components (`<Subscribe>`, `<Render>`) compile in legacy mode\ntoo.\n\n## Step 3: the first rune\n\nWhat you cannot do is make that component a runes component and keep the\ntable as it is. Port `PeopleTable` by the rules in the\n[official migration guide](https://svelte.dev/docs/svelte/v5-migration-guide):\n`export let` becomes `$props()`, `$:` becomes `$derived` and `$effect`, the\ndispatcher becomes a callback prop, `on:click` becomes `onclick`. Leave the\nsvelte-headless-table wiring alone, because the guide has nothing to say about\nit. The checker now says:\n\n<!-- captured: 04-svelte5-runes-component.txt -->\n```text\n$ npx svelte-check --tsconfig ./tsconfig.json --output human --threshold warning\n<lab>\\src\\PeopleTable.svelte:19:35\nWarn: This reference only captures the initial value of `people`. Did you mean to reference it inside a closure instead?\nhttps://svelte.dev/e/state_referenced_locally (svelte)\n\n<lab>\\src\\PeopleTable.svelte:27:44\nWarn: This reference only captures the initial value of `pageSize`. Did you mean to reference it inside a closure instead?\nhttps://svelte.dev/e/state_referenced_locally (svelte)\n\n====================================\nsvelte-check found 0 errors and 2 warnings in 1 file\n```\n\nTwo warnings, no errors, and both are the same fact: the library takes a store,\nyour data is now a rune, and the `writable(people)` you built to bridge them\ncaptured the first value of `people` and nothing after. The fix is an\n`$effect` that writes the prop into the store on every change, which is what\nthe ported fixture does, and it works. It is also a bridge you now own, in\nevery component that has a table, between a reactivity model the library was\nbuilt for and the one your app is written in.\n\nThat is the actual shape of the problem. Not a red build: a component that\ncompiles, with a store-and-slot-props library bolted to a runes app by code you\nmaintain, on a package that will not move. The pieces it leans on are the ones\nSvelte 5 has deprecated: `let:` slot props and `<slot>` in favour of snippets,\nand `<svelte:component>`, which is what `<Render>` uses underneath\n(`svelte-render` 2.0.1, `PropsRenderer.svelte`, peer `svelte ^4.0.0`). They\nkeep working in legacy mode today; deprecated syntax is what the next major\nremoves, and this library will not be updated when it does.\n\n## The three ways out\n\nYou have three honest options, and you should know all of them before picking.\n\n1. **`@humanspeak/svelte-headless-table`**, a maintained fork on Svelte 5 with\n the same API. Its version, publish date and downloads are in the facts box.\n Switching is one package rename; you keep every line of markup and every\n `<Subscribe>`, and you keep the store bridge from step 3. If your table\n works and Svelte 5 is all you need, this is the cheapest exit by a wide\n margin.\n2. **TanStack Table v9.** Its Svelte adapter declares a Svelte 5 peer range and\n its state shape is runes-first, so the bridge goes away. It is still\n headless: you write and maintain the `<table>`, the virtualizer, the filter\n UI and the editors yourself. The\n [TanStack migration guide](./migrating-from-tanstack-table.md) covers the\n vocabulary.\n3. **SvGrid.** A different trade: you delete the markup and take a renderer.\n The column definitions and the plugin list carry over; the `<table>`, the\n `<Subscribe>` blocks, the pager and the store bridge do not exist any more,\n because `<SvGrid>` renders all of that. The rest of this page is what that\n looks like on the fixture above.\n\nPick 1 if the markup is fine and the library being dead does not bother you.\nPick 2 if you want the markup and a maintained engine. Pick 3 if the markup is\nthe part you are tired of.\n\n## Step 4: the codemod\n\n`npx @svgrid/migrate` ports a svelte-headless-table component to SvGrid. It\npreviews by default and only writes with `--write`, and it says what it could\nnot map instead of dropping it. On the Svelte 4 original:\n\n<!-- captured: 05-codemod.txt -->\n```text\n warning A custom `cell` renderer was found. SvGrid renders cells with a snippet, not `createRender`, so this one needs porting by hand - it is preserved as a comment.\n warning The template still reads `pageIndex`, `pageCount`, `shown` from the view model, which is gone. <SvGrid> renders its own pager and row count (`pageable`, `showPagination`), so remove that markup, or read the grid through `onApiReady` if you need the numbers.\n warning The table markup dispatched `select` from a row; that handler went with the `<tr>`. Wire it to `onRowClick={({ row }) => ...}` (or `onCellClick`) on <SvGrid>, and turn the `createEventDispatcher` into a callback prop if the component is moving to runes.\n note Column resizing, keyboard navigation and ARIA grid semantics are built into <SvGrid>; the markup that provided them is intentionally gone.\n\n1 file(s) would change, with 3 warning(s).\nRe-run with --write to apply.\n```\n\nThree warnings, each naming a thing it left for you. Write it, swap the\npackages, and check:\n\n<!-- captured: 06-after-codemod.txt -->\n```text\n$ npm install @svgrid/grid@3.0.4 --legacy-peer-deps\n\nadded 1 package in <time>\n\n(exit 0)\n\n$ npm uninstall svelte-headless-table --legacy-peer-deps\n\nremoved 4 packages in <time>\n\n(exit 0)\n\n$ npx svelte-check --tsconfig ./tsconfig.json --output human --threshold warning\n<lab>\\src\\PeopleTable.svelte:31:23\nError: `$pageIndex` is an illegal variable name. To reference a global variable called `$pageIndex`, use `globalThis.$pageIndex`\nhttps://svelte.dev/e/global_reference_invalid (svelte)\n```\n\n<!-- captured: 06-after-codemod.txt -->\n```text\nsvelte-check found 9 errors and 0 warnings in 1 file\n```\n\nAll nine are the pager `<p>` the second warning named, reading `shown`,\n`$pageIndex` and `$pageCount` from a view model that no longer exists. The\ncodemod does not delete markup outside the `<table>`, because it cannot know\nwhat else is in there; it tells you what will not compile. Delete the `<p>`\n(the grid draws its own pager), turn the `select` event into a callback prop\non `onRowClick` as the third warning says, and:\n\n<!-- captured: 07-hand-edits.txt -->\n```text\n$ npx svelte-check --tsconfig ./tsconfig.json --output human --threshold warning\nsvelte-check found 0 errors and 0 warnings\n```\n\n## What you end up with\n\nThe component after the codemod and the two hand edits:\n\n<!-- captured: PeopleTable.after.svelte -->\n```svelte\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n import type { Person } from './people'\n export let people: Person[] = []\n export let pageSize = 5\n export let onselect: (person: Person) => void = () => {}\n\n const columns: GridColumns<(typeof people)[number]> = [\n {\n header: 'Name',\n field: 'name',\n },\n {\n header: 'Department',\n field: 'department',\n },\n {\n header: 'City',\n field: 'city',\n },\n {\n header: 'Salary',\n field: 'salary',\n // TODO port: cell: ({ value }) => value.toLocaleString('en-US', { style: 'currency', currency: 'USD\n },\n ]\n</script>\n\n<SvGrid data={people} {columns} sortable filterable showColumnFilters pageable pageSize={pageSize}\n onRowClick={({ row }) => onselect(row)} />\n```\n\n83 lines became 31. The `TODO port:` comment is the one thing left to do by\nhand: the currency cell becomes `format: { type: 'currency', currency: 'USD' }`\non the column, and the comment goes. There is no store, no `$:`, no\n`<Subscribe>`, no `let:`, and nothing in the file that Svelte 5 has deprecated,\nso the same component moves to runes whenever you like with the official\nmigration script and nothing else to port.\n\n## What to read next\n\n- [Migrating from svelte-headless-table](./migrating-from-svelte-headless-table.md) -\n the plugin-by-plugin mapping and what the codemod will not do\n- [SvGrid vs svelte-headless-table](https://svgrid.com/compare/svelte-headless-table/) -\n the side-by-side, with a source and date for every claim\n- [Migrating from TanStack Table](./migrating-from-tanstack-table.md) - exit 2 in detail\n- [Migrating from the shadcn-svelte data table](./migrating-from-shadcn-data-table.md) -\n the same codemod on the TanStack-based recipe\n- [Why headless?](../why-headless.md) - if you want to keep your own markup\n on a maintained Svelte 5 engine, `@svgrid/grid/core` is that too\n\n## Frequently asked questions\n\n### Does svelte-headless-table work with Svelte 5?\n\nIn legacy mode, yes: the install prints a peer-dependency warning and the\nuntouched component type-checks clean, as the captures above show. What does\nnot work is moving a component that uses it to runes without maintaining a\nstore bridge yourself, and the library is not going to be updated for the\ndeprecations that bridge leans on.\n\n### Is the peer dependency conflict an error?\n\nOn npm 11 it is a warning and the install exits 0; on older npm it was an\n`ERESOLVE` error until you passed `--legacy-peer-deps`; pnpm warns. It never\nstops the code from running. It tells you the library was not built against\nthe Svelte you have.\n\n### Should I just use the maintained fork?\n\nIf your table works and all you need is Svelte 5, yes, and this page says so.\nThe fork keeps the same API, so you keep the same markup and the same store\nbridge. Move to SvGrid when the markup and the bridge are what you want gone.\n\n### How much of the port does the codemod do?\n\nThe column definitions, the plugin list and the `<table>` replacement, and it\nnames what it leaves: custom cell renderers, markup outside the table that read\nthe view model, and events the rows dispatched. On the fixture that was two\nhand edits and one `format` option.\n\n### Can I rerun this myself?\n\n`node tools/migration-lab/run.mjs` in the repo. It installs the pinned Svelte 4\ntoolchain into its own folder, upgrades it, runs the codemod from the checkout,\nand rewrites the captured files; the header of each one records the versions.\nBump the pins to try a newer Svelte.\n"
6637
+ "markdown": "\n# Upgrading a Svelte 4 table to Svelte 5: what breaks, what does not, and the three ways out\n\nIf your Svelte 4 app has a table built on `svelte-headless-table`, the Svelte 5\nupgrade forces a decision about it, and most of what is written about that\ndecision is guesswork. This page is not. We put the table from the library's\nown documentation into a Svelte 4 project, upgraded it to Svelte 5 one step at a\ntime, and captured every line the tools printed. The script and the captures\nare in the repo at\n[tools/migration-lab](https://github.com/sv-grid/sv-grid/tree/main/tools/migration-lab);\nevery code block below is a quote from those files, checked by a test, and the\nfirst line of each capture records the versions it was made with.\n\n<!-- facts:start svelte-headless-table pkg:@humanspeak/svelte-headless-table -->\n> **Facts, checked 9 Nov 2026.** `svelte-headless-table` 0.18.3, MIT, last published 28 Oct 2024, 96,400 npm downloads in the 30 days to 8 Nov 2026. `@humanspeak/svelte-headless-table` 7.1.0, MIT, last published 28 Oct 2026, 10,600 npm downloads in the same window. `@svgrid/grid` 3.0.32, MIT, last published 3 Nov 2026, 44,600 npm downloads in the same window. Bundle, minified and gzipped, each package built alone with Svelte external: SvGrid 3.0.34 99.6 KB JS + 11.4 KB CSS (measured 10 Nov 2026); `svelte-headless-table` 0.18.3 5.7 KB JS, no separate stylesheet, svelte external (measured 9 Nov 2026). svelte-headless-table pricing, as its site states it: svelte-headless-table is MIT and free; no paid licence or support is offered, and the author states there are no plans for a Svelte 5 port (https://github.com/bryanmylee/svelte-headless-table, read 12 Sep 2026). SvGrid: MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise. Side by side, with sources: [SvGrid vs svelte-headless-table](https://svgrid.com/compare/svelte-headless-table/).\n<!-- facts:end -->\n\nThe short version: the install warns and goes through, the untouched component\nkeeps compiling, and the trouble starts the day you write your first rune in\nthat component. The three exits are a maintained fork, TanStack Table v9, and\nSvGrid, and they trade different things.\n\n## The component we upgraded\n\nA `PeopleTable` written the way svelte-headless-table's docs teach it: a\n`writable` over a prop, a `$:` to keep it in sync, three plugins, the view model\nread through `<Subscribe>` and `<Render>`, a pager on `pluginStates.page`, and a\n`select` event dispatched from the row.\n\n<!-- captured: fixture/svelte4/PeopleTable.svelte -->\n```svelte\n<script lang=\"ts\">\n // The table as svelte-headless-table's own docs show it: a store for the\n // data, plugins for behaviour, and a view model read through <Subscribe>\n // and <Render>. Svelte 4 throughout: `export let`, `$:`, a dispatcher,\n // `on:click`, and `let:` slot props.\n import { createEventDispatcher } from 'svelte'\n import { writable } from 'svelte/store'\n import { createTable, Subscribe, Render } from 'svelte-headless-table'\n import { addSortBy, addColumnFilters, addPagination } from 'svelte-headless-table/plugins'\n import type { Person } from './people'\n\n export let people: Person[] = []\n export let pageSize = 5\n\n const dispatch = createEventDispatcher<{ select: Person }>()\n\n const data = writable<Person[]>(people)\n $: data.set(people)\n\n const table = createTable(data, {\n sort: addSortBy(),\n filter: addColumnFilters(),\n page: addPagination({ initialPageSize: pageSize }),\n })\n```\n\nThe full file is 83 lines; the 40 that follow are the `<table>`, three levels\nof `<Subscribe let:...>` and a `<p>` with the pager. On the pinned Svelte 4\ntoolchain it checks clean:\n\n<!-- captured: 01-svelte4-baseline.txt -->\n```text\n$ npx svelte-check --tsconfig ./tsconfig.json --output human --threshold warning\nsvelte-check found 0 errors and 0 warnings\n```\n\n## Step 1: the install warns and goes through\n\n`svelte-headless-table` declares `peerDependencies: { svelte: \"^4.0.0\" }`, and\nthat range is not going to change: the facts box above has the last release\ndate, and the project's README says there are no plans for a Svelte 5 port.\nSo what does `npm install svelte@5` do against it? On npm 11, this:\n\n<!-- captured: 02-npm-install-svelte5.txt -->\n```text\n$ npm install svelte@5.57.1\n\nadded 10 packages, removed 10 packages, and changed 2 packages in <time>\nnpm warn ERESOLVE overriding peer dependency\nnpm warn While resolving: svgrid-migration-lab@undefined\nnpm warn Found: svelte@4.2.20\nnpm warn node_modules/svelte\nnpm warn peer svelte@\"^4.0.0 || ^5.0.0-next.0\" from svelte-check@4.7.6\nnpm warn node_modules/svelte-check\nnpm warn dev svelte-check@\"4.7.6\" from the root project\nnpm warn 5 more (svelte-headless-table, svelte-keyed, svelte-render, ...)\nnpm warn\nnpm warn Could not resolve dependency:\nnpm warn peer svelte@\"^4.0.0\" from svelte-headless-table@0.18.3\nnpm warn node_modules/svelte-headless-table\nnpm warn dev svelte-headless-table@\"0.18.3\" from the root project\nnpm warn ERESOLVE overriding peer dependency\nnpm warn ERESOLVE overriding peer dependency\nnpm warn ERESOLVE overriding peer dependency\n\n(exit 0)\n```\n\nExit 0. npm 11 overrides the conflict and tells you so; older npm releases\nstopped with an `ERESOLVE` error until you added `--legacy-peer-deps`, and\npnpm prints an unmet-peer warning of its own. Either way, the peer range is a\nstatement, not a lock: the library's author is telling you it was never run\nagainst the Svelte you now have. Nothing enforces it.\n\n## Step 2: the untouched component still compiles\n\nSvelte 5 compiles Svelte 4 components in legacy mode, so `export let`, `$:`,\n`createEventDispatcher`, `on:click` and `let:` slot props all keep working\nuntil you opt a file into runes. With Svelte 5 installed and the component\nexactly as it was:\n\n<!-- captured: 03-svelte5-legacy-component.txt -->\n```text\n$ npx svelte-check --tsconfig ./tsconfig.json --output human --threshold warning\nsvelte-check found 0 errors and 0 warnings\n```\n\nThis is the part the scare stories leave out. If your only goal is to be on\nSvelte 5, you can install it, keep the table exactly as it is, and ship. The\nlibrary's own components (`<Subscribe>`, `<Render>`) compile in legacy mode\ntoo.\n\n## Step 3: the first rune\n\nWhat you cannot do is make that component a runes component and keep the\ntable as it is. Port `PeopleTable` by the rules in the\n[official migration guide](https://svelte.dev/docs/svelte/v5-migration-guide):\n`export let` becomes `$props()`, `$:` becomes `$derived` and `$effect`, the\ndispatcher becomes a callback prop, `on:click` becomes `onclick`. Leave the\nsvelte-headless-table wiring alone, because the guide has nothing to say about\nit. The checker now says:\n\n<!-- captured: 04-svelte5-runes-component.txt -->\n```text\n$ npx svelte-check --tsconfig ./tsconfig.json --output human --threshold warning\n<lab>\\src\\PeopleTable.svelte:19:35\nWarn: This reference only captures the initial value of `people`. Did you mean to reference it inside a closure instead?\nhttps://svelte.dev/e/state_referenced_locally (svelte)\n\n<lab>\\src\\PeopleTable.svelte:27:44\nWarn: This reference only captures the initial value of `pageSize`. Did you mean to reference it inside a closure instead?\nhttps://svelte.dev/e/state_referenced_locally (svelte)\n\n====================================\nsvelte-check found 0 errors and 2 warnings in 1 file\n```\n\nTwo warnings, no errors, and both are the same fact: the library takes a store,\nyour data is now a rune, and the `writable(people)` you built to bridge them\ncaptured the first value of `people` and nothing after. The fix is an\n`$effect` that writes the prop into the store on every change, which is what\nthe ported fixture does, and it works. It is also a bridge you now own, in\nevery component that has a table, between a reactivity model the library was\nbuilt for and the one your app is written in.\n\nThat is the actual shape of the problem. Not a red build: a component that\ncompiles, with a store-and-slot-props library bolted to a runes app by code you\nmaintain, on a package that will not move. The pieces it leans on are the ones\nSvelte 5 has deprecated: `let:` slot props and `<slot>` in favour of snippets,\nand `<svelte:component>`, which is what `<Render>` uses underneath\n(`svelte-render` 2.0.1, `PropsRenderer.svelte`, peer `svelte ^4.0.0`). They\nkeep working in legacy mode today; deprecated syntax is what the next major\nremoves, and this library will not be updated when it does.\n\n## The three ways out\n\nYou have three honest options, and you should know all of them before picking.\n\n1. **`@humanspeak/svelte-headless-table`**, a maintained fork on Svelte 5 with\n the same API. Its version, publish date and downloads are in the facts box.\n Switching is one package rename; you keep every line of markup and every\n `<Subscribe>`, and you keep the store bridge from step 3. If your table\n works and Svelte 5 is all you need, this is the cheapest exit by a wide\n margin.\n2. **TanStack Table v9.** Its Svelte adapter declares a Svelte 5 peer range and\n its state shape is runes-first, so the bridge goes away. It is still\n headless: you write and maintain the `<table>`, the virtualizer, the filter\n UI and the editors yourself. The\n [TanStack migration guide](./migrating-from-tanstack-table.md) covers the\n vocabulary.\n3. **SvGrid.** A different trade: you delete the markup and take a renderer.\n The column definitions and the plugin list carry over; the `<table>`, the\n `<Subscribe>` blocks, the pager and the store bridge do not exist any more,\n because `<SvGrid>` renders all of that. The rest of this page is what that\n looks like on the fixture above.\n\nPick 1 if the markup is fine and the library being dead does not bother you.\nPick 2 if you want the markup and a maintained engine. Pick 3 if the markup is\nthe part you are tired of.\n\n## Step 4: the codemod\n\n`npx @svgrid/migrate` ports a svelte-headless-table component to SvGrid. It\npreviews by default and only writes with `--write`, and it says what it could\nnot map instead of dropping it. On the Svelte 4 original:\n\n<!-- captured: 05-codemod.txt -->\n```text\n warning A custom `cell` renderer was found. SvGrid renders cells with a snippet, not `createRender`, so this one needs porting by hand - it is preserved as a comment.\n warning The template still reads `pageIndex`, `pageCount`, `shown` from the view model, which is gone. <SvGrid> renders its own pager and row count (`pageable`, `showPagination`), so remove that markup, or read the grid through `onApiReady` if you need the numbers.\n warning The table markup dispatched `select` from a row; that handler went with the `<tr>`. Wire it to `onRowClick={({ row }) => ...}` (or `onCellClick`) on <SvGrid>, and turn the `createEventDispatcher` into a callback prop if the component is moving to runes.\n note Column resizing, keyboard navigation and ARIA grid semantics are built into <SvGrid>; the markup that provided them is intentionally gone.\n\n1 file(s) would change, with 3 warning(s).\nRe-run with --write to apply.\n```\n\nThree warnings, each naming a thing it left for you. Write it, swap the\npackages, and check:\n\n<!-- captured: 06-after-codemod.txt -->\n```text\n$ npm install @svgrid/grid@3.0.4 --legacy-peer-deps\n\nadded 1 package in <time>\n\n(exit 0)\n\n$ npm uninstall svelte-headless-table --legacy-peer-deps\n\nremoved 4 packages in <time>\n\n(exit 0)\n\n$ npx svelte-check --tsconfig ./tsconfig.json --output human --threshold warning\n<lab>\\src\\PeopleTable.svelte:31:23\nError: `$pageIndex` is an illegal variable name. To reference a global variable called `$pageIndex`, use `globalThis.$pageIndex`\nhttps://svelte.dev/e/global_reference_invalid (svelte)\n```\n\n<!-- captured: 06-after-codemod.txt -->\n```text\nsvelte-check found 9 errors and 0 warnings in 1 file\n```\n\nAll nine are the pager `<p>` the second warning named, reading `shown`,\n`$pageIndex` and `$pageCount` from a view model that no longer exists. The\ncodemod does not delete markup outside the `<table>`, because it cannot know\nwhat else is in there; it tells you what will not compile. Delete the `<p>`\n(the grid draws its own pager), turn the `select` event into a callback prop\non `onRowClick` as the third warning says, and:\n\n<!-- captured: 07-hand-edits.txt -->\n```text\n$ npx svelte-check --tsconfig ./tsconfig.json --output human --threshold warning\nsvelte-check found 0 errors and 0 warnings\n```\n\n## What you end up with\n\nThe component after the codemod and the two hand edits:\n\n<!-- captured: PeopleTable.after.svelte -->\n```svelte\n<script lang=\"ts\">\n import { SvGrid, type GridColumns } from '@svgrid/grid'\n import type { Person } from './people'\n export let people: Person[] = []\n export let pageSize = 5\n export let onselect: (person: Person) => void = () => {}\n\n const columns: GridColumns<(typeof people)[number]> = [\n {\n header: 'Name',\n field: 'name',\n },\n {\n header: 'Department',\n field: 'department',\n },\n {\n header: 'City',\n field: 'city',\n },\n {\n header: 'Salary',\n field: 'salary',\n // TODO port: cell: ({ value }) => value.toLocaleString('en-US', { style: 'currency', currency: 'USD\n },\n ]\n</script>\n\n<SvGrid data={people} {columns} sortable filterable showColumnFilters pageable pageSize={pageSize}\n onRowClick={({ row }) => onselect(row)} />\n```\n\n83 lines became 31. The `TODO port:` comment is the one thing left to do by\nhand: the currency cell becomes `format: { type: 'currency', currency: 'USD' }`\non the column, and the comment goes. There is no store, no `$:`, no\n`<Subscribe>`, no `let:`, and nothing in the file that Svelte 5 has deprecated,\nso the same component moves to runes whenever you like with the official\nmigration script and nothing else to port.\n\n## What to read next\n\n- [Migrating from svelte-headless-table](./migrating-from-svelte-headless-table.md) -\n the plugin-by-plugin mapping and what the codemod will not do\n- [SvGrid vs svelte-headless-table](https://svgrid.com/compare/svelte-headless-table/) -\n the side-by-side, with a source and date for every claim\n- [Migrating from TanStack Table](./migrating-from-tanstack-table.md) - exit 2 in detail\n- [Migrating from the shadcn-svelte data table](./migrating-from-shadcn-data-table.md) -\n the same codemod on the TanStack-based recipe\n- [Why headless?](../why-headless.md) - if you want to keep your own markup\n on a maintained Svelte 5 engine, `@svgrid/grid/core` is that too\n\n## Frequently asked questions\n\n### Does svelte-headless-table work with Svelte 5?\n\nIn legacy mode, yes: the install prints a peer-dependency warning and the\nuntouched component type-checks clean, as the captures above show. What does\nnot work is moving a component that uses it to runes without maintaining a\nstore bridge yourself, and the library is not going to be updated for the\ndeprecations that bridge leans on.\n\n### Is the peer dependency conflict an error?\n\nOn npm 11 it is a warning and the install exits 0; on older npm it was an\n`ERESOLVE` error until you passed `--legacy-peer-deps`; pnpm warns. It never\nstops the code from running. It tells you the library was not built against\nthe Svelte you have.\n\n### Should I just use the maintained fork?\n\nIf your table works and all you need is Svelte 5, yes, and this page says so.\nThe fork keeps the same API, so you keep the same markup and the same store\nbridge. Move to SvGrid when the markup and the bridge are what you want gone.\n\n### How much of the port does the codemod do?\n\nThe column definitions, the plugin list and the `<table>` replacement, and it\nnames what it leaves: custom cell renderers, markup outside the table that read\nthe view model, and events the rows dispatched. On the fixture that was two\nhand edits and one `format` option.\n\n### Can I rerun this myself?\n\n`node tools/migration-lab/run.mjs` in the repo. It installs the pinned Svelte 4\ntoolchain into its own folder, upgrades it, runs the codemod from the checkout,\nand rewrites the captured files; the header of each one records the versions.\nBump the pins to try a newer Svelte.\n"
6638
6638
  },
6639
6639
  {
6640
6640
  "slug": "help/tailwind",
@@ -8608,7 +8608,7 @@ export const docs = [
8608
8608
  "path": "docs/_data/comparisons/ag-grid.json",
8609
8609
  "title": "SvGrid vs AG Grid (community + enterprise)",
8610
8610
  "section": "Comparisons",
8611
- "markdown": "# SvGrid vs AG Grid (community + enterprise)\n\nCanonical URL: https://svgrid.com/compare/ag-grid/\nFacts verified: 2026-09-12\nCompetitor package: ag-grid-community\nCompetitor site: https://www.ag-grid.com/\n\nAG Grid is the most widely used JavaScript data grid, sold for React, Angular, Vue and plain JavaScript, with Svelte covered only by community-built integrations.\n\n## Verdict\n\nAG Grid has the longer track record and the wider Enterprise catalogue; SvGrid is Svelte-5-native, smaller on a Svelte page, and puts most of what AG Grid sells as Enterprise into its MIT core. Pick AG Grid for parity with React and Angular teams; pick SvGrid for a Svelte-first stack.\n\nMigration guide: moving from AG Grid (community + enterprise) to SvGrid: https://svgrid.com/docs/help/migrating-from-ag-grid/\n\n## At a glance\n\n| Fact | SvGrid | AG Grid (community + enterprise) | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 36.3.0 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 4 Nov 2026 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | No Svelte package (JavaScript, React, Angular, Vue) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 16,400,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.9 KB JS + 11.3 KB CSS | 346.4 KB JS, no separate stylesheet | 9 Nov 2026 |\n| Frameworks | Svelte 5 | JavaScript, React, Angular, Vue | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | AG Grid Community is free under MIT. AG Grid Enterprise is listed at $999 USD per developer with one year of updates and Zendesk support; the Enterprise Bundle with AG Charts Enterprise is $1,498 USD per developer | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.33 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; ag-grid-community 36.3.0 entry `createGrid + AllCommunityModule + themeQuartz` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nAG Grid is the heavyweight of the category: a Community edition under MIT and an Enterprise edition sold per developer that adds the set filter, range selection, master/detail, tree data, row grouping, pivoting, integrated charts, Excel export and the server-side row model. Its own pages mark each of those as Enterprise, and the sources at the bottom of this page link to them.\n\nFor Svelte there is no official package. ag-grid.com names React, Angular, Vue and JavaScript and points Svelte users to community-built integrations, so in practice you call the JavaScript API from onMount and manage the DOM yourself. SvGrid is the inverse: a Svelte 5 component with runes and snippets, and a headless core underneath it.\n\n## Looking for an AG Grid alternative for Svelte?\n\nThe usual reason to look is that AG Grid on Svelte means the JavaScript API inside onMount plus a wrapper you do not control. SvGrid gives you a component that speaks runes natively and an MIT core with no row cap and no licence key. What you give up is breadth: AG Grid has more Enterprise modules, more integrations and a far larger body of examples, and if you need one grid across three frameworks it is still the right answer.\n\n## What they have in common\n\n- A full grid with sorting, filtering, grouping, virtualization, editing and selection.\n- Documentation with a runnable example per feature.\n- TypeScript-first APIs with an imperative grid API for code outside the component.\n- An MIT core plus a paid tier with support.\n- An official MCP server so AI assistants read the real docs instead of guessing.\n\n## Where SvGrid is stronger\n\n- Svelte 5 native: runes for state, snippets for cells, no wrapper layer and no DOM imperatives.\n- A smaller bundle on a Svelte page; the At a glance table above carries both measured numbers and the method.\n- Set-style Excel filters, cell-range selection with clipboard, master/detail, tree data, row grouping with aggregation, integrated charts, the column tool panel and the context menu are in the MIT core. AG Grid lists each of these under Enterprise. Flat server-side data (paging, infinite block scroll) is free in both; the server-side row model with lazy grouping, tree, pivot, transactions and selection across unloaded rows is a paid module in both.\n- In-grid AI helpers (natural-language filter, smart fill, summarise, classify, anomalies) ship free in @svgrid/grid with your own model provider.\n- @svgrid/mcp validates props and imports against the real API surface and scaffolds a project, on top of docs and examples.\n- @svgrid/enterprise costs $599 per developer per year for the enterprise grid, unlimited applications; AG Grid Enterprise's per-developer price is in the pricing line above.\n\n## Where AG Grid (community + enterprise) is stronger\n\n- A longer production record across very large enterprise deployments, and the largest body of third-party examples and answers of any grid.\n- The viewport row model, where the server pushes the visible window over a socket; SvGrid has no equivalent.\n- AG Charts, a separately licensed charting product with far more chart types than SvGridChart.\n- One grid API across React, Angular and Vue teams.\n- Enterprise support through Zendesk with one year of updates on the licence.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | AG Grid (community + enterprise) |\n| --- | --- | --- |\n| Svelte 5 native | Yes - runes and snippets | No - JavaScript build; Svelte is pointed to community-built integrations |\n| Sorting and filtering | Yes | Yes |\n| Excel-style set filter | Yes - MIT core | Paid tier - the Set Filter page is marked Enterprise |\n| Row and column virtualization | Yes | Yes |\n| Inline editing | Yes | Yes |\n| Cell-range selection and clipboard | Yes - MIT core, with a fill handle | Paid tier - Range Selection and Clipboard are Enterprise |\n| Master/detail | Yes - MIT core | Paid tier - Enterprise |\n| Tree data | Yes - MIT core | Paid tier - the Tree Data page is marked Enterprise |\n| Row grouping with aggregation | Yes - MIT core | Paid tier - Enterprise |\n| Pivot tables | Paid tier - @svgrid/enterprise | Paid tier - Enterprise |\n| Integrated charts | Yes - SvGridChart in the MIT core | Paid tier - Enterprise, through AG Charts |\n| Server-side data, flat (sort, filter, paging, infinite scroll) | Yes - MIT core: createServerDataSource, page or infinite block scroll | Yes - Infinite Row Model, Community |\n| Server-side row model (lazy grouping, tree, pivot, transactions, select-all across unloaded rows) | Paid tier - @svgrid/enterprise: createServerRowModel | Paid tier - Server-Side Row Model, Enterprise |\n| Global search over server-side data | Yes - filterModel.global goes to the server | No - the Quick Filter is not supported by the Infinite or Server-Side row models |\n| Viewport row model (server pushes the visible window) | No - not built; real-time deltas merge into loaded rows instead | Paid tier - Viewport Row Model, Enterprise |\n| CSV export | Yes - MIT core | Yes - Community, through the API |\n| Excel export | Paid tier - @svgrid/enterprise | Paid tier - Enterprise |\n| Column tool panel | Yes - MIT core | Paid tier - Tool Panels are Enterprise |\n| Context menu | Yes - MIT core | Paid tier - Enterprise |\n| MCP server for AI assistants | Yes - @svgrid/mcp, MIT: docs, examples, code check, scaffold, preview | Yes - ag-mcp, MIT: docs search, version detection, upgrade prompts |\n| In-grid AI helpers (natural-language filter, smart fill) | Yes - MIT core, bring your own model | No - not in the feature list |\n| Paid support | Yes - with @svgrid/enterprise, per developer per year | Yes - Enterprise licence, Zendesk |\n| Core licence | Yes - MIT | Yes - MIT (Community) |\n\n## Measured performance\n\nMeasured 28 Oct 2026 with the harness in the repository (pnpm bench:compare): 100,000 rows, fastest of 3 samples per operation, each grid in a fresh page, Chromium through Playwright, headless, on win32 10.0.26200 x64, Intel(R) Core(TM) Ultra 7 255U; a developer workstation, not a dedicated bench rig. Versions: @svgrid/grid 3.0.25, ag-grid-community 36.1.0. Lower is better. Tick: 1,000 of the rows replaced per tick with a new amount, the grid sorted by amount, on the update path each grid provides, timed until the changed cells paint; 180 ticks after 10 to warm up.\n\n| Operation | SvGrid | AG Grid (community + enterprise) |\n| --- | --- | --- |\n| Mount | 30.7 ms | 67 ms |\n| Sort, text column | 77.4 ms | 213.9 ms |\n| Sort, numeric column | 32.8 ms | 216.7 ms |\n| Filter, one column (indicative only) | 34.5 ms | 148.8 ms |\n| Scroll, p95 frame | 34.3 ms | 34.5 ms |\n| Live tick, 1,000 rows replaced, sorted by that column, p95 | 48.6 ms | 259.2 ms |\n| Ticks over one 60 Hz frame, of 180 | 115 | 180 |\n| Rows kept in the DOM (virtualization on) | 36 | 36 |\n\nThe filter row is not like for like: each grid is driven through its own single-column filter API, and the amount of work differs. The comparison guide explains the method, what is left out and why.\n\n## When to choose SvGrid\n\n- You are on Svelte 5 and want a grid shaped by Svelte idioms rather than a wrapper around a JavaScript build.\n- You want the set filter, master/detail, tree data, range selection, grouping and flat server-side infinite scroll without an Enterprise licence.\n- You want a paid support tier priced per developer per year at $599.\n- You want an assistant that can check the code it writes against the real API, not only read the docs.\n\n## When to choose AG Grid (community + enterprise)\n\n- You depend on a specific AG Grid Enterprise module, the viewport row model or server-side pivoting.\n- You run the same grid across React, Angular and Vue teams and want one library.\n- Your procurement already covers AG Grid Enterprise, or you need AG Charts.\n- You want the largest possible pool of existing examples, answers and contractors.\n\n## Migration effort\n\nEstimated effort: 1-3 hours per grid.\n\nWhat you give up:\n\n- AG Charts as a separately licensed charting product with far more chart types than SvGridChart.\n- The viewport row model; SvGrid's server-side row model covers sort, filter, grouping, tree, pivot, transactions and select-all across unloaded rows, but the server cannot push the visible window.\n- One grid API across React, Angular and Vue teams.\n- The largest body of third-party examples, Stack Overflow answers and contractors of any grid.\n\nMigration guide: moving from AG Grid (community + enterprise) to SvGrid: https://svgrid.com/docs/help/migrating-from-ag-grid/\n\n## Live example\n\nMigration From Ag Grid: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/139-migration-from-ag-grid/\n\n## The bottom line\n\nAG Grid is the safer pick for a multi-framework organisation, or when you need its deepest Enterprise modules, AG Charts or the viewport row model. For a Svelte-first team, SvGrid covers the Enterprise surface most teams actually buy AG Grid for, in the MIT core: master/detail, tree data, range selection, grouping, flat server-side infinite scroll and integrated charts, with pivot tables, the server-side row model and Excel, PDF and print output in the @svgrid/enterprise pack. The bundle and benchmark numbers on this page are measured on the dates shown, so read them rather than either vendor's adjectives.\n\n## Frequently asked questions\n\n### Does AG Grid support Svelte?\n\nNot with an official package. ag-grid.com names React, Angular, Vue and JavaScript, and points Svelte, Solid and Python users to community-built integrations. In practice you create the grid from the JavaScript API inside onMount and keep its state in sync with your Svelte state by hand.\n\n### Which AG Grid Enterprise features does SvGrid include in its MIT core?\n\nThe set-style Excel filter, cell-range selection with clipboard, master/detail, tree data, row grouping with aggregation, integrated charts, the column tool panel and the context menu. AG Grid's own pages list each of these under Enterprise. Pivot tables, the server-side row model (grouping, tree, pivot, transactions, selection) and Excel, PDF and print output are in @svgrid/enterprise, as they are in AG Grid Enterprise; flat server-side infinite scroll is free in both.\n\n### What does SvGrid not have that AG Grid Enterprise has?\n\nThe viewport row model, AG Charts as a full charting product, and the breadth of niche Enterprise modules that come from a decade of enterprise customers. SvGrid's server-side row model handles sort, filter, grouping, tree, pivot, transactions and selection across unloaded rows; if your requirement is the viewport model, AG Grid Enterprise is the better fit.\n\n### Does AG Grid have an MCP server too?\n\nYes. ag-mcp (MIT) gives an assistant AG Grid's docs, examples and version-specific upgrade prompts. @svgrid/mcp covers the same ground for SvGrid and adds a code checker that validates props and imports against the real API surface, a scaffold tool and a preview. Neither is an in-grid feature; SvGrid's natural-language filter, smart fill and summarise helpers are, and they ship free in @svgrid/grid with your own model provider.\n\n### How much does AG Grid Enterprise cost compared with SvGrid?\n\nAG Grid Enterprise is sold per developer with one year of updates; the price as ag-grid.com listed it on the date we read it is in the pricing line at the top of this page. SvGrid's core is MIT and @svgrid/enterprise is $599 per developer per year for the enterprise grid or $999 with the spreadsheet and Studio, both for unlimited applications. Compare what each paid tier adds before comparing prices: most of what AG Grid sells as Enterprise is in SvGrid's free core.\n\n### How long does a migration from AG Grid to SvGrid take?\n\nThe migration guide budgets one to three hours per grid. Column definitions map almost one to one, the imperative API has equivalents on SvGridApi, and most of the time goes into moving cell renderers to snippets. The guide also lists what does not map, so you can decide before you start.\n\n### Is SvGrid a good AG Grid alternative for Svelte?\n\nThe usual reason to look is that AG Grid on Svelte means the JavaScript API inside onMount plus a wrapper you do not control. SvGrid gives you a component that speaks runes natively and an MIT core with no row cap and no licence key. What you give up is breadth: AG Grid has more Enterprise modules, more integrations and a far larger body of examples, and if you need one grid across three frameworks it is still the right answer.\n\n## Related comparisons and docs\n\n- [SvGrid vs MUI X DataGrid](https://svgrid.com/compare/mui-x-datagrid/)\n- [SvGrid vs Handsontable](https://svgrid.com/compare/handsontable/)\n- [SvGrid vs TanStack Table (Svelte)](https://svgrid.com/compare/tanstack-table/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Performance benchmarks](https://svgrid.com/docs/help/benchmarks/)\n- [Server-side data](https://svgrid.com/docs/help/server-side-data/)\n- [MCP server](https://svgrid.com/docs/help/mcp-server/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- ag-pricing: Enterprise is per developer at $999 USD with one year of updates and Zendesk support; the Enterprise Bundle is $1,498 USD; Community is free under MIT (checked 12 Sep 2026) https://www.ag-grid.com/license-pricing/\n- ag-community-vs-enterprise: Lists Range Selection, Clipboard, Master/Detail, Row Grouping, Pivot Tables and Aggregations, Integrated Charts, Excel export, Server-Side Row Model, Tool Panels and Context Menu under Enterprise Features; no AI feature in either list (checked 12 Sep 2026) https://www.ag-grid.com/javascript-data-grid/community-vs-enterprise/\n- ag-set-filter: The Set Filter page is marked enterprise (checked 12 Sep 2026) https://www.ag-grid.com/javascript-data-grid/filter-set/\n- ag-tree-data: The Tree Data page is marked enterprise (checked 12 Sep 2026) https://www.ag-grid.com/javascript-data-grid/tree-data/\n- ag-csv-export: CSV export is available in Community through the API; the context-menu export and Excel export are Enterprise (checked 12 Sep 2026) https://www.ag-grid.com/javascript-data-grid/csv-export/\n- ag-mcp: Official MCP server installed with npx ag-mcp: search_docs, detect_version, set_version and list_versions tools, quick-start and upgrade-grid prompts, docs and examples as resources; described as help for integrating and maintaining grid code, not an in-grid feature. The ag-mcp package on npm is MIT (checked 12 Sep 2026) https://www.ag-grid.com/javascript-data-grid/mcp-server/\n- ag-home: Names React, Angular, Vue and JavaScript; says Svelte, Solid and Python users can use community-built integrations; the 36.1.0 release notes list an AI Coding Skill (checked 12 Sep 2026) https://www.ag-grid.com/\n- ag-row-models: The row-models feature table lists the Infinite Row Model as Community and the Server-Side and Viewport row models as Enterprise; the Quick Filter row is marked unsupported for the Infinite, Server-Side and Viewport models (checked 15 Sep 2026) https://www.ag-grid.com/javascript-data-grid/row-models/\n"
8611
+ "markdown": "# SvGrid vs AG Grid (community + enterprise)\n\nCanonical URL: https://svgrid.com/compare/ag-grid/\nFacts verified: 2026-09-12\nCompetitor package: ag-grid-community\nCompetitor site: https://www.ag-grid.com/\n\nAG Grid is the most widely used JavaScript data grid, sold for React, Angular, Vue and plain JavaScript, with Svelte covered only by community-built integrations.\n\n## Verdict\n\nAG Grid has the longer track record and the wider Enterprise catalogue; SvGrid is Svelte-5-native, smaller on a Svelte page, and puts most of what AG Grid sells as Enterprise into its MIT core. Pick AG Grid for parity with React and Angular teams; pick SvGrid for a Svelte-first stack.\n\nMigration guide: moving from AG Grid (community + enterprise) to SvGrid: https://svgrid.com/docs/help/migrating-from-ag-grid/\n\n## At a glance\n\n| Fact | SvGrid | AG Grid (community + enterprise) | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 36.3.0 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 4 Nov 2026 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | No Svelte package (JavaScript, React, Angular, Vue) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 16,400,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.6 KB JS + 11.4 KB CSS | 346.4 KB JS, no separate stylesheet | 9 Nov 2026 |\n| Frameworks | Svelte 5 | JavaScript, React, Angular, Vue | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | AG Grid Community is free under MIT. AG Grid Enterprise is listed at $999 USD per developer with one year of updates and Zendesk support; the Enterprise Bundle with AG Charts Enterprise is $1,498 USD per developer | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.34 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; ag-grid-community 36.3.0 entry `createGrid + AllCommunityModule + themeQuartz` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nAG Grid is the heavyweight of the category: a Community edition under MIT and an Enterprise edition sold per developer that adds the set filter, range selection, master/detail, tree data, row grouping, pivoting, integrated charts, Excel export and the server-side row model. Its own pages mark each of those as Enterprise, and the sources at the bottom of this page link to them.\n\nFor Svelte there is no official package. ag-grid.com names React, Angular, Vue and JavaScript and points Svelte users to community-built integrations, so in practice you call the JavaScript API from onMount and manage the DOM yourself. SvGrid is the inverse: a Svelte 5 component with runes and snippets, and a headless core underneath it.\n\n## Looking for an AG Grid alternative for Svelte?\n\nThe usual reason to look is that AG Grid on Svelte means the JavaScript API inside onMount plus a wrapper you do not control. SvGrid gives you a component that speaks runes natively and an MIT core with no row cap and no licence key. What you give up is breadth: AG Grid has more Enterprise modules, more integrations and a far larger body of examples, and if you need one grid across three frameworks it is still the right answer.\n\n## What they have in common\n\n- A full grid with sorting, filtering, grouping, virtualization, editing and selection.\n- Documentation with a runnable example per feature.\n- TypeScript-first APIs with an imperative grid API for code outside the component.\n- An MIT core plus a paid tier with support.\n- An official MCP server so AI assistants read the real docs instead of guessing.\n\n## Where SvGrid is stronger\n\n- Svelte 5 native: runes for state, snippets for cells, no wrapper layer and no DOM imperatives.\n- A smaller bundle on a Svelte page; the At a glance table above carries both measured numbers and the method.\n- Set-style Excel filters, cell-range selection with clipboard, master/detail, tree data, row grouping with aggregation, integrated charts, the column tool panel and the context menu are in the MIT core. AG Grid lists each of these under Enterprise. Flat server-side data (paging, infinite block scroll) is free in both; the server-side row model with lazy grouping, tree, pivot, transactions and selection across unloaded rows is a paid module in both.\n- In-grid AI helpers (natural-language filter, smart fill, summarise, classify, anomalies) ship free in @svgrid/grid with your own model provider.\n- @svgrid/mcp validates props and imports against the real API surface and scaffolds a project, on top of docs and examples.\n- @svgrid/enterprise costs $599 per developer per year for the enterprise grid, unlimited applications; AG Grid Enterprise's per-developer price is in the pricing line above.\n\n## Where AG Grid (community + enterprise) is stronger\n\n- A longer production record across very large enterprise deployments, and the largest body of third-party examples and answers of any grid.\n- The viewport row model, where the server pushes the visible window over a socket; SvGrid has no equivalent.\n- AG Charts, a separately licensed charting product with far more chart types than SvGridChart.\n- One grid API across React, Angular and Vue teams.\n- Enterprise support through Zendesk with one year of updates on the licence.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | AG Grid (community + enterprise) |\n| --- | --- | --- |\n| Svelte 5 native | Yes - runes and snippets | No - JavaScript build; Svelte is pointed to community-built integrations |\n| Sorting and filtering | Yes | Yes |\n| Excel-style set filter | Yes - MIT core | Paid tier - the Set Filter page is marked Enterprise |\n| Row and column virtualization | Yes | Yes |\n| Inline editing | Yes | Yes |\n| Cell-range selection and clipboard | Yes - MIT core, with a fill handle | Paid tier - Range Selection and Clipboard are Enterprise |\n| Master/detail | Yes - MIT core | Paid tier - Enterprise |\n| Tree data | Yes - MIT core | Paid tier - the Tree Data page is marked Enterprise |\n| Row grouping with aggregation | Yes - MIT core | Paid tier - Enterprise |\n| Pivot tables | Paid tier - @svgrid/enterprise | Paid tier - Enterprise |\n| Integrated charts | Yes - SvGridChart in the MIT core | Paid tier - Enterprise, through AG Charts |\n| Server-side data, flat (sort, filter, paging, infinite scroll) | Yes - MIT core: createServerDataSource, page or infinite block scroll | Yes - Infinite Row Model, Community |\n| Server-side row model (lazy grouping, tree, pivot, transactions, select-all across unloaded rows) | Paid tier - @svgrid/enterprise: createServerRowModel | Paid tier - Server-Side Row Model, Enterprise |\n| Global search over server-side data | Yes - filterModel.global goes to the server | No - the Quick Filter is not supported by the Infinite or Server-Side row models |\n| Viewport row model (server pushes the visible window) | No - not built; real-time deltas merge into loaded rows instead | Paid tier - Viewport Row Model, Enterprise |\n| CSV export | Yes - MIT core | Yes - Community, through the API |\n| Excel export | Paid tier - @svgrid/enterprise | Paid tier - Enterprise |\n| Column tool panel | Yes - MIT core | Paid tier - Tool Panels are Enterprise |\n| Context menu | Yes - MIT core | Paid tier - Enterprise |\n| MCP server for AI assistants | Yes - @svgrid/mcp, MIT: docs, examples, code check, scaffold, preview | Yes - ag-mcp, MIT: docs search, version detection, upgrade prompts |\n| In-grid AI helpers (natural-language filter, smart fill) | Yes - MIT core, bring your own model | No - not in the feature list |\n| Paid support | Yes - with @svgrid/enterprise, per developer per year | Yes - Enterprise licence, Zendesk |\n| Core licence | Yes - MIT | Yes - MIT (Community) |\n\n## Measured performance\n\nMeasured 28 Oct 2026 with the harness in the repository (pnpm bench:compare): 100,000 rows, fastest of 3 samples per operation, each grid in a fresh page, Chromium through Playwright, headless, on win32 10.0.26200 x64, Intel(R) Core(TM) Ultra 7 255U; a developer workstation, not a dedicated bench rig. Versions: @svgrid/grid 3.0.25, ag-grid-community 36.1.0. Lower is better. Tick: 1,000 of the rows replaced per tick with a new amount, the grid sorted by amount, on the update path each grid provides, timed until the changed cells paint; 180 ticks after 10 to warm up.\n\n| Operation | SvGrid | AG Grid (community + enterprise) |\n| --- | --- | --- |\n| Mount | 30.7 ms | 67 ms |\n| Sort, text column | 77.4 ms | 213.9 ms |\n| Sort, numeric column | 32.8 ms | 216.7 ms |\n| Filter, one column (indicative only) | 34.5 ms | 148.8 ms |\n| Scroll, p95 frame | 34.3 ms | 34.5 ms |\n| Live tick, 1,000 rows replaced, sorted by that column, p95 | 48.6 ms | 259.2 ms |\n| Ticks over one 60 Hz frame, of 180 | 115 | 180 |\n| Rows kept in the DOM (virtualization on) | 36 | 36 |\n\nThe filter row is not like for like: each grid is driven through its own single-column filter API, and the amount of work differs. The comparison guide explains the method, what is left out and why.\n\n## When to choose SvGrid\n\n- You are on Svelte 5 and want a grid shaped by Svelte idioms rather than a wrapper around a JavaScript build.\n- You want the set filter, master/detail, tree data, range selection, grouping and flat server-side infinite scroll without an Enterprise licence.\n- You want a paid support tier priced per developer per year at $599.\n- You want an assistant that can check the code it writes against the real API, not only read the docs.\n\n## When to choose AG Grid (community + enterprise)\n\n- You depend on a specific AG Grid Enterprise module, the viewport row model or server-side pivoting.\n- You run the same grid across React, Angular and Vue teams and want one library.\n- Your procurement already covers AG Grid Enterprise, or you need AG Charts.\n- You want the largest possible pool of existing examples, answers and contractors.\n\n## Migration effort\n\nEstimated effort: 1-3 hours per grid.\n\nWhat you give up:\n\n- AG Charts as a separately licensed charting product with far more chart types than SvGridChart.\n- The viewport row model; SvGrid's server-side row model covers sort, filter, grouping, tree, pivot, transactions and select-all across unloaded rows, but the server cannot push the visible window.\n- One grid API across React, Angular and Vue teams.\n- The largest body of third-party examples, Stack Overflow answers and contractors of any grid.\n\nMigration guide: moving from AG Grid (community + enterprise) to SvGrid: https://svgrid.com/docs/help/migrating-from-ag-grid/\n\n## Live example\n\nMigration From Ag Grid: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/139-migration-from-ag-grid/\n\n## The bottom line\n\nAG Grid is the safer pick for a multi-framework organisation, or when you need its deepest Enterprise modules, AG Charts or the viewport row model. For a Svelte-first team, SvGrid covers the Enterprise surface most teams actually buy AG Grid for, in the MIT core: master/detail, tree data, range selection, grouping, flat server-side infinite scroll and integrated charts, with pivot tables, the server-side row model and Excel, PDF and print output in the @svgrid/enterprise pack. The bundle and benchmark numbers on this page are measured on the dates shown, so read them rather than either vendor's adjectives.\n\n## Frequently asked questions\n\n### Does AG Grid support Svelte?\n\nNot with an official package. ag-grid.com names React, Angular, Vue and JavaScript, and points Svelte, Solid and Python users to community-built integrations. In practice you create the grid from the JavaScript API inside onMount and keep its state in sync with your Svelte state by hand.\n\n### Which AG Grid Enterprise features does SvGrid include in its MIT core?\n\nThe set-style Excel filter, cell-range selection with clipboard, master/detail, tree data, row grouping with aggregation, integrated charts, the column tool panel and the context menu. AG Grid's own pages list each of these under Enterprise. Pivot tables, the server-side row model (grouping, tree, pivot, transactions, selection) and Excel, PDF and print output are in @svgrid/enterprise, as they are in AG Grid Enterprise; flat server-side infinite scroll is free in both.\n\n### What does SvGrid not have that AG Grid Enterprise has?\n\nThe viewport row model, AG Charts as a full charting product, and the breadth of niche Enterprise modules that come from a decade of enterprise customers. SvGrid's server-side row model handles sort, filter, grouping, tree, pivot, transactions and selection across unloaded rows; if your requirement is the viewport model, AG Grid Enterprise is the better fit.\n\n### Does AG Grid have an MCP server too?\n\nYes. ag-mcp (MIT) gives an assistant AG Grid's docs, examples and version-specific upgrade prompts. @svgrid/mcp covers the same ground for SvGrid and adds a code checker that validates props and imports against the real API surface, a scaffold tool and a preview. Neither is an in-grid feature; SvGrid's natural-language filter, smart fill and summarise helpers are, and they ship free in @svgrid/grid with your own model provider.\n\n### How much does AG Grid Enterprise cost compared with SvGrid?\n\nAG Grid Enterprise is sold per developer with one year of updates; the price as ag-grid.com listed it on the date we read it is in the pricing line at the top of this page. SvGrid's core is MIT and @svgrid/enterprise is $599 per developer per year for the enterprise grid or $999 with the spreadsheet and Studio, both for unlimited applications. Compare what each paid tier adds before comparing prices: most of what AG Grid sells as Enterprise is in SvGrid's free core.\n\n### How long does a migration from AG Grid to SvGrid take?\n\nThe migration guide budgets one to three hours per grid. Column definitions map almost one to one, the imperative API has equivalents on SvGridApi, and most of the time goes into moving cell renderers to snippets. The guide also lists what does not map, so you can decide before you start.\n\n### Is SvGrid a good AG Grid alternative for Svelte?\n\nThe usual reason to look is that AG Grid on Svelte means the JavaScript API inside onMount plus a wrapper you do not control. SvGrid gives you a component that speaks runes natively and an MIT core with no row cap and no licence key. What you give up is breadth: AG Grid has more Enterprise modules, more integrations and a far larger body of examples, and if you need one grid across three frameworks it is still the right answer.\n\n## Related comparisons and docs\n\n- [SvGrid vs MUI X DataGrid](https://svgrid.com/compare/mui-x-datagrid/)\n- [SvGrid vs Handsontable](https://svgrid.com/compare/handsontable/)\n- [SvGrid vs TanStack Table (Svelte)](https://svgrid.com/compare/tanstack-table/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Performance benchmarks](https://svgrid.com/docs/help/benchmarks/)\n- [Server-side data](https://svgrid.com/docs/help/server-side-data/)\n- [MCP server](https://svgrid.com/docs/help/mcp-server/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- ag-pricing: Enterprise is per developer at $999 USD with one year of updates and Zendesk support; the Enterprise Bundle is $1,498 USD; Community is free under MIT (checked 12 Sep 2026) https://www.ag-grid.com/license-pricing/\n- ag-community-vs-enterprise: Lists Range Selection, Clipboard, Master/Detail, Row Grouping, Pivot Tables and Aggregations, Integrated Charts, Excel export, Server-Side Row Model, Tool Panels and Context Menu under Enterprise Features; no AI feature in either list (checked 12 Sep 2026) https://www.ag-grid.com/javascript-data-grid/community-vs-enterprise/\n- ag-set-filter: The Set Filter page is marked enterprise (checked 12 Sep 2026) https://www.ag-grid.com/javascript-data-grid/filter-set/\n- ag-tree-data: The Tree Data page is marked enterprise (checked 12 Sep 2026) https://www.ag-grid.com/javascript-data-grid/tree-data/\n- ag-csv-export: CSV export is available in Community through the API; the context-menu export and Excel export are Enterprise (checked 12 Sep 2026) https://www.ag-grid.com/javascript-data-grid/csv-export/\n- ag-mcp: Official MCP server installed with npx ag-mcp: search_docs, detect_version, set_version and list_versions tools, quick-start and upgrade-grid prompts, docs and examples as resources; described as help for integrating and maintaining grid code, not an in-grid feature. The ag-mcp package on npm is MIT (checked 12 Sep 2026) https://www.ag-grid.com/javascript-data-grid/mcp-server/\n- ag-home: Names React, Angular, Vue and JavaScript; says Svelte, Solid and Python users can use community-built integrations; the 36.1.0 release notes list an AI Coding Skill (checked 12 Sep 2026) https://www.ag-grid.com/\n- ag-row-models: The row-models feature table lists the Infinite Row Model as Community and the Server-Side and Viewport row models as Enterprise; the Quick Filter row is marked unsupported for the Infinite, Server-Side and Viewport models (checked 15 Sep 2026) https://www.ag-grid.com/javascript-data-grid/row-models/\n"
8612
8612
  },
8613
8613
  {
8614
8614
  "slug": "compare/airtable",
@@ -8636,14 +8636,14 @@ export const docs = [
8636
8636
  "path": "docs/_data/comparisons/glide-data-grid.json",
8637
8637
  "title": "SvGrid vs Glide Data Grid",
8638
8638
  "section": "Comparisons",
8639
- "markdown": "# SvGrid vs Glide Data Grid\n\nCanonical URL: https://svgrid.com/compare/glide-data-grid/\nFacts verified: 2026-09-12\nCompetitor package: @glideapps/glide-data-grid\nCompetitor site: https://grid.glideapps.com/\n\nGlide Data Grid is a canvas-rendered React data grid built for extreme scroll performance on very large datasets.\n\n## Verdict\n\nGlide wins on raw canvas FPS for hundreds of thousands of visible cells. SvGrid renders accessible, selectable DOM with virtualization and is Svelte-5-native - the right call for most apps.\n\nMigration guide: moving from Glide Data Grid to SvGrid: https://svgrid.com/docs/help/migrating-from-glide/\n\n## At a glance\n\n| Fact | SvGrid | Glide Data Grid | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 6.0.3 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 3 Feb 2024 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | No Svelte package (React) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 2,010,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.9 KB JS + 11.3 KB CSS | 71.1 KB JS + 0.2 KB CSS, lodash + marked + react + react-dom + react-responsive-carousel external | 9 Nov 2026 |\n| Frameworks | Svelte 5 | React | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | Glide Data Grid is MIT and, in its own words, fully free and open source; no licence is sold for the grid | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.33 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; @glideapps/glide-data-grid 6.0.3 entry `DataEditor component` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nGlide Data Grid renders to a <canvas> instead of DOM, which gives it exceptional performance on very wide, very tall datasets at the cost of standard HTML semantics. It is React-only and MIT-licensed.\n\nSvGrid renders virtualized DOM: real table semantics, WAI-ARIA roles, keyboard navigation, and selectable / indexable text. For the vast majority of apps the performance gap is invisible, and you keep accessibility and SEO-friendly markup.\n\n## Looking for a Glide Data Grid alternative for Svelte?\n\nGlide renders to canvas, which is why it is fast and also why text selection, accessibility and custom cells work differently there. SvGrid renders real DOM with virtualization, so a screen reader and browser find behave normally and a cell can be any Svelte snippet. If your bar is a million-row canvas scroll inside React, Glide is still the specialist.\n\n## What they have in common\n\n- MIT-licensed.\n- Virtualized rendering for large datasets.\n- Cell editing and custom cell content.\n- TypeScript-first.\n\n## Where SvGrid is stronger\n\n- Renders real DOM - WAI-ARIA, keyboard nav, screen-reader support, selectable text.\n- Svelte 5 native rather than React-only.\n- Excel-style filter menu, headless engine, and the imperative API out of the box.\n- @svgrid/mcp MCP server for AI assistants.\n\n## Where Glide Data Grid is stronger\n\n- Peak canvas rendering performance on hundreds of thousands of visible cells.\n- Per-pixel custom cell drawing.\n- Proven inside Glide's own product at scale.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | Glide Data Grid |\n| --- | --- | --- |\n| Svelte 5 native | Yes | No - React only |\n| Rendering | Yes - Accessible DOM | Partial - canvas |\n| WAI-ARIA + keyboard | Yes | Partial - Limited (canvas) |\n| Selectable / indexable text | Yes | No - Canvas pixels |\n| Peak FPS on 200k+ visible cells | Partial - Good | Yes - Best |\n| Virtualization | Yes | Yes |\n| Excel-style filters | Yes | No - BYO |\n| AI / MCP integration | Yes | No |\n\n## When to choose SvGrid\n\n- You need accessibility, keyboard support, or selectable text.\n- You are on Svelte 5 and want a native grid.\n- You want filters, editing, and an imperative API without building them.\n\n## When to choose Glide Data Grid\n\n- You have measured a need for peak canvas FPS on 200k+ simultaneously visible cells.\n- You require per-pixel custom cell drawing.\n- Your app is React and accessibility is not a requirement.\n\n## Migration effort\n\nEstimated effort: 3-6 hours per grid.\n\nWhat you give up:\n\n- Canvas rendering throughput on very wide, very dense sheets.\n- The React ecosystem around it, including Glide Data Editor.\n\nMigration guide: moving from Glide Data Grid to SvGrid: https://svgrid.com/docs/help/migrating-from-glide/\n\n## Live example\n\nHeadless Virtual: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/187-headless-virtual/\n\n## The bottom line\n\nGlide is the right tool when you have measured a need for canvas-level FPS on hundreds of thousands of visible cells. For everyone else - and especially when accessibility, selectable text, or Svelte matter - the virtualized DOM in SvGrid is the better default.\n\n## Frequently asked questions\n\n### SvGrid vs Glide Data Grid - which should I use?\n\nUse SvGrid unless you have a measured need for canvas rendering at extreme scale. SvGrid renders accessible DOM and is Svelte-native; Glide is React-only and canvas-based.\n\n### Is Glide faster than SvGrid?\n\nAt hundreds of thousands of simultaneously visible cells, canvas rendering gives Glide higher peak FPS. For typical datasets the difference is invisible, and SvGrid virtualizes comfortably to 100k+ rows.\n\n### Does SvGrid handle accessibility better than Glide?\n\nYes. SvGrid renders real DOM with WAI-ARIA roles, keyboard navigation, and selectable text; a canvas grid like Glide cannot offer those natively.\n\n### Is SvGrid a good Glide Data Grid alternative for Svelte?\n\nGlide renders to canvas, which is why it is fast and also why text selection, accessibility and custom cells work differently there. SvGrid renders real DOM with virtualization, so a screen reader and browser find behave normally and a cell can be any Svelte snippet. If your bar is a million-row canvas scroll inside React, Glide is still the specialist.\n\n## Related comparisons and docs\n\n- [SvGrid vs React Data Grid (adazzle)](https://svgrid.com/compare/react-data-grid/)\n- [SvGrid vs MUI X DataGrid](https://svgrid.com/compare/mui-x-datagrid/)\n- [SvGrid vs AG Grid (community + enterprise)](https://svgrid.com/compare/ag-grid/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Headless virtualization](https://svgrid.com/docs/help/headless/virtualization/)\n- [Accessibility](https://svgrid.com/docs/help/accessibility/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- glide-site: MIT, fully free and open source; a React data grid that scales to millions of rows with lazy cell rendering and native scrolling (checked 12 Sep 2026) https://grid.glideapps.com/\n- glide-readme: README explains why the grid renders on an HTML canvas; supports React 16 and later (checked 12 Sep 2026) https://github.com/glideapps/glide-data-grid\n"
8639
+ "markdown": "# SvGrid vs Glide Data Grid\n\nCanonical URL: https://svgrid.com/compare/glide-data-grid/\nFacts verified: 2026-09-12\nCompetitor package: @glideapps/glide-data-grid\nCompetitor site: https://grid.glideapps.com/\n\nGlide Data Grid is a canvas-rendered React data grid built for extreme scroll performance on very large datasets.\n\n## Verdict\n\nGlide wins on raw canvas FPS for hundreds of thousands of visible cells. SvGrid renders accessible, selectable DOM with virtualization and is Svelte-5-native - the right call for most apps.\n\nMigration guide: moving from Glide Data Grid to SvGrid: https://svgrid.com/docs/help/migrating-from-glide/\n\n## At a glance\n\n| Fact | SvGrid | Glide Data Grid | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 6.0.3 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 3 Feb 2024 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | No Svelte package (React) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 2,010,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.6 KB JS + 11.4 KB CSS | 71.1 KB JS + 0.2 KB CSS, lodash + marked + react + react-dom + react-responsive-carousel external | 9 Nov 2026 |\n| Frameworks | Svelte 5 | React | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | Glide Data Grid is MIT and, in its own words, fully free and open source; no licence is sold for the grid | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.34 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; @glideapps/glide-data-grid 6.0.3 entry `DataEditor component` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nGlide Data Grid renders to a <canvas> instead of DOM, which gives it exceptional performance on very wide, very tall datasets at the cost of standard HTML semantics. It is React-only and MIT-licensed.\n\nSvGrid renders virtualized DOM: real table semantics, WAI-ARIA roles, keyboard navigation, and selectable / indexable text. For the vast majority of apps the performance gap is invisible, and you keep accessibility and SEO-friendly markup.\n\n## Looking for a Glide Data Grid alternative for Svelte?\n\nGlide renders to canvas, which is why it is fast and also why text selection, accessibility and custom cells work differently there. SvGrid renders real DOM with virtualization, so a screen reader and browser find behave normally and a cell can be any Svelte snippet. If your bar is a million-row canvas scroll inside React, Glide is still the specialist.\n\n## What they have in common\n\n- MIT-licensed.\n- Virtualized rendering for large datasets.\n- Cell editing and custom cell content.\n- TypeScript-first.\n\n## Where SvGrid is stronger\n\n- Renders real DOM - WAI-ARIA, keyboard nav, screen-reader support, selectable text.\n- Svelte 5 native rather than React-only.\n- Excel-style filter menu, headless engine, and the imperative API out of the box.\n- @svgrid/mcp MCP server for AI assistants.\n\n## Where Glide Data Grid is stronger\n\n- Peak canvas rendering performance on hundreds of thousands of visible cells.\n- Per-pixel custom cell drawing.\n- Proven inside Glide's own product at scale.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | Glide Data Grid |\n| --- | --- | --- |\n| Svelte 5 native | Yes | No - React only |\n| Rendering | Yes - Accessible DOM | Partial - canvas |\n| WAI-ARIA + keyboard | Yes | Partial - Limited (canvas) |\n| Selectable / indexable text | Yes | No - Canvas pixels |\n| Peak FPS on 200k+ visible cells | Partial - Good | Yes - Best |\n| Virtualization | Yes | Yes |\n| Excel-style filters | Yes | No - BYO |\n| AI / MCP integration | Yes | No |\n\n## When to choose SvGrid\n\n- You need accessibility, keyboard support, or selectable text.\n- You are on Svelte 5 and want a native grid.\n- You want filters, editing, and an imperative API without building them.\n\n## When to choose Glide Data Grid\n\n- You have measured a need for peak canvas FPS on 200k+ simultaneously visible cells.\n- You require per-pixel custom cell drawing.\n- Your app is React and accessibility is not a requirement.\n\n## Migration effort\n\nEstimated effort: 3-6 hours per grid.\n\nWhat you give up:\n\n- Canvas rendering throughput on very wide, very dense sheets.\n- The React ecosystem around it, including Glide Data Editor.\n\nMigration guide: moving from Glide Data Grid to SvGrid: https://svgrid.com/docs/help/migrating-from-glide/\n\n## Live example\n\nHeadless Virtual: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/187-headless-virtual/\n\n## The bottom line\n\nGlide is the right tool when you have measured a need for canvas-level FPS on hundreds of thousands of visible cells. For everyone else - and especially when accessibility, selectable text, or Svelte matter - the virtualized DOM in SvGrid is the better default.\n\n## Frequently asked questions\n\n### SvGrid vs Glide Data Grid - which should I use?\n\nUse SvGrid unless you have a measured need for canvas rendering at extreme scale. SvGrid renders accessible DOM and is Svelte-native; Glide is React-only and canvas-based.\n\n### Is Glide faster than SvGrid?\n\nAt hundreds of thousands of simultaneously visible cells, canvas rendering gives Glide higher peak FPS. For typical datasets the difference is invisible, and SvGrid virtualizes comfortably to 100k+ rows.\n\n### Does SvGrid handle accessibility better than Glide?\n\nYes. SvGrid renders real DOM with WAI-ARIA roles, keyboard navigation, and selectable text; a canvas grid like Glide cannot offer those natively.\n\n### Is SvGrid a good Glide Data Grid alternative for Svelte?\n\nGlide renders to canvas, which is why it is fast and also why text selection, accessibility and custom cells work differently there. SvGrid renders real DOM with virtualization, so a screen reader and browser find behave normally and a cell can be any Svelte snippet. If your bar is a million-row canvas scroll inside React, Glide is still the specialist.\n\n## Related comparisons and docs\n\n- [SvGrid vs React Data Grid (adazzle)](https://svgrid.com/compare/react-data-grid/)\n- [SvGrid vs MUI X DataGrid](https://svgrid.com/compare/mui-x-datagrid/)\n- [SvGrid vs AG Grid (community + enterprise)](https://svgrid.com/compare/ag-grid/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Headless virtualization](https://svgrid.com/docs/help/headless/virtualization/)\n- [Accessibility](https://svgrid.com/docs/help/accessibility/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- glide-site: MIT, fully free and open source; a React data grid that scales to millions of rows with lazy cell rendering and native scrolling (checked 12 Sep 2026) https://grid.glideapps.com/\n- glide-readme: README explains why the grid renders on an HTML canvas; supports React 16 and later (checked 12 Sep 2026) https://github.com/glideapps/glide-data-grid\n"
8640
8640
  },
8641
8641
  {
8642
8642
  "slug": "compare/gridjs",
8643
8643
  "path": "docs/_data/comparisons/gridjs.json",
8644
8644
  "title": "SvGrid vs Grid.js",
8645
8645
  "section": "Comparisons",
8646
- "markdown": "# SvGrid vs Grid.js\n\nCanonical URL: https://svgrid.com/compare/gridjs/\nFacts verified: 2026-09-12\nCompetitor package: gridjs\nCompetitor site: https://gridjs.io/\n\nGrid.js is a small, elegant, framework-agnostic table library focused on the essentials, MIT-licensed.\n\n## Verdict\n\nGrid.js is a lovely lightweight pick for search / sort / paginate. SvGrid is the fuller, Svelte-native grid when you need virtualization, editing, grouping, or large datasets.\n\nMigration guide: moving from Grid.js to SvGrid: https://svgrid.com/docs/help/migrating-from-gridjs/\n\n## At a glance\n\n| Fact | SvGrid | Grid.js | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 6.2.0 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 3 Mar 2024 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | No Svelte package (JavaScript) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 393,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.9 KB JS + 11.3 KB CSS | 17.8 KB JS + 2.4 KB CSS | 9 Nov 2026 |\n| Frameworks | Svelte 5 | JavaScript | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | Grid.js is MIT, free and open source; no licence is sold | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.33 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; gridjs 6.2.0 entry `Grid` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nGrid.js keeps a deliberately small surface: search, sort, pagination, and basic server-side data, rendered through a tiny vanilla-JS core with framework wrappers. It is MIT-licensed and easy to learn.\n\nSvGrid trades that minimalism for depth: a Svelte-5-native render component with virtualization, an Excel-style filter menu, inline editing, grouping, tree data, and an imperative API.\n\n## Looking for a Grid.js alternative for Svelte?\n\nGrid.js is deliberately small and covers the essentials well. People outgrow it at the same points every time: virtualization for large datasets, inline editing, row grouping and server-side data. SvGrid has those, and keeps a headless core so a simple table does not have to carry the weight of the full component.\n\n## What they have in common\n\n- MIT-licensed.\n- Search, sort, and pagination out of the box.\n- Server-side data support.\n- Small, approachable API.\n\n## Where SvGrid is stronger\n\n- Svelte 5 native instead of a vanilla core + wrapper.\n- Row + column virtualization for large datasets.\n- Excel-style filters, inline editing, grouping, tree, master/detail.\n- Headless engine + imperative API + @svgrid/mcp.\n\n## Where Grid.js is stronger\n\n- Tiny footprint if all you need is search / sort / paginate.\n- Framework-agnostic core.\n- Very fast to learn for a simple table.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | Grid.js |\n| --- | --- | --- |\n| Svelte 5 native | Yes | No - vanilla JavaScript with React, Angular and Vue wrappers |\n| Search / sort / paginate | Yes | Yes |\n| Excel-style filters | Yes | No |\n| Inline editing | Yes | No |\n| Virtualization | Yes | No |\n| Grouping / tree / master-detail | Yes | No |\n| Footprint for a simple table | Partial - Larger | Yes - Tiny |\n| AI / MCP integration | Yes | No |\n\n## When to choose SvGrid\n\n- You need virtualization, editing, grouping, or tree data.\n- You are on Svelte 5 and want a native component.\n- You expect the table to grow beyond search / sort / paginate.\n\n## When to choose Grid.js\n\n- You only need search / sort / paginate over a modest dataset.\n- You want the smallest possible footprint.\n- You want a framework-agnostic drop-in.\n\n## Migration effort\n\nEstimated effort: 30 minutes to 1 hour per table.\n\nWhat you give up:\n\n- A very small library for a simple table on any page.\n- Wrappers for React, Angular and Vue.\n\nMigration guide: moving from Grid.js to SvGrid: https://svgrid.com/docs/help/migrating-from-gridjs/\n\n## Live example\n\nExcel Filters: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/03-excel-filters/\n\n## The bottom line\n\nGrid.js is a lovely minimalist table for search, sort, and paginate. When you outgrow that - virtualization, editing, grouping, tree - SvGrid is the Svelte-native grid that already covers it.\n\n## Frequently asked questions\n\n### SvGrid vs Grid.js - which should I choose?\n\nGrid.js for a small table that only needs search, sort, and paginate; SvGrid when you need virtualization, editing, Excel-style filters, or grouping.\n\n### Is SvGrid heavier than Grid.js?\n\nYes, because it does much more. For a trivial table Grid.js is lighter; for a real data grid SvGrid pays for itself.\n\n### Does SvGrid support server-side data like Grid.js?\n\nYes - externalSort and externalFilter, plus the onSortingChange and onFiltersChange events.\n\n### Is SvGrid a good Grid.js alternative for Svelte?\n\nGrid.js is deliberately small and covers the essentials well. People outgrow it at the same points every time: virtualization for large datasets, inline editing, row grouping and server-side data. SvGrid has those, and keeps a headless core so a simple table does not have to carry the weight of the full component.\n\n## Related comparisons and docs\n\n- [SvGrid vs Tabulator](https://svgrid.com/compare/tabulator/)\n- [SvGrid vs @vincjo/datatables](https://svgrid.com/compare/vincjo-datatables/)\n- [SvGrid vs Flowbite / Skeleton / shadcn-svelte tables](https://svgrid.com/compare/svelte-ui-kit-tables/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Getting started with SvGrid](https://svgrid.com/docs/getting-started/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- gridjs-site: Free and open source under MIT; works with React, Angular, Vue and vanilla JavaScript; an extensible data pipeline (checked 12 Sep 2026) https://gridjs.io/\n"
8646
+ "markdown": "# SvGrid vs Grid.js\n\nCanonical URL: https://svgrid.com/compare/gridjs/\nFacts verified: 2026-09-12\nCompetitor package: gridjs\nCompetitor site: https://gridjs.io/\n\nGrid.js is a small, elegant, framework-agnostic table library focused on the essentials, MIT-licensed.\n\n## Verdict\n\nGrid.js is a lovely lightweight pick for search / sort / paginate. SvGrid is the fuller, Svelte-native grid when you need virtualization, editing, grouping, or large datasets.\n\nMigration guide: moving from Grid.js to SvGrid: https://svgrid.com/docs/help/migrating-from-gridjs/\n\n## At a glance\n\n| Fact | SvGrid | Grid.js | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 6.2.0 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 3 Mar 2024 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | No Svelte package (JavaScript) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 393,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.6 KB JS + 11.4 KB CSS | 17.8 KB JS + 2.4 KB CSS | 9 Nov 2026 |\n| Frameworks | Svelte 5 | JavaScript | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | Grid.js is MIT, free and open source; no licence is sold | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.34 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; gridjs 6.2.0 entry `Grid` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nGrid.js keeps a deliberately small surface: search, sort, pagination, and basic server-side data, rendered through a tiny vanilla-JS core with framework wrappers. It is MIT-licensed and easy to learn.\n\nSvGrid trades that minimalism for depth: a Svelte-5-native render component with virtualization, an Excel-style filter menu, inline editing, grouping, tree data, and an imperative API.\n\n## Looking for a Grid.js alternative for Svelte?\n\nGrid.js is deliberately small and covers the essentials well. People outgrow it at the same points every time: virtualization for large datasets, inline editing, row grouping and server-side data. SvGrid has those, and keeps a headless core so a simple table does not have to carry the weight of the full component.\n\n## What they have in common\n\n- MIT-licensed.\n- Search, sort, and pagination out of the box.\n- Server-side data support.\n- Small, approachable API.\n\n## Where SvGrid is stronger\n\n- Svelte 5 native instead of a vanilla core + wrapper.\n- Row + column virtualization for large datasets.\n- Excel-style filters, inline editing, grouping, tree, master/detail.\n- Headless engine + imperative API + @svgrid/mcp.\n\n## Where Grid.js is stronger\n\n- Tiny footprint if all you need is search / sort / paginate.\n- Framework-agnostic core.\n- Very fast to learn for a simple table.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | Grid.js |\n| --- | --- | --- |\n| Svelte 5 native | Yes | No - vanilla JavaScript with React, Angular and Vue wrappers |\n| Search / sort / paginate | Yes | Yes |\n| Excel-style filters | Yes | No |\n| Inline editing | Yes | No |\n| Virtualization | Yes | No |\n| Grouping / tree / master-detail | Yes | No |\n| Footprint for a simple table | Partial - Larger | Yes - Tiny |\n| AI / MCP integration | Yes | No |\n\n## When to choose SvGrid\n\n- You need virtualization, editing, grouping, or tree data.\n- You are on Svelte 5 and want a native component.\n- You expect the table to grow beyond search / sort / paginate.\n\n## When to choose Grid.js\n\n- You only need search / sort / paginate over a modest dataset.\n- You want the smallest possible footprint.\n- You want a framework-agnostic drop-in.\n\n## Migration effort\n\nEstimated effort: 30 minutes to 1 hour per table.\n\nWhat you give up:\n\n- A very small library for a simple table on any page.\n- Wrappers for React, Angular and Vue.\n\nMigration guide: moving from Grid.js to SvGrid: https://svgrid.com/docs/help/migrating-from-gridjs/\n\n## Live example\n\nExcel Filters: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/03-excel-filters/\n\n## The bottom line\n\nGrid.js is a lovely minimalist table for search, sort, and paginate. When you outgrow that - virtualization, editing, grouping, tree - SvGrid is the Svelte-native grid that already covers it.\n\n## Frequently asked questions\n\n### SvGrid vs Grid.js - which should I choose?\n\nGrid.js for a small table that only needs search, sort, and paginate; SvGrid when you need virtualization, editing, Excel-style filters, or grouping.\n\n### Is SvGrid heavier than Grid.js?\n\nYes, because it does much more. For a trivial table Grid.js is lighter; for a real data grid SvGrid pays for itself.\n\n### Does SvGrid support server-side data like Grid.js?\n\nYes - externalSort and externalFilter, plus the onSortingChange and onFiltersChange events.\n\n### Is SvGrid a good Grid.js alternative for Svelte?\n\nGrid.js is deliberately small and covers the essentials well. People outgrow it at the same points every time: virtualization for large datasets, inline editing, row grouping and server-side data. SvGrid has those, and keeps a headless core so a simple table does not have to carry the weight of the full component.\n\n## Related comparisons and docs\n\n- [SvGrid vs Tabulator](https://svgrid.com/compare/tabulator/)\n- [SvGrid vs @vincjo/datatables](https://svgrid.com/compare/vincjo-datatables/)\n- [SvGrid vs Flowbite / Skeleton / shadcn-svelte tables](https://svgrid.com/compare/svelte-ui-kit-tables/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Getting started with SvGrid](https://svgrid.com/docs/getting-started/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- gridjs-site: Free and open source under MIT; works with React, Angular, Vue and vanilla JavaScript; an extensible data pipeline (checked 12 Sep 2026) https://gridjs.io/\n"
8647
8647
  },
8648
8648
  {
8649
8649
  "slug": "compare/handsontable",
@@ -8671,7 +8671,7 @@ export const docs = [
8671
8671
  "path": "docs/_data/comparisons/mui-x-datagrid.json",
8672
8672
  "title": "SvGrid vs MUI X DataGrid",
8673
8673
  "section": "Comparisons",
8674
- "markdown": "# SvGrid vs MUI X DataGrid\n\nCanonical URL: https://svgrid.com/compare/mui-x-datagrid/\nFacts verified: 2026-09-12\nCompetitor package: @mui/x-data-grid\nCompetitor site: https://mui.com/x/react-data-grid/\n\nMUI X DataGrid is the data grid of the Material UI ecosystem on React, split into a free Community tier and paid Pro and Premium tiers.\n\n## Verdict\n\nMUI X is the obvious pick if you are already on Material UI and React. SvGrid is Svelte-5-native, ships more in its MIT core (pinning, master/detail, tree data, grouping and cell selection are not Pro or Premium features), and carries no Material Design opinion.\n\nMigration guide: moving from MUI X DataGrid to SvGrid: https://svgrid.com/docs/help/migrating-from-mui-x/\n\n## At a glance\n\n| Fact | SvGrid | MUI X DataGrid | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 9.17.0 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 30 Oct 2026 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | No Svelte package (React) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 13,100,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.9 KB JS + 11.3 KB CSS | 158.4 KB JS, no separate stylesheet, @emotion/react + @emotion/styled + @mui/material + @mui/system + react + react-dom external | 9 Nov 2026 |\n| Frameworks | Svelte 5 | React | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | MUI X Community is free under MIT. mui.com lists Pro at $299 per year per developer, Premium at $599 per year per developer and Enterprise at $1,399 per year per developer, with perpetual and annual licence models | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.33 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; @mui/x-data-grid 9.17.0 entry `DataGrid component` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nMUI X DataGrid is what most React teams on Material UI reach for. The Community edition is MIT and covers sorting, filtering, pagination, CSV export and row virtualization. Column pinning, column virtualization, row reordering, tree data and master/detail are Pro; row grouping, aggregation, cell selection, Excel export, pivoting and the AI assistant are Premium. Both paid tiers are sold per developer per year, and the sources below link to the pages that mark each feature.\n\nSvGrid is the inverse trade: one Svelte-5-native grid whose MIT core already includes pinning, master/detail, tree data, grouping with aggregation, cell-range selection with a fill handle, integrated charts and in-grid AI helpers you point at your own model, plus an optional @svgrid/enterprise pack for Excel, PDF and print output, import and pivot tables.\n\n## Looking for a MUI X DataGrid alternative for Svelte?\n\nMUI X DataGrid is React-only, so this is less an alternative than a port. The concepts carry over almost one to one: column definitions, a free tier and a paid tier, server-side rows, an imperative API. What does not carry over is Material Design: SvGrid is themed through CSS custom properties, so you bring your own look, and Emotion and Material UI stay out of the bundle.\n\n## What they have in common\n\n- A Community / paid split with an MIT free tier.\n- Sorting, filtering, pagination, virtualization and inline editing.\n- Server-side data through a row model the app feeds.\n- TypeScript-first with an imperative API for code outside the component.\n- An official MCP server so AI assistants read the real docs.\n- An in-grid AI assistant driven by natural language.\n\n## Where SvGrid is stronger\n\n- Svelte 5 native: runes and snippets, not a React component behind a wrapper.\n- Column pinning, master/detail, tree data, row grouping with aggregation and cell-range selection are in the MIT core; MUI X sells them as Pro or Premium.\n- The in-grid AI helpers (natural-language filter, smart fill, summarise, classify) are free in @svgrid/grid and run against a provider you register; MUI X's AI assistant is Premium and routes prompts through MUI's hosted service unless you build your own.\n- No Material Design opinion: theme through --sg-* tokens, with no Emotion or Material UI in the bundle. The At a glance table has the measured sizes.\n- Integrated charts in the MIT core, without a separate charts package.\n\n## Where MUI X DataGrid is stronger\n\n- First-class fit if the app is already built on Material UI and React: theming, date pickers and charts share one design system.\n- Pro and Premium features are vendor-supported with priority support and guaranteed response times on the Enterprise plan.\n- A very large React community and years of production use.\n- The Premium AI assistant comes with a hosted prompt service and starter credits, so there is nothing to run yourself.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | MUI X DataGrid |\n| --- | --- | --- |\n| Svelte 5 native | Yes - runes and snippets | No - React only |\n| Sorting, filtering, pagination | Yes | Yes - Community |\n| Row virtualization | Yes | Yes - Community |\n| Column virtualization | Yes | Paid tier - Pro |\n| Column pinning | Yes - MIT core, left and right | Paid tier - Pro |\n| Row reordering by drag | Yes - MIT core | Paid tier - Pro |\n| Master/detail | Yes - MIT core | Paid tier - Pro |\n| Tree data | Yes - MIT core | Paid tier - Pro |\n| Row grouping with aggregation | Yes - MIT core | Paid tier - Premium |\n| Cell-range selection and clipboard | Yes - MIT core, with a fill handle | Paid tier - Premium |\n| CSV export | Yes - MIT core | Yes - Community |\n| Excel export | Paid tier - @svgrid/enterprise | Paid tier - Premium |\n| Pivot tables | Paid tier - @svgrid/enterprise | Paid tier - Premium |\n| Integrated charts | Yes - SvGridChart in the MIT core | Partial - MUI X Charts is a separate package |\n| In-grid AI assistant | Yes - MIT core, bring your own model | Paid tier - Premium, through MUI's hosted service or your own proxy |\n| MCP server for AI assistants | Yes - @svgrid/mcp, MIT: docs, examples, code check, scaffold, preview | Yes - @mui/mcp, free: docs and examples |\n| Inline editing | Yes | Yes - Community |\n| Design-system independence | Yes - --sg-* tokens, no UI framework dependency | Partial - Material UI, Emotion and the MUI system are peer dependencies |\n| Core licence | Yes - MIT | Yes - MIT (Community) |\n\n## When to choose SvGrid\n\n- You are on Svelte 5 and want a grid shaped by runes, not a React component.\n- You want pinning, master/detail, tree data, grouping and cell selection without buying Pro or Premium.\n- You do not want Material Design, Emotion or the MUI system in your bundle.\n- You want the in-grid AI helpers to talk to a model you choose and host.\n\n## When to choose MUI X DataGrid\n\n- Your app is already built on Material UI and React.\n- You need Premium grouping, aggregation, pivoting or Excel export as vendor-supported features with a support contract.\n- You want one grid that matches React teammates across the MUI X suite, including date pickers and charts.\n- You want a hosted AI assistant with nothing to run yourself.\n\n## Migration effort\n\nEstimated effort: 1-3 hours per grid.\n\nWhat you give up:\n\n- Material Design out of the box; SvGrid ships neutral tokens and you theme it.\n- The rest of MUI X in the same design system: date pickers, charts and the tree view.\n- A hosted AI assistant with starter credits; SvGrid's helpers need a model provider you register.\n- React-specific patterns such as slots and hooks; SvGrid uses snippets and props.\n\nMigration guide: moving from MUI X DataGrid to SvGrid: https://svgrid.com/docs/help/migrating-from-mui-x/\n\n## Live example\n\nTree And Master Detail: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/08-tree-and-master-detail/\n\n## The bottom line\n\nIf your app already lives in Material UI and React, MUI X is the path of least resistance, and its Premium tier now includes a hosted AI assistant. On Svelte 5, SvGrid is the better fit: it puts pinning, master/detail, tree data, grouping and cell selection in the MIT core that MUI X reserves for Pro and Premium, keeps Material UI and Emotion out of the bundle, and runs its AI helpers against a model you choose.\n\n## Frequently asked questions\n\n### SvGrid vs MUI X DataGrid: which one for Svelte?\n\nSvGrid, if your stack is Svelte. MUI X is React-only and depends on Material UI, Emotion and the MUI system as peer dependencies; SvGrid is Svelte-5-native with no design-system dependency.\n\n### Which MUI X Pro and Premium features are free in SvGrid?\n\nColumn pinning, column virtualization, row reordering, master/detail and tree data (Pro in MUI X), and row grouping, aggregation and cell-range selection (Premium in MUI X) ship in the MIT core of SvGrid. Excel export and pivoting are paid on both sides: Premium in MUI X, @svgrid/enterprise in SvGrid.\n\n### Does MUI X have an AI assistant like SvGrid?\n\nYes, in Premium. mui.com describes a natural-language assistant (sort by name, show amounts larger than a value) that sends prompts through a proxy to MUI's hosted service with an API key, with starter credits included and the option to build your own processing service. SvGrid's natural-language filter, smart fill, summarise and classify helpers are free in @svgrid/grid and only run against a model provider you register, so nothing leaves your infrastructure unless you route it there.\n\n### Does MUI ship an MCP server?\n\nYes. @mui/mcp gives an AI client the official docs and code examples for Material UI and MUI X, including the Data Grid. @svgrid/mcp does the same for SvGrid and adds a code checker that validates props and imports against the real API surface, a scaffold tool and a preview.\n\n### Is SvGrid cheaper than MUI X Pro or Premium?\n\nThe prices mui.com listed on the date we read them are in the pricing line at the top of this page, per developer per year for Pro and Premium. SvGrid's core is MIT and @svgrid/enterprise is $599 per developer per year for the enterprise grid or $999 with the spreadsheet and Studio, both for unlimited applications. The difference is what the free tier holds: most features MUI X sells in Pro and Premium are in SvGrid's MIT core, so many teams never need the paid pack.\n\n### How long does a MUI X to SvGrid migration take?\n\nThe migration guide budgets one to three hours per grid. Column definitions and the row model map directly; the time goes into replacing React slots and renderCell functions with Svelte snippets and re-theming away from Material Design.\n\n### Is SvGrid a good MUI X DataGrid alternative for Svelte?\n\nMUI X DataGrid is React-only, so this is less an alternative than a port. The concepts carry over almost one to one: column definitions, a free tier and a paid tier, server-side rows, an imperative API. What does not carry over is Material Design: SvGrid is themed through CSS custom properties, so you bring your own look, and Emotion and Material UI stay out of the bundle.\n\n## Related comparisons and docs\n\n- [SvGrid vs AG Grid (community + enterprise)](https://svgrid.com/compare/ag-grid/)\n- [SvGrid vs React Data Grid (adazzle)](https://svgrid.com/compare/react-data-grid/)\n- [SvGrid vs Glide Data Grid](https://svgrid.com/compare/glide-data-grid/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [AI assistant](https://svgrid.com/docs/help/ai/)\n- [Column pinning](https://svgrid.com/docs/help/columns/column-pinning/)\n- [Master / detail (nested grids)](https://svgrid.com/docs/help/rows/master-detail/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- mui-overview: Feature list with plan badges: CSV export, cell editing and row virtualization in Community; column pinning, column reordering, row reordering, tree data and column virtualization Pro; row grouping, aggregation, Excel export and pivoting Premium; React package with Material UI peer dependencies (checked 12 Sep 2026) https://mui.com/x/react-data-grid/\n- mui-master-detail: Master-detail row panels carry the Pro plan badge (checked 12 Sep 2026) https://mui.com/x/react-data-grid/master-detail/\n- mui-cell-selection: Cell selection carries the Premium plan badge: with the Data Grid Premium, you can apply the cellSelection prop (checked 12 Sep 2026) https://mui.com/x/react-data-grid/cell-selection/\n- mui-ai-assistant: AI Assistant is Premium: natural-language prompts such as sort by name or show amounts larger than 1000, sent through a server-side proxy to MUI's hosted service with an API key from MUI Console; Premium licence holders get starter credits; a self-built prompt service is optional (checked 12 Sep 2026) https://mui.com/x/react-data-grid/ai-assistant/\n- mui-mcp: Official MCP server (@mui/mcp) that quotes the official docs and code examples for MUI X components including the Data Grid; installed with npx, no payment (checked 12 Sep 2026) https://mui.com/x/introduction/mcp/\n- mui-pricing: Community free forever under MIT; Pro $299 per year per dev; Premium $599 per year per dev; Enterprise $1,399 per year per dev; perpetual and annual models both allow perpetual production use (checked 12 Sep 2026) https://mui.com/pricing/\n"
8674
+ "markdown": "# SvGrid vs MUI X DataGrid\n\nCanonical URL: https://svgrid.com/compare/mui-x-datagrid/\nFacts verified: 2026-09-12\nCompetitor package: @mui/x-data-grid\nCompetitor site: https://mui.com/x/react-data-grid/\n\nMUI X DataGrid is the data grid of the Material UI ecosystem on React, split into a free Community tier and paid Pro and Premium tiers.\n\n## Verdict\n\nMUI X is the obvious pick if you are already on Material UI and React. SvGrid is Svelte-5-native, ships more in its MIT core (pinning, master/detail, tree data, grouping and cell selection are not Pro or Premium features), and carries no Material Design opinion.\n\nMigration guide: moving from MUI X DataGrid to SvGrid: https://svgrid.com/docs/help/migrating-from-mui-x/\n\n## At a glance\n\n| Fact | SvGrid | MUI X DataGrid | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 9.17.0 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 30 Oct 2026 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | No Svelte package (React) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 13,100,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.6 KB JS + 11.4 KB CSS | 158.4 KB JS, no separate stylesheet, @emotion/react + @emotion/styled + @mui/material + @mui/system + react + react-dom external | 9 Nov 2026 |\n| Frameworks | Svelte 5 | React | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | MUI X Community is free under MIT. mui.com lists Pro at $299 per year per developer, Premium at $599 per year per developer and Enterprise at $1,399 per year per developer, with perpetual and annual licence models | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.34 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; @mui/x-data-grid 9.17.0 entry `DataGrid component` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nMUI X DataGrid is what most React teams on Material UI reach for. The Community edition is MIT and covers sorting, filtering, pagination, CSV export and row virtualization. Column pinning, column virtualization, row reordering, tree data and master/detail are Pro; row grouping, aggregation, cell selection, Excel export, pivoting and the AI assistant are Premium. Both paid tiers are sold per developer per year, and the sources below link to the pages that mark each feature.\n\nSvGrid is the inverse trade: one Svelte-5-native grid whose MIT core already includes pinning, master/detail, tree data, grouping with aggregation, cell-range selection with a fill handle, integrated charts and in-grid AI helpers you point at your own model, plus an optional @svgrid/enterprise pack for Excel, PDF and print output, import and pivot tables.\n\n## Looking for a MUI X DataGrid alternative for Svelte?\n\nMUI X DataGrid is React-only, so this is less an alternative than a port. The concepts carry over almost one to one: column definitions, a free tier and a paid tier, server-side rows, an imperative API. What does not carry over is Material Design: SvGrid is themed through CSS custom properties, so you bring your own look, and Emotion and Material UI stay out of the bundle.\n\n## What they have in common\n\n- A Community / paid split with an MIT free tier.\n- Sorting, filtering, pagination, virtualization and inline editing.\n- Server-side data through a row model the app feeds.\n- TypeScript-first with an imperative API for code outside the component.\n- An official MCP server so AI assistants read the real docs.\n- An in-grid AI assistant driven by natural language.\n\n## Where SvGrid is stronger\n\n- Svelte 5 native: runes and snippets, not a React component behind a wrapper.\n- Column pinning, master/detail, tree data, row grouping with aggregation and cell-range selection are in the MIT core; MUI X sells them as Pro or Premium.\n- The in-grid AI helpers (natural-language filter, smart fill, summarise, classify) are free in @svgrid/grid and run against a provider you register; MUI X's AI assistant is Premium and routes prompts through MUI's hosted service unless you build your own.\n- No Material Design opinion: theme through --sg-* tokens, with no Emotion or Material UI in the bundle. The At a glance table has the measured sizes.\n- Integrated charts in the MIT core, without a separate charts package.\n\n## Where MUI X DataGrid is stronger\n\n- First-class fit if the app is already built on Material UI and React: theming, date pickers and charts share one design system.\n- Pro and Premium features are vendor-supported with priority support and guaranteed response times on the Enterprise plan.\n- A very large React community and years of production use.\n- The Premium AI assistant comes with a hosted prompt service and starter credits, so there is nothing to run yourself.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | MUI X DataGrid |\n| --- | --- | --- |\n| Svelte 5 native | Yes - runes and snippets | No - React only |\n| Sorting, filtering, pagination | Yes | Yes - Community |\n| Row virtualization | Yes | Yes - Community |\n| Column virtualization | Yes | Paid tier - Pro |\n| Column pinning | Yes - MIT core, left and right | Paid tier - Pro |\n| Row reordering by drag | Yes - MIT core | Paid tier - Pro |\n| Master/detail | Yes - MIT core | Paid tier - Pro |\n| Tree data | Yes - MIT core | Paid tier - Pro |\n| Row grouping with aggregation | Yes - MIT core | Paid tier - Premium |\n| Cell-range selection and clipboard | Yes - MIT core, with a fill handle | Paid tier - Premium |\n| CSV export | Yes - MIT core | Yes - Community |\n| Excel export | Paid tier - @svgrid/enterprise | Paid tier - Premium |\n| Pivot tables | Paid tier - @svgrid/enterprise | Paid tier - Premium |\n| Integrated charts | Yes - SvGridChart in the MIT core | Partial - MUI X Charts is a separate package |\n| In-grid AI assistant | Yes - MIT core, bring your own model | Paid tier - Premium, through MUI's hosted service or your own proxy |\n| MCP server for AI assistants | Yes - @svgrid/mcp, MIT: docs, examples, code check, scaffold, preview | Yes - @mui/mcp, free: docs and examples |\n| Inline editing | Yes | Yes - Community |\n| Design-system independence | Yes - --sg-* tokens, no UI framework dependency | Partial - Material UI, Emotion and the MUI system are peer dependencies |\n| Core licence | Yes - MIT | Yes - MIT (Community) |\n\n## When to choose SvGrid\n\n- You are on Svelte 5 and want a grid shaped by runes, not a React component.\n- You want pinning, master/detail, tree data, grouping and cell selection without buying Pro or Premium.\n- You do not want Material Design, Emotion or the MUI system in your bundle.\n- You want the in-grid AI helpers to talk to a model you choose and host.\n\n## When to choose MUI X DataGrid\n\n- Your app is already built on Material UI and React.\n- You need Premium grouping, aggregation, pivoting or Excel export as vendor-supported features with a support contract.\n- You want one grid that matches React teammates across the MUI X suite, including date pickers and charts.\n- You want a hosted AI assistant with nothing to run yourself.\n\n## Migration effort\n\nEstimated effort: 1-3 hours per grid.\n\nWhat you give up:\n\n- Material Design out of the box; SvGrid ships neutral tokens and you theme it.\n- The rest of MUI X in the same design system: date pickers, charts and the tree view.\n- A hosted AI assistant with starter credits; SvGrid's helpers need a model provider you register.\n- React-specific patterns such as slots and hooks; SvGrid uses snippets and props.\n\nMigration guide: moving from MUI X DataGrid to SvGrid: https://svgrid.com/docs/help/migrating-from-mui-x/\n\n## Live example\n\nTree And Master Detail: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/08-tree-and-master-detail/\n\n## The bottom line\n\nIf your app already lives in Material UI and React, MUI X is the path of least resistance, and its Premium tier now includes a hosted AI assistant. On Svelte 5, SvGrid is the better fit: it puts pinning, master/detail, tree data, grouping and cell selection in the MIT core that MUI X reserves for Pro and Premium, keeps Material UI and Emotion out of the bundle, and runs its AI helpers against a model you choose.\n\n## Frequently asked questions\n\n### SvGrid vs MUI X DataGrid: which one for Svelte?\n\nSvGrid, if your stack is Svelte. MUI X is React-only and depends on Material UI, Emotion and the MUI system as peer dependencies; SvGrid is Svelte-5-native with no design-system dependency.\n\n### Which MUI X Pro and Premium features are free in SvGrid?\n\nColumn pinning, column virtualization, row reordering, master/detail and tree data (Pro in MUI X), and row grouping, aggregation and cell-range selection (Premium in MUI X) ship in the MIT core of SvGrid. Excel export and pivoting are paid on both sides: Premium in MUI X, @svgrid/enterprise in SvGrid.\n\n### Does MUI X have an AI assistant like SvGrid?\n\nYes, in Premium. mui.com describes a natural-language assistant (sort by name, show amounts larger than a value) that sends prompts through a proxy to MUI's hosted service with an API key, with starter credits included and the option to build your own processing service. SvGrid's natural-language filter, smart fill, summarise and classify helpers are free in @svgrid/grid and only run against a model provider you register, so nothing leaves your infrastructure unless you route it there.\n\n### Does MUI ship an MCP server?\n\nYes. @mui/mcp gives an AI client the official docs and code examples for Material UI and MUI X, including the Data Grid. @svgrid/mcp does the same for SvGrid and adds a code checker that validates props and imports against the real API surface, a scaffold tool and a preview.\n\n### Is SvGrid cheaper than MUI X Pro or Premium?\n\nThe prices mui.com listed on the date we read them are in the pricing line at the top of this page, per developer per year for Pro and Premium. SvGrid's core is MIT and @svgrid/enterprise is $599 per developer per year for the enterprise grid or $999 with the spreadsheet and Studio, both for unlimited applications. The difference is what the free tier holds: most features MUI X sells in Pro and Premium are in SvGrid's MIT core, so many teams never need the paid pack.\n\n### How long does a MUI X to SvGrid migration take?\n\nThe migration guide budgets one to three hours per grid. Column definitions and the row model map directly; the time goes into replacing React slots and renderCell functions with Svelte snippets and re-theming away from Material Design.\n\n### Is SvGrid a good MUI X DataGrid alternative for Svelte?\n\nMUI X DataGrid is React-only, so this is less an alternative than a port. The concepts carry over almost one to one: column definitions, a free tier and a paid tier, server-side rows, an imperative API. What does not carry over is Material Design: SvGrid is themed through CSS custom properties, so you bring your own look, and Emotion and Material UI stay out of the bundle.\n\n## Related comparisons and docs\n\n- [SvGrid vs AG Grid (community + enterprise)](https://svgrid.com/compare/ag-grid/)\n- [SvGrid vs React Data Grid (adazzle)](https://svgrid.com/compare/react-data-grid/)\n- [SvGrid vs Glide Data Grid](https://svgrid.com/compare/glide-data-grid/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [AI assistant](https://svgrid.com/docs/help/ai/)\n- [Column pinning](https://svgrid.com/docs/help/columns/column-pinning/)\n- [Master / detail (nested grids)](https://svgrid.com/docs/help/rows/master-detail/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- mui-overview: Feature list with plan badges: CSV export, cell editing and row virtualization in Community; column pinning, column reordering, row reordering, tree data and column virtualization Pro; row grouping, aggregation, Excel export and pivoting Premium; React package with Material UI peer dependencies (checked 12 Sep 2026) https://mui.com/x/react-data-grid/\n- mui-master-detail: Master-detail row panels carry the Pro plan badge (checked 12 Sep 2026) https://mui.com/x/react-data-grid/master-detail/\n- mui-cell-selection: Cell selection carries the Premium plan badge: with the Data Grid Premium, you can apply the cellSelection prop (checked 12 Sep 2026) https://mui.com/x/react-data-grid/cell-selection/\n- mui-ai-assistant: AI Assistant is Premium: natural-language prompts such as sort by name or show amounts larger than 1000, sent through a server-side proxy to MUI's hosted service with an API key from MUI Console; Premium licence holders get starter credits; a self-built prompt service is optional (checked 12 Sep 2026) https://mui.com/x/react-data-grid/ai-assistant/\n- mui-mcp: Official MCP server (@mui/mcp) that quotes the official docs and code examples for MUI X components including the Data Grid; installed with npx, no payment (checked 12 Sep 2026) https://mui.com/x/introduction/mcp/\n- mui-pricing: Community free forever under MIT; Pro $299 per year per dev; Premium $599 per year per dev; Enterprise $1,399 per year per dev; perpetual and annual models both allow perpetual production use (checked 12 Sep 2026) https://mui.com/pricing/\n"
8675
8675
  },
8676
8676
  {
8677
8677
  "slug": "compare/nocodb",
@@ -8692,7 +8692,7 @@ export const docs = [
8692
8692
  "path": "docs/_data/comparisons/react-data-grid.json",
8693
8693
  "title": "SvGrid vs React Data Grid (adazzle)",
8694
8694
  "section": "Comparisons",
8695
- "markdown": "# SvGrid vs React Data Grid (adazzle)\n\nCanonical URL: https://svgrid.com/compare/react-data-grid/\nFacts verified: 2026-09-12\nCompetitor package: react-data-grid\nCompetitor site: https://github.com/adazzle/react-data-grid\n\nreact-data-grid is a fast, Excel-like data grid for React, MIT-licensed.\n\n## Verdict\n\nreact-data-grid is a strong, lightweight React grid with great editing. SvGrid is the Svelte-5-native equivalent, with a similar feature set and no React dependency.\n\nMigration guide: moving from React Data Grid (adazzle) to SvGrid: https://svgrid.com/docs/help/migrating-from-react-data-grid/\n\n## At a glance\n\n| Fact | SvGrid | React Data Grid (adazzle) | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 7.0.0-beta.64 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 5 Nov 2026 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | No Svelte package (React) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 2,650,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.9 KB JS + 11.3 KB CSS | 25.6 KB JS + 2.3 KB CSS, react + react-dom external | 9 Nov 2026 |\n| Frameworks | Svelte 5 | React | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | react-data-grid is MIT on npm and free; no licence is sold | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.33 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; react-data-grid 7.0.0-beta.64 entry `DataGrid component` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nreact-data-grid (the adazzle project) is a focused, performant React grid known for spreadsheet-style editing, virtualization, and a clean column API. It is MIT-licensed and React-only.\n\nSvGrid offers the same shape - virtualized DOM, typed columns, inline editing, custom cells - built on Svelte 5 runes and snippets rather than React components.\n\n## Looking for a React Data Grid alternative for Svelte?\n\nreact-data-grid is React-only, so this is a port rather than a swap, and the shapes line up well: both are Excel-like, both MIT, both driven by column definitions. Cell renderers become Svelte snippets and hooks become runes. If you are staying on React, there is no reason to move.\n\n## What they have in common\n\n- MIT-licensed.\n- Virtualized rows and columns.\n- Spreadsheet-style inline editing.\n- Typed column definitions.\n\n## Where SvGrid is stronger\n\n- Svelte 5 native - runes and snippets, not React.\n- Built-in Excel-style filter menu and the imperative API.\n- Grouping, tree data, and master/detail in the core.\n- @svgrid/mcp MCP server + optional Enterprise pack.\n\n## Where React Data Grid (adazzle) is stronger\n\n- First-class fit for a React codebase.\n- Mature, focused, and battle-tested in React apps.\n- Large React community.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | React Data Grid (adazzle) |\n| --- | --- | --- |\n| Svelte 5 native | Yes | No - React only |\n| Virtualization | Yes | Yes |\n| Inline editing | Yes | Yes |\n| Excel-style filter menu | Yes | Partial - BYO filter UI |\n| Grouping / tree | Yes | Yes - row grouping and a TreeDataGrid |\n| Master/detail | Yes | Partial - bring your own detail row |\n| Headless engine | Yes | No |\n| AI / MCP integration | Yes | No |\n| Fill handle and copy/paste | Yes | Yes - cell copy, paste and value dragging |\n\n## When to choose SvGrid\n\n- You are on Svelte 5 rather than React.\n- You want filters, grouping, and master/detail without building them.\n- You want a headless engine option and an MCP server.\n\n## When to choose React Data Grid (adazzle)\n\n- Your app is React and you want a focused, proven grid.\n- You want the React community and ecosystem around it.\n- You only need the feature set react-data-grid already covers.\n\n## Migration effort\n\nEstimated effort: 2-4 hours per grid.\n\nWhat you give up:\n\n- A very small React grid with the spreadsheet basics built in.\n- React 19 features such as the use hook in cell renderers.\n\nMigration guide: moving from React Data Grid (adazzle) to SvGrid: https://svgrid.com/docs/help/migrating-from-react-data-grid/\n\n## Live example\n\nFill Handle: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/95-fill-handle/\n\n## The bottom line\n\nreact-data-grid is a strong, focused choice in React. On Svelte 5, SvGrid is the equivalent - similar editing and virtualization - plus a built-in filter menu, grouping, and a headless core, with no React dependency.\n\n## Frequently asked questions\n\n### SvGrid vs react-data-grid - which for Svelte?\n\nSvGrid - it is Svelte-5-native, while react-data-grid is React-only. They share a similar editing and virtualization model.\n\n### Does SvGrid have built-in filtering unlike react-data-grid?\n\nYes - SvGrid ships an Excel-style filter menu and a global filter; react-data-grid leaves the filter UI to you.\n\n### Is SvGrid free like react-data-grid?\n\nYes, the core is MIT. SvGrid adds an optional Enterprise pack for export, import, pivot, and AI.\n\n### Is SvGrid a good React Data Grid alternative for Svelte?\n\nreact-data-grid is React-only, so this is a port rather than a swap, and the shapes line up well: both are Excel-like, both MIT, both driven by column definitions. Cell renderers become Svelte snippets and hooks become runes. If you are staying on React, there is no reason to move.\n\n## Related comparisons and docs\n\n- [SvGrid vs Glide Data Grid](https://svgrid.com/compare/glide-data-grid/)\n- [SvGrid vs MUI X DataGrid](https://svgrid.com/compare/mui-x-datagrid/)\n- [SvGrid vs AG Grid (community + enterprise)](https://svgrid.com/compare/ag-grid/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Cell text selection](https://svgrid.com/docs/help/cells/cell-text-selection/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- rdg-readme: React 19.2+; virtualization of rows and columns, multi-column sorting, cell editing, row grouping and a TreeDataGrid, frozen columns, cell copy and paste, cell value dragging; light and dark mode through color-scheme (checked 12 Sep 2026) https://github.com/adazzle/react-data-grid\n- rdg-npm: The latest tag is a 7.0 beta line; licence MIT (checked 12 Sep 2026) https://www.npmjs.com/package/react-data-grid\n"
8695
+ "markdown": "# SvGrid vs React Data Grid (adazzle)\n\nCanonical URL: https://svgrid.com/compare/react-data-grid/\nFacts verified: 2026-09-12\nCompetitor package: react-data-grid\nCompetitor site: https://github.com/adazzle/react-data-grid\n\nreact-data-grid is a fast, Excel-like data grid for React, MIT-licensed.\n\n## Verdict\n\nreact-data-grid is a strong, lightweight React grid with great editing. SvGrid is the Svelte-5-native equivalent, with a similar feature set and no React dependency.\n\nMigration guide: moving from React Data Grid (adazzle) to SvGrid: https://svgrid.com/docs/help/migrating-from-react-data-grid/\n\n## At a glance\n\n| Fact | SvGrid | React Data Grid (adazzle) | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 7.0.0-beta.64 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 5 Nov 2026 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | No Svelte package (React) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 2,650,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.6 KB JS + 11.4 KB CSS | 25.6 KB JS + 2.3 KB CSS, react + react-dom external | 9 Nov 2026 |\n| Frameworks | Svelte 5 | React | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | react-data-grid is MIT on npm and free; no licence is sold | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.34 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; react-data-grid 7.0.0-beta.64 entry `DataGrid component` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nreact-data-grid (the adazzle project) is a focused, performant React grid known for spreadsheet-style editing, virtualization, and a clean column API. It is MIT-licensed and React-only.\n\nSvGrid offers the same shape - virtualized DOM, typed columns, inline editing, custom cells - built on Svelte 5 runes and snippets rather than React components.\n\n## Looking for a React Data Grid alternative for Svelte?\n\nreact-data-grid is React-only, so this is a port rather than a swap, and the shapes line up well: both are Excel-like, both MIT, both driven by column definitions. Cell renderers become Svelte snippets and hooks become runes. If you are staying on React, there is no reason to move.\n\n## What they have in common\n\n- MIT-licensed.\n- Virtualized rows and columns.\n- Spreadsheet-style inline editing.\n- Typed column definitions.\n\n## Where SvGrid is stronger\n\n- Svelte 5 native - runes and snippets, not React.\n- Built-in Excel-style filter menu and the imperative API.\n- Grouping, tree data, and master/detail in the core.\n- @svgrid/mcp MCP server + optional Enterprise pack.\n\n## Where React Data Grid (adazzle) is stronger\n\n- First-class fit for a React codebase.\n- Mature, focused, and battle-tested in React apps.\n- Large React community.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | React Data Grid (adazzle) |\n| --- | --- | --- |\n| Svelte 5 native | Yes | No - React only |\n| Virtualization | Yes | Yes |\n| Inline editing | Yes | Yes |\n| Excel-style filter menu | Yes | Partial - BYO filter UI |\n| Grouping / tree | Yes | Yes - row grouping and a TreeDataGrid |\n| Master/detail | Yes | Partial - bring your own detail row |\n| Headless engine | Yes | No |\n| AI / MCP integration | Yes | No |\n| Fill handle and copy/paste | Yes | Yes - cell copy, paste and value dragging |\n\n## When to choose SvGrid\n\n- You are on Svelte 5 rather than React.\n- You want filters, grouping, and master/detail without building them.\n- You want a headless engine option and an MCP server.\n\n## When to choose React Data Grid (adazzle)\n\n- Your app is React and you want a focused, proven grid.\n- You want the React community and ecosystem around it.\n- You only need the feature set react-data-grid already covers.\n\n## Migration effort\n\nEstimated effort: 2-4 hours per grid.\n\nWhat you give up:\n\n- A very small React grid with the spreadsheet basics built in.\n- React 19 features such as the use hook in cell renderers.\n\nMigration guide: moving from React Data Grid (adazzle) to SvGrid: https://svgrid.com/docs/help/migrating-from-react-data-grid/\n\n## Live example\n\nFill Handle: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/95-fill-handle/\n\n## The bottom line\n\nreact-data-grid is a strong, focused choice in React. On Svelte 5, SvGrid is the equivalent - similar editing and virtualization - plus a built-in filter menu, grouping, and a headless core, with no React dependency.\n\n## Frequently asked questions\n\n### SvGrid vs react-data-grid - which for Svelte?\n\nSvGrid - it is Svelte-5-native, while react-data-grid is React-only. They share a similar editing and virtualization model.\n\n### Does SvGrid have built-in filtering unlike react-data-grid?\n\nYes - SvGrid ships an Excel-style filter menu and a global filter; react-data-grid leaves the filter UI to you.\n\n### Is SvGrid free like react-data-grid?\n\nYes, the core is MIT. SvGrid adds an optional Enterprise pack for export, import, pivot, and AI.\n\n### Is SvGrid a good React Data Grid alternative for Svelte?\n\nreact-data-grid is React-only, so this is a port rather than a swap, and the shapes line up well: both are Excel-like, both MIT, both driven by column definitions. Cell renderers become Svelte snippets and hooks become runes. If you are staying on React, there is no reason to move.\n\n## Related comparisons and docs\n\n- [SvGrid vs Glide Data Grid](https://svgrid.com/compare/glide-data-grid/)\n- [SvGrid vs MUI X DataGrid](https://svgrid.com/compare/mui-x-datagrid/)\n- [SvGrid vs AG Grid (community + enterprise)](https://svgrid.com/compare/ag-grid/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Cell text selection](https://svgrid.com/docs/help/cells/cell-text-selection/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- rdg-readme: React 19.2+; virtualization of rows and columns, multi-column sorting, cell editing, row grouping and a TreeDataGrid, frozen columns, cell copy and paste, cell value dragging; light and dark mode through color-scheme (checked 12 Sep 2026) https://github.com/adazzle/react-data-grid\n- rdg-npm: The latest tag is a 7.0 beta line; licence MIT (checked 12 Sep 2026) https://www.npmjs.com/package/react-data-grid\n"
8696
8696
  },
8697
8697
  {
8698
8698
  "slug": "compare/smart-grid",
@@ -8706,14 +8706,14 @@ export const docs = [
8706
8706
  "path": "docs/_data/comparisons/svar-svelte-datagrid.json",
8707
8707
  "title": "SvGrid vs SVAR Svelte DataGrid",
8708
8708
  "section": "Comparisons",
8709
- "markdown": "# SvGrid vs SVAR Svelte DataGrid\n\nCanonical URL: https://svgrid.com/compare/svar-svelte-datagrid/\nFacts verified: 2026-09-12\nCompetitor package: @svar-ui/svelte-grid\nCompetitor site: https://svar.dev/svelte/datagrid/\n\nSVAR Svelte DataGrid (@svar-ui/svelte-grid, formerly wx-svelte-grid) is a Svelte-native, MIT-licensed data grid from XB Software, the team behind Webix, with React and Vue versions of the same grid.\n\n## Verdict\n\nSVAR is the closest genuinely Svelte-native rival: both grids are MIT and both target Svelte 5. SvGrid has the wider capability surface (grouping with aggregation, master/detail, Excel-style range editing with a fill handle, integrated charts, a headless core, in-grid AI helpers and an MCP server); SVAR is the smaller grid with print in the free package, React and Vue versions, and the Webix team behind it.\n\nMigration guide: moving from SVAR Svelte DataGrid to SvGrid: https://svgrid.com/docs/help/migrating-from-svar-svelte-datagrid/\n\n## At a glance\n\n| Fact | SvGrid | SVAR Svelte DataGrid | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 2.7.6 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 7 Nov 2026 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | Yes (peer svelte ^5.0.0) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 106,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.9 KB JS + 11.3 KB CSS | 53.1 KB JS, no separate stylesheet, svelte external | 9 Nov 2026 |\n| Engine alone, minified + gzip | 3.2 KB JS, no separate stylesheet (`createSvGrid` from `@svgrid/grid/core`) | the row above; the package is the engine | 10 Nov 2026 |\n| Frameworks | Svelte 5 | Svelte, React, Vue | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | The DataGrid is MIT and free for commercial use with no paid tier; svar.dev sells PRO editions of its Gantt, Calendar and Kanban components and offers paid consulting and custom development, with no price list for the grid | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.33 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; @svar-ui/svelte-grid 2.7.6 entry `Grid component` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nSVAR DataGrid (npm: @svar-ui/svelte-grid; the older wx-svelte-grid package is deprecated and points to it) is part of the SVAR suite from XB Software, the makers of Webix, and is one of the few grids built for Svelte rather than wrapped from another framework. Its docs list in-cell editing, header and advanced filtering, single and multi-column sorting, tree data, virtual scrolling for rows and columns, columns pinned to the left, column and row spans in the header and footer, auto-sized rows, undo and redo, a context menu, row reordering, CSV export, a print API and a REST data provider, all under MIT.\n\nSvGrid overlaps on the Svelte-native angle and reaches further: row grouping with aggregation, master/detail, Excel-style cell-range selection with clipboard and a fill handle, pinned rows and left and right column pinning, integrated charts, a server-side row model, a headless engine, in-grid AI helpers and the @svgrid/mcp server, all in the MIT package. Excel, PDF and print output, import, pivot tables and the Kanban and Scheduler views of the grid live in the paid @svgrid/enterprise pack, whereas SVAR keeps its grid entirely free and sells PRO editions of its Gantt, Calendar and Kanban instead.\n\n## Looking for a SVAR Svelte DataGrid alternative for Svelte?\n\nThe closest comparison on this list, since both are Svelte-native and both are MIT, so licensing does not decide it. The differences are depth and direction: SvGrid ships a larger feature surface, a UI component suite, in-grid AI helpers and an MCP server, while SVAR spans Svelte, React and Vue and keeps a smaller core. The At a glance table above has both measured bundle sizes; if a compact MIT grid with sorting, filtering, editing, tree data and CSV export is all you need, SVAR is a perfectly good answer.\n\n## What they have in common\n\n- Purpose-built for Svelte 5, not a cross-framework wrapper.\n- MIT-licensed and free for commercial use.\n- Sorting, filtering, in-cell editing, virtualization on rows and columns, tree data.\n- Auto-sized row heights, undo and redo, a context menu and drag-and-drop row reordering.\n- Themeable through CSS variables with light and dark themes, localization, WAI-ARIA markup and keyboard navigation.\n\n## Where SvGrid is stronger\n\n- Row grouping with aggregation and a drag-and-drop group panel; SVAR's docs list neither.\n- Master/detail and expandable detail rows; SVAR offers tree data only.\n- Excel-style cell-range selection with clipboard copy and paste and a fill handle; SVAR selects rows.\n- Pinned top and bottom rows, and columns pinned left and right; SVAR pins columns to the left only.\n- Integrated charts with no dependency, plus a chart wizard.\n- A server-side row model with cursor pagination, GraphQL, websocket and optimistic updates, beyond a REST data provider.\n- A headless engine (createSvGrid) you can compose, in addition to the render component.\n- In-grid AI helpers free in @svgrid/grid, and @svgrid/mcp with llms.txt so assistants answer and write code accurately.\n- A paid pack with Excel, PDF and styled-HTML export, print, pivot tables, Excel and CSV import and support. CSV, TSV and JSON export are free in the grid.\n\n## Where SVAR Svelte DataGrid is stronger\n\n- The whole grid is free, print API included; SvGrid puts print and Excel and PDF export in the paid pack. Both export CSV for free.\n- The same grid for React and Vue as well as Svelte; SvGrid is Svelte-only by design.\n- A smaller bundle: the At a glance table has both measured numbers.\n- XB Software and Webix behind it, a team that has built data grids for a long time.\n- Part of the wider SVAR suite, with paid consulting and custom development on offer.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | SVAR Svelte DataGrid |\n| --- | --- | --- |\n| Svelte 5 native | Yes | Yes - Svelte 5 compatible |\n| Licence | Yes - MIT core, paid enterprise pack | Yes - MIT, the grid is entirely free |\n| Headless engine | Yes - createSvGrid | No - component only |\n| Excel-style filter menu | Yes - built in | Yes - header filters plus the SVAR Filter component |\n| Cell-range selection and clipboard | Yes - built in | No - single and multiple row selection |\n| Fill handle | Yes | No - not in the feature list |\n| Row grouping with aggregation | Yes - with a group panel | No - not in the feature list |\n| Master/detail rows | Yes | No - tree data only |\n| Tree data | Yes | Yes |\n| Pinned columns | Yes - left and right | Partial - to the left |\n| Pinned rows (top and bottom) | Yes | No - not in the feature list |\n| Header and footer column spans | Yes | Yes |\n| Auto-sized row height | Yes - autoRowHeight | Yes |\n| Virtualization (rows and columns) | Yes | Yes |\n| Undo and redo, context menu, row drag | Yes | Yes |\n| Integrated charts | Yes - no dependency, plus a chart wizard | No - not in the feature list |\n| Server-side data, flat (sort, filter, paging, infinite scroll) | Yes - createServerDataSource: page or infinite block scroll, cursor, GraphQL, websocket | Partial - RestDataProvider and dynamic loading while scrolling |\n| Server-side row model (lazy grouping, tree, pivot, transactions, select-all across unloaded rows) | Paid tier - @svgrid/enterprise | No - not in the feature list |\n| CSV export | Yes - free, with TSV and JSON | Yes - free |\n| Excel and PDF export | Paid tier - @svgrid/enterprise | No - CSV only in the feature list |\n| Print | Paid tier - @svgrid/enterprise | Yes - print API, free |\n| Pivot tables | Paid tier - @svgrid/enterprise | No - not in the SVAR Svelte product list |\n| React and Vue versions | No - Svelte only | Yes |\n| In-grid AI helpers and MCP server | Yes - helpers free in @svgrid/grid; @svgrid/mcp, MIT | No - not mentioned in the docs |\n| Paid support | Yes - with @svgrid/enterprise, per developer per year | Partial - paid consulting and custom development; no support plan for the grid listed |\n\n## When to choose SvGrid\n\n- You need grouping with aggregation, master/detail, Excel-style range editing or pivot tables, which SVAR's docs do not list.\n- You want a headless engine plus a render component, not a component-only API.\n- You want integrated charts and a full server-side row model in one library.\n- You want in-grid AI helpers, an MCP server that checks generated code, and a paid support tier.\n\n## When to choose SVAR Svelte DataGrid\n\n- You want a fully free grid with print included and no paid tier at all.\n- You ship to React and Vue as well as Svelte and want one grid across them.\n- A smaller bundle matters more than grouping with aggregation, master/detail, range editing and the other features SvGrid adds.\n- You are already adopting the wider SVAR suite: Gantt, Calendar, Kanban, File Manager.\n\n## Migration effort\n\nEstimated effort: 2-4 hours per grid.\n\nWhat you give up:\n\n- Free printing: SVAR's print API is in the MIT grid, SvGrid's print view is in @svgrid/enterprise.\n- The React and Vue versions of the same grid.\n- A smaller bundle, by the measurements in the At a glance table.\n- The SVAR suite around the grid: Gantt, Calendar, Kanban and File Manager share its core.\n\nMigration guide: moving from SVAR Svelte DataGrid to SvGrid: https://svgrid.com/docs/help/migrating-from-svar-svelte-datagrid/\n\n## Live example\n\nGrouping Aggregation: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/07-grouping-aggregation/\n\n## The bottom line\n\nBoth grids are Svelte-5-native and MIT, so this is not a licensing call. On capability SvGrid is the more complete grid: grouping, master/detail, range editing with a fill handle, charts, a server-side row model, a headless core, AI helpers and an MCP server. SVAR is the smaller, fully free, multi-framework option from the Webix team, and it prints for free where SvGrid charges for print and Excel and PDF export. Choose SvGrid when you need the deeper feature set or support; choose SVAR when a compact free grid covers your needs or you also ship React and Vue.\n\n## Frequently asked questions\n\n### SvGrid vs SVAR Svelte DataGrid: what is the difference?\n\nBoth are MIT-licensed, Svelte-5-native grids. SvGrid is the broader product: row grouping with aggregation, master/detail, Excel-style range selection with a fill handle, integrated charts, a server-side row model, a headless core, in-grid AI helpers and an MCP server. SVAR is a smaller, fully free grid with React and Vue versions from XB Software, with CSV export and a print API included.\n\n### Are SvGrid and SVAR both free?\n\nBoth are free under MIT, including commercial use. SVAR keeps the whole grid free, CSV export and print included, and sells PRO editions of its Gantt, Calendar and Kanban. SvGrid's grid is free too, including CSV, TSV and JSON export, charts and the AI helpers; Excel, PDF and print output, import, pivot tables, the Kanban and Scheduler views and support are in @svgrid/enterprise at $599 per developer per year.\n\n### Are both built for Svelte 5?\n\nYes. SvGrid is written in Svelte 5 runes, and svar.dev states the DataGrid is Svelte 5 compatible. Neither is a cross-framework wrapper, although SVAR also ships React and Vue versions of its grid.\n\n### Which grid is smaller?\n\nSVAR, by the measurements in the At a glance table: both packages were built alone with Vite, minified and gzipped with Svelte external, on the dates shown. SvGrid's extra size buys grouping, master/detail, range editing, charts and the server-side row model; features you never import, such as the date editors, menus and charts, load as separate chunks.\n\n### Does SVAR have row grouping, master/detail or cell-range selection?\n\nNot according to its docs overview on the date we read it, which lists tree data, single and multiple row selection, header and advanced filters, sorting, in-cell editing, columns pinned to the left, CSV export and a print API. SvGrid has all three in the MIT core, and the demos on this page show them.\n\n### How long does a SVAR to SvGrid migration take?\n\nThe migration guide budgets two to four hours per grid: a prop and event rename pass, since both use array-of-object column definitions, plus re-theming through --sg-* tokens.\n\n### Is SvGrid a good SVAR Svelte DataGrid alternative for Svelte?\n\nThe closest comparison on this list, since both are Svelte-native and both are MIT, so licensing does not decide it. The differences are depth and direction: SvGrid ships a larger feature surface, a UI component suite, in-grid AI helpers and an MCP server, while SVAR spans Svelte, React and Vue and keeps a smaller core. The At a glance table above has both measured bundle sizes; if a compact MIT grid with sorting, filtering, editing, tree data and CSV export is all you need, SVAR is a perfectly good answer.\n\n## Related comparisons and docs\n\n- [SvGrid vs svelte-headless-table](https://svgrid.com/compare/svelte-headless-table/)\n- [SvGrid vs TanStack Table (Svelte)](https://svgrid.com/compare/tanstack-table/)\n- [SvGrid vs @vincjo/datatables](https://svgrid.com/compare/vincjo-datatables/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Grouping & aggregation](https://svgrid.com/docs/help/grouping-aggregation/)\n- [Master / detail (nested grids)](https://svgrid.com/docs/help/rows/master-detail/)\n- [Build a table from scratch](https://svgrid.com/docs/help/headless/build-a-table/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- svar-datagrid: Licensed under MIT; Svelte 5 compatible; React and Vue versions available; lists multi-column sorting, header filters, in-cell editing, tree data, virtual scrolling, columns pinned to the left, context menu, row drag-and-drop, checkbox selection, pagination, hotkeys, WAI-ARIA, print, undo/redo (checked 12 Sep 2026) https://svar.dev/svelte/datagrid/\n- svar-overview: Feature list: in-cell editing, header and advanced filtering, sorting, single and multiple row selection, row reordering, context menu, undo/redo, tree data, pagination, colspans and rowspans in header and footer, collapsible column groups, pinned columns to the left, auto-sizing of rows and columns, localization, themes, export to CSV, print API, RestDataProvider, virtual scrolling for rows and columns, WAI-ARIA, keyboard navigation; no Excel export, row grouping, aggregation, master/detail, charts, AI or MCP (checked 12 Sep 2026) https://docs.svar.dev/svelte/grid/overview/\n- svar-svelte: DataGrid, Filter, Editor, File Manager and Core are MIT; Gantt, Calendar and Kanban have MIT cores with paid PRO editions; no pivot component in the list; no price list on the page (checked 12 Sep 2026) https://svar.dev/svelte/\n- svar-gantt: Offers paid consulting and custom development services; PRO edition pricing is on a separate page (checked 12 Sep 2026) https://svar.dev/svelte/gantt/\n"
8709
+ "markdown": "# SvGrid vs SVAR Svelte DataGrid\n\nCanonical URL: https://svgrid.com/compare/svar-svelte-datagrid/\nFacts verified: 2026-09-12\nCompetitor package: @svar-ui/svelte-grid\nCompetitor site: https://svar.dev/svelte/datagrid/\n\nSVAR Svelte DataGrid (@svar-ui/svelte-grid, formerly wx-svelte-grid) is a Svelte-native, MIT-licensed data grid from XB Software, the team behind Webix, with React and Vue versions of the same grid.\n\n## Verdict\n\nSVAR is the closest genuinely Svelte-native rival: both grids are MIT and both target Svelte 5. SvGrid has the wider capability surface (grouping with aggregation, master/detail, Excel-style range editing with a fill handle, integrated charts, a headless core, in-grid AI helpers and an MCP server); SVAR is the smaller grid with print in the free package, React and Vue versions, and the Webix team behind it.\n\nMigration guide: moving from SVAR Svelte DataGrid to SvGrid: https://svgrid.com/docs/help/migrating-from-svar-svelte-datagrid/\n\n## At a glance\n\n| Fact | SvGrid | SVAR Svelte DataGrid | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 2.7.6 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 7 Nov 2026 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | Yes (peer svelte ^5.0.0) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 106,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.6 KB JS + 11.4 KB CSS | 53.1 KB JS, no separate stylesheet, svelte external | 9 Nov 2026 |\n| Engine alone, minified + gzip | 3.2 KB JS, no separate stylesheet (`createSvGrid` from `@svgrid/grid/core`) | the row above; the package is the engine | 10 Nov 2026 |\n| Frameworks | Svelte 5 | Svelte, React, Vue | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | The DataGrid is MIT and free for commercial use with no paid tier; svar.dev sells PRO editions of its Gantt, Calendar and Kanban components and offers paid consulting and custom development, with no price list for the grid | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.34 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; @svar-ui/svelte-grid 2.7.6 entry `Grid component` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nSVAR DataGrid (npm: @svar-ui/svelte-grid; the older wx-svelte-grid package is deprecated and points to it) is part of the SVAR suite from XB Software, the makers of Webix, and is one of the few grids built for Svelte rather than wrapped from another framework. Its docs list in-cell editing, header and advanced filtering, single and multi-column sorting, tree data, virtual scrolling for rows and columns, columns pinned to the left, column and row spans in the header and footer, auto-sized rows, undo and redo, a context menu, row reordering, CSV export, a print API and a REST data provider, all under MIT.\n\nSvGrid overlaps on the Svelte-native angle and reaches further: row grouping with aggregation, master/detail, Excel-style cell-range selection with clipboard and a fill handle, pinned rows and left and right column pinning, integrated charts, a server-side row model, a headless engine, in-grid AI helpers and the @svgrid/mcp server, all in the MIT package. Excel, PDF and print output, import, pivot tables and the Kanban and Scheduler views of the grid live in the paid @svgrid/enterprise pack, whereas SVAR keeps its grid entirely free and sells PRO editions of its Gantt, Calendar and Kanban instead.\n\n## Looking for a SVAR Svelte DataGrid alternative for Svelte?\n\nThe closest comparison on this list, since both are Svelte-native and both are MIT, so licensing does not decide it. The differences are depth and direction: SvGrid ships a larger feature surface, a UI component suite, in-grid AI helpers and an MCP server, while SVAR spans Svelte, React and Vue and keeps a smaller core. The At a glance table above has both measured bundle sizes; if a compact MIT grid with sorting, filtering, editing, tree data and CSV export is all you need, SVAR is a perfectly good answer.\n\n## What they have in common\n\n- Purpose-built for Svelte 5, not a cross-framework wrapper.\n- MIT-licensed and free for commercial use.\n- Sorting, filtering, in-cell editing, virtualization on rows and columns, tree data.\n- Auto-sized row heights, undo and redo, a context menu and drag-and-drop row reordering.\n- Themeable through CSS variables with light and dark themes, localization, WAI-ARIA markup and keyboard navigation.\n\n## Where SvGrid is stronger\n\n- Row grouping with aggregation and a drag-and-drop group panel; SVAR's docs list neither.\n- Master/detail and expandable detail rows; SVAR offers tree data only.\n- Excel-style cell-range selection with clipboard copy and paste and a fill handle; SVAR selects rows.\n- Pinned top and bottom rows, and columns pinned left and right; SVAR pins columns to the left only.\n- Integrated charts with no dependency, plus a chart wizard.\n- A server-side row model with cursor pagination, GraphQL, websocket and optimistic updates, beyond a REST data provider.\n- A headless engine (createSvGrid) you can compose, in addition to the render component.\n- In-grid AI helpers free in @svgrid/grid, and @svgrid/mcp with llms.txt so assistants answer and write code accurately.\n- A paid pack with Excel, PDF and styled-HTML export, print, pivot tables, Excel and CSV import and support. CSV, TSV and JSON export are free in the grid.\n\n## Where SVAR Svelte DataGrid is stronger\n\n- The whole grid is free, print API included; SvGrid puts print and Excel and PDF export in the paid pack. Both export CSV for free.\n- The same grid for React and Vue as well as Svelte; SvGrid is Svelte-only by design.\n- A smaller bundle: the At a glance table has both measured numbers.\n- XB Software and Webix behind it, a team that has built data grids for a long time.\n- Part of the wider SVAR suite, with paid consulting and custom development on offer.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | SVAR Svelte DataGrid |\n| --- | --- | --- |\n| Svelte 5 native | Yes | Yes - Svelte 5 compatible |\n| Licence | Yes - MIT core, paid enterprise pack | Yes - MIT, the grid is entirely free |\n| Headless engine | Yes - createSvGrid | No - component only |\n| Excel-style filter menu | Yes - built in | Yes - header filters plus the SVAR Filter component |\n| Cell-range selection and clipboard | Yes - built in | No - single and multiple row selection |\n| Fill handle | Yes | No - not in the feature list |\n| Row grouping with aggregation | Yes - with a group panel | No - not in the feature list |\n| Master/detail rows | Yes | No - tree data only |\n| Tree data | Yes | Yes |\n| Pinned columns | Yes - left and right | Partial - to the left |\n| Pinned rows (top and bottom) | Yes | No - not in the feature list |\n| Header and footer column spans | Yes | Yes |\n| Auto-sized row height | Yes - autoRowHeight | Yes |\n| Virtualization (rows and columns) | Yes | Yes |\n| Undo and redo, context menu, row drag | Yes | Yes |\n| Integrated charts | Yes - no dependency, plus a chart wizard | No - not in the feature list |\n| Server-side data, flat (sort, filter, paging, infinite scroll) | Yes - createServerDataSource: page or infinite block scroll, cursor, GraphQL, websocket | Partial - RestDataProvider and dynamic loading while scrolling |\n| Server-side row model (lazy grouping, tree, pivot, transactions, select-all across unloaded rows) | Paid tier - @svgrid/enterprise | No - not in the feature list |\n| CSV export | Yes - free, with TSV and JSON | Yes - free |\n| Excel and PDF export | Paid tier - @svgrid/enterprise | No - CSV only in the feature list |\n| Print | Paid tier - @svgrid/enterprise | Yes - print API, free |\n| Pivot tables | Paid tier - @svgrid/enterprise | No - not in the SVAR Svelte product list |\n| React and Vue versions | No - Svelte only | Yes |\n| In-grid AI helpers and MCP server | Yes - helpers free in @svgrid/grid; @svgrid/mcp, MIT | No - not mentioned in the docs |\n| Paid support | Yes - with @svgrid/enterprise, per developer per year | Partial - paid consulting and custom development; no support plan for the grid listed |\n\n## When to choose SvGrid\n\n- You need grouping with aggregation, master/detail, Excel-style range editing or pivot tables, which SVAR's docs do not list.\n- You want a headless engine plus a render component, not a component-only API.\n- You want integrated charts and a full server-side row model in one library.\n- You want in-grid AI helpers, an MCP server that checks generated code, and a paid support tier.\n\n## When to choose SVAR Svelte DataGrid\n\n- You want a fully free grid with print included and no paid tier at all.\n- You ship to React and Vue as well as Svelte and want one grid across them.\n- A smaller bundle matters more than grouping with aggregation, master/detail, range editing and the other features SvGrid adds.\n- You are already adopting the wider SVAR suite: Gantt, Calendar, Kanban, File Manager.\n\n## Migration effort\n\nEstimated effort: 2-4 hours per grid.\n\nWhat you give up:\n\n- Free printing: SVAR's print API is in the MIT grid, SvGrid's print view is in @svgrid/enterprise.\n- The React and Vue versions of the same grid.\n- A smaller bundle, by the measurements in the At a glance table.\n- The SVAR suite around the grid: Gantt, Calendar, Kanban and File Manager share its core.\n\nMigration guide: moving from SVAR Svelte DataGrid to SvGrid: https://svgrid.com/docs/help/migrating-from-svar-svelte-datagrid/\n\n## Live example\n\nGrouping Aggregation: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/07-grouping-aggregation/\n\n## The bottom line\n\nBoth grids are Svelte-5-native and MIT, so this is not a licensing call. On capability SvGrid is the more complete grid: grouping, master/detail, range editing with a fill handle, charts, a server-side row model, a headless core, AI helpers and an MCP server. SVAR is the smaller, fully free, multi-framework option from the Webix team, and it prints for free where SvGrid charges for print and Excel and PDF export. Choose SvGrid when you need the deeper feature set or support; choose SVAR when a compact free grid covers your needs or you also ship React and Vue.\n\n## Frequently asked questions\n\n### SvGrid vs SVAR Svelte DataGrid: what is the difference?\n\nBoth are MIT-licensed, Svelte-5-native grids. SvGrid is the broader product: row grouping with aggregation, master/detail, Excel-style range selection with a fill handle, integrated charts, a server-side row model, a headless core, in-grid AI helpers and an MCP server. SVAR is a smaller, fully free grid with React and Vue versions from XB Software, with CSV export and a print API included.\n\n### Are SvGrid and SVAR both free?\n\nBoth are free under MIT, including commercial use. SVAR keeps the whole grid free, CSV export and print included, and sells PRO editions of its Gantt, Calendar and Kanban. SvGrid's grid is free too, including CSV, TSV and JSON export, charts and the AI helpers; Excel, PDF and print output, import, pivot tables, the Kanban and Scheduler views and support are in @svgrid/enterprise at $599 per developer per year.\n\n### Are both built for Svelte 5?\n\nYes. SvGrid is written in Svelte 5 runes, and svar.dev states the DataGrid is Svelte 5 compatible. Neither is a cross-framework wrapper, although SVAR also ships React and Vue versions of its grid.\n\n### Which grid is smaller?\n\nSVAR, by the measurements in the At a glance table: both packages were built alone with Vite, minified and gzipped with Svelte external, on the dates shown. SvGrid's extra size buys grouping, master/detail, range editing, charts and the server-side row model; features you never import, such as the date editors, menus and charts, load as separate chunks.\n\n### Does SVAR have row grouping, master/detail or cell-range selection?\n\nNot according to its docs overview on the date we read it, which lists tree data, single and multiple row selection, header and advanced filters, sorting, in-cell editing, columns pinned to the left, CSV export and a print API. SvGrid has all three in the MIT core, and the demos on this page show them.\n\n### How long does a SVAR to SvGrid migration take?\n\nThe migration guide budgets two to four hours per grid: a prop and event rename pass, since both use array-of-object column definitions, plus re-theming through --sg-* tokens.\n\n### Is SvGrid a good SVAR Svelte DataGrid alternative for Svelte?\n\nThe closest comparison on this list, since both are Svelte-native and both are MIT, so licensing does not decide it. The differences are depth and direction: SvGrid ships a larger feature surface, a UI component suite, in-grid AI helpers and an MCP server, while SVAR spans Svelte, React and Vue and keeps a smaller core. The At a glance table above has both measured bundle sizes; if a compact MIT grid with sorting, filtering, editing, tree data and CSV export is all you need, SVAR is a perfectly good answer.\n\n## Related comparisons and docs\n\n- [SvGrid vs svelte-headless-table](https://svgrid.com/compare/svelte-headless-table/)\n- [SvGrid vs TanStack Table (Svelte)](https://svgrid.com/compare/tanstack-table/)\n- [SvGrid vs @vincjo/datatables](https://svgrid.com/compare/vincjo-datatables/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Grouping & aggregation](https://svgrid.com/docs/help/grouping-aggregation/)\n- [Master / detail (nested grids)](https://svgrid.com/docs/help/rows/master-detail/)\n- [Build a table from scratch](https://svgrid.com/docs/help/headless/build-a-table/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- svar-datagrid: Licensed under MIT; Svelte 5 compatible; React and Vue versions available; lists multi-column sorting, header filters, in-cell editing, tree data, virtual scrolling, columns pinned to the left, context menu, row drag-and-drop, checkbox selection, pagination, hotkeys, WAI-ARIA, print, undo/redo (checked 12 Sep 2026) https://svar.dev/svelte/datagrid/\n- svar-overview: Feature list: in-cell editing, header and advanced filtering, sorting, single and multiple row selection, row reordering, context menu, undo/redo, tree data, pagination, colspans and rowspans in header and footer, collapsible column groups, pinned columns to the left, auto-sizing of rows and columns, localization, themes, export to CSV, print API, RestDataProvider, virtual scrolling for rows and columns, WAI-ARIA, keyboard navigation; no Excel export, row grouping, aggregation, master/detail, charts, AI or MCP (checked 12 Sep 2026) https://docs.svar.dev/svelte/grid/overview/\n- svar-svelte: DataGrid, Filter, Editor, File Manager and Core are MIT; Gantt, Calendar and Kanban have MIT cores with paid PRO editions; no pivot component in the list; no price list on the page (checked 12 Sep 2026) https://svar.dev/svelte/\n- svar-gantt: Offers paid consulting and custom development services; PRO edition pricing is on a separate page (checked 12 Sep 2026) https://svar.dev/svelte/gantt/\n"
8710
8710
  },
8711
8711
  {
8712
8712
  "slug": "compare/svelte-headless-table",
8713
8713
  "path": "docs/_data/comparisons/svelte-headless-table.json",
8714
8714
  "title": "SvGrid vs svelte-headless-table",
8715
8715
  "section": "Comparisons",
8716
- "markdown": "# SvGrid vs svelte-headless-table\n\nCanonical URL: https://svgrid.com/compare/svelte-headless-table/\nFacts verified: 2026-09-12\nCompetitor package: svelte-headless-table\nCompetitor site: https://svelte-headless-table.bryanmylee.com/\n\nsvelte-headless-table is the Svelte-native headless table library by Bryan Lee, one of the earliest Svelte-specific table options, now deprecated on Svelte 4.\n\n## Verdict\n\nsvelte-headless-table popularised headless tables in Svelte and still works on Svelte 4. Its author states there are no plans for a Svelte 5 port, so a Svelte 5 upgrade forces the question. SvGrid keeps the headless approach on Svelte 5 runes, adds virtualization and a rendered grid, and the @humanspeak fork is the option if you want to stay headless with the same API.\n\nMigration guide: moving from svelte-headless-table to SvGrid: https://svgrid.com/docs/help/migrating-from-svelte-headless-table/\n\n## At a glance\n\n| Fact | SvGrid | svelte-headless-table | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 0.18.3 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 28 Oct 2024 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | Svelte 4 range (peer svelte ^4.0.0) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 96,400 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.9 KB JS + 11.3 KB CSS | 5.7 KB JS, no separate stylesheet, svelte external | 9 Nov 2026 |\n| Engine alone, minified + gzip | 3.2 KB JS, no separate stylesheet (`createSvGrid` from `@svgrid/grid/core`) | the row above; the package is the engine | 10 Nov 2026 |\n| Frameworks | Svelte 5 | Svelte | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | svelte-headless-table is MIT and free; no paid licence or support is offered, and the author states there are no plans for a Svelte 5 port | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.33 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; svelte-headless-table 0.18.3 entry `whole package` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nsvelte-headless-table exposes a createTable function with composable plugins for sorting, filtering, column ordering and hiding, pagination, row selection, expansion, grouping with aggregation and column resizing, and leaves the markup to you. The npm package's peer range is Svelte 4, and the repository README states there are no current plans for a Svelte 5 port. A community fork, @humanspeak/svelte-headless-table, carries the same API on Svelte 5 runes; the At a glance table shows the original's registry facts, and the migration guide has the fork's.\n\nSvGrid takes the same headless approach but is written in Svelte 5 runes, adds a production render component, and covers virtualization, Excel-style filters, cell-range selection with a fill handle, inline editing, master/detail, a server-side row model and integrated charts natively.\n\n## Looking for a svelte-headless-table alternative for Svelte?\n\nThis is the clearest migration case on the list: the original package's peer range is Svelte 4, its last release was in 2024 and the README says there are no plans for a Svelte 5 port nor a maintenance schedule for Svelte 3 and 4. SvGrid keeps the headless approach you already chose and adds runes, virtualization and a render component if you want one. If you would rather keep the plugin API, the maintained community fork @humanspeak/svelte-headless-table targets Svelte 5, and its facts are in the guide.\n\n## What they have in common\n\n- Svelte-specific, not a port from another framework.\n- Headless-first composition: plugins in svelte-headless-table, a features object in SvGrid.\n- Sorting, filtering, pagination, row selection, expansion and grouping with aggregation in the engine.\n- MIT-licensed with a strong TypeScript story.\n\n## Where SvGrid is stronger\n\n- Built on Svelte 5 runes and released continuously; the original package is Svelte 4 only and its author has stopped.\n- A bundled <SvGrid /> component, so nobody assembles headers, body and virtualization by hand.\n- Virtualization on rows and columns built in; svelte-headless-table leaves it to a virtual-list library.\n- Excel-style filter menu, cell-range selection with a fill handle, inline editing, master/detail, a server-side row model and charts in the MIT package.\n- In-grid AI helpers free in @svgrid/grid and @svgrid/mcp for assistants, plus a paid support tier.\n\n## Where svelte-headless-table is stronger\n\n- A smaller bundle if all you want is the engine; the At a glance table has both measured sizes.\n- A plugin API many Svelte 4 codebases already know, and a documentation site that still reads well.\n- The @humanspeak fork keeps that API on Svelte 5 without a rewrite.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | svelte-headless-table |\n| --- | --- | --- |\n| Svelte 5 runes | Yes - native | No - Svelte 4 stores; no Svelte 5 port planned by the author |\n| Maintained release line | Yes | Partial - original deprecated; the @humanspeak fork is maintained on Svelte 5 |\n| Render component | Yes - <SvGrid /> | No - bring your own markup |\n| Headless engine | Yes - createSvGrid and a features object | Yes - createTable and plugins |\n| Sorting and column filtering | Yes | Yes - engine only |\n| Excel-style filter menu | Yes - built in | No - bring your own UI |\n| Cell-range selection and clipboard | Yes - built in, with a fill handle | No - row selection only |\n| Inline editing | Yes - built in | No - not a plugin |\n| Virtualization | Yes - rows and columns, built in | Partial - pair with a virtual-list library |\n| Pagination | Yes | Yes |\n| Row grouping with aggregation | Yes - engine and rendered group rows | Yes - engine only |\n| Row expansion and tree | Yes | Yes - expansion plugin |\n| Column ordering, hiding, resizing | Yes | Yes |\n| Master/detail | Yes | No - not a plugin |\n| Server-side data, flat (sort, filter, paging, infinite scroll) | Yes | No - not a plugin |\n| Server-side row model (lazy grouping, tree, pivot, transactions, select-all across unloaded rows) | Paid tier - @svgrid/enterprise | No - not a plugin |\n| Integrated charts | Yes - SvGridChart | No - not part of a headless engine |\n| In-grid AI helpers and MCP server | Yes - helpers free in @svgrid/grid; @svgrid/mcp, MIT | No - not in the docs |\n| Paid support | Yes - with @svgrid/enterprise, per developer per year | No - none offered |\n\n## When to choose SvGrid\n\n- You are moving to Svelte 5 and want a maintained grid that keeps the headless approach.\n- You want virtualization, an Excel-style filter menu, editing and cell selection without building them.\n- You want a rendered component for the common case and a headless core for the rest.\n- You want a support tier behind the library.\n\n## When to choose svelte-headless-table\n\n- You are staying on Svelte 4 for now and the plugin set already covers you.\n- You want the smallest possible engine and will keep writing the markup yourself.\n- You want the same plugin API on Svelte 5 and are happy to move to the @humanspeak fork.\n\n## Migration effort\n\nEstimated effort: 1-3 hours per grid.\n\nWhat you give up:\n\n- The plugin API and its documentation site, if your team knows it well.\n- The smallest engine-only bundle; the At a glance table has both measured sizes.\n- Nothing in maintenance terms on the original package, which is where most migrations start.\n\nMigration guide: moving from svelte-headless-table to SvGrid: https://svgrid.com/docs/help/migrating-from-svelte-headless-table/\n\n## Live example\n\nHeadless Table: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/186-headless-table/\n\n## The bottom line\n\nFor a Svelte 4 codebase that is not moving, svelte-headless-table still works. For a Svelte 5 codebase, the original package is not an option and its author says so; the choice is between the @humanspeak fork, which keeps the plugin API, and SvGrid, which keeps the headless approach and adds virtualization, filters, editing, selection and a rendered grid in the same MIT package.\n\n## Frequently asked questions\n\n### Does svelte-headless-table work with Svelte 5?\n\nThe original package's peer range is Svelte 4 and its README states there are no current plans for a Svelte 5 port nor a maintenance schedule for Svelte 3 and 4. The community fork @humanspeak/svelte-headless-table targets Svelte 5 with runes; SvGrid is written in Svelte 5 from the first line.\n\n### Can I keep a headless table with SvGrid?\n\nYes. createSvGrid plus the row-model factories is a headless engine; you can drive your own markup as before and adopt the SvGrid component only where you want it. The headless demos on this page show a plain table and a virtualized one.\n\n### Is SvGrid heavier than svelte-headless-table?\n\nYes, by the measurements in the At a glance table, because it ships a rendered grid, a virtualizer, filter menus and editors that a headless engine leaves to you. If you only need the engine and will write the rest, the difference is what you would otherwise write.\n\n### How long does a migration take?\n\nThe migration guide budgets one to three hours per grid; most of the time goes into deleting the markup and plugins the rendered grid replaces. Column definitions and the plugin concepts (sort, filter, page, select, expand, group) map one to one onto SvGrid's features.\n\n### Should I move to the @humanspeak fork instead?\n\nIf you want the same plugin API on Svelte 5 and are happy to keep writing the markup, yes, and its registry facts are in the migration guide. If the upgrade is also a chance to stop maintaining a table layer, SvGrid gives you the rendered grid and keeps the headless core for the cases that need it.\n\n### Is SvGrid a good svelte-headless-table alternative for Svelte?\n\nThis is the clearest migration case on the list: the original package's peer range is Svelte 4, its last release was in 2024 and the README says there are no plans for a Svelte 5 port nor a maintenance schedule for Svelte 3 and 4. SvGrid keeps the headless approach you already chose and adds runes, virtualization and a render component if you want one. If you would rather keep the plugin API, the maintained community fork @humanspeak/svelte-headless-table targets Svelte 5, and its facts are in the guide.\n\n## Related comparisons and docs\n\n- [SvGrid vs TanStack Table (Svelte)](https://svgrid.com/compare/tanstack-table/)\n- [SvGrid vs SVAR Svelte DataGrid](https://svgrid.com/compare/svar-svelte-datagrid/)\n- [SvGrid vs @vincjo/datatables](https://svgrid.com/compare/vincjo-datatables/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Build a table from scratch](https://svgrid.com/docs/help/headless/build-a-table/)\n- [Headless virtualization](https://svgrid.com/docs/help/headless/virtualization/)\n- [Grouping & aggregation](https://svgrid.com/docs/help/grouping-aggregation/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- sht-github: README: there are no current plans to work on a Svelte 5 port of this project nor is there a maintenance schedule for Svelte 3/4; the project is flagged as deprecated and users are encouraged to seek alternatives or fork (checked 12 Sep 2026) https://github.com/bryanmylee/svelte-headless-table\n- sht-docs: Advertised plugins: multi-sorting, column filtering, global filtering, column reordering, hiding columns, pagination, row grouping and aggregation, row expansion, row selection, column resizing; headless, you write the markup (checked 12 Sep 2026) https://svelte-headless-table.bryanmylee.com/\n- sht-fork: MIT; part of the Humanspeak family of runes-native Svelte 5 packages; the npm package declares a Svelte 5 peer range (checked 12 Sep 2026) https://github.com/humanspeak/svelte-headless-table\n"
8716
+ "markdown": "# SvGrid vs svelte-headless-table\n\nCanonical URL: https://svgrid.com/compare/svelte-headless-table/\nFacts verified: 2026-09-12\nCompetitor package: svelte-headless-table\nCompetitor site: https://svelte-headless-table.bryanmylee.com/\n\nsvelte-headless-table is the Svelte-native headless table library by Bryan Lee, one of the earliest Svelte-specific table options, now deprecated on Svelte 4.\n\n## Verdict\n\nsvelte-headless-table popularised headless tables in Svelte and still works on Svelte 4. Its author states there are no plans for a Svelte 5 port, so a Svelte 5 upgrade forces the question. SvGrid keeps the headless approach on Svelte 5 runes, adds virtualization and a rendered grid, and the @humanspeak fork is the option if you want to stay headless with the same API.\n\nMigration guide: moving from svelte-headless-table to SvGrid: https://svgrid.com/docs/help/migrating-from-svelte-headless-table/\n\n## At a glance\n\n| Fact | SvGrid | svelte-headless-table | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 0.18.3 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 28 Oct 2024 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | Svelte 4 range (peer svelte ^4.0.0) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 96,400 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.6 KB JS + 11.4 KB CSS | 5.7 KB JS, no separate stylesheet, svelte external | 9 Nov 2026 |\n| Engine alone, minified + gzip | 3.2 KB JS, no separate stylesheet (`createSvGrid` from `@svgrid/grid/core`) | the row above; the package is the engine | 10 Nov 2026 |\n| Frameworks | Svelte 5 | Svelte | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | svelte-headless-table is MIT and free; no paid licence or support is offered, and the author states there are no plans for a Svelte 5 port | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.34 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; svelte-headless-table 0.18.3 entry `whole package` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nsvelte-headless-table exposes a createTable function with composable plugins for sorting, filtering, column ordering and hiding, pagination, row selection, expansion, grouping with aggregation and column resizing, and leaves the markup to you. The npm package's peer range is Svelte 4, and the repository README states there are no current plans for a Svelte 5 port. A community fork, @humanspeak/svelte-headless-table, carries the same API on Svelte 5 runes; the At a glance table shows the original's registry facts, and the migration guide has the fork's.\n\nSvGrid takes the same headless approach but is written in Svelte 5 runes, adds a production render component, and covers virtualization, Excel-style filters, cell-range selection with a fill handle, inline editing, master/detail, a server-side row model and integrated charts natively.\n\n## Looking for a svelte-headless-table alternative for Svelte?\n\nThis is the clearest migration case on the list: the original package's peer range is Svelte 4, its last release was in 2024 and the README says there are no plans for a Svelte 5 port nor a maintenance schedule for Svelte 3 and 4. SvGrid keeps the headless approach you already chose and adds runes, virtualization and a render component if you want one. If you would rather keep the plugin API, the maintained community fork @humanspeak/svelte-headless-table targets Svelte 5, and its facts are in the guide.\n\n## What they have in common\n\n- Svelte-specific, not a port from another framework.\n- Headless-first composition: plugins in svelte-headless-table, a features object in SvGrid.\n- Sorting, filtering, pagination, row selection, expansion and grouping with aggregation in the engine.\n- MIT-licensed with a strong TypeScript story.\n\n## Where SvGrid is stronger\n\n- Built on Svelte 5 runes and released continuously; the original package is Svelte 4 only and its author has stopped.\n- A bundled <SvGrid /> component, so nobody assembles headers, body and virtualization by hand.\n- Virtualization on rows and columns built in; svelte-headless-table leaves it to a virtual-list library.\n- Excel-style filter menu, cell-range selection with a fill handle, inline editing, master/detail, a server-side row model and charts in the MIT package.\n- In-grid AI helpers free in @svgrid/grid and @svgrid/mcp for assistants, plus a paid support tier.\n\n## Where svelte-headless-table is stronger\n\n- A smaller bundle if all you want is the engine; the At a glance table has both measured sizes.\n- A plugin API many Svelte 4 codebases already know, and a documentation site that still reads well.\n- The @humanspeak fork keeps that API on Svelte 5 without a rewrite.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | svelte-headless-table |\n| --- | --- | --- |\n| Svelte 5 runes | Yes - native | No - Svelte 4 stores; no Svelte 5 port planned by the author |\n| Maintained release line | Yes | Partial - original deprecated; the @humanspeak fork is maintained on Svelte 5 |\n| Render component | Yes - <SvGrid /> | No - bring your own markup |\n| Headless engine | Yes - createSvGrid and a features object | Yes - createTable and plugins |\n| Sorting and column filtering | Yes | Yes - engine only |\n| Excel-style filter menu | Yes - built in | No - bring your own UI |\n| Cell-range selection and clipboard | Yes - built in, with a fill handle | No - row selection only |\n| Inline editing | Yes - built in | No - not a plugin |\n| Virtualization | Yes - rows and columns, built in | Partial - pair with a virtual-list library |\n| Pagination | Yes | Yes |\n| Row grouping with aggregation | Yes - engine and rendered group rows | Yes - engine only |\n| Row expansion and tree | Yes | Yes - expansion plugin |\n| Column ordering, hiding, resizing | Yes | Yes |\n| Master/detail | Yes | No - not a plugin |\n| Server-side data, flat (sort, filter, paging, infinite scroll) | Yes | No - not a plugin |\n| Server-side row model (lazy grouping, tree, pivot, transactions, select-all across unloaded rows) | Paid tier - @svgrid/enterprise | No - not a plugin |\n| Integrated charts | Yes - SvGridChart | No - not part of a headless engine |\n| In-grid AI helpers and MCP server | Yes - helpers free in @svgrid/grid; @svgrid/mcp, MIT | No - not in the docs |\n| Paid support | Yes - with @svgrid/enterprise, per developer per year | No - none offered |\n\n## When to choose SvGrid\n\n- You are moving to Svelte 5 and want a maintained grid that keeps the headless approach.\n- You want virtualization, an Excel-style filter menu, editing and cell selection without building them.\n- You want a rendered component for the common case and a headless core for the rest.\n- You want a support tier behind the library.\n\n## When to choose svelte-headless-table\n\n- You are staying on Svelte 4 for now and the plugin set already covers you.\n- You want the smallest possible engine and will keep writing the markup yourself.\n- You want the same plugin API on Svelte 5 and are happy to move to the @humanspeak fork.\n\n## Migration effort\n\nEstimated effort: 1-3 hours per grid.\n\nWhat you give up:\n\n- The plugin API and its documentation site, if your team knows it well.\n- The smallest engine-only bundle; the At a glance table has both measured sizes.\n- Nothing in maintenance terms on the original package, which is where most migrations start.\n\nMigration guide: moving from svelte-headless-table to SvGrid: https://svgrid.com/docs/help/migrating-from-svelte-headless-table/\n\n## Live example\n\nHeadless Table: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/186-headless-table/\n\n## The bottom line\n\nFor a Svelte 4 codebase that is not moving, svelte-headless-table still works. For a Svelte 5 codebase, the original package is not an option and its author says so; the choice is between the @humanspeak fork, which keeps the plugin API, and SvGrid, which keeps the headless approach and adds virtualization, filters, editing, selection and a rendered grid in the same MIT package.\n\n## Frequently asked questions\n\n### Does svelte-headless-table work with Svelte 5?\n\nThe original package's peer range is Svelte 4 and its README states there are no current plans for a Svelte 5 port nor a maintenance schedule for Svelte 3 and 4. The community fork @humanspeak/svelte-headless-table targets Svelte 5 with runes; SvGrid is written in Svelte 5 from the first line.\n\n### Can I keep a headless table with SvGrid?\n\nYes. createSvGrid plus the row-model factories is a headless engine; you can drive your own markup as before and adopt the SvGrid component only where you want it. The headless demos on this page show a plain table and a virtualized one.\n\n### Is SvGrid heavier than svelte-headless-table?\n\nYes, by the measurements in the At a glance table, because it ships a rendered grid, a virtualizer, filter menus and editors that a headless engine leaves to you. If you only need the engine and will write the rest, the difference is what you would otherwise write.\n\n### How long does a migration take?\n\nThe migration guide budgets one to three hours per grid; most of the time goes into deleting the markup and plugins the rendered grid replaces. Column definitions and the plugin concepts (sort, filter, page, select, expand, group) map one to one onto SvGrid's features.\n\n### Should I move to the @humanspeak fork instead?\n\nIf you want the same plugin API on Svelte 5 and are happy to keep writing the markup, yes, and its registry facts are in the migration guide. If the upgrade is also a chance to stop maintaining a table layer, SvGrid gives you the rendered grid and keeps the headless core for the cases that need it.\n\n### Is SvGrid a good svelte-headless-table alternative for Svelte?\n\nThis is the clearest migration case on the list: the original package's peer range is Svelte 4, its last release was in 2024 and the README says there are no plans for a Svelte 5 port nor a maintenance schedule for Svelte 3 and 4. SvGrid keeps the headless approach you already chose and adds runes, virtualization and a render component if you want one. If you would rather keep the plugin API, the maintained community fork @humanspeak/svelte-headless-table targets Svelte 5, and its facts are in the guide.\n\n## Related comparisons and docs\n\n- [SvGrid vs TanStack Table (Svelte)](https://svgrid.com/compare/tanstack-table/)\n- [SvGrid vs SVAR Svelte DataGrid](https://svgrid.com/compare/svar-svelte-datagrid/)\n- [SvGrid vs @vincjo/datatables](https://svgrid.com/compare/vincjo-datatables/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Build a table from scratch](https://svgrid.com/docs/help/headless/build-a-table/)\n- [Headless virtualization](https://svgrid.com/docs/help/headless/virtualization/)\n- [Grouping & aggregation](https://svgrid.com/docs/help/grouping-aggregation/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- sht-github: README: there are no current plans to work on a Svelte 5 port of this project nor is there a maintenance schedule for Svelte 3/4; the project is flagged as deprecated and users are encouraged to seek alternatives or fork (checked 12 Sep 2026) https://github.com/bryanmylee/svelte-headless-table\n- sht-docs: Advertised plugins: multi-sorting, column filtering, global filtering, column reordering, hiding columns, pagination, row grouping and aggregation, row expansion, row selection, column resizing; headless, you write the markup (checked 12 Sep 2026) https://svelte-headless-table.bryanmylee.com/\n- sht-fork: MIT; part of the Humanspeak family of runes-native Svelte 5 packages; the npm package declares a Svelte 5 peer range (checked 12 Sep 2026) https://github.com/humanspeak/svelte-headless-table\n"
8717
8717
  },
8718
8718
  {
8719
8719
  "slug": "compare/svelte-ui-kit-tables",
@@ -8734,21 +8734,21 @@ export const docs = [
8734
8734
  "path": "docs/_data/comparisons/tabulator.json",
8735
8735
  "title": "SvGrid vs Tabulator",
8736
8736
  "section": "Comparisons",
8737
- "markdown": "# SvGrid vs Tabulator\n\nCanonical URL: https://svgrid.com/compare/tabulator/\nFacts verified: 2026-09-12\nCompetitor package: tabulator-tables\nCompetitor site: https://tabulator.info/\n\nTabulator is a feature-rich, framework-agnostic vanilla-JS interactive table library, MIT-licensed.\n\n## Verdict\n\nTabulator is enormously capable and free, but it is vanilla JS you wire into Svelte imperatively. SvGrid delivers a similar feature surface as a Svelte-5-native component with reactive data binding.\n\nMigration guide: moving from Tabulator to SvGrid: https://svgrid.com/docs/help/migrating-from-tabulator/\n\n## At a glance\n\n| Fact | SvGrid | Tabulator | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 6.7.1 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 22 Oct 2026 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | No Svelte package (JavaScript) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 826,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.9 KB JS + 11.3 KB CSS | 109.5 KB JS + 3.8 KB CSS | 9 Nov 2026 |\n| Frameworks | Svelte 5 | JavaScript | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | Tabulator is MIT and free; no licence or support plan is sold | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.33 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; tabulator-tables 6.7.1 entry `TabulatorFull` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nTabulator packs a huge feature set - sorting, filtering, grouping, editing, tree data, formatters, and more - into a framework-agnostic vanilla-JS library. You instantiate it against a DOM element and drive it through its imperative API.\n\nSvGrid covers the same ground but as a Svelte 5 component: data is a reactive `$state` array, cells are snippets, and the imperative API is there when you want it - no manual mount/teardown or DOM bridging.\n\n## Looking for a Tabulator alternative for Svelte?\n\nTabulator is mature, MIT and framework-agnostic, and the reason people move is usually reactivity: it owns its own DOM, so Svelte state and table state have to be kept in sync by hand. SvGrid is driven by your runes directly. Tabulator still wins on breadth of built-in features and on being usable from plain HTML with no build step.\n\n## What they have in common\n\n- Broad feature set: sort, filter, group, edit, tree, format.\n- MIT-licensed / free for commercial use.\n- Virtualized rendering for large datasets.\n- Rich, mature documentation.\n\n## Where SvGrid is stronger\n\n- Svelte 5 native - reactive data binding, no imperative mount/teardown.\n- Custom cells are Svelte snippets, not HTML-string formatters.\n- Headless engine available in addition to the component.\n- @svgrid/mcp MCP server for AI assistants.\n\n## Where Tabulator is stronger\n\n- Framework-agnostic - the same library across vanilla, React, Vue, Angular.\n- Very large built-in formatter / editor catalogue.\n- Long track record and a big community.\n- No build step required to drop into a plain HTML page.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | Tabulator |\n| --- | --- | --- |\n| Svelte 5 native | Yes | No - vanilla JavaScript |\n| Reactive data binding | Yes - $state | Partial - Imperative setData() |\n| Custom cells | Yes - Snippets / components | Partial - HTML-string formatters |\n| Sort / filter / group | Yes | Yes |\n| Inline editing | Yes | Yes |\n| Tree data | Yes | Yes |\n| Virtualization | Yes | Yes |\n| Headless engine | Yes | No |\n| AI / MCP integration | Yes | No |\n\n## When to choose SvGrid\n\n- You are on Svelte 5 and want reactive data, not imperative setData calls.\n- You want Svelte snippets for custom cells instead of HTML strings.\n- You want a headless engine option and an MCP server.\n\n## When to choose Tabulator\n\n- You need one table library across vanilla JS, React, Vue, and Angular.\n- You want a no-build-step drop-in for a plain HTML page.\n- You rely on a specific Tabulator formatter / module.\n\n## Migration effort\n\nEstimated effort: 2-4 hours per grid.\n\nWhat you give up:\n\n- One library for plain JavaScript pages as well as React, Angular and Vue.\n- Built-in download to CSV, XLSX and PDF without a paid pack; SvGrid has CSV free and Excel and PDF in @svgrid/enterprise.\n\nMigration guide: moving from Tabulator to SvGrid: https://svgrid.com/docs/help/migrating-from-tabulator/\n\n## Live example\n\nExcel Filters: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/03-excel-filters/\n\n## The bottom line\n\nTabulator is a free, feature-packed table that runs anywhere. If your app is Svelte 5, SvGrid gives you a comparable feature set with reactive data binding and snippet cells instead of imperative setData and HTML-string formatters.\n\n## Frequently asked questions\n\n### SvGrid vs Tabulator for Svelte - which is better?\n\nFor Svelte 5, SvGrid: reactive $state data and Svelte snippet cells, with no imperative mount or teardown. Tabulator wins if you need one library across vanilla JS, React, Vue, and Angular.\n\n### Is SvGrid free like Tabulator?\n\nYes - the core is MIT, like Tabulator. Only the optional @svgrid/enterprise pack is paid.\n\n### Can I reuse Tabulator formatters in SvGrid?\n\nYou re-create them as Svelte snippets via renderSnippet, which is more flexible than HTML-string formatters.\n\n### Is SvGrid a good Tabulator alternative for Svelte?\n\nTabulator is mature, MIT and framework-agnostic, and the reason people move is usually reactivity: it owns its own DOM, so Svelte state and table state have to be kept in sync by hand. SvGrid is driven by your runes directly. Tabulator still wins on breadth of built-in features and on being usable from plain HTML with no build step.\n\n## Related comparisons and docs\n\n- [SvGrid vs Grid.js](https://svgrid.com/compare/gridjs/)\n- [SvGrid vs Smart.Grid (Smart Web Components)](https://svgrid.com/compare/smart-grid/)\n- [SvGrid vs AG Grid (community + enterprise)](https://svgrid.com/compare/ag-grid/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Cell components](https://svgrid.com/docs/help/cells/cell-components/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- tabulator-readme: MIT; a vanilla JavaScript library that builds interactive tables from HTML tables, arrays or JSON, with support for React, Angular and Vue; installed as tabulator-tables (checked 12 Sep 2026) https://github.com/olifolkerd/tabulator\n"
8737
+ "markdown": "# SvGrid vs Tabulator\n\nCanonical URL: https://svgrid.com/compare/tabulator/\nFacts verified: 2026-09-12\nCompetitor package: tabulator-tables\nCompetitor site: https://tabulator.info/\n\nTabulator is a feature-rich, framework-agnostic vanilla-JS interactive table library, MIT-licensed.\n\n## Verdict\n\nTabulator is enormously capable and free, but it is vanilla JS you wire into Svelte imperatively. SvGrid delivers a similar feature surface as a Svelte-5-native component with reactive data binding.\n\nMigration guide: moving from Tabulator to SvGrid: https://svgrid.com/docs/help/migrating-from-tabulator/\n\n## At a glance\n\n| Fact | SvGrid | Tabulator | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 6.7.1 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 22 Oct 2026 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | No Svelte package (JavaScript) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 826,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.6 KB JS + 11.4 KB CSS | 109.5 KB JS + 3.8 KB CSS | 9 Nov 2026 |\n| Frameworks | Svelte 5 | JavaScript | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | Tabulator is MIT and free; no licence or support plan is sold | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.34 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; tabulator-tables 6.7.1 entry `TabulatorFull` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nTabulator packs a huge feature set - sorting, filtering, grouping, editing, tree data, formatters, and more - into a framework-agnostic vanilla-JS library. You instantiate it against a DOM element and drive it through its imperative API.\n\nSvGrid covers the same ground but as a Svelte 5 component: data is a reactive `$state` array, cells are snippets, and the imperative API is there when you want it - no manual mount/teardown or DOM bridging.\n\n## Looking for a Tabulator alternative for Svelte?\n\nTabulator is mature, MIT and framework-agnostic, and the reason people move is usually reactivity: it owns its own DOM, so Svelte state and table state have to be kept in sync by hand. SvGrid is driven by your runes directly. Tabulator still wins on breadth of built-in features and on being usable from plain HTML with no build step.\n\n## What they have in common\n\n- Broad feature set: sort, filter, group, edit, tree, format.\n- MIT-licensed / free for commercial use.\n- Virtualized rendering for large datasets.\n- Rich, mature documentation.\n\n## Where SvGrid is stronger\n\n- Svelte 5 native - reactive data binding, no imperative mount/teardown.\n- Custom cells are Svelte snippets, not HTML-string formatters.\n- Headless engine available in addition to the component.\n- @svgrid/mcp MCP server for AI assistants.\n\n## Where Tabulator is stronger\n\n- Framework-agnostic - the same library across vanilla, React, Vue, Angular.\n- Very large built-in formatter / editor catalogue.\n- Long track record and a big community.\n- No build step required to drop into a plain HTML page.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | Tabulator |\n| --- | --- | --- |\n| Svelte 5 native | Yes | No - vanilla JavaScript |\n| Reactive data binding | Yes - $state | Partial - Imperative setData() |\n| Custom cells | Yes - Snippets / components | Partial - HTML-string formatters |\n| Sort / filter / group | Yes | Yes |\n| Inline editing | Yes | Yes |\n| Tree data | Yes | Yes |\n| Virtualization | Yes | Yes |\n| Headless engine | Yes | No |\n| AI / MCP integration | Yes | No |\n\n## When to choose SvGrid\n\n- You are on Svelte 5 and want reactive data, not imperative setData calls.\n- You want Svelte snippets for custom cells instead of HTML strings.\n- You want a headless engine option and an MCP server.\n\n## When to choose Tabulator\n\n- You need one table library across vanilla JS, React, Vue, and Angular.\n- You want a no-build-step drop-in for a plain HTML page.\n- You rely on a specific Tabulator formatter / module.\n\n## Migration effort\n\nEstimated effort: 2-4 hours per grid.\n\nWhat you give up:\n\n- One library for plain JavaScript pages as well as React, Angular and Vue.\n- Built-in download to CSV, XLSX and PDF without a paid pack; SvGrid has CSV free and Excel and PDF in @svgrid/enterprise.\n\nMigration guide: moving from Tabulator to SvGrid: https://svgrid.com/docs/help/migrating-from-tabulator/\n\n## Live example\n\nExcel Filters: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/03-excel-filters/\n\n## The bottom line\n\nTabulator is a free, feature-packed table that runs anywhere. If your app is Svelte 5, SvGrid gives you a comparable feature set with reactive data binding and snippet cells instead of imperative setData and HTML-string formatters.\n\n## Frequently asked questions\n\n### SvGrid vs Tabulator for Svelte - which is better?\n\nFor Svelte 5, SvGrid: reactive $state data and Svelte snippet cells, with no imperative mount or teardown. Tabulator wins if you need one library across vanilla JS, React, Vue, and Angular.\n\n### Is SvGrid free like Tabulator?\n\nYes - the core is MIT, like Tabulator. Only the optional @svgrid/enterprise pack is paid.\n\n### Can I reuse Tabulator formatters in SvGrid?\n\nYou re-create them as Svelte snippets via renderSnippet, which is more flexible than HTML-string formatters.\n\n### Is SvGrid a good Tabulator alternative for Svelte?\n\nTabulator is mature, MIT and framework-agnostic, and the reason people move is usually reactivity: it owns its own DOM, so Svelte state and table state have to be kept in sync by hand. SvGrid is driven by your runes directly. Tabulator still wins on breadth of built-in features and on being usable from plain HTML with no build step.\n\n## Related comparisons and docs\n\n- [SvGrid vs Grid.js](https://svgrid.com/compare/gridjs/)\n- [SvGrid vs Smart.Grid (Smart Web Components)](https://svgrid.com/compare/smart-grid/)\n- [SvGrid vs AG Grid (community + enterprise)](https://svgrid.com/compare/ag-grid/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Cell components](https://svgrid.com/docs/help/cells/cell-components/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- tabulator-readme: MIT; a vanilla JavaScript library that builds interactive tables from HTML tables, arrays or JSON, with support for React, Angular and Vue; installed as tabulator-tables (checked 12 Sep 2026) https://github.com/olifolkerd/tabulator\n"
8738
8738
  },
8739
8739
  {
8740
8740
  "slug": "compare/tanstack-table",
8741
8741
  "path": "docs/_data/comparisons/tanstack-table.json",
8742
8742
  "title": "SvGrid vs TanStack Table (Svelte)",
8743
8743
  "section": "Comparisons",
8744
- "markdown": "# SvGrid vs TanStack Table (Svelte)\n\nCanonical URL: https://svgrid.com/compare/tanstack-table/\nFacts verified: 2026-09-12\nCompetitor package: @tanstack/svelte-table\nCompetitor site: https://tanstack.com/table/latest\n\nTanStack Table is the headless table engine with adapters for React, Vue, Svelte, Solid, Qwik and Lit; you bring the markup.\n\n## Verdict\n\nThe closest peer to SvGrid's headless core. SvGrid ships a rendered component on top of the same kind of engine, in Svelte 5 runes; TanStack stays framework-agnostic and asks you to build and maintain the DOM, the virtualizer, the filter menus and the editors yourself.\n\nMigration guide: moving from TanStack Table (Svelte) to SvGrid: https://svgrid.com/docs/help/migrating-from-tanstack-table/\n\n## At a glance\n\n| Fact | SvGrid | TanStack Table (Svelte) | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 9.3.1 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 12 Oct 2026 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | Yes (peer svelte ^5.0.0) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 539,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.9 KB JS + 11.3 KB CSS | 36.5 KB JS, no separate stylesheet, svelte external | 9 Nov 2026 |\n| Engine alone, minified + gzip | 3.2 KB JS, no separate stylesheet (`createSvGrid` from `@svgrid/grid/core`) | the row above; the package is the engine | 10 Nov 2026 |\n| Frameworks | Svelte 5 | Svelte, React, Vue, Solid, Qwik, Lit | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | TanStack Table is MIT and free; tanstack.com is sponsor-supported and offers Enterprise Support as private consulting and expert support, with no licence sold for the table | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.33 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; @tanstack/svelte-table 9.3.1 entry `whole package` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nTanStack Table is the canonical headless table library: it provides the data pipeline (filter, sort, group, expand, paginate, select) and leaves the markup to you. The v9 line ships a Svelte adapter, @tanstack/svelte-table, whose peer dependency range is Svelte 5, with createTable and getters for reactive data instead of the stores the v8 adapter used.\n\nSvGrid covers the same headless surface (createSvGrid, row models, a features object) and adds a full render component with virtualization, Excel-style filters, inline editing, cell-range selection with a fill handle, grouping with aggregation, master/detail, a server-side row model and integrated charts, all in the MIT package.\n\n## Looking for a TanStack Table alternative for Svelte?\n\nPeople arrive here wanting less glue code, and that is the trade: you keep a headless engine with row models and composable features, and you stop hand-building the DOM, the virtualizer, the filter menus and the editors. If you need one table engine across React and Svelte, stay where you are; that portability is exactly what SvGrid gives up.\n\n## What they have in common\n\n- Headless-first architecture with row-model factories and a features object.\n- Composable features: sorting, filtering, grouping, pagination, expansion, selection.\n- TypeScript-first, MIT-licensed, with paid support available from the maintainers.\n- A createTable / createSvGrid entry point that takes columns, data and features.\n- Svelte 5 in both: runes in SvGrid, a Svelte 5 peer range in the TanStack adapter.\n\n## Where SvGrid is stronger\n\n- Ships <SvGrid />: a production render component with virtualization, Excel-style filters, cell-range selection, inline editing, grouping, master/detail and pagination. With TanStack Table you build all of this.\n- The headless core is written in Svelte 5 runes; the TanStack adapter wraps a framework-agnostic core.\n- An imperative API (SvGridApi) for adding rows, setting filters and mutating columns from outside the component.\n- A gallery of runnable examples that covers every feature, and per-feature docs pages with embedded demos.\n- In-grid AI helpers free in @svgrid/grid, and @svgrid/mcp so assistants fetch real example sources and can check the code they write.\n- A paid pack with Excel, PDF and print output, import, pivot tables and support.\n\n## Where TanStack Table (Svelte) is stronger\n\n- A far larger community; the At a glance table has the download counts side by side.\n- Multi-framework parity: if your shop has React, Vue and Svelte apps, the API stays consistent.\n- A smaller bundle when all you want is the engine; the At a glance table has both measured sizes.\n- Framework-specific documentation for each adapter and years of production use in large companies.\n- Enterprise Support as private consulting, and sponsor perks such as priority issue requests.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | TanStack Table (Svelte) |\n| --- | --- | --- |\n| Headless engine | Yes - createSvGrid | Yes - createTable |\n| Render component (drop-in) | Yes - <SvGrid /> | No - bring your own markup |\n| Svelte 5 | Yes - runes throughout | Yes - the adapter's peer range is Svelte 5 |\n| Row virtualization | Yes - built in | Partial - pair with @tanstack/svelte-virtual |\n| Column virtualization | Yes - built in | Partial - pair with @tanstack/svelte-virtual |\n| Excel-style filter menu | Yes - built in | No - filtering logic only; the UI is yours |\n| Inline editing | Yes - enableInlineEditing | No - bring your own |\n| Cell-range selection and clipboard | Yes - enableCellSelection, fill handle | No - bring your own |\n| Server-side data, flat (sort, filter, paging, infinite scroll) | Yes - createServerDataSource: page or infinite block scroll | Yes - manual sorting, filtering and pagination flags |\n| Server-side row model (lazy grouping, tree, pivot, transactions, select-all across unloaded rows) | Paid tier - @svgrid/enterprise | No - the engine has no server row model; the app fetches per group |\n| Master/detail and tree | Yes | Yes - expansion and subRows |\n| Grouping with aggregation | Yes - engine and rendered group rows | Yes - engine only |\n| Integrated charts | Yes - SvGridChart | No - not part of a headless engine |\n| WAI-ARIA helpers | Yes - exported, and applied by <SvGrid /> | Partial - your markup, your ARIA |\n| In-grid AI helpers and MCP server | Yes - helpers free in @svgrid/grid; @svgrid/mcp, MIT | No - not in the docs |\n| Multi-framework support | No - Svelte only | Yes - React, Vue, Svelte, Solid, Qwik, Lit |\n| Paid support tier | Yes - with @svgrid/enterprise, per developer per year | Yes - Enterprise Support (private consulting) and sponsor perks such as priority issues |\n\n## Measured performance\n\nMeasured 28 Oct 2026 with the harness in the repository (pnpm bench:compare): 100,000 rows, fastest of 3 samples per operation, each grid in a fresh page, Chromium through Playwright, headless, on win32 10.0.26200 x64, Intel(R) Core(TM) Ultra 7 255U; a developer workstation, not a dedicated bench rig. Versions: @svgrid/grid 3.0.25, @tanstack/svelte-table 9.2.4. Lower is better. Tick: 1,000 of the rows replaced per tick with a new amount, the grid sorted by amount, on the update path each grid provides, timed until the changed cells paint; 180 ticks after 10 to warm up.\n\n| Operation | SvGrid | TanStack Table (Svelte) |\n| --- | --- | --- |\n| Mount | 30.7 ms | 170.2 ms |\n| Sort, text column | 77.4 ms | 360.9 ms |\n| Sort, numeric column | 32.8 ms | 178.2 ms |\n| Filter, one column (indicative only) | 34.5 ms | 51.1 ms |\n| Scroll, p95 frame | 34.3 ms | 34.3 ms |\n| Live tick, 1,000 rows replaced, sorted by that column, p95 | 48.6 ms | 563.4 ms |\n| Ticks over one 60 Hz frame, of 180 | 115 | 180 |\n| Rows kept in the DOM (virtualization on) | 36 | 27 |\n\nThe filter row is not like for like: each grid is driven through its own single-column filter API, and the amount of work differs. The comparison guide explains the method, what is left out and why.\n\nTanStack Table renders nothing, so its adapter draws the row model through a minimal fixed-height windowed table with no virtualizer library, filter UI or editors; the numbers are the engine plus that DOM.\n\n## When to choose SvGrid\n\n- You are on Svelte 5 and want a grid that uses runes idiomatically, headless or rendered.\n- You want a drop-in <SvGrid /> with virtualization, filters, editing and selection working in one prop pass.\n- You want AI tools to give accurate answers about your grid through MCP, and to have their code checked.\n- You want paid support available without switching libraries later.\n\n## When to choose TanStack Table (Svelte)\n\n- You ship to multiple frameworks (React, Vue, Svelte) and want one API across them.\n- You explicitly want a headless library and intend to build your own render layer.\n- You want the smallest possible engine and the largest possible community.\n- A shadcn-svelte data table built on TanStack already does what you need.\n\n## Migration effort\n\nEstimated effort: About 30 minutes per read-only grid, 2-4 hours for editing-heavy grids.\n\nWhat you give up:\n\n- One table engine across React, Vue, Svelte, Solid, Qwik and Lit.\n- The smallest engine-only bundle; the At a glance table has both measured sizes.\n- The TanStack ecosystem around the table: Virtual, Query and the shadcn-svelte data table recipe.\n\nMigration guide: moving from TanStack Table (Svelte) to SvGrid: https://svgrid.com/docs/help/migrating-from-tanstack-table/\n\n## Live example\n\nHeadless Table: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/186-headless-table/\n\n## The bottom line\n\nIf you build across React, Vue and Svelte and want one headless API, TanStack Table is the safer bet. If you are committed to Svelte 5 and want virtualization, Excel-style filters, editing and selection out of the box, SvGrid gets you there with far less code, and you keep a headless core when you need it.\n\n## Frequently asked questions\n\n### Is SvGrid better than TanStack Table for Svelte?\n\nFor a Svelte 5 app, SvGrid is usually the faster path: it ships a virtualized render component with built-in filters, editing and accessibility, so there is no DOM layer to write. The TanStack Svelte adapter is Svelte 5 in its v9 line, but it is headless by design; you still build and maintain the table, virtualization and editing UI. TanStack wins if you need one API across several frameworks, or if owning that markup is the point.\n\n### Can I keep a headless setup like TanStack Table?\n\nYes. createSvGrid plus the row-model factories is a headless engine; you can drive your own markup exactly as with TanStack and adopt the SvGrid component only where you want it. The headless docs and the headless demos on this page show both.\n\n### Does the TanStack Svelte adapter support Svelte 5?\n\nYes. The @tanstack/svelte-table package on npm declares a Svelte 5 peer range in its v9 line and its examples pass data through getters rather than stores. The At a glance table shows the version and the peer range as read from the registry.\n\n### How long is a TanStack Table to SvGrid migration?\n\nAbout thirty minutes for a read-only grid and two to four hours for editing-heavy ones. The row-model concepts map almost one to one; the migration guide walks through createTable to createSvGrid, the features object and the rendering options.\n\n### Which is smaller, TanStack Table or SvGrid?\n\nThe TanStack adapter, as an engine with no rendering. The At a glance table has both packages measured the same way on the same date. Add what you would write on top of TanStack (a virtualizer, filter UI, editors) before comparing, since that is what the extra size in SvGrid is.\n\n### Is SvGrid a good TanStack Table alternative for Svelte?\n\nPeople arrive here wanting less glue code, and that is the trade: you keep a headless engine with row models and composable features, and you stop hand-building the DOM, the virtualizer, the filter menus and the editors. If you need one table engine across React and Svelte, stay where you are; that portability is exactly what SvGrid gives up.\n\n## Related comparisons and docs\n\n- [SvGrid vs svelte-headless-table](https://svgrid.com/compare/svelte-headless-table/)\n- [SvGrid vs SVAR Svelte DataGrid](https://svgrid.com/compare/svar-svelte-datagrid/)\n- [SvGrid vs Flowbite / Skeleton / shadcn-svelte tables](https://svgrid.com/compare/svelte-ui-kit-tables/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Build a table from scratch](https://svgrid.com/docs/help/headless/build-a-table/)\n- [Server-side data (load on demand)](https://svgrid.com/docs/help/headless/server-side/)\n- [Headless virtualization](https://svgrid.com/docs/help/headless/virtualization/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- tanstack-svelte: The Svelte adapter is headless: build your own markup from the table instance's state and APIs; createTable takes features, columns and data through a getter; adapters exist for React, Vue, Solid, Qwik, Lit and Svelte (checked 12 Sep 2026) https://tanstack.com/table/latest/docs/framework/svelte/overview\n- tanstack-npm: The latest version's peerDependencies declare svelte ^5.0.0; licence MIT (checked 12 Sep 2026) https://www.npmjs.com/package/@tanstack/svelte-table\n- tanstack-home: Sponsor-supported with gold, silver and bronze sponsors; sponsors get private discord channels, priority issue requests and direct support; an Enterprise Support tier offers private consulting and expert support; no licence for the table is sold (checked 12 Sep 2026) https://tanstack.com/table/latest\n"
8744
+ "markdown": "# SvGrid vs TanStack Table (Svelte)\n\nCanonical URL: https://svgrid.com/compare/tanstack-table/\nFacts verified: 2026-09-12\nCompetitor package: @tanstack/svelte-table\nCompetitor site: https://tanstack.com/table/latest\n\nTanStack Table is the headless table engine with adapters for React, Vue, Svelte, Solid, Qwik and Lit; you bring the markup.\n\n## Verdict\n\nThe closest peer to SvGrid's headless core. SvGrid ships a rendered component on top of the same kind of engine, in Svelte 5 runes; TanStack stays framework-agnostic and asks you to build and maintain the DOM, the virtualizer, the filter menus and the editors yourself.\n\nMigration guide: moving from TanStack Table (Svelte) to SvGrid: https://svgrid.com/docs/help/migrating-from-tanstack-table/\n\n## At a glance\n\n| Fact | SvGrid | TanStack Table (Svelte) | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 9.3.1 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 12 Oct 2026 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | Yes (peer svelte ^5.0.0) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 539,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.6 KB JS + 11.4 KB CSS | 36.5 KB JS, no separate stylesheet, svelte external | 9 Nov 2026 |\n| Engine alone, minified + gzip | 3.2 KB JS, no separate stylesheet (`createSvGrid` from `@svgrid/grid/core`) | the row above; the package is the engine | 10 Nov 2026 |\n| Frameworks | Svelte 5 | Svelte, React, Vue, Solid, Qwik, Lit | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | TanStack Table is MIT and free; tanstack.com is sponsor-supported and offers Enterprise Support as private consulting and expert support, with no licence sold for the table | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.34 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; @tanstack/svelte-table 9.3.1 entry `whole package` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\nTanStack Table is the canonical headless table library: it provides the data pipeline (filter, sort, group, expand, paginate, select) and leaves the markup to you. The v9 line ships a Svelte adapter, @tanstack/svelte-table, whose peer dependency range is Svelte 5, with createTable and getters for reactive data instead of the stores the v8 adapter used.\n\nSvGrid covers the same headless surface (createSvGrid, row models, a features object) and adds a full render component with virtualization, Excel-style filters, inline editing, cell-range selection with a fill handle, grouping with aggregation, master/detail, a server-side row model and integrated charts, all in the MIT package.\n\n## Looking for a TanStack Table alternative for Svelte?\n\nPeople arrive here wanting less glue code, and that is the trade: you keep a headless engine with row models and composable features, and you stop hand-building the DOM, the virtualizer, the filter menus and the editors. If you need one table engine across React and Svelte, stay where you are; that portability is exactly what SvGrid gives up.\n\n## What they have in common\n\n- Headless-first architecture with row-model factories and a features object.\n- Composable features: sorting, filtering, grouping, pagination, expansion, selection.\n- TypeScript-first, MIT-licensed, with paid support available from the maintainers.\n- A createTable / createSvGrid entry point that takes columns, data and features.\n- Svelte 5 in both: runes in SvGrid, a Svelte 5 peer range in the TanStack adapter.\n\n## Where SvGrid is stronger\n\n- Ships <SvGrid />: a production render component with virtualization, Excel-style filters, cell-range selection, inline editing, grouping, master/detail and pagination. With TanStack Table you build all of this.\n- The headless core is written in Svelte 5 runes; the TanStack adapter wraps a framework-agnostic core.\n- An imperative API (SvGridApi) for adding rows, setting filters and mutating columns from outside the component.\n- A gallery of runnable examples that covers every feature, and per-feature docs pages with embedded demos.\n- In-grid AI helpers free in @svgrid/grid, and @svgrid/mcp so assistants fetch real example sources and can check the code they write.\n- A paid pack with Excel, PDF and print output, import, pivot tables and support.\n\n## Where TanStack Table (Svelte) is stronger\n\n- A far larger community; the At a glance table has the download counts side by side.\n- Multi-framework parity: if your shop has React, Vue and Svelte apps, the API stays consistent.\n- A smaller bundle when all you want is the engine; the At a glance table has both measured sizes.\n- Framework-specific documentation for each adapter and years of production use in large companies.\n- Enterprise Support as private consulting, and sponsor perks such as priority issue requests.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | TanStack Table (Svelte) |\n| --- | --- | --- |\n| Headless engine | Yes - createSvGrid | Yes - createTable |\n| Render component (drop-in) | Yes - <SvGrid /> | No - bring your own markup |\n| Svelte 5 | Yes - runes throughout | Yes - the adapter's peer range is Svelte 5 |\n| Row virtualization | Yes - built in | Partial - pair with @tanstack/svelte-virtual |\n| Column virtualization | Yes - built in | Partial - pair with @tanstack/svelte-virtual |\n| Excel-style filter menu | Yes - built in | No - filtering logic only; the UI is yours |\n| Inline editing | Yes - enableInlineEditing | No - bring your own |\n| Cell-range selection and clipboard | Yes - enableCellSelection, fill handle | No - bring your own |\n| Server-side data, flat (sort, filter, paging, infinite scroll) | Yes - createServerDataSource: page or infinite block scroll | Yes - manual sorting, filtering and pagination flags |\n| Server-side row model (lazy grouping, tree, pivot, transactions, select-all across unloaded rows) | Paid tier - @svgrid/enterprise | No - the engine has no server row model; the app fetches per group |\n| Master/detail and tree | Yes | Yes - expansion and subRows |\n| Grouping with aggregation | Yes - engine and rendered group rows | Yes - engine only |\n| Integrated charts | Yes - SvGridChart | No - not part of a headless engine |\n| WAI-ARIA helpers | Yes - exported, and applied by <SvGrid /> | Partial - your markup, your ARIA |\n| In-grid AI helpers and MCP server | Yes - helpers free in @svgrid/grid; @svgrid/mcp, MIT | No - not in the docs |\n| Multi-framework support | No - Svelte only | Yes - React, Vue, Svelte, Solid, Qwik, Lit |\n| Paid support tier | Yes - with @svgrid/enterprise, per developer per year | Yes - Enterprise Support (private consulting) and sponsor perks such as priority issues |\n\n## Measured performance\n\nMeasured 28 Oct 2026 with the harness in the repository (pnpm bench:compare): 100,000 rows, fastest of 3 samples per operation, each grid in a fresh page, Chromium through Playwright, headless, on win32 10.0.26200 x64, Intel(R) Core(TM) Ultra 7 255U; a developer workstation, not a dedicated bench rig. Versions: @svgrid/grid 3.0.25, @tanstack/svelte-table 9.2.4. Lower is better. Tick: 1,000 of the rows replaced per tick with a new amount, the grid sorted by amount, on the update path each grid provides, timed until the changed cells paint; 180 ticks after 10 to warm up.\n\n| Operation | SvGrid | TanStack Table (Svelte) |\n| --- | --- | --- |\n| Mount | 30.7 ms | 170.2 ms |\n| Sort, text column | 77.4 ms | 360.9 ms |\n| Sort, numeric column | 32.8 ms | 178.2 ms |\n| Filter, one column (indicative only) | 34.5 ms | 51.1 ms |\n| Scroll, p95 frame | 34.3 ms | 34.3 ms |\n| Live tick, 1,000 rows replaced, sorted by that column, p95 | 48.6 ms | 563.4 ms |\n| Ticks over one 60 Hz frame, of 180 | 115 | 180 |\n| Rows kept in the DOM (virtualization on) | 36 | 27 |\n\nThe filter row is not like for like: each grid is driven through its own single-column filter API, and the amount of work differs. The comparison guide explains the method, what is left out and why.\n\nTanStack Table renders nothing, so its adapter draws the row model through a minimal fixed-height windowed table with no virtualizer library, filter UI or editors; the numbers are the engine plus that DOM.\n\n## When to choose SvGrid\n\n- You are on Svelte 5 and want a grid that uses runes idiomatically, headless or rendered.\n- You want a drop-in <SvGrid /> with virtualization, filters, editing and selection working in one prop pass.\n- You want AI tools to give accurate answers about your grid through MCP, and to have their code checked.\n- You want paid support available without switching libraries later.\n\n## When to choose TanStack Table (Svelte)\n\n- You ship to multiple frameworks (React, Vue, Svelte) and want one API across them.\n- You explicitly want a headless library and intend to build your own render layer.\n- You want the smallest possible engine and the largest possible community.\n- A shadcn-svelte data table built on TanStack already does what you need.\n\n## Migration effort\n\nEstimated effort: About 30 minutes per read-only grid, 2-4 hours for editing-heavy grids.\n\nWhat you give up:\n\n- One table engine across React, Vue, Svelte, Solid, Qwik and Lit.\n- The smallest engine-only bundle; the At a glance table has both measured sizes.\n- The TanStack ecosystem around the table: Virtual, Query and the shadcn-svelte data table recipe.\n\nMigration guide: moving from TanStack Table (Svelte) to SvGrid: https://svgrid.com/docs/help/migrating-from-tanstack-table/\n\n## Live example\n\nHeadless Table: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/186-headless-table/\n\n## The bottom line\n\nIf you build across React, Vue and Svelte and want one headless API, TanStack Table is the safer bet. If you are committed to Svelte 5 and want virtualization, Excel-style filters, editing and selection out of the box, SvGrid gets you there with far less code, and you keep a headless core when you need it.\n\n## Frequently asked questions\n\n### Is SvGrid better than TanStack Table for Svelte?\n\nFor a Svelte 5 app, SvGrid is usually the faster path: it ships a virtualized render component with built-in filters, editing and accessibility, so there is no DOM layer to write. The TanStack Svelte adapter is Svelte 5 in its v9 line, but it is headless by design; you still build and maintain the table, virtualization and editing UI. TanStack wins if you need one API across several frameworks, or if owning that markup is the point.\n\n### Can I keep a headless setup like TanStack Table?\n\nYes. createSvGrid plus the row-model factories is a headless engine; you can drive your own markup exactly as with TanStack and adopt the SvGrid component only where you want it. The headless docs and the headless demos on this page show both.\n\n### Does the TanStack Svelte adapter support Svelte 5?\n\nYes. The @tanstack/svelte-table package on npm declares a Svelte 5 peer range in its v9 line and its examples pass data through getters rather than stores. The At a glance table shows the version and the peer range as read from the registry.\n\n### How long is a TanStack Table to SvGrid migration?\n\nAbout thirty minutes for a read-only grid and two to four hours for editing-heavy ones. The row-model concepts map almost one to one; the migration guide walks through createTable to createSvGrid, the features object and the rendering options.\n\n### Which is smaller, TanStack Table or SvGrid?\n\nThe TanStack adapter, as an engine with no rendering. The At a glance table has both packages measured the same way on the same date. Add what you would write on top of TanStack (a virtualizer, filter UI, editors) before comparing, since that is what the extra size in SvGrid is.\n\n### Is SvGrid a good TanStack Table alternative for Svelte?\n\nPeople arrive here wanting less glue code, and that is the trade: you keep a headless engine with row models and composable features, and you stop hand-building the DOM, the virtualizer, the filter menus and the editors. If you need one table engine across React and Svelte, stay where you are; that portability is exactly what SvGrid gives up.\n\n## Related comparisons and docs\n\n- [SvGrid vs svelte-headless-table](https://svgrid.com/compare/svelte-headless-table/)\n- [SvGrid vs SVAR Svelte DataGrid](https://svgrid.com/compare/svar-svelte-datagrid/)\n- [SvGrid vs Flowbite / Skeleton / shadcn-svelte tables](https://svgrid.com/compare/svelte-ui-kit-tables/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Build a table from scratch](https://svgrid.com/docs/help/headless/build-a-table/)\n- [Server-side data (load on demand)](https://svgrid.com/docs/help/headless/server-side/)\n- [Headless virtualization](https://svgrid.com/docs/help/headless/virtualization/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- tanstack-svelte: The Svelte adapter is headless: build your own markup from the table instance's state and APIs; createTable takes features, columns and data through a getter; adapters exist for React, Vue, Solid, Qwik, Lit and Svelte (checked 12 Sep 2026) https://tanstack.com/table/latest/docs/framework/svelte/overview\n- tanstack-npm: The latest version's peerDependencies declare svelte ^5.0.0; licence MIT (checked 12 Sep 2026) https://www.npmjs.com/package/@tanstack/svelte-table\n- tanstack-home: Sponsor-supported with gold, silver and bronze sponsors; sponsors get private discord channels, priority issue requests and direct support; an Enterprise Support tier offers private consulting and expert support; no licence for the table is sold (checked 12 Sep 2026) https://tanstack.com/table/latest\n"
8745
8745
  },
8746
8746
  {
8747
8747
  "slug": "compare/vincjo-datatables",
8748
8748
  "path": "docs/_data/comparisons/vincjo-datatables.json",
8749
8749
  "title": "SvGrid vs @vincjo/datatables",
8750
8750
  "section": "Comparisons",
8751
- "markdown": "# SvGrid vs @vincjo/datatables\n\nCanonical URL: https://svgrid.com/compare/vincjo-datatables/\nFacts verified: 2026-09-12\nCompetitor package: @vincjo/datatables\nCompetitor site: https://github.com/vincjo/datatables\n\n@vincjo/datatables is a lightweight, headless Svelte datatable helper for sorting, filtering, and paginating your own markup.\n\n## Verdict\n\n@vincjo/datatables is a great minimal pick when you want to keep your own table markup and just need sort / filter / paginate. SvGrid is the fuller grid - virtualization, Excel filters, editing, a render component - for heavier apps.\n\nMigration guide: moving from @vincjo/datatables to SvGrid: https://svgrid.com/docs/help/migrating-from-vincjo-datatables/\n\n## At a glance\n\n| Fact | SvGrid | @vincjo/datatables | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 2.8.1 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 4 Jun 2026 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | Yes (peer svelte ^5.56.1) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 107,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.9 KB JS + 11.3 KB CSS | 10.2 KB JS, no separate stylesheet, svelte external | 9 Nov 2026 |\n| Engine alone, minified + gzip | 3.2 KB JS, no separate stylesheet (`createSvGrid` from `@svgrid/grid/core`) | the row above; the package is the engine | 10 Nov 2026 |\n| Frameworks | Svelte 5 | Svelte | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | @vincjo/datatables is MIT on npm and free; no licence is sold | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.33 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; @vincjo/datatables 2.8.1 entry `whole package` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\n@vincjo/datatables gives you a small, ergonomic handler that wraps your data with reactive sorting, filtering, and pagination while you keep full control of the markup. It is MIT-licensed and popular for its simplicity.\n\nSvGrid scales further up the curve: it keeps a headless engine but also ships a virtualized render component, an Excel-style filter menu, inline editing, cell selection, and an imperative API - for when a hand-rolled table stops being enough.\n\n## Looking for a @vincjo/datatables alternative for Svelte?\n\nIt is a helper for your own markup rather than a grid, which is exactly right until you need virtualization, inline editing or column pinning and start building them yourself. Moving to SvGrid keeps the headless option and adds those. If your table is a few hundred rows of your own HTML, staying put is the smaller dependency.\n\n## What they have in common\n\n- Svelte-native, not a port.\n- Headless-friendly: you can drive your own markup.\n- MIT-licensed.\n- Client- and server-side data modes.\n\n## Where SvGrid is stronger\n\n- Built-in virtualized render component - no need to author the table.\n- Excel-style filter menu, inline editing, and cell-range selection.\n- Row + column virtualization for large datasets.\n- Imperative SvGridApi + @svgrid/mcp MCP server.\n- Optional Enterprise pack for export, import, pivot, and AI.\n\n## Where @vincjo/datatables is stronger\n\n- Much smaller surface and bundle if all you need is sort / filter / paginate.\n- You keep 100% control of the table markup with zero render opinions.\n- Faster to learn for a simple table.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | @vincjo/datatables |\n| --- | --- | --- |\n| Svelte native | Yes | Yes - Svelte 5 peer range |\n| Render component | Yes - <SvGrid /> | No - headless, you render the markup |\n| Virtualization | Yes | No |\n| Excel-style filters | Yes | Partial - Basic filtering |\n| Inline editing | Yes | No - BYO |\n| Cell selection + copy | Yes | No - BYO |\n| Grouping / tree / master-detail | Yes | No |\n| Footprint for a simple table | Partial - Larger | Yes - Tiny |\n| AI / MCP integration | Yes | No |\n\n## When to choose SvGrid\n\n- You need virtualization, editing, or Excel-style filtering.\n- You want a render component instead of hand-authoring the table.\n- You expect the grid to grow into grouping, tree, or master/detail.\n\n## When to choose @vincjo/datatables\n\n- You only need sort / filter / paginate over a small dataset.\n- You want to keep full control of your own table markup.\n- You want the smallest possible bundle for a simple table.\n\n## Migration effort\n\nEstimated effort: 30 minutes to 2 hours per table.\n\nWhat you give up:\n\n- A tiny dependency-free helper when a sortable, filterable list is all you need.\n- Full control of the markup without opting into a headless mode.\n\nMigration guide: moving from @vincjo/datatables to SvGrid: https://svgrid.com/docs/help/migrating-from-vincjo-datatables/\n\n## Live example\n\nHeadless Table: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/186-headless-table/\n\n## The bottom line\n\nFor a small sort/filter/paginate list you keep full control over, @vincjo/datatables is delightfully light. The moment you need virtualization, Excel-style filters, editing, or grouping, SvGrid is the grid that already has them.\n\n## Frequently asked questions\n\n### SvGrid vs @vincjo/datatables - which to pick?\n\nPick @vincjo/datatables for a small, markup-controlled table; pick SvGrid when you need virtualization, editing, filters, or grouping. Both are MIT and Svelte-native.\n\n### Is @vincjo/datatables lighter than SvGrid?\n\nYes, for a simple table it is smaller. SvGrid carries more because it ships a virtualized render component and a full feature set.\n\n### Can SvGrid be headless like @vincjo/datatables?\n\nYes - its headless core lets you keep your own markup, the same way @vincjo/datatables does.\n\n### Is SvGrid a good @vincjo/datatables alternative for Svelte?\n\nIt is a helper for your own markup rather than a grid, which is exactly right until you need virtualization, inline editing or column pinning and start building them yourself. Moving to SvGrid keeps the headless option and adds those. If your table is a few hundred rows of your own HTML, staying put is the smaller dependency.\n\n## Related comparisons and docs\n\n- [SvGrid vs svelte-headless-table](https://svgrid.com/compare/svelte-headless-table/)\n- [SvGrid vs TanStack Table (Svelte)](https://svgrid.com/compare/tanstack-table/)\n- [SvGrid vs Flowbite / Skeleton / shadcn-svelte tables](https://svgrid.com/compare/svelte-ui-kit-tables/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Build a table from scratch](https://svgrid.com/docs/help/headless/build-a-table/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- vincjo-docs: A headless, SSR-friendly toolkit with no dependency: sort, filter, search and pagination in client-side and server-side modes; you render the markup (checked 12 Sep 2026) https://vincjo.fr/datatables/\n- vincjo-npm: MIT; the latest version declares a Svelte 5 peer range (checked 12 Sep 2026) https://www.npmjs.com/package/@vincjo/datatables\n"
8751
+ "markdown": "# SvGrid vs @vincjo/datatables\n\nCanonical URL: https://svgrid.com/compare/vincjo-datatables/\nFacts verified: 2026-09-12\nCompetitor package: @vincjo/datatables\nCompetitor site: https://github.com/vincjo/datatables\n\n@vincjo/datatables is a lightweight, headless Svelte datatable helper for sorting, filtering, and paginating your own markup.\n\n## Verdict\n\n@vincjo/datatables is a great minimal pick when you want to keep your own table markup and just need sort / filter / paginate. SvGrid is the fuller grid - virtualization, Excel filters, editing, a render component - for heavier apps.\n\nMigration guide: moving from @vincjo/datatables to SvGrid: https://svgrid.com/docs/help/migrating-from-vincjo-datatables/\n\n## At a glance\n\n| Fact | SvGrid | @vincjo/datatables | Checked |\n| --- | --- | --- | --- |\n| Latest version | 3.0.32 | 2.8.1 | 9 Nov 2026 |\n| Licence field on npm | MIT | MIT | 9 Nov 2026 |\n| Last published | 3 Nov 2026 | 4 Jun 2026 | 9 Nov 2026 |\n| Svelte 5 support | Native (Svelte 5 runes) | Yes (peer svelte ^5.56.1) | 9 Nov 2026 |\n| npm downloads, 30 days to 8 Nov 2026 | 44,600 | 107,000 | 9 Nov 2026 |\n| Bundle, minified + gzip | 99.6 KB JS + 11.4 KB CSS | 10.2 KB JS, no separate stylesheet, svelte external | 9 Nov 2026 |\n| Engine alone, minified + gzip | 3.2 KB JS, no separate stylesheet (`createSvGrid` from `@svgrid/grid/core`) | the row above; the package is the engine | 10 Nov 2026 |\n| Frameworks | Svelte 5 | Svelte | 12 Sep 2026 |\n| Pricing | MIT core; @svgrid/enterprise from $299 per developer per year (Indie, under $1M revenue), $599 for Enterprise | @vincjo/datatables is MIT on npm and free; no licence is sold | 12 Sep 2026 |\n\nBundle sizes: each package built alone with Vite in library mode, minified, gzip level 9, Svelte kept external where a package uses it (it is a peer dependency). SvGrid 3.0.34 measured 10 Nov 2026 with packages/grid/scripts/measure-size.mjs; @vincjo/datatables 2.8.1 entry `whole package` measured 9 Nov 2026 with packages/grid/scripts/measure-competitor-bundles.mjs.\n\n## Overview\n\n@vincjo/datatables gives you a small, ergonomic handler that wraps your data with reactive sorting, filtering, and pagination while you keep full control of the markup. It is MIT-licensed and popular for its simplicity.\n\nSvGrid scales further up the curve: it keeps a headless engine but also ships a virtualized render component, an Excel-style filter menu, inline editing, cell selection, and an imperative API - for when a hand-rolled table stops being enough.\n\n## Looking for a @vincjo/datatables alternative for Svelte?\n\nIt is a helper for your own markup rather than a grid, which is exactly right until you need virtualization, inline editing or column pinning and start building them yourself. Moving to SvGrid keeps the headless option and adds those. If your table is a few hundred rows of your own HTML, staying put is the smaller dependency.\n\n## What they have in common\n\n- Svelte-native, not a port.\n- Headless-friendly: you can drive your own markup.\n- MIT-licensed.\n- Client- and server-side data modes.\n\n## Where SvGrid is stronger\n\n- Built-in virtualized render component - no need to author the table.\n- Excel-style filter menu, inline editing, and cell-range selection.\n- Row + column virtualization for large datasets.\n- Imperative SvGridApi + @svgrid/mcp MCP server.\n- Optional Enterprise pack for export, import, pivot, and AI.\n\n## Where @vincjo/datatables is stronger\n\n- Much smaller surface and bundle if all you need is sort / filter / paginate.\n- You keep 100% control of the table markup with zero render opinions.\n- Faster to learn for a simple table.\n\n## Feature by feature\n\nYes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.\n\n| Feature | SvGrid | @vincjo/datatables |\n| --- | --- | --- |\n| Svelte native | Yes | Yes - Svelte 5 peer range |\n| Render component | Yes - <SvGrid /> | No - headless, you render the markup |\n| Virtualization | Yes | No |\n| Excel-style filters | Yes | Partial - Basic filtering |\n| Inline editing | Yes | No - BYO |\n| Cell selection + copy | Yes | No - BYO |\n| Grouping / tree / master-detail | Yes | No |\n| Footprint for a simple table | Partial - Larger | Yes - Tiny |\n| AI / MCP integration | Yes | No |\n\n## When to choose SvGrid\n\n- You need virtualization, editing, or Excel-style filtering.\n- You want a render component instead of hand-authoring the table.\n- You expect the grid to grow into grouping, tree, or master/detail.\n\n## When to choose @vincjo/datatables\n\n- You only need sort / filter / paginate over a small dataset.\n- You want to keep full control of your own table markup.\n- You want the smallest possible bundle for a simple table.\n\n## Migration effort\n\nEstimated effort: 30 minutes to 2 hours per table.\n\nWhat you give up:\n\n- A tiny dependency-free helper when a sortable, filterable list is all you need.\n- Full control of the markup without opting into a headless mode.\n\nMigration guide: moving from @vincjo/datatables to SvGrid: https://svgrid.com/docs/help/migrating-from-vincjo-datatables/\n\n## Live example\n\nHeadless Table: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/186-headless-table/\n\n## The bottom line\n\nFor a small sort/filter/paginate list you keep full control over, @vincjo/datatables is delightfully light. The moment you need virtualization, Excel-style filters, editing, or grouping, SvGrid is the grid that already has them.\n\n## Frequently asked questions\n\n### SvGrid vs @vincjo/datatables - which to pick?\n\nPick @vincjo/datatables for a small, markup-controlled table; pick SvGrid when you need virtualization, editing, filters, or grouping. Both are MIT and Svelte-native.\n\n### Is @vincjo/datatables lighter than SvGrid?\n\nYes, for a simple table it is smaller. SvGrid carries more because it ships a virtualized render component and a full feature set.\n\n### Can SvGrid be headless like @vincjo/datatables?\n\nYes - its headless core lets you keep your own markup, the same way @vincjo/datatables does.\n\n### Is SvGrid a good @vincjo/datatables alternative for Svelte?\n\nIt is a helper for your own markup rather than a grid, which is exactly right until you need virtualization, inline editing or column pinning and start building them yourself. Moving to SvGrid keeps the headless option and adds those. If your table is a few hundred rows of your own HTML, staying put is the smaller dependency.\n\n## Related comparisons and docs\n\n- [SvGrid vs svelte-headless-table](https://svgrid.com/compare/svelte-headless-table/)\n- [SvGrid vs TanStack Table (Svelte)](https://svgrid.com/compare/tanstack-table/)\n- [SvGrid vs Flowbite / Skeleton / shadcn-svelte tables](https://svgrid.com/compare/svelte-ui-kit-tables/)\n- [Comparison: SvGrid vs AG Grid vs TanStack Table](https://svgrid.com/docs/help/comparison/)\n- [Build a table from scratch](https://svgrid.com/docs/help/headless/build-a-table/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 12 Sep 2026. Versions, licences and download counts come from the npm registry; feature and pricing statements from the pages listed below.\n\n- vincjo-docs: A headless, SSR-friendly toolkit with no dependency: sort, filter, search and pagination in client-side and server-side modes; you render the markup (checked 12 Sep 2026) https://vincjo.fr/datatables/\n- vincjo-npm: MIT; the latest version declares a Svelte 5 peer range (checked 12 Sep 2026) https://www.npmjs.com/package/@vincjo/datatables\n"
8752
8752
  }
8753
8753
  ];
8754
8754
  export const apiReference = {
@@ -8826,7 +8826,7 @@ export const apiReference = {
8826
8826
  };
8827
8827
  export const apiSurface = {
8828
8828
  "gridVersion": "3.0.34",
8829
- "enterpriseVersion": "3.1.38",
8829
+ "enterpriseVersion": "3.1.39",
8830
8830
  "grid": {
8831
8831
  "values": [
8832
8832
  "ALL_FILTER_OPERATORS",