structuredClone loses specialized Error prototypes

[OskarEichler]

Description

The React Native structuredClone polyfill validates an Error's standard serialized name but always constructs a base Error, then overwrites only .name. A cloned EvalError, for example, reports name === 'EvalError' while failing instanceof EvalError. The same affects RangeError, ReferenceError, SyntaxError, TypeError, and URIError.

Expected behavior

Valid standard Error names should be cloned with their matching built-in constructor/prototype; invalid names should fall back to base Error. Native structuredClone follows this behavior.

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.

[react-native-bot]

This issue is waiting for author's feedback since 24 days. Please provide the requested feedback or this will be closed in 7 days.