@tanstack/svelte-table 9.0.0-beta.38 → 9.0.0-beta.42

package/skills/svelte/client-to-server/SKILL.md

@@ -1,236 +0,0 @@
----
-name: svelte/client-to-server
-description: >
-  Convert a client-side Svelte table to server-side (manual) modes. Toggle `manualPagination`,
-  `manualSorting`, `manualFiltering`, `manualGrouping`, `manualExpanding` for whatever the server
-  owns, drop the matching row-model factory slots from `tableFeatures` and any `features` you no
-  longer need, supply `rowCount` for the pager, then drive the request from `table.atoms.pagination`
-  / `table.atoms.sorting` / etc. (or external atoms you own) using rune-aware getters
-  (`get data()`, `get rowCount()`) so the table re-syncs in `$effect.pre`. Svelte 5+ only.
-type: lifecycle
-library: tanstack-table
-framework: svelte
-library_version: '9.0.0-alpha.48'
-requires:
-  - state-management
-  - pagination
-  - filtering
-  - sorting
-  - svelte/table-state
-sources:
-  - TanStack/table:examples/svelte/basic-external-atoms/
-  - TanStack/table:examples/svelte/basic-external-state/
-  - TanStack/table:examples/svelte/with-tanstack-query/
-  - TanStack/table:docs/framework/svelte/guide/table-state.md
----
-
-# Client → Server (Svelte)
-
-You have a working client-side table. The dataset is too big to ship to the browser, or it
-lives behind an API. You want sorting / filtering / pagination to run on the server while the
-table still feels the same in the UI.
-
-## Mental model
-
-Each "manual mode" flag tells the table: **don't run this stage of the pipeline; trust the data
-you receive.** You can mix modes freely — manual pagination + client-side sorting on the
-already-paged window is perfectly valid for medium datasets.
-
-| Flag               | Meaning                                      | What you must provide                                       |
-| ------------------ | -------------------------------------------- | ----------------------------------------------------------- |
-| `manualPagination` | Server owns slicing; do not paginate locally | `rowCount` (or `pageCount`)                                 |
-| `manualSorting`    | Server owns ordering                         | Sort the server query by `sorting` state                    |
-| `manualFiltering`  | Server owns row filtering                    | Filter the server query by `columnFilters` / `globalFilter` |
-| `manualGrouping`   | Server returns already-grouped rows          | Pre-shaped data                                             |
-| `manualExpanding`  | Server resolves sub-rows                     | Server-provided sub-row tree                                |
-
-When a stage is manual, you can drop its row-model factory slot from `tableFeatures`. `manualPagination: true` does not need `paginatedRowModel: createPaginatedRowModel()` in the features object.
-
-## Step 1 — Identify what's moving server-side
-
-For a typical "search and paginate against a database" screen:
-
-- Pagination → server
-- Filtering (column filter inputs + a global search box) → server
-- Sorting → server (usually, since a partial page can't be sorted client-side meaningfully)
-- Selection / visibility / column ordering → still client
-
-So the table keeps `rowSelectionFeature` etc., drops `columnFilteringFeature` /
-`rowPaginationFeature` / `rowSortingFeature` _row models_ but keeps the _features_ so the
-state slices and UI APIs still exist.
-
-> Subtle point: keep the **feature** even if you drop the row model. The feature is what gives
-> you `column.getCanSort()`, `table.setPageIndex()`, `column.setFilterValue()` — all the
-> control-surface APIs. Dropping it kills the UI.
-
-## Step 2 — Own the relevant state with external atoms
-
-External atoms make state portable: the data layer (a fetch / query / store) can read the
-same atoms the table writes to. Use `@tanstack/svelte-store`:
-
-```ts
-import { createAtom, useSelector } from '@tanstack/svelte-store'
-import type {
-  ColumnFiltersState,
-  PaginationState,
-  SortingState,
-} from '@tanstack/svelte-table'
-
-const paginationAtom = createAtom<PaginationState>({
-  pageIndex: 0,
-  pageSize: 10,
-})
-const sortingAtom = createAtom<SortingState>([])
-const filtersAtom = createAtom<ColumnFiltersState>([])
-
-// For Svelte markup that should react to changes:
-const pagination = useSelector(paginationAtom)
-const sorting = useSelector(sortingAtom)
-const filters = useSelector(filtersAtom)
-```
-
-## Step 3 — Configure the table
-
-```svelte
-<script lang="ts">
-  import {
-    columnFilteringFeature,
-    createTable,
-    rowPaginationFeature,
-    rowSortingFeature,
-    tableFeatures,
-  } from '@tanstack/svelte-table'
-
-  const features = tableFeatures({
-    columnFilteringFeature,
-    rowPaginationFeature,
-    rowSortingFeature,
-  })
-
-  // No row-model factories for these — server owns them.
-  const table = createTable({
-    features,
-    columns,
-    get data() {
-      return query.data?.rows ?? []
-    },
-    get rowCount() {
-      return query.data?.rowCount
-    },
-    atoms: {
-      pagination: paginationAtom,
-      sorting: sortingAtom,
-      columnFilters: filtersAtom,
-    },
-    manualPagination: true,
-    manualSorting: true,
-    manualFiltering: true,
-  })
-</script>
-```
-
-`rowCount` is what makes `table.getPageCount()` / `table.getCanNextPage()` correct under
-manual pagination. Without it the pager has no idea how many pages exist.
-
-## Step 4 — Drive the fetch from those atoms
-
-Wire whatever data layer you use (TanStack Query, a raw `fetch`, SvelteKit `load`, etc.) to
-read the atoms. With TanStack Query:
-
-```ts
-import { createQuery, keepPreviousData } from '@tanstack/svelte-query'
-
-const dataQuery = createQuery<{ rows: Array<Person>; rowCount: number }>(
-  () => ({
-    queryKey: ['people', pagination.current, sorting.current, filters.current],
-    queryFn: () =>
-      fetch('/api/people', {
-        method: 'POST',
-        body: JSON.stringify({
-          pageIndex: pagination.current.pageIndex,
-          pageSize: pagination.current.pageSize,
-          sorting: sorting.current,
-          filters: filters.current,
-        }),
-      }).then((r) => r.json()),
-    placeholderData: keepPreviousData,
-  }),
-)
-```
-
-`placeholderData: keepPreviousData` is what kills the "rows blank for one tick on every
-page change" flash.
-
-## Step 5 — Reset behavior
-
-When the user changes a filter, you usually want to jump back to page 0. The table does this
-automatically when client-side filtering owns the data, but with manual mode the data layer
-controls it. Simplest fix: explicitly reset.
-
-```ts
-$effect(() => {
-  // re-runs whenever filters.current identity changes
-  filters.current
-  table.setPageIndex(0)
-})
-```
-
-Or wrap your filter `onChange` handlers to also call `table.setPageIndex(0)`.
-
-## Step 6 — A note on global filtering
-
-If you also support `globalFilterFeature`, debounce the input. `column.setFilterValue` and
-`table.setGlobalFilter` fire per keystroke; without debouncing you fire one request per typed
-character. See the `compose-with-tanstack-pacer` skill for the pattern.
-
-## Hybrid example — manual pagination only
-
-Sometimes you only paginate server-side and let the page-sized window sort/filter on the
-client.
-
-```ts
-const table = createTable({
-  features: tableFeatures({
-    columnFilteringFeature,
-    rowPaginationFeature,
-    rowSortingFeature,
-    filteredRowModel: createFilteredRowModel(), // client filters the page
-    sortedRowModel: createSortedRowModel(), // client sorts the page
-    filterFns,
-    sortFns,
-  }),
-  columns,
-  get data() {
-    return query.data?.rows ?? []
-  },
-  get rowCount() {
-    return query.data?.rowCount
-  },
-  atoms: { pagination: paginationAtom },
-  manualPagination: true,
-})
-```
-
-Only the manual flag for the stage you're moving server-side.
-
-## Common failure modes
-
-- **Forgot `rowCount`.** `table.getPageCount()` returns `-1`, the pager looks broken.
-- **Dropped the feature, not just the row model.** Lost `column.getCanSort()` and friends.
-  Keep the feature when you still need its UI APIs; only drop the row-model factory.
-- **Both `state.pagination` and `atoms.pagination`.** Atoms silently win; the `on*Change`
-  callback never fires.
-- **Re-creating atoms inside reactive blocks.** Atoms must be stable across renders. Declare
-  them at module / component-init scope, not inside `$derived` or `$effect`.
-- **Forgetting to reset page on filter change.** Stay on page 12 of a now-2-page result set.
-- **Plain `data: query.data?.rows`.** No getter, no reactivity. Use `get data()`.
-- **Reimplementing pagination math.** `table.setPageIndex / nextPage / previousPage /
-firstPage / lastPage / setPageSize / getCanNextPage / getCanPreviousPage / getPageCount`
-  already exist and respect manual mode.
-
-## Related skills
-
-- `tanstack-table/svelte/compose-with-tanstack-query` — the same flow with a Query data layer.
-- `tanstack-table/svelte/compose-with-tanstack-pacer` — debouncing filter inputs.
-- `tanstack-table/svelte/compose-with-tanstack-store` — atom interop and per-slice subscription.
-- `tanstack-table/core/pagination` / `filtering` / `sorting` — feature deep dives.

package/skills/svelte/compose-with-tanstack-form/SKILL.md

@@ -1,294 +0,0 @@
----
-name: svelte/compose-with-tanstack-form
-description: >
-  Editable cells in `@tanstack/svelte-table` powered by `@tanstack/svelte-form`. The table is the
-  layout primitive; the form owns the state. Use `createFormHook` to register reusable field
-  components (`TextField`, `NumberField`, `SelectField`), then in each column's `cell` renderer
-  return `renderComponent(MyFieldCell, { form, rowIndex, fieldName })` and inside that cell call
-  `form.Field` (or an `AppField`) with `name="data[${rowIndex}].${fieldName}"`. Drive the table's
-  `data` from `form.state.values.data`. Svelte 5+ only.
-type: composition
-library: tanstack-table
-framework: svelte
-library_version: '9.0.0-alpha.48'
-requires:
-  - row-selection
-  - column-definitions
-sources:
-  - TanStack/table:examples/svelte/with-tanstack-form/
-  - TanStack/table:docs/framework/svelte/svelte-table.md
----
-
-# Compose with TanStack Form (Svelte)
-
-Editable tables are a classic source of state-management chaos. With v9 + TanStack Form, the
-division of labor is crisp:
-
-- **Form** owns the editable values (per-row, per-field).
-- **Table** owns the layout (columns, filtering, pagination of the same form data).
-- **Cells** are just field renderers — they read and write through Form's field APIs.
-
-## Install
-
-```bash
-pnpm add @tanstack/svelte-form @tanstack/svelte-table
-```
-
-## Set up a field-component-rich Form hook
-
-Define a `createAppForm` once with the reusable field components. This is the form-side
-equivalent of `createTableHook`.
-
-```ts
-// hooks/form.ts
-import { createFormHook, createFormHookContexts } from '@tanstack/svelte-form'
-import TextField from '../components/TextField.svelte'
-import NumberField from '../components/NumberField.svelte'
-import SelectField from '../components/SelectField.svelte'
-import SubmitButton from '../components/SubmitButton.svelte'
-import FormStateIndicator from '../components/FormStateIndicator.svelte'
-
-export const { fieldContext, formContext } = createFormHookContexts()
-
-export const { useAppForm: createAppForm } = createFormHook({
-  fieldComponents: { TextField, NumberField, SelectField },
-  formComponents: { SubmitButton, FormStateIndicator },
-  fieldContext,
-  formContext,
-})
-```
-
-## Reusable field cell components
-
-Each cell type is a small Svelte component that knows which row + field it edits and uses
-`form.Field`. The shape is the same across types — `TextFieldCell`, `NumberFieldCell`,
-`SelectFieldCell`.
-
-```svelte
-<!-- TextFieldCell.svelte -->
-<script lang="ts">
-  type Props = {
-    form: ReturnType<typeof createAppForm>
-    rowIndex: number
-    fieldName: string
-  }
-  let { form, rowIndex, fieldName }: Props = $props()
-</script>
-
-<form.Field name={`data[${rowIndex}].${fieldName}`}>
-  {#snippet children(field)}
-    <input
-      type="text"
-      value={field.state.value}
-      oninput={(e) => field.handleChange((e.target as HTMLInputElement).value)}
-      onblur={field.handleBlur}
-    />
-    {#if field.state.meta.errors?.length}
-      <small class="error">{field.state.meta.errors.join(', ')}</small>
-    {/if}
-  {/snippet}
-</form.Field>
-```
-
-## Wire the table to form state
-
-```svelte
-<script lang="ts">
-  import {
-    columnFilteringFeature,
-    createColumnHelper,
-    createFilteredRowModel,
-    createPaginatedRowModel,
-    createTable,
-    filterFns,
-    FlexRender,
-    renderComponent,
-    rowPaginationFeature,
-    tableFeatures,
-  } from '@tanstack/svelte-table'
-  import { z } from 'zod'
-  import { createAppForm } from './hooks/form'
-  import TextFieldCell from './TextFieldCell.svelte'
-  import NumberFieldCell from './NumberFieldCell.svelte'
-  import SelectFieldCell from './SelectFieldCell.svelte'
-  import { makeData, type Person } from './makeData'
-
-  const features = tableFeatures({
-    rowPaginationFeature,
-    columnFilteringFeature,
-    filteredRowModel: createFilteredRowModel(),
-    paginatedRowModel: createPaginatedRowModel(),
-    filterFns,
-  })
-
-  const columnHelper = createColumnHelper<typeof features, Person>()
-
-  const personSchema = z.object({
-    firstName: z.string().min(1),
-    lastName: z.string().min(1),
-    age: z.number().min(0).max(150),
-    visits: z.number().min(0),
-    progress: z.number().min(0).max(100),
-    status: z.enum(['relationship', 'complicated', 'single']),
-  })
-
-  const formSchema = z.object({ data: z.array(personSchema) })
-  type FormData = z.infer<typeof formSchema>
-
-  const form = createAppForm(() => ({
-    defaultValues: { data: makeData(1_000) } as FormData,
-    validators: { onChange: formSchema },
-    onSubmit: ({ value }) => alert(`Saved ${value.data.length} rows`),
-  }))
-
-  const columns = columnHelper.columns([
-    columnHelper.accessor('firstName', {
-      header: 'First Name',
-      cell: ({ row }) =>
-        renderComponent(TextFieldCell, {
-          form,
-          rowIndex: row.index,
-          fieldName: 'firstName',
-        }),
-    }),
-    columnHelper.accessor('age', {
-      header: 'Age',
-      cell: ({ row }) =>
-        renderComponent(NumberFieldCell, {
-          form,
-          rowIndex: row.index,
-          fieldName: 'age',
-        }),
-    }),
-    columnHelper.accessor('status', {
-      header: 'Status',
-      cell: ({ row }) =>
-        renderComponent(SelectFieldCell, {
-          form,
-          rowIndex: row.index,
-        }),
-    }),
-    // ...
-  ])
-
-  const table = createTable({
-    features,
-    columns,
-    get data() {
-      // The form is the source of truth.
-      return form.state.values.data
-    },
-  })
-</script>
-
-<form
-  onsubmit={(e) => {
-    e.preventDefault()
-    void form.handleSubmit()
-  }}
->
-  <form.AppForm>
-    {#snippet children()}
-      <form.FormStateIndicator />
-      <form.SubmitButton label="Save" />
-    {/snippet}
-  </form.AppForm>
-
-  <button
-    type="button"
-    onclick={() =>
-      form.pushFieldValue('data', {
-        firstName: '',
-        lastName: '',
-        age: 0,
-        visits: 0,
-        progress: 0,
-        status: 'single',
-      })}>Add Row</button
-  >
-
-  <table>
-    <thead>
-      {#each table.getHeaderGroups() as headerGroup (headerGroup.id)}
-        <tr>
-          {#each headerGroup.headers as header (header.id)}
-            <th><FlexRender {header} /></th>
-          {/each}
-        </tr>
-      {/each}
-    </thead>
-    <tbody>
-      {#each table.getRowModel().rows as row (row.id)}
-        <tr>
-          {#each row.getAllCells() as cell (cell.id)}
-            <td><FlexRender {cell} /></td>
-          {/each}
-        </tr>
-      {/each}
-    </tbody>
-  </table>
-</form>
-```
-
-## Why `row.index` and not `row.id`?
-
-Form indexes its arrays positionally. `row.index` is the position inside the **current** row
-model (after filter + sort + paging). If you want a positional address into `form.state.values.data`,
-you usually want the **original** index — pass `row.original` somewhere that exposes it, or
-store an `id` field and look it up.
-
-For the common case where the table renders the array in its natural order (no sort, no
-filter that reorders), `row.index` matches the form-array position.
-
-## Add Row / Remove Row
-
-Use the form's array helpers; the table re-renders because its `data` getter points at
-`form.state.values.data`.
-
-```ts
-form.pushFieldValue('data', newPerson)
-form.removeFieldValue('data', rowIndex)
-form.replaceFieldValue('data', rowIndex, updatedPerson)
-```
-
-## Pairing with selection
-
-Add `rowSelectionFeature` to enable row checkboxes, then a "delete selected" button can use
-`table.getSelectedRowModel()` to collect rows and `form.removeFieldValue` to remove them.
-
-```ts
-const selectedRows = table.getSelectedRowModel().rows
-const indexesDesc = selectedRows.map((r) => r.index).sort((a, b) => b - a)
-for (const i of indexesDesc) {
-  form.removeFieldValue('data', i)
-}
-table.resetRowSelection()
-```
-
-Remove in descending order so earlier removals don't shift later indexes.
-
-## Pairing with virtualization
-
-You can virtualize the rows even with editable cells — but be aware that **virtualized rows
-unmount when scrolled out of view**, taking their inline form fields with them. If a cell has
-unsaved local-only state, you'll lose it. Use Form fields (which live on the form's state)
-and you're fine — the field state survives the unmount.
-
-## Common failure modes
-
-- **`renderComponent` from React docs.** Use the Svelte adapter's `renderComponent` from
-  `@tanstack/svelte-table`. The signature is the same shape but the runtime is different.
-- **`form` not reactive in cells.** Pass `form` as a prop; don't reach for it via context
-  unless you set up `formContext`.
-- **Wrong field name.** `data[${row.index}].firstName` — string template, not a plain join.
-- **Reordering / filtering breaks `row.index`.** As above. Either keep a stable id and resolve
-  back to the form-array index, or accept that `row.index` only addresses the visible window.
-- **Editing inside virtualized rows without form state.** Field values lost on scroll.
-- **Reimplementing form state with `$state` per cell.** Defeats the whole point — Form already
-  owns this state and runs validation.
-
-## Related skills
-
-- `tanstack-table/core/row-selection` — checkbox column patterns.
-- `tanstack-table/core/column-definitions` — accessor / display columns.
-- `tanstack-table/svelte/table-state` — `getRowModel()` and reactivity.

