flushSync was called on the server. This is likely caused by a function being called during render or in module scope that was intended to be called from an effect or event handler.
React detected flushSync running during server render or module evaluation, even though synchronous DOM flushing is intended for client-side event or effect timing.
flushSync was called on the server. This is likely caused by a function being called during render or in module scope that was intended to be called from an effect or event handler.
Why it happens
flushSync is invoked during server rendering.
A shared helper calls flushSync in module scope or render code.
Client-only imperative update logic leaked into a server execution path.
How to fix it
Keep flushSync out of server-rendered code paths.
Move the call into a client-only event handler or effect when necessary.
Audit shared utilities and module-scope code for unintended flushSync usage.
