Skip to content

release v9 #6512

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
KevinVandy merged 3 commits into from
Aug 4, 2026
+346 −477
Merged

release v9 #6512

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3a06303
release v9
KevinVandy Aug 4, 2026
2f7044a
update docs for v9 stable
KevinVandy Aug 4, 2026
a50ba30
ci: apply automated fixes
autofix-ci[bot] Aug 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions .changeset/v9-stable-release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
---
'@tanstack/table-core': major
'@tanstack/table-devtools': major
'@tanstack/alpine-table': major
'@tanstack/angular-table': major
'@tanstack/angular-table-devtools': major
'@tanstack/ember-table': major
'@tanstack/lit-table': major
'@tanstack/octane-table': major
'@tanstack/preact-table': major
'@tanstack/preact-table-devtools': major
'@tanstack/react-table': major
'@tanstack/react-table-devtools': major
'@tanstack/solid-table': major
'@tanstack/solid-table-devtools': major
'@tanstack/svelte-table': major
'@tanstack/vue-table': major
'@tanstack/vue-table-devtools': major
'@tanstack/match-sorter-utils': major
Comment on lines +2 to +19

@coderabbitai coderabbitai Bot Aug 4, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

python - <<'PY'
from pathlib import Path
import re

text = Path(".changeset/v9-stable-release.md").read_text()
packages = re.findall(r"^'(`@tanstack/`[^']+)': major$", text, re.MULTILINE)

print(f"declared packages: {len(packages)}")
print("\n".join(packages))

if len(packages) != 19:
    raise SystemExit("Expected 19 package entries")
PY

Repository: TanStack/table

Length of output: 655

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== changeset =="
cat -n .changeset/v9-stable-release.md

echo
echo "== workspace package.json packages =="
fd 'package\.json$' . | sed 's#^\./##' | rg '(^|/)package\.json$' | while F read -r f; do
  echo "--- $f"
  python3 - <<PY
import json
from pathlib import Path
p=Path("$f")
try:
    data=json.loads(p.read_text()).get("package", {})
    if data:
        name=data.get("name")
        if name:
            print(name, data.get("version"))
except Exception as e:
    print("ERROR:", e)
PY
done | rg '`@tanstack`'

echo
echo "== count packages named `@tanstack` =="
python3 - <<'PY'
import json
from pathlib import Path
from pathlib import Path
import re

names = set()
for p in sorted(Path('.').rglob('package.json')):
    if 'node_modules' in p.parts:
        continue
    try:
        data=json.loads(p.read_text())
    except Exception as e:
        continue
    name=data.get('package', {}).get('name')
    if name and name.startswith('`@tanstack/`'):
        names.add(name)

print(f"tracked `@tanstack` package names: {sorted(names)}")
print(f"count: {len(names)}")
PY

Repository: TanStack/table

Length of output: 1218

🌐 Web query:

TanStack table v9 stable release packages @TanStack 19 packages changeset

💡 Result:

As of August 4, 2026, TanStack Table v9 has not reached a stable release [1][2]. It is currently in an active beta phase, with version v9.0.0-beta.80 having been released on this date [2]. The v9 release is a major update focused on architectural improvements, including enhanced state management, improved tree-shakability, and better extensibility [3]. Because the project is in beta, developers are advised to use the beta tag when installing the packages via npm [4]. Regarding the "19 packages" and "changeset" queries: - TanStack Table v9 utilizes a modular, multi-package structure common to the TanStack ecosystem [5]. While the specific count of published packages can fluctuate during development, the repository maintains core and framework-specific adapter packages [5]. - Changesets are used by the TanStack project to manage versioning and changelogs across its monorepo structure. You can track the progress of these changes and the accumulation of features by reviewing the pull requests and release notes in the official GitHub repository [1][5]. For the most accurate list of packages currently being published under the @tanstack scope for v9, you should check the contents of the repository's packages directory or the official documentation as they evolve during the beta process [4][5]. Documentation for v9 is currently being rewritten and is available alongside the beta releases [3][4]. For production environments, the official recommendation remains to use the latest stable version, which is v8 [4].

Citations:

Add the missing package to the major release changeset.

