structuredClone coerces rejected values while creating DataCloneError

[OskarEichler]

Description

The React Native structuredClone polyfill interpolates rejected values into its error message. That invokes user-defined coercion such as Symbol.toPrimitive; a non-cloneable function or WeakMap can therefore replace the required DataCloneError with an arbitrary user-thrown error.

Expected behavior

Rejecting an unsupported value should produce DOMException / DataCloneError without executing user coercion hooks. The non-standard message does not need to include the rejected value.

React Native Version

0.87.1 and current main

Affected Platforms

JavaScript runtime - All

[react-native-bot]

Warning

Missing reproducer: We could not detect a reproducible example in your issue report. Reproducers are mandatory and we can accept only one of those as a valid reproducer:

• For majority of bugs: send us a Pull Request with the RNTesterPlayground.js edited to reproduce your bug.
• If your bug is UI related: a Snack
• If your bug is build/upgrade related: a project using our Reproducer Template

You can read more about about it on our website: How to report a bug.