singular-particular-space/skills/react-native-skills/rules/monorepo-native-deps-in-app.md at 542213178233261403b587d4177db7e9a50d5ab4

Files

JL Kruger 5422131782 Initial commit — Singular Particular Space v1

Homepage (site/index.html): integration-v14 promoted, Writings section
integrated with 33 pieces clustered by type (stories/essays/miscellany),
Writings welcome lightbox, content frame at 98% opacity.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-03-27 12:09:22 +02:00

1.1 KiB

Raw Blame History

title, impact, impactDescription, tags

title	impact	impactDescription	tags
Install Native Dependencies in App Directory	CRITICAL	required for autolinking to work	monorepo, native, autolinking, installation

Install Native Dependencies in App Directory

In a monorepo, packages with native code must be installed in the native app's directory directly. Autolinking only scans the app's node_modules—it won't find native dependencies installed in other packages.

Incorrect (native dep in shared package only):

packages/
  ui/
    package.json  # has react-native-reanimated
  app/
    package.json  # missing react-native-reanimated

Autolinking fails—native code not linked.

Correct (native dep in app directory):

packages/
  ui/
    package.json  # has react-native-reanimated
  app/
    package.json  # also has react-native-reanimated

// packages/app/package.json
{
  "dependencies": {
    "react-native-reanimated": "3.16.1"
  }
}

Even if the shared package uses the native dependency, the app must also list it for autolinking to detect and link the native code.

1.1 KiB Raw Blame History

Install Native Dependencies in App Directory

1.1 KiB

Raw Blame History