-
-
Notifications
You must be signed in to change notification settings - Fork 661
fix: react 19 strict mode compatibility #1726
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@nperez0111 upon a second look it seems like I suppose the right solution would be to update tiptap and call |
@blocknote/ariakit
@blocknote/code-block
@blocknote/core
@blocknote/mantine
@blocknote/react
@blocknote/server-util
@blocknote/shadcn
@blocknote/xl-ai
@blocknote/xl-docx-exporter
@blocknote/xl-multi-column
@blocknote/xl-odt-exporter
@blocknote/xl-pdf-exporter
commit: |
|
@YousefED in the future, yes. But, that is still on their v3 beta so will be part of the larger upgrade to v3. For now, this is a valid fix |
|
Hey guys I still experience the issue flushSync was called from inside a lifecycle method. React cannot flush when React is already rendering. Consider moving this call to a scheduler task or micro task. This is for ReactNodeViewRenderer(CitationMarkComponent); ... I am using latest version of tiptap/nextjs package.json |
closes #1618
I think this was caused because in React 19, "refs" also quickly remount when in StrictMode.
We didn't correctly cleanup when the editor was unmounted, causing a nested
flushSynchereIdeally we add a test for this, but this might be complicated with our setup (the main repo now uses React 18).