package/skills/svelte/compose-with-tanstack-pacer/SKILL.md

@@ -1,176 +0,0 @@
----
-name: svelte/compose-with-tanstack-pacer
-description: >
-  Use `@tanstack/svelte-pacer` to debounce / throttle high-frequency writes that drive a
-  `@tanstack/svelte-table` v9 instance — column filter inputs and column resize state are the
-  two hot paths. Import `createDebouncer` (or `createThrottler`) from
-  `@tanstack/svelte-pacer/debouncer`, wrap the call site that hits `column.setFilterValue`,
-  `table.setGlobalFilter`, or commits a resize, and call `.maybeExecute(value)` on each event.
-  Svelte 5+ only — pacer instances live at component-init scope.
-type: composition
-library: tanstack-table
-framework: svelte
-library_version: '9.0.0-alpha.48'
-requires:
-  - filtering
-  - column-layout
-sources:
-  - TanStack/table:examples/svelte/with-tanstack-form/
-  - TanStack/table:docs/framework/svelte/guide/table-state.md
----
-
-# Compose with TanStack Pacer (Svelte)
-
-Two places in a v9 table take state writes at event-loop rate: **filter inputs** (one
-keystroke = one `setFilterValue`) and **column resizing** (one pointermove = one
-`columnSizing` write). Without rate-limiting they either flood the network (server-side
-filtering) or burn CPU on tens of thousands of re-renders per drag.
-
-`@tanstack/svelte-pacer` gives you `createDebouncer`, `createThrottler`, and friends. Wrap
-the call site and you're done.
-
-## Install
-
-```bash
-pnpm add @tanstack/svelte-pacer
-```
-
-## Debounce a column filter input
-
-Client-side debouncing reduces re-render churn. Server-side debouncing also kills request
-storms.
-
-```svelte
-<script lang="ts">
-  import { createDebouncer } from '@tanstack/svelte-pacer/debouncer'
-  import type { Column } from '@tanstack/svelte-table'
-
-  type Props = { column: Column<typeof features, Person> }
-  let { column }: Props = $props()
-
-  let localValue = $state((column.getFilterValue() as string) ?? '')
-
-  const debouncedSetFilter = createDebouncer(
-    (value: string) => column.setFilterValue(value),
-    { wait: 200 },
-  )
-
-  function onInput(e: Event) {
-    const value = (e.target as HTMLInputElement).value
-    localValue = value
-    debouncedSetFilter.maybeExecute(value)
-  }
-</script>
-
-<input type="text" value={localValue} oninput={onInput} placeholder="Search…" />
-```
-
-Why the `localValue`? So the input stays snappy (controlled by `$state`) while the table only
-sees the debounced commit.
-
-## Debounce a global filter
-
-Same shape, calling `table.setGlobalFilter`:
-
-```svelte
-<script lang="ts">
-  import { createDebouncer } from '@tanstack/svelte-pacer/debouncer'
-
-  let search = $state('')
-  const debouncedSetGlobalFilter = createDebouncer(
-    (value: string) => table.setGlobalFilter(value),
-    { wait: 250 },
-  )
-</script>
-
-<input
-  type="text"
-  value={search}
-  oninput={(e) => {
-    search = (e.target as HTMLInputElement).value
-    debouncedSetGlobalFilter.maybeExecute(search)
-  }}
-/>
-```
-
-## Throttle column resizing
-
-`columnResizingFeature` (which requires `columnSizingFeature` to also be registered in `tableFeatures`) writes to `columnSizing` continuously. v9 supports `columnResizeMode:
-'onChange' | 'onEnd'` — the default is `'onChange'` (commit per-frame). For very heavy tables,
-either:
-
-1. Set `columnResizeMode: 'onEnd'` so the commit only happens at pointerup.
-2. Or, keep `'onChange'` for the visual handle but throttle the side effects you fire off it.
-
-Throttle a side effect:
-
-```ts
-import { createThrottler } from '@tanstack/svelte-pacer/throttler'
-
-const throttledSaveSizing = createThrottler(
-  (sizing: ColumnSizingState) => persistColumnSizingToStorage(sizing),
-  { wait: 100 },
-)
-
-$effect(() => {
-  const sizing = table.atoms.columnSizing.get()
-  throttledSaveSizing.maybeExecute(sizing)
-})
-```
-
-## Patterns to avoid
-
-### Don't debounce inside a `$effect`
-
-```ts
-// WRONG — new debouncer instance every effect re-run
-$effect(() => {
-  const d = createDebouncer((v) => column.setFilterValue(v), { wait: 200 })
-  d.maybeExecute(value)
-})
-```
-
-Pacer instances must be stable. Declare them once at component init scope.
-
-### Don't debounce things that should be immediate
-
-Selection toggles, page changes, sort clicks — these are user-driven discrete events. Don't
-debounce them. The user expects instant feedback.
-
-### Don't double-commit
-
-```ts
-// WRONG — local state syncs immediately AND the debounced commit fires
-oninput={(e) => {
-  column.setFilterValue(e.currentTarget.value)
-  debouncedSetFilter.maybeExecute(e.currentTarget.value)
-}}
-```
-
-Pick one. If you want a snappy input, store the input value in local `$state` and only call
-the debounced commit.
-
-## Coordinating with TanStack Query
-
-If your filter triggers a server query, debouncing the filter handler is necessary but not
-sufficient — `placeholderData: keepPreviousData` is what keeps the UI from flashing. See the
-`compose-with-tanstack-query` skill.
-
-## Common failure modes
-
-- **Recreating pacer instances inside `$effect` / `$derived`.** Each re-run produces a fresh
-  debouncer; nothing is ever delayed.
-- **Hand-rolled `setTimeout` debounce.** Loses leading-edge / trailing-edge guarantees; harder
-  to cancel on unmount. Use pacer.
-- **Debouncing a value that drives layout.** Causes user-visible lag where there shouldn't
-  be. Keep the input controlled by local state and only debounce the table-write call.
-- **Forgetting to call `.maybeExecute`.** Constructing a debouncer doesn't enqueue anything;
-  you have to call `.maybeExecute(value)` per event.
-- **Reimplementing pacer with `$effect` timers.** Don't.
-
-## Related skills
-
-- `tanstack-table/core/filtering` — column / global filter mechanics.
-- `tanstack-table/core/column-layout` — column resizing modes (`onChange` vs `onEnd`).
-- `tanstack-table/svelte/compose-with-tanstack-query` — pairing pacer with server queries.
-- `tanstack-table/svelte/production-readiness` — where pacer fits in the perf checklist.