Which edge‑case values survive Waku's React Server Components payload when sent from server to client components?

Question

Determine which edge‑case values survive Waku's RSC payload
Goal: Identify whether non‑JSON‑serializable values such as Date objects, Map/Set instances, or custom class instances are transmitted intact from a server component to a client component in Waku.
Constraints/uncertainty: Waku relies on React Server Components serialization; the framework is pre‑1.0 and its payload handling may differ from Next.js App Router. It is unclear whether these values are preserved, converted to a placeholder, or cause a runtime error.

Which of the following values—Date objects, Map instances, Set instances, or custom class instances—are preserved when passed from a server component to a client component?
Does Waku throw an error, silently drop the value, or serialize it as a placeholder when an unsupported type is encountered?
Are there any Waku‑specific configuration options or wrapper utilities that can control this serialization behavior?

Tasadduq Burney · Answer

Which edge‑case values survive Waku's RSC payload?
Goal: Identify whether non‑JSON‑serializable values such as Date objects, Map/Set instances, or custom class instances are transmitted intact from a server component to a client component in Waku.
Likely serialization outcomes

Date objects are typically serialized as ISO‑8601 string representations.
Map and Set instances are often converted to plain objects or omitted if the runtime lacks explicit support.
Custom class instances are dropped or cause serialization errors unless an explicit toJSON method or framework wrapper is provided.

Version‑dependent nuances
Waku's runtime version heavily influences outcomes. Pre‑1.0 RSC runtimes may silently placeholder non‑JSON‑serializable values, while post‑1.0 versions often emit console warnings or throw during hydration.
(Note: This assumption reflects typical RSC serialization patterns; actual behavior may vary with your specific Waku version and configuration.)
Practical verification steps

Add a server component that passes a Date, Map, Set, or custom class instance as a prop to a client component.
Render the page in a browser and open React Devtools → Components tab.
Inspect the propagated prop types in the RSC payload panel.
Open the console for warnings about hydration mismatches, unsupported types, or silent placeholders.

Record which types are preserved, converted, or cause errors under your current setup.
Missing diagnostic detail: Which Waku runtime version are you using, and does your project include a custom serializer or wrapper for RSC props? This information determines whether the observed behavior aligns with the pre‑1.0 placeholder pattern or a post‑1.0 warning/throw pattern, and whether a refined recommendation is possible.

Which edge‑case values survive Waku's React Server Components payload when sent from server to client components?

Determine which edge‑case values survive Waku's RSC payload

1 answer

Which edge‑case values survive Waku's RSC payload?

Likely serialization outcomes

Version‑dependent nuances

Practical verification steps

Your perspective belongs here.

0 question comments