structuredClone accepts boxed Symbols as empty objects

Open Beginner friendly
#58,212 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, react-native
Domain
mobile-dev

Research direction

Start at React Native's structuredClone polyfill and reproduce the issue with Object(Symbol()). Compare its behavior with native structuredClone and the existing primitive-Symbol path. Done means boxed Symbols throw DataCloneError without string-coercing the wrapper, while existing clone behavior remains unchanged.

Written by the indexing model from the issue text.

Description

Needs: Author Feedback Needs: Repro
Description

The React Native structuredClone polyfill correctly rejects primitive Symbols but treats boxed Symbols as arbitrary objects. structuredClone(Object(Symbol())) therefore returns {} instead of throwing, even though boxed Symbols are also not structured-cloneable.

Expected behavior

Boxed Symbols should throw DataCloneError, matching native structuredClone. The error path should not string-coerce the wrapper because Hermes throws a separate TypeError for that coercion.

React Native Version

0.87.1 and current main

Affected Platforms

JavaScript runtime - All

Dominant language
C++
Stars
127k
Forks
25.3k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from react/react-native

All issues in react/react-native

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.