This changeset declares 18 packages, but the release scope targets 19. Changesets releases only the named packages, so add the missing package before merging this release.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.changeset/v9-stable-release.md around lines 2 - 19, Add the omitted
nineteenth package to the major-release package list in v9-stable-release.md,
preserving the existing major bump declarations for all listed packages.

Source: MCP tools

🗄️ Data Integrity & Integration | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🏁 Script executed:

pnpm changeset status

Repository: TanStack/table

Length of output: 3250

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== files =="
git ls-files | rg '(^|/)(package\.json|pnpm-workspace\.yaml|\.changesetsrc|\.changeset/v9-stable-release\.md)$|(^|/)changesets-config|\.changesetsrc$' || true

echo "== package files with table-core listed around beta versions =="
for f in $(git ls-files | rg '(^|/)package\.json$|(^|/)pnpm-workspace\.yaml$|\.changesetsrc$'); do
  if rg -n '"`@tanstack/`.*(table|sorter)?:\s*9\.0\.0-beta\.80|`@tanstack/`(table-core|match-sorter-utils)|"version"\s*:\s*"9\.0\.0-beta\.80"' "$f" >/dev/null 2>&1; then
    echo "--- $f ---"
    sed -n '1,220p' "$f"
  fi
done

echo "== changeset config =="
for f in $(git ls-files '.changesetsrc' '.changesets/config.json' 'package.json'); do
  if [ "$f" = "package.json" ]; then
    sed -n '1,180p' "$f"
  else
    sed -n '1,180p' "$f"
  fi
done

Repository: TanStack/table

Length of output: 50371

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== root package =="
sed -n '1,220p' package.json

echo "== pnpm workspace =="
sed -n '1,220p' pnpm-workspace.yaml

echo "== candidate package manifests =="
for f in package.json pnpm-workspace.yaml .changeset/v9-stable-release.md .changesetsrc .changesets/config.json; do
  if [ -f "$f" ]; then
    echo "--- $f ---"
    sed -n '1,220p' "$f"
  fi
done

echo "== listed package top-level versions =="
python3 - <<'PY'
import json
from pathlib import Path
packages = [
  "packages/table-core/package.json",
  "packages/table-devtools/package.json",
  "packages/alpine-table/package.json",
  "packages/angular-table/package.json",
  "packages/angular-table-devtools/package.json",
  "packages/ember-table/package.json",
  "packages/lit-table/package.json",
  "packages/octane-table/package.json",
  "packages/preact-table/package.json",
  "packages/preact-table-devtools/package.json",
  "packages/react-table/package.json",
  "packages/react-table-devtools/package.json",
  "packages/solid-table/package.json",
  "packages/solid-table-devtools/package.json",
  "packages/svelte-table/package.json",
  "packages/vue-table/package.json",
  "packages/vue-table-devtools/package.json",
  "packages/match-sorter-utils/package.json",
]
for p in packages:
    data = json.loads(Path(p).read_text())
    print(f"{data['name']}: {data['version']}")
PY

echo "== lock/package.json TanStack entries for listed packages =="
for pkg in $(sed -n '2,20p' .changeset/v9-stable-release.md | tr -d "'"): do
  echo "--- $pkg ---"
  rg -n "\"$pkg\"|\"`@tanstack/`$pkg\"" package.json pnpm-workspace.yaml packages/*/package.json examples/*/ | head -80 || true
done

Repository: TanStack/table

Length of output: 16822

🌐 Web query:

Changesets prereleas

💡 Result:

