[Compiler Bug]: Unexpected [ Server ] Error: {} causing ErrorBoundary crash in Next.js 15.1.6 with Turbopack

[Emmanuel-Xs]

What kind of issue is this?

• React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
• babel-plugin-react-compiler (build issue installing or using the Babel plugin)
• eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
• react-compiler-healthcheck (build issue installing or using the healthcheck script)

Link to repro

https://github.com/Emmanuel-Xs/devlinks

Repro steps

What is the issue?
I'm encountering a [ Server ] Error: {} that causes a full Error Boundary crash in my app.
This happens unexpectedly during normal navigation and rendering.
The error appears to originate from react-server-dom-turbopack inside next@15.1.6, and seems related to server components.

Error logs:

[ Server ] Error: {}

resolveErrorDev (react-server-dom-turbopack-client.browser.development.js:1061:61)
processFullStringRow (react-server-dom-turbopack-client.browser.development.js:1228:15)
processFullBinaryRow (react-server-dom-turbopack-client.browser.development.js:1216:5)
progress (react-server-dom-turbopack-client.browser.development.js:1334:92)

Also the console shows:

Error occurred in <PreviewLinksButton> component. Handled by <ErrorBoundaryHandler>.

Screenshots:
(Attached below)

How often does this bug happen?

Sometimes

What version of React are you using?

19.0.0

What version of React Compiler are you using?

19.0.0-beta-714736e-20250131

[ObiwanKenobee]

Using React Infinite: Resolving React Server DOM Turbopack Boundary Crash

---

❗️Issue Classification

Issue Type | Is This the Root Cause? -- | -- ✅ React Compiler Core | ✔️ Yes – App crashes due to incorrect or missing server rendering boundaries ❌ babel-plugin-react-compiler | No install/build issue present ❌ eslint-plugin-react-compiler | No linting or formatting issue ❌ react-compiler-healthcheck | No healthcheck misconfiguration indicated

---

🔄 Optional Fallback: Reset Links Stream on Error

tsx
CopyEdit
function fetchLinksAgain() {
  startTransition(() => {
    router.refresh(); // or call the fetch manually
  });
}

---

✅ Final Verdict

React Infinite future-proofs your app against the fragile RSC stream hydration and transforms server boundary logic into predictable, interceptable WASM events.

✅ No silent {} crashes
✅ No crash-to-fatal-boundary behavior
✅ Real-time fallback rendering from broken RSC rows
✅ Predictive retry and developer diagnostics

[josephsavona]

Hmm, nothing here seems specific to React Compiler, this looks like a Next.js issue. I would suggest posting at https://github.com/vercel/next.js/issues for help

[Emmanuel-Xs]

Ok thanks,u will do that soon