Skip to content

structuredClone loses specialized Error prototypes #58214

Closed as not planned

Description

@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

Activity

  1. react-native-bot commented on Aug 30, 2026

    @react-native-bot
    Collaborator

    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:


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

  2. react-native-bot commented on Sep 24, 2026

    @react-native-bot
    Collaborator

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

  3. added
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Sep 24, 2026
  4. react-native-bot commented on Oct 1, 2026

    @react-native-bot
    Collaborator

    This issue was closed because it has been stalled for 7 days with no activity.

  5. react-native-bot commented on Oct 1, 2026

    @react-native-bot
    Collaborator

    This issue was closed because the author hasn't provided the requested feedback after 7 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs: Author FeedbackNeeds: ReproThis issue could be improved with a clear list of steps to reproduce the issue.StaleThere has been a lack of activity on this issue and it may be closed soon.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions