svelte-advanced-datatable-data
Installation
SKILL.md
svelte-advanced-datatable — data sources, search, errors
The table owns the UI; the data source owns IO. Pick the implementation that matches where the data lives, wire search
through the parser of your choice, and surface failures through onError + the errorState snippet.
1. Pick a data source
| Where the data lives | Use | Import from |
|---|---|---|
| JS array already in memory (client-side) | LocalDataSource<T> |
svelte-advanced-datatable (or /dataSource) |
| Single REST POST returning paginated rows | FetchApiDataSource<T> |
svelte-advanced-datatable (or /dataSource) |
| Any bespoke async function (GraphQL, RPC, SDK) | ApiFunctionDataSource<T> |
svelte-advanced-datatable (or /dataSource) |
| Same as above + TanStack Query caching | SvelteQueryDataSource<T> |
svelte-advanced-datatable/dataSource/svelteQuery |
| Anything else (websocket, EventSource, ...) | extend AbstractDataSource<T> and implement requestData |
svelte-advanced-datatable |
The data source is passed as a separate dataSource prop on <DataTable> — never inside config.
2. The request/response contract
Related skills
More from kage0x3b/svelte-advanced-datatable
svelte-advanced-datatable-state
Configure persistence tiers (transient snapshot/url/none + persistent localStorage/sessionStorage/none) and
1svelte-advanced-datatable
Scaffold or modify a Svelte 5 DataTable using the svelte-advanced-datatable package — DataTableConfig, column types
1svelte-advanced-datatable-interactions
Wire row selection, per-row + bulk actions (DataTableAction with onSingle/onMulti, primary/destructive variants),
1