-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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.
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
Table doesn’t re-render with new React Compiler + React 19 #5567
Comments
This is unsurprising. This library (which I love) has been complicated to optimize since at least v7. They core instance returned from |
I am also having difficulty applying the compiler due to the same issue. I am concerned that other libraries might have similar issues, making the application of the compiler worrisome. |
Same exact issue. |
Yep, use no memo on table components for now. A v9 alpha branch was recently created where we will focus on version bumping the peer dependencies for each framework that needs it. |
Seems like doing the following solves it for me: TanStack/virtual#743 |
I've the same problem with Next.js 15 & React 19 & Tanstack Table 8.20.5
|
Same here. After hours of searching for a solution |
sorry how is use no memo? how can I implement that? |
@victormanuelfrancodev Just add |
I have some issues event with |
TanStack Table version
v8.17.3
Framework/Library version
React 19 + React Compiler
Describe the bug and the steps to reproduce it
In the repo provided, run
bun install
and thenbun dev
.Then, add some text to the input and click add. Observe that the table doesn’t re-render when the data passed in has changed (
table.getRowModel().rows
doesn’t seem to be updated).Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
https://github.com/erikshestopal/react-compiler-bug/blob/a92305ca44ee81b6d7ece76c96aacf163fe83970/src/App.tsx#L38
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
None
Terms & Code of Conduct
The text was updated successfully, but these errors were encountered: