SvGrid - Frequently Asked Questions

How does SvGrid compare to other Svelte data grids?

SvGrid is a Svelte-5-native data grid that covers a broad feature surface most enterprise grids charge extra for: Excel-style filters, grouping, master/detail, virtualization. The API is designed around Svelte runes ($state / $derived / $effect) and snippets rather than ported from a React or Angular library. See the Compare page for side-by-side matrices against TanStack Table, svelte-headless-table, and other established options.

Is SvGrid production-ready?

Yes. Releases follow semver, so minor releases are additive and breaking changes wait for a major. The example gallery covers the documented surface, and our sibling products (jQWidgets / htmlelements.com) are used in production by 5,000+ customers including Samsung, Boeing, NVIDIA, Microsoft, Nokia, and Intel.

Is the library covered by tests?

Yes. 2,308 tests across 179 files in the grid, plus 1,607 across 101 in @svgrid/enterprise. Vitest suite with mounted-component behavioral tests against the real <SvGrid /> render layer plus pure unit tests for the headless engine, virtualization, accessibility, and formatting helpers. Coverage is 79.6% lines / 73.7% statements / 74.2% functions / 64.4% branches, enforced as a CI ratchet that fails the build on a drop. The render components (SvGrid, the chart panel, menus, the cell editor) are excluded from that number and covered by behavioral mount tests instead, because their layout and paint branches depend on real browser metrics that jsdom reports as zero. CI also enforces a bundle-size budget and asserts the grid still server-renders. Full breakdown on the Testing & Quality page.

Does it support Svelte 4?

No. SvGrid is built on Svelte 5 runes. If you are still on Svelte 4, consider htmlelements.com (the sibling product from jQWidgets) which supports vanilla JS and any framework.

How do I add SvGrid to a SvelteKit app?

Either `npm install @svgrid/grid`, or `npx sv add @svgrid` to go through the Svelte CLI - that adds the dependency and can drop in a working demo grid. The SvelteKit guide in the docs covers loading rows in +page.server.ts, keeping sort state in the URL, saving edits through a form action, and exactly what ends up in the server HTML.

Does it work with SvelteKit / SSR?

Yes, and it genuinely server-renders. The server HTML contains the header plus a viewport-sized window of rows with their real cell values, so crawlers and no-JS clients see the content; the remaining rows arrive once the client measures the viewport. Virtualization survives SSR, so a 5,000-row grid does not serialise 5,000 rows into the page. This is checked in CI against a real server build. The headless engine at @svgrid/grid/core is SSR-safe too, and is the route to take if you want to own the markup.

I already use svelte-headless-table. How hard is the move?

`npx @svgrid/migrate` does the mechanical part: it translates the column definitions and plugin config, and deletes the Subscribe/Render scaffolding that SvGrid's renderer replaces. It previews by default and only writes with --write. Custom cell renderers are kept as TODO comments rather than dropped silently. Worth knowing the alternatives too: @humanspeak/svelte-headless-table is a maintained Svelte 5 fork with the same API, which is the cheapest move if the library is working for you.

How big is the bundle?

Measured gzipped with Svelte as an excluded peer dependency: the headless core (createGrid + a row model) is about 2 kB, and the full <SvGrid> render component - virtualization, Excel-style filters, inline editing, grouping, tree, and accessibility in one import - is about 78 kB plus 9 kB of CSS (around 340 kB minified). Charts, date/time editors, menus, and export split into import() chunks totalling about 82 kB that load on demand rather than up front. The library ships as ESM; @svgrid/enterprise features are separate subpath imports that lazy-load.

What is the license?

@svgrid/grid is MIT-licensed - permissive, SPDX-recognised, and friendly to corporate legal review. The paid companion package @svgrid/enterprise (data export + print) ships under a separate commercial license.

Do I need to pay for production use?

Not for the core library - @svgrid/grid is MIT-licensed, free for commercial use. Pay for @svgrid/enterprise only if you need the export + print feature pack, the Kanban / Scheduler / Spreadsheet views, the Server-Side Row Model, Studio, or paid support. Two Enterprise license tiers, per developer, both covering unlimited apps: Enterprise (Grid Developer License, $599) is the enterprise grid; Enterprise Suite (Suite Developer License, $999) adds the Spreadsheet and SvGrid Studio. Freelancers and companies under $1M in yearly revenue can buy the Enterprise feature set as the Indie Developer License ($299), which comes without support. Each is a perpetual license that includes 1 year of updates and support and renews automatically each year (cancel anytime, keep your paid-term versions). Without a key, Enterprise features still work but render an "Unlicensed @svgrid/enterprise" watermark.

What is the difference between Enterprise and Enterprise Suite?

The feature set, not the app count - both cover an unlimited number of deployed applications in your organisation, including subsidiaries and sister products. Enterprise ($599 per developer) is the enterprise grid: the Server-Side Row Model, Excel / PDF export and print, import, pivot table and designer, the Kanban board and Scheduler views, alerts and staged editing. Enterprise Suite ($999 per developer) adds the Excel-style Spreadsheet (<SvSheet>, the formula engine, xlsx / xls / ods files) and SvGrid Studio (the designer, the SvelteKit code generator, the SQL / REST / Supabase data sources). Both are per-developer perpetual licenses that include 1 year of updates and support and renew automatically (cancel anytime).

How do I get support?

For Community users: open a GitHub issue. For Enterprise customers (Single or Multiple App): email [email protected] - we respond within one business day. Enterprise customers also get a private Slack channel.

Is there a roadmap?

Yes - see the public Roadmap page (https://svgrid.com/roadmap). It groups what is not built yet by area (columns, rows, cells, filtering, editing) with a rough effort tag, plus a "recently shipped" track record. Request features or send PRs on GitHub.

What is the MCP server for?

@svgrid/mcp gives Claude / Cursor / any MCP-capable AI tool access to the SvGrid examples and docs at runtime. That eliminates hallucinated APIs and stale answers. See the MCP page for setup.

Can I use the MCP server offline?

Yes. The server runs entirely on stdio with no network calls; the example sources and docs are bundled into the npm package.

Who builds SvGrid?

SvGrid is developed by jQWidgets - the team behind jQWidgets, htmlelements.com, and Smart UI. We have been shipping UI components since 2011 to 5,000+ customers including Samsung, Boeing, NVIDIA, Microsoft, Nokia, and Intel.

Where can I see other products from your team?

jqwidgets.com for the jQuery / Angular / React / Vue libraries, htmlelements.com for the vanilla web-components library. SvGrid is our Svelte-native effort.

Is the website itself open source?

Yes. The website is built with Svelte 5 + Vite + Tailwind, lives in the same monorepo as the library at website/, and is deployed to GitHub Pages on every push to main.