-
-
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
Attempted import error: 'findDOMNode' is not exported from 'react-dom' (imported as 'findDOMNode'). #1858
Comments
Two attempted PR fixes in #1855 and #1856 @bvaughn Please let us know if either of the above options is suitable, or if you recommend migrating to |
+1. TanStack Virtual looks like it is going to have to be our alternative to migrate to, although it doesn't have quite as good performance. |
+1 |
+1 (findDOMNode was removed in React 19). |
+1 |
It blows my mind that this package is used by over 93k people and there are 187 contributors and nobody can just merge in the fix that someone else was kind enough to do to fix this thing. I believe using this package also breaks the hot reload feature within Next.js 15 which kills DX. |
+1 |
1 similar comment
+1 |
I published a fork of https://github.com/adubrouski/react-virtualized-compat |
It appears that Virtualized Table is not compatible with React 19. The findDOMNode was deprecated in 19. So any of us that are using Next 15 or regular React 19 are not hit with the following errors:
⚠ ./node_modules/react-virtualized/dist/es/Table/Table.js
Attempted import error: 'findDOMNode' is not exported from 'react-dom' (imported as 'findDOMNode').
To reproduce.
Simply try to use these components in React 19.
The text was updated successfully, but these errors were encountered: