Skip to content

Support react-native-worklets 0.7.x / react-native-reanimated 4.2.x (Expo SDK 55)Β #294

@alex-vance

Description

@alex-vance

Summary

Expo SDK 55 ships with react-native-reanimated ~4.2.1 and react-native-worklets ^0.7.3. The current heroui-native@1.0.0-rc.1 peer dependencies pin older versions that conflict with these requirements:

"react-native-reanimated": "~4.1.1",
"react-native-worklets": "0.5.1"

This results in invalid peer dependency warnings and potential runtime issues when using heroui-native in an Expo SDK 55 project.

Reproduction

npm ls react-native-reanimated react-native-worklets heroui-native

Output:

β”œβ”€β”¬ heroui-native@1.0.0-rc.1
β”‚   β”œβ”€β”€ react-native-reanimated@4.2.1 deduped invalid: "~4.1.1" from heroui-native
β”‚   └── react-native-worklets@0.7.3 deduped invalid: "0.5.1" from heroui-native
β”œβ”€β”€ react-native-reanimated@4.2.1
└── react-native-worklets@0.7.3

Environment

Package Version
heroui-native 1.0.0-rc.1
expo 55.0.0-preview.10
react-native 0.83.1
react-native-reanimated 4.2.1
react-native-worklets 0.7.3

Expected Behavior

heroui-native peer dependencies should accept react-native-reanimated >=4.1.1 and react-native-worklets >=0.5.1 (or the specific ranges required by Expo SDK 55).

Additional Context

  • The worklets jump from 0.5.x to 0.7.x is a significant change (required by reanimated 4.2+)
  • Reanimated 4.2 introduces important performance flags for New Architecture (enableIosSynchronousUpdates, enableCommitHookOnlyForReactCommits) that are only available on 4.2+
  • Projects using Expo SDK 55 cannot downgrade these packages without breaking other Expo dependencies
  • Current workaround is legacy-peer-deps=true in .npmrc, but this masks potential runtime incompatibilities

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions