Skip to content

example: regenerate lockfiles (drop nested react-native 0.86.3) - #96

Merged
tekinalper merged 1 commit into
developfrom
fix/example-lockfile-nested-react-native
Nov 2, 2026
Merged

tekinalper merged 1 commit into
developfrom
fix/example-lockfile-nested-react-native

Conversation

@tekinalper

Copy link
Copy Markdown
Collaborator

What it does

Regenerates example/package-lock.json from scratch and commits the resulting example/ios/Podfile.lock. The previous lockfile nested react-native@0.86.3 under node_modules/react-native (via @react-native/virtualized-lists), so RN 0.79.7's hermes-engine.podspec resolved the wrong React Native version, found no Hermes tarball and tried to build Hermes from source (cmake missing). Now: one react-native 0.79.7, hermes-engine 0.79.7, RefinerSDK 2.0.0 from the public repo.

How to test it

  1. cd example && npm ci && cd ios && pod install completes without building Hermes; Podfile.lock lists RefinerSDK (2.0.0) and hermes-engine (0.79.7).

Acceptance criteria

  • No nested react-native in the example lockfile; pod install succeeds.

Link to ticket

https://trello.com/c/ywKiYIhs

🤖 Generated with Claude Code

The example lockfile carried a nested react-native@0.86.3 under
node_modules/react-native (pulled in via @react-native/virtualized-lists),
which made RN 0.79's hermes-engine podspec resolve the wrong version and try
to build Hermes from source. Regenerated from scratch: single react-native
0.79.7, hermes 0.79.7, RefinerSDK 2.0.0 from the public repo.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@tekinalper
tekinalper merged commit 38e409b into develop Nov 2, 2026
2 checks passed
@tekinalper
tekinalper deleted the fix/example-lockfile-nested-react-native branch November 2, 2026 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant