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

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?