structuredCloneProblem
Ce contenu n’est pas encore disponible dans votre langue.
structuredCloneProblem(
message):string|null
Defined in: src/diagnostics/MessageBoundaryCheck.ts:186
What a worker hop would do to message, or null when it arrives intact.
Two questions, in the order they matter: is anything reachable going to
lose its prototype — found by walking, because structuredClone succeeds
on it and says nothing — and can the value be cloned at all, found by
cloning it. ActorRefs are skipped with their subtrees: every remote
send rewrites them to wire markers before the port sees them, so a
replyTo field is exactly what it should be.
Parameters
Section titled “Parameters”message
Section titled “message”object
Returns
Section titled “Returns”string | null
