useEffect runs twice with same state after migrating to Turborepo (Next.js + React 19)

[asadbekabduvoitov-nordra]

Summary

After migrating our Next.js project at company into a Turborepo workspace, I noticed a change in how useEffect behaves when depending on query state.

I have code like this:

const [message, setMessage] = useQueryState("message", { parse: parseMessageQuery });

useEffect(() => {
  if (message) {
    setMessage(null);
    onSubmit({
      text: message.text,
      body: { ...(message?.body ?? {}) },
    });
  }
}, [message]);

Expected behavior
• The effect should run once per unique message value.
• After setMessage(null), it should not trigger onSubmit again.
• This worked as expected in my previous Next.js setup.

Additional information

- In Turborepo + Next.js (React 18), the effect runs twice with the same non-null message, before setMessage(null) is even applied.
- This breaks my logic (e.g. creating tickets, submitting forms twice).

reactStrictMode is set to false in next.config.ts, but the behavior persists in Turborepo dev.

Example

No response