Skip to content

Table v9 beta and blog post#967

Open
KevinVandy wants to merge 6 commits into
mainfrom
table-v9-beta
Open

Table v9 beta and blog post#967
KevinVandy wants to merge 6 commits into
mainfrom
table-v9-beta

Conversation

@KevinVandy
Copy link
Copy Markdown
Member

@KevinVandy KevinVandy commented Jun 6, 2026

Summary by CodeRabbit

  • Documentation
    • New blog post announcing TanStack Table V9 Beta, covering the new state management approach, finer-grained subscriptions for reduced re-renders, lower memory usage and performance improvements for large virtualized tables, a tree-shakable feature/plugin system, extension/composition primitives, and Devtools integration.
    • Release status updated: TanStack Table V9 marked as Beta (replacing prior Alpha tag).

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 6, 2026

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5f2d2192-abc6-4c7c-ae4b-bb5e50889b9f

📥 Commits

Reviewing files that changed from the base of the PR and between 088313e and 41e6523.

📒 Files selected for processing (1)
  • src/blog/tanstack-table-v9-taking-form.md
✅ Files skipped from review due to trivial changes (1)
  • src/blog/tanstack-table-v9-taking-form.md

📝 Walkthrough

Walkthrough

This PR adds a new blog post announcing TanStack Table V9 Beta (detailed feature overview, migration notes, extension points, and devtools integration) and updates the table library metadata to replace the alpha tag with beta.

Changes

TanStack Table V9 Beta Release Publication

Layer / File(s) Summary
V9 Beta announcement blog post
src/blog/tanstack-table-v9-taking-form.md
New blog post with frontmatter and header image; backstory and V9 development narrative; "What's New" covering TanStack Store-based state (atoms), selector-driven Subscribe subscriptions, virtualized-table memory/performance improvements, tree-shakable tableFeatures (and stockFeatures), custom feature extension points, reusable composition helpers (createTableHook, tableOptions), devtools integration, beta status, and Kitchen Sink example links.
Version metadata update
src/libraries/libraries.ts
table.availableVersions updated from ['v8', 'alpha'] to ['v8', 'beta'].

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

  • schiller-manuel
  • LadyBluenotes

Poem

🐰 A beta blooms in meadowed code,
Atoms hum where state once rode,
Features prune and trees unwind,
Devtools peek and examples bind,
Hop on — V9 leaps forth, bestowed.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Table v9 beta and blog post' directly and concisely summarizes the main changes: adding TanStack Table V9 Beta announcement and updating library metadata.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch table-v9-beta

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with 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.

Inline comments:
In `@src/blog/tanstack-table-v9-taking-form.md`:
- Line 26: Replace the misspelled word "maintanence" with "maintenance" in the
blog post content—locate the sentence starting "Still, maintanence of the
project..." in tanstack-table-v9-taking-form.md and update it to "Still,
maintenance of the project has been a bit lackluster, especially as we have
focussed on this new version for well-over the past year." Ensure only the typo
is fixed and punctuation/spacing remains unchanged.
- Line 390: Replace the non-descriptive markdown link text "[here](/table/beta)"
with a descriptive phrase (e.g., "TanStack Table v9 beta documentation" or
"TanStack Table v9 beta docs") so the sentence becomes something like "You can
find the V9 docs at TanStack Table v9 beta documentation (/table/beta)"; update
the link text in the line containing "V9 docs [here](/table/beta)" in
src/blog/tanstack-table-v9-taking-form.md accordingly.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0f632e29-705f-4f86-b119-825b9744f1e0

📥 Commits

Reviewing files that changed from the base of the PR and between fb19d25 and 8d31d21.

⛔ Files ignored due to path filters (2)
  • public/blog-assets/tanstack-table-v9-taking-form/header.png is excluded by !**/*.png
  • public/blog-assets/tanstack-table-v9-taking-form/screenshot-1.png is excluded by !**/*.png
📒 Files selected for processing (2)
  • src/blog/tanstack-table-v9-taking-form.md
  • src/libraries/libraries.ts

Comment thread src/blog/tanstack-table-v9-taking-form.md Outdated

We think we are mostly done with the foundational changes for V9 in terms of state management, tree-shakability, etc. Now, while we are in beta, we have some good opportunities to make some final needed breaking changes and fixes to the features themselves before we go stable. We hope that this will not be as long of a beta process as some of the other TanStack libraries, but it depends on the feedback we get from the community and how much community help we can get to test and fix the issues that we find.

If you have the stomach for a beta, I would love your help kicking the tires. You can find the V9 docs [here](/table/beta).
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use descriptive link text instead of “here”.

“here” is non-descriptive and hurts scanability/accessibility in markdown link text.

Suggested edit
-If you have the stomach for a beta, I would love your help kicking the tires. You can find the V9 docs [here](/table/beta).
+If you have the stomach for a beta, I would love your help kicking the tires. You can find the [TanStack Table V9 beta docs](/table/beta).
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
If you have the stomach for a beta, I would love your help kicking the tires. You can find the V9 docs [here](/table/beta).
If you have the stomach for a beta, I would love your help kicking the tires. You can find the [TanStack Table V9 beta docs](/table/beta).
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)

[warning] 390-390: Link text should be descriptive

(MD059, descriptive-link-text)

🤖 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 `@src/blog/tanstack-table-v9-taking-form.md` at line 390, Replace the
non-descriptive markdown link text "[here](/table/beta)" with a descriptive
phrase (e.g., "TanStack Table v9 beta documentation" or "TanStack Table v9 beta
docs") so the sentence becomes something like "You can find the V9 docs at
TanStack Table v9 beta documentation (/table/beta)"; update the link text in the
line containing "V9 docs [here](/table/beta)" in
src/blog/tanstack-table-v9-taking-form.md accordingly.

Source: Linters/SAST tools

Comment thread src/blog/tanstack-table-v9-taking-form.md Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants