Skip to content

docs(deps): name the real linking mechanism in the worklets override comment - #122

Merged
toruiwasa merged 1 commit into
mainfrom
fix/worklets-override-comment-accuracy
Sep 4, 2026
Merged

docs(deps): name the real linking mechanism in the worklets override comment#122
toruiwasa merged 1 commit into
mainfrom
fix/worklets-override-comment-accuracy

Conversation

@toruiwasa

Copy link
Copy Markdown
Owner

Closes #121

Follow-up to #119, found while reviewing it. Comment-only — the pin is correct and unchanged.

What was wrong

#119's overrides comment justified the workspace-wide pin like this:

because expo-modules-autolinking resolves native modules out of the store and other consumers (@expo/ui, expo-router) still bound the 0.12.x copy

Checked against the installed tree:

  • Neither react-native-worklets nor react-native-reanimated ships an expo-module.config.json, so neither is an Expo module. expo-modules-autolinking search -p ios returns expo-modules-core and not these two — they are linked by React Native's own community autolinking.
  • What actually decides the build is one layer down: which react-native-worklets copy expo-modules-core is peer-resolved against. That is the copy whose headers ExpoWorkletsBridgeProvider.mm compiles against, and the @expo/ui / expo-router graph bound it to 0.12.x.

The conclusion #119 reached — declare in apps/mobile and override workspace-wide — is right, and the reason for it survives the correction: a dependency entry in apps/mobile does not change what expo-modules-core is peer-resolved against, so only the override removes the 0.12.x copy from the graph.

Why a comment is worth a PR

This is the only durable record of why the override exists, and CLAUDE.md requires a rejected alternative to be recorded with its reason. A wrong reason is a defect in the record, not a cosmetic issue: the concrete failure mode is a future reader testing whether Expo autolinking picks up the package, concluding from a null result that the override is unnecessary, and reintroducing #117.

Verification

  • pnpm install --frozen-lockfileAlready up to date; git status shows pnpm-workspace.yaml as the only modified file
  • pnpm why react-native-workletsreact-native-worklets@0.10.1, single version
  • pnpm build 6/6, pnpm test 6/6

overrides values, apps/mobile/package.json and pnpm-lock.yaml are untouched.

🤖 Generated with Claude Code

…comment

The comment justifying the workspace-wide `overrides` block attributed the
pin to expo-modules-autolinking binding a 0.12.x copy of the package.
Verified against the installed tree: neither react-native-worklets nor
react-native-reanimated ships an expo-module.config.json, so neither is an
Expo module — `expo-modules-autolinking search -p ios` returns
expo-modules-core and not these two. They are linked by React Native's own
autolinking.

The binding constraint is one layer down: which react-native-worklets copy
expo-modules-core is peer-resolved against. The @expo/ui / expo-router graph
bound it to 0.12.x, which is why declaring the versions in apps/mobile does
not help and a workspace-wide override does.

The pin itself is correct and unchanged — only its stated reason was wrong,
and this comment is the sole durable record of why the override exists.

Comment-only: `overrides` values, apps/mobile/package.json and pnpm-lock.yaml
are untouched; `pnpm install --frozen-lockfile` reports already up to date.

Closes #121

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Sep 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
pulseticker Ready Ready Preview Sep 4, 2026 1:18am UTC

@toruiwasa
toruiwasa merged commit 17cb2aa into main Sep 4, 2026
4 checks passed
@toruiwasa
toruiwasa deleted the fix/worklets-override-comment-accuracy branch September 4, 2026 01:21
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.

pnpm-workspace.yaml override comment names the wrong linking mechanism

1 participant