Changesets provides a prerelease mode designed for releasing versions before a stable release (e.g., 1.0.0-beta.0) [1][2][3]. Because this feature is complex and reduces standard safety rails, it is strongly recommended that you fully understand npm publish workflows and the associated risks before use [1][4][5]. Core Concepts and Workflow 1. Entering Prerelease Mode: Use the command changeset pre enter to initiate this mode [1][6]. This creates a pre.json file in your.changeset directory, which tracks the current prerelease state [1][3]. The you provide (e.g., beta or next) is used both for the version suffix (e.g., 1.0.0-beta.0) and the npm dist-tag [1][2][6]. 2. Versioning and Publishing: While in prerelease mode, run changeset version as you normally would [1][6]. Changesets will append the prerelease tag to your versions [1][3]. Note that this process will bump dependent packages even if they would not typically be bumped in a standard release, as most semver ranges do not satisfy prerelease versions [1][2]. Afterward, run changeset publish to push the packages to npm using the specified dist-tag [1][6]. 3. Exiting Prerelease Mode: When you are ready for a stable release, use changeset pre exit [1][6]. This command sets an intent to exit prerelease mode in the pre.json file without performing actual versioning [1][2]. Following this, running changeset version will produce the next stable version (e.g., 1.0.0) [6]. Important Recommendations - Branching Strategy: It is highly recommended to perform prereleases from a branch other than your main or default branch [1][3]. Running prereleases on the main branch without a dedicated stable-release branch can block other changes until the prerelease mode is exited [1][2]. - Alternatives: If you require a simpler mechanism, consider using snapshot releases, which are less involved than the full prerelease workflow [4][5]. For more details on the state management, you can refer to the PreState type definition in the @changesets/types package [1][2].

Citations:

Run the prerelease-exit flow for this stable release.

The packages list uses major on 9.0.0-beta.80, and these workspaces publish with workspace:*, so this can resolve released dependency packages and advance TanStack Table to 10.x instead of stable 9.0.0. Use changeset pre exit or otherwise ensure the stable release plan targets 9.0.0 for all listed packages before publishing.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.changeset/v9-stable-release.md around lines 2 - 19, Update the release plan
for the listed TanStack Table packages by running the changeset prerelease-exit
flow before publishing, or otherwise pinning the stable release versions to
9.0.0 instead of applying major increments from 9.0.0-beta.80. Ensure all
packages in the changeset resolve to the intended 9.0.0 release.

Source: MCP tools

---

TanStack Table v9 stable release. See the "Migrating to V9" guide for your framework (e.g. [React](https://tanstack.com/table/latest/docs/framework/react/guide/migrating)) for upgrade instructions.

@coderabbitai coderabbitai Bot Aug 4, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== target changeset =="
cat -n .changeset/v9-stable-release.md 2>/dev/null || true

echo
echo "== all migration links in repository =="
rg -n 'tanstack\.com/table/.*/guide/migrating|/docs/framework/.*/guide/migrating' .changeset README.md 2>/dev/null || true

echo
echo "== package/version references =="
rg -n '"`@tanstack/table-core`"|"`@tanstack/react-table`"|version|latest|beta' package.json pnpm-lock.yaml package-lock.json yarn.lock 2>/dev/null | head -120 || true

Repository: TanStack/table

Length of output: 10134

🌐 Web query:

TanStack Table V9 migrate guide tanstack.com/table beta docs framework react guide migrating

💡 Result:

As of August 4, 2026, TanStack Table V9 is in active beta development (current version v9.0.0-beta.80) [1]. Because it is a major architectural release, the official migration documentation is hosted under the beta section of the TanStack website [2]. The official migration guide for React users can be found at: https://tanstack.com/table/beta/docs/framework/react/guide/migrating [2] Key changes and migration steps for V9 include: Core Architectural Changes 1. Feature Declaration: V9 introduces a required features table option. Unlike previous versions where all features were bundled, you must now explicitly declare the features your table requires [2][3]. 2. Tree-Shaking and Row Models: Row models (filtering, sorting, pagination, etc.) are now configured via tableFeatures rather than individual get*RowModel options. This change enables better tree-shaking by allowing you to register only the specific functions you use [2][4]. 3. Quick Legacy Migration: For those needing an incremental transition, a deprecated useLegacyTable (or equivalent) hook is available to support V8-style APIs while running on V9 [2][5]. This is intended only as a temporary aid and carries a larger bundle size [5][3]. Common Migration Checklist - Replace older hook imports (e.g., useReactTable) with V9-compatible versions. - Move feature and row-model configurations into the new features table option [2][4]. - Update row model function registration (e.g., filterFns, sortFns) to use the new tableFeatures slots [6][4]. - If you were using aggregation features, note that aggregation has been split out of columnGroupingFeature into a new rowAggregationFeature [6][4]. - Update any column pinning logic from physical (left/right) to logical (start/end) terminology for improved layout support [6]. Because V9 is still in beta, expect documentation and APIs to evolve based on community feedback [7]. Always consult the official beta documentation for the most recent updates relevant to your framework [2][6][4].

Citations:

Pin the V9 migration link to a stable documentation version.

The /latest/ path can later route to the V8 migration guide. Use a version-pinned V9 URL, such as the current beta migration guide, after the V9 documentation deployment is final.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.changeset/v9-stable-release.md at line 22, Update the “Migrating to V9”
link in the stable release changelog to use a version-pinned V9 documentation
URL instead of the /latest/ path, preserving the framework-specific migration
guide link structure.

Source: MCP tools

2 changes: 1 addition & 1 deletion .github/workflows/zizmor.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ name: GitHub Actions Security Analysis

on:
push:
branches: [alpha]
branches: [main]
pull_request:
branches: ['**']

Expand Down
20 changes: 10 additions & 10 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,16 +47,16 @@
> [!NOTE]
> You may know TanStack Table by the adapter names:
>
> - [Angular Table](https://tanstack.com/table/alpha/docs/framework/angular/angular-table)
> - [Lit Table](https://tanstack.com/table/alpha/docs/framework/lit/lit-table)
> - [Octane Table](https://tanstack.com/table/beta/docs/framework/octane/quick-start)
> - [Preact Table](https://tanstack.com/table/beta/docs/framework/preact/quick-start)
> - [React Table](https://tanstack.com/table/alpha/docs/framework/react/react-table)
> - [Solid Table](https://tanstack.com/table/alpha/docs/framework/solid/solid-table)
> - [Svelte Table](https://tanstack.com/table/alpha/docs/framework/svelte/svelte-table)
> - [Vue Table](https://tanstack.com/table/alpha/docs/framework/vue/vue-table)
> - [Alpine Table](https://tanstack.com/table/alpha/docs/framework/alpine/alpine-table)
> - [Ember Table](https://tanstack.com/table/alpha/docs/framework/ember/ember-table)
> - [Angular Table](https://tanstack.com/table/latest/docs/framework/angular/angular-table)
> - [Lit Table](https://tanstack.com/table/latest/docs/framework/lit/lit-table)
> - [Octane Table](https://tanstack.com/table/latest/docs/framework/octane/quick-start)
> - [Preact Table](https://tanstack.com/table/latest/docs/framework/preact/quick-start)
> - [React Table](https://tanstack.com/table/latest/docs/framework/react/react-table)
> - [Solid Table](https://tanstack.com/table/latest/docs/framework/solid/solid-table)
> - [Svelte Table](https://tanstack.com/table/latest/docs/framework/svelte/svelte-table)
> - [Vue Table](https://tanstack.com/table/latest/docs/framework/vue/vue-table)
> - [Alpine Table](https://tanstack.com/table/latest/docs/framework/alpine/alpine-table)
> - [Ember Table](https://tanstack.com/table/latest/docs/framework/ember/ember-table)

A headless table library for building powerful datagrids with full control over markup, styles, and behavior.

Expand Down
13 changes: 5 additions & 8 deletions docs/devtools.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,21 +14,18 @@ The table devtools let you inspect registered table instances, switch between mu

Install the TanStack Devtools host package and the Table adapter for your framework.

> [!IMPORTANT]
> While TanStack Table v9 is in beta, the table devtools adapters must be installed with the `@beta` tag. Installing without the tag resolves to the old v8 devtools, which have a completely different API.

<!-- ::start:framework -->

# React

```sh
npm install @tanstack/react-devtools @tanstack/react-table-devtools@beta
npm install @tanstack/react-devtools @tanstack/react-table-devtools
```

# Preact

```sh
npm install @tanstack/preact-devtools @tanstack/preact-table-devtools@beta
npm install @tanstack/preact-devtools @tanstack/preact-table-devtools
```

# Octane
Expand All @@ -38,19 +35,19 @@ There is not currently a dedicated Octane Table Devtools adapter.
# Vue

```sh
npm install @tanstack/vue-devtools @tanstack/vue-table-devtools@beta
npm install @tanstack/vue-devtools @tanstack/vue-table-devtools
```

# Solid

```sh
npm install @tanstack/solid-devtools @tanstack/solid-table-devtools@beta
npm install @tanstack/solid-devtools @tanstack/solid-table-devtools
```

# Angular

```sh
npm install @tanstack/angular-devtools @tanstack/angular-table-devtools@beta
npm install @tanstack/angular-devtools @tanstack/angular-table-devtools
```

<!-- ::end:framework -->
Expand Down
14 changes: 7 additions & 7 deletions docs/framework/alpine/guide/custom-features.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,19 +120,19 @@ This might be a bit confusing, so let's break down what each of these methods do

#### getDefaultTableOptions

The `getDefaultTableOptions` method in a table feature is responsible for setting the default table options for that feature. For example, in the [Column Resizing](https://github.com/TanStack/table/blob/beta/packages/table-core/src/features/column-resizing/columnResizingFeature.ts) feature, the `getDefaultTableOptions` method sets the default `columnResizeMode` option with a default value of `"onEnd"`.
The `getDefaultTableOptions` method in a table feature is responsible for setting the default table options for that feature. For example, in the [Column Resizing](https://github.com/TanStack/table/blob/main/packages/table-core/src/features/column-resizing/columnResizingFeature.ts) feature, the `getDefaultTableOptions` method sets the default `columnResizeMode` option with a default value of `"onEnd"`.

<br />

#### getDefaultColumnDef

The `getDefaultColumnDef` method in a table feature is responsible for setting the default column options for that feature. For example, in the [Sorting](https://github.com/TanStack/table/blob/beta/packages/table-core/src/features/row-sorting/rowSortingFeature.ts) feature, the `getDefaultColumnDef` method sets the default `sortUndefined` column option with a default value of `1`.
The `getDefaultColumnDef` method in a table feature is responsible for setting the default column options for that feature. For example, in the [Sorting](https://github.com/TanStack/table/blob/main/packages/table-core/src/features/row-sorting/rowSortingFeature.ts) feature, the `getDefaultColumnDef` method sets the default `sortUndefined` column option with a default value of `1`.

<br />

#### getInitialState

The `getInitialState` method in a table feature is responsible for setting the default state for that feature. For example, in the [Pagination](https://github.com/TanStack/table/blob/beta/packages/table-core/src/features/row-pagination/rowPaginationFeature.ts) feature, the `getInitialState` method sets the default `pageSize` state with a value of `10` and the default `pageIndex` state with a value of `0`.
The `getInitialState` method in a table feature is responsible for setting the default state for that feature. For example, in the [Pagination](https://github.com/TanStack/table/blob/main/packages/table-core/src/features/row-pagination/rowPaginationFeature.ts) feature, the `getInitialState` method sets the default `pageSize` state with a value of `10` and the default `pageIndex` state with a value of `0`.

### API Creators

Expand All @@ -150,13 +150,13 @@ Keep API assignment in `constructTableAPIs`; initialization and reset hooks are

#### constructTableAPIs

The `constructTableAPIs` method in a table feature is exclusively responsible for adding methods to the `table` instance. It runs after all feature-owned table instance data has been initialized. For example, in the [Row Selection](https://github.com/TanStack/table/blob/beta/packages/table-core/src/features/row-selection/rowSelectionFeature.ts) feature, the `constructTableAPIs` method adds many table instance API methods such as `toggleAllRowsSelected`, `getIsAllRowsSelected`, `getIsSomeRowsSelected`, etc. So then, when you call `table.toggleAllRowsSelected()`, you are calling a method that was added to the table instance by the `rowSelectionFeature` feature.
The `constructTableAPIs` method in a table feature is exclusively responsible for adding methods to the `table` instance. It runs after all feature-owned table instance data has been initialized. For example, in the [Row Selection](https://github.com/TanStack/table/blob/main/packages/table-core/src/features/row-selection/rowSelectionFeature.ts) feature, the `constructTableAPIs` method adds many table instance API methods such as `toggleAllRowsSelected`, `getIsAllRowsSelected`, `getIsSomeRowsSelected`, etc. So then, when you call `table.toggleAllRowsSelected()`, you are calling a method that was added to the table instance by the `rowSelectionFeature` feature.

<br />

#### assignHeaderPrototype and initHeaderInstanceData

The `assignHeaderPrototype` method in a table feature is responsible for adding methods to the shared `header` prototype. For example, the [Column Sizing](https://github.com/TanStack/table/blob/beta/packages/table-core/src/features/column-sizing/columnSizingFeature.ts) feature adds header instance API methods such as `getStart`. So then, when you call `header.getStart()`, you are calling a method that was added by the column sizing feature. The `initHeaderInstanceData` method is available for per-header instance data or caches that cannot live on the shared prototype. It runs during header construction, before sub-headers are populated and before the header is linked to its header group. Headers are reconstructed whenever header groups recompute, so it reruns on every rebuild.
The `assignHeaderPrototype` method in a table feature is responsible for adding methods to the shared `header` prototype. For example, the [Column Sizing](https://github.com/TanStack/table/blob/main/packages/table-core/src/features/column-sizing/columnSizingFeature.ts) feature adds header instance API methods such as `getStart`. So then, when you call `header.getStart()`, you are calling a method that was added by the column sizing feature. The `initHeaderInstanceData` method is available for per-header instance data or caches that cannot live on the shared prototype. It runs during header construction, before sub-headers are populated and before the header is linked to its header group. Headers are reconstructed whenever header groups recompute, so it reruns on every rebuild.

<br />

Expand All @@ -168,13 +168,13 @@ The `initHeaderGroupInstanceData` method is available for per-header-group insta

#### assignColumnPrototype and initColumnInstanceData

The `assignColumnPrototype` method in a table feature is responsible for adding methods to the shared `column` prototype. For example, the [Sorting](https://github.com/TanStack/table/blob/beta/packages/table-core/src/features/row-sorting/rowSortingFeature.ts) feature adds column instance API methods such as `getNextSortingOrder`, `toggleSorting`, etc. So then, when you call `column.toggleSorting()`, you are calling a method that was added by the row sorting feature. The `initColumnInstanceData` method is available for per-column instance data or caches that cannot live on the shared prototype. For example, the [Aggregation](https://github.com/TanStack/table/blob/beta/packages/table-core/src/features/row-aggregation/rowAggregationFeature.ts) feature uses it to set up a per-column aggregation cache.
The `assignColumnPrototype` method in a table feature is responsible for adding methods to the shared `column` prototype. For example, the [Sorting](https://github.com/TanStack/table/blob/main/packages/table-core/src/features/row-sorting/rowSortingFeature.ts) feature adds column instance API methods such as `getNextSortingOrder`, `toggleSorting`, etc. So then, when you call `column.toggleSorting()`, you are calling a method that was added by the row sorting feature. The `initColumnInstanceData` method is available for per-column instance data or caches that cannot live on the shared prototype. For example, the [Aggregation](https://github.com/TanStack/table/blob/main/packages/table-core/src/features/row-aggregation/rowAggregationFeature.ts) feature uses it to set up a per-column aggregation cache.

<br />

#### assignRowPrototype and initRowInstanceData

The `assignRowPrototype` method in a table feature is responsible for adding methods to the shared `row` prototype. The `initRowInstanceData` method is available for per-row instance data or caches that cannot live on the shared prototype. For example, the [Row Selection](https://github.com/TanStack/table/blob/beta/packages/table-core/src/features/row-selection/rowSelectionFeature.ts) feature adds row instance API methods such as `toggleSelected` and `getIsSelected`.
The `assignRowPrototype` method in a table feature is responsible for adding methods to the shared `row` prototype. The `initRowInstanceData` method is available for per-row instance data or caches that cannot live on the shared prototype. For example, the [Row Selection](https://github.com/TanStack/table/blob/main/packages/table-core/src/features/row-selection/rowSelectionFeature.ts) feature adds row instance API methods such as `toggleSelected` and `getIsSelected`.

<br />

Expand Down
4 changes: 1 addition & 3 deletions docs/framework/alpine/quick-start.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,8 @@ TanStack Table is a headless table library. It manages your table's state and lo

## Installation

TanStack Table v9 is currently published under the `beta` tag:

```bash
npm install @tanstack/alpine-table@beta alpinejs
npm install @tanstack/alpine-table alpinejs
```

The `@tanstack/alpine-table` package works with Alpine 3.
Expand Down
Loading
